This is an archive of CompuServe forum messages from 1985 to 1995, as saved in transcripts by John Foust.
Search Results (187 messages)
John – Sorry, what I meant was that the Illuminator (and I therefore assumed the Illuminator Pro) is a TARGA Classic clone. I mentioned Targa+ because we support that device, not TARGA Classic. Chuck Walbourn – Vibrant Graphics
Illuminator Pro is not an MGA. The Matrox MGA Pro is based on the MGA-1 chipset, which is supported by the 1.0.3 version of the Vibrant Inline driver. The Illuminator series is a TARGA-clone, which we don't currently support (we do support the Targa+). Chuck Walbourn – Vibrant Graphics
To be honest, I am a little confused by your problem description… Ok. What is the device set for Display, Materials, and Render? If you have cleared RCPADI and RDPADI, and just select VIBRANT, does it work? The Spea HiLite is a TIGA board, correct? If so, you can use…
Scott – We really don't know what is going on. Matrox is sending us some updated code for some new boards soon, which may fix the problem. You might want to try running the setup for a different refresh rate and see if the Inline driver matches the Windows/Matrox 3DS…
By the way… The new 1.0.3 Version of the Vibrant Inline driver supports Targa+…. Check it out. Chuck Walbourn – Vibrant Graphics
Again, no harm done. Our European office got a few calls, so they wanted to know why we hadn't given them the release… Chuck Walbourn – Vibrant Graphics
No problem. This time there were no changes… I'll be sending the production build later today to David Ang @ Autodesk. Chuck Walbourn – Vibrant Graphics
Nik – You guys posted 1.0.3 here??!?!?!? Bad Autodesk… The 1.0.3 I sent to David Ang was a pre-release… not a production build. It should NOT have been posted yet. I was planning on sending the production version today. Can you please make sure that whoever put it up knows…
I assume that you mean the Orchid Kelvin 64? We have been trying to get an Orchid Kelvin in house for some time… We have had several reports of people trying to use the Vibrant driver without success. I'll put in another request for the board. Sorry for the incovience.…
> Yes, Matrox somehow got authorization to post their beta-Vibrant >drivers on their forum. They are a major improvement (for the MGA-II, anyway) >in that the Materials editor can be 24-bit, preview colors are functional, and >it all around looks better. The Version 1.0.2 Beta that Matrox' has on their…
>Jonas, the Vibrant file says leave a message for sysop with problems. I have a >Number Nine GXE PCI board and there are still problems with the Vibrant >drivers. How can I get support for them? I haven't seen new ones uploaded for >some time. The main problem is in…
>You got beta VIBRANT drivers from MATROX? Vibrant announced that the Matrox >MGA will be supported in the future. Since it's beta code you may have to >contact them. Matrox got a Beta because we did not want to make an offical release for them. The Version 1.0.2 contains the…
MGA 2+
Message #105388
Please check that MGA is set to to the drive and path where your MGA.MON file is set. Chuck Walbourn – Vibrant Graphics
I am not clear what you mean by 'distorted'? I assume that you are using a 256 color device for all devices… You should use a 256 color for main, but a hi/true-color for materials and rendering is best… The P9000 does support 24-bit color. There is no difference in…
>I second a request for a Kelvin Driver.. Please e-mail me when you know >whether or not you will have a supporting driver for the Kelvin 2MB PCI. It >included in a system I'm looking at. thanks. We defintely plan to support it. We have had MANY requests for this…
Just as a note, the Mach64 BIOS takes 4-8 seconds to return the memory size of the chip so initializing is quite a bit slower than normal. 20secs does sound a bit outrageous however… Chuck Walbourn – Vibrant Graphics
There are some problems with the 1.0.2 version of the Mach64 support. Some of the Mach64 DACs don't respond correctly to the command to set them to 8-bit color depth, and many of the modes appear dim or incorrectly colored. 1.0.3 should be out soon, try it out with this…
The Impression 1024 is an S3 911/924 card. We support it in 16/256 colors, but not the true-color modes. Matrox developed this weird propritary system for true-color on the S3 911/924 card, which we don't have any current plans to deal with… Sorry. Chuck Walbourn – Vibrant Graphics
Version 1.0.2 has partial support. There were some problems with the earlier rev's of the board. Version 1.0.3 (out soon) fixes all of the rest of the problems with the 864/964 cards we are aware of.
#104397-
driver for Orchid Kelvin
Message #104922
>Sorry, none of the Cirrus Logic configurations worked. But let me know if >there ever is a driver that I can use. Thanks. -Gregory Hmmm.. We put in a request for an Orchid Kelvin… I am waiting for a response from our guys on it.
>This is what Vibrant inline offered for the s3 801/805 chip set. What does the >at&t mean? If you need what orchid's rcpadi42.exp driver offered let, me know >and I'll pass it along. AT&T RAMDAC… Various S3 cards have different RAMDACs and therefore slightly different hi/true-color initialization. > main display;…
>rate at a specific resolution. It seem like the Vibrant drivers are ignoring >the MGA.MON file the refresh rates are specified. To be honest, we are using Matrox's initialization code for the Matrox support, so they should be handling this… I'll have our contact look into it. >…Liquid Speed… Actually,…
>How good is 3DS used in conjunction with C++ for producing games? Any other >tools? How about sound track? > >Any comment or experiences are welcome. > >Mei-Tien Lots of game companies use 3D Studio for game design. They use 3D Studio to generate 3D models, cut-scenes, and sometimes background…
>Tad, > >
Please try the 1.0.2 version on this forum. (VIB3DS.ZIP is generally the filename of the driver). Chuck Walbourn – Vibrant Graphics
The 801/805 are pretty much the same draw code… Can you send me a list of which modes worked in the Orchid Faharenheit and the S3 801/805 listings and I'll put the correct listings into the next driver… PS: We rewrote *ALL* of the S3 drawcode recently, 1.0.3 inline will…
Please let me know if the 1.0.3 Alpha fixes the problems with the PCI. We should be making a Beta 1.0.3 in about 1-2 weeks: Targa+ MGA-1 (MGA Impression and MGA Pro) other minor changes. Chuck Walbourn – Vibrant Graphics.
Nik – The problem is that we check the validity of the address even on the PCI version, which allows a lot more addresses. The version I sent to Gary Yost was 1.0.3 Alpha with the fixed code and it seemed to work for him–basically we allow ANY address for…
Can you please describe your card? It is an Orchid P9000… We have the VLB version working here. I'll send a note to our QA guys to make sure it still works–I assume you are using 1.0.2 of the Inline driver? You will not be able to get true-color materials…
Yep. 1.0.3 should fix it. I am investigating this now. Chuck Walbourn – Vibrant Graphics
The version on the BBS and on CompuServe should be 1.0.2–this seems to be the one with the MEMADDR problem on PCIs. 1.0.3 should deal with this–the Alpha I sent to Gary Yost seems to work…
#101544-
Beta Vibrant driver
Message #102305
I have a 'NULL' vdc in the 1.0.3 Alpha I am working… That should help.
#101337-
PCI Viper not VLB Viper
Message #102004
>Chuck, >> > >Ya although there are no jumpers or anything to change it on the card. Oddley >I seem to recall running the some DOS utility that said the card was at D000 >or at least part of it was. This address however didn't work either. Are you using…
#100752-
Vibrant Drivers
Message #102002
>I'm fuzzy on it now, but it seems that when I used your 4/8/94 version it kept >telling me the MemAddr in my .ini file was incorrect. It said that a Viper >should be @ 2000, 8000, or A000, while my .ini file said B800. I tried >changing to each…
I can't seem to the find the original description of the problem… Can someone give me the run down of the problem and the attempted fixes to this point? Chuck Walbourn – Vibrant Graphics
If you need contact information, run 3D Studio Release 3 with 'vibcfg' on the command line and check out the title page… try your local dealer first. Chuck Walbourn – Vibrant Graphics
> I am using the Orchid 1280 Vibrant drivers that came with 3DSr3. Note that Does the problem happen in all resolution/color-depths? Are you able to test the video mode from the configuration? Chuck Walbourn – Vibrant Graphics
Mach 64 (ATI Pro Turbo) is in version 1.0.2 of the Inline driver. See LIB 9 for file VIB3DS.ZIP. Chuck Walbourn – Vibrant Graphics
Firstly, you should get the udpated VIB3DS.ZIP (v1.01 or v1.02) in LIB 9… there were some problems with PCI versions of the Diamond Viper. The problem you are having is because the driver is configured, but default, to use VESA mode for the Materials Editor… The Diamond Viper PCI BIOS…
The released version should be 1.0.2… I think it is in LIB 9… Anyone know if 3D Studio Inline driver v1.0.2 is in LIB 9? The only problems we were having was with MGA-1, which we removed from the cardlist–you can try it with the generic Matrox MGA settings. 1.0.3…
Hmm.. I'll send a question to our draw-code guys about it… When you tried the other addresses, did you get another message or still "MEMADDR" invalid? Chuck Walbourn – Vibrant Graphics
You are right! Basically, the 34010 doesn't support true-color, but the Hercules guys did some weird hacks to get it work. In this mode, however, TIGA can't be used to do the drawing. To implement this, we had to rewrite our TIGA VDC to take advantage of a generic draw-code…
Hmmm. Does the product work ok with that INI file and the Windows driver? If so, then maybe that weird address is valid. Chuck Walbourn – Vibrant Graphics
>> The advantage you have with the fact that 3DS is running in a DOS session >> under Windows is that it is in a seperate VM from the other Windows apps, >> so you can explicitly control how much CPU time gets dedicated to it, aka: >> pre-emptive multi-tasking.…
Just as a clairfication, I am not the 'offical' Vibrant Rep (That is Brian Massey). I am the programmer who works on 3DS Inline and Liquid Speed (our 3D Studio accelerator product), so I like to lurk about the ASOFT forum to check for techinical questions. The VIB3DS.ZIP in Lib…
I just did some testing under Windows with 3D Studio R3… I see what you mean by it not being real useful. I think that if used the 'text' emulation, you would have the same problem with the DOS box hanging because the text call would cause Windows to stop…
The STB Pegasus is listed… There are not seperate listings for the different bus types. Chuck Walbourn – Vibrant Graphics
Sorry if you are offended by my earlier comment. I had originally assumed that it was a 'tounge-in-check' request. I appologize. Thank you for giving us your feedback and I am truely sorry if you feel that I belittled your input. Vibrant's current work with the Inline driver has not…
Thanks… 🙂 How about a special driver that allows you to run 3D Studio on DOS without Windows… 🙂 Think of how much faster this would be! Chuck Walbourn – Vibrant Graphics
The Diamond Viper is supposed to have (when we did the work on it) a VIPER.INI file. When we look for an INI, this is the sequence we go through: o If Diamond Viper mode: o Search current directory, via the VIPERPATH, and then via PATH for VIPER.INI. o Search…
Page 3 of 4