This is an archive of CompuServe forum messages from 1985 to 1995, as saved in transcripts by John Foust.
Search Results (187 messages)
> Why won't your Vibrant drivers load with VESA COMPATIBLE parameters if I >invoke the UNIVESA TSR? It works with Diamond and Tseng… The VESA Compatables should work just fine with standard VESA. Does it not work with UNIVESA? Have you tried an Orchid specific VESA driver? Chuck Walbourn -…
>Chuck, did you see my request for support of the C&T 6554? I might have missed >the reply. It is a very common chip now across notebooks. It is nice to have >true-color rendering on a notebook…if only we can get it supported. Thanks! Please direct your request to Nik…
>It's possible that the differences in the Impression Plus (it uses several >chipsets in addition to the MGA chip) make it as yet not supported. You >should contact Chuck Walbourn from Vibrant for confirmation on this, though. >He hangs out on the forum, but I don't have his CIS #…
>chipset support, not just VESA, and is slightly faster in display modes (has >essentially an early version of Liquid Speed in it). >> > >Any chance of a press release or a list of supported cards uploaded into the >libs? please. I'll ask our marketing department to get something up……
#130777-
#3DS and #9GXE64Pro Card
Message #130953
>I have 3DS v3 and my video card is a #9GXE64Pro. I used the default >definition VESA Compatible 640X480 for the configuration. When I'm modeling >in 3DS everything looks fine. As soon as I render an image the screen has >these annoying flickers and when I go back to the…
>I have problems trying to install the new Liquid Speed for R4. At one point >in the install, it asks for your MASTER DISK. I put in my original Liquid >Speed disk, (which BTW has the EXACT SAME LABEL as the new one (!) ) but it >gives me an…
#130225-
Stealth64 Drivers
Message #130951
>Does anyone know where can I get the 3DS r3 drivers for the Stealth64 video >accelerator?? The Diamond Stealth 64 is supported by version 1.0.5, which should be available on this forum. Chuck Walbourn – Vibrant Graphics
>Vibrant wants $95.00 for their drivers that support r2. How much will Autodesk >charge me to upgrade? Note that the Vibrant drivers for r2 support lots of cards with direct chipset support, not just VESA, and is slightly faster in display modes (has essentially an early version of Liquid Speed…
>Vibrant graphics said they just took it off the bbs. if any has the file >id124103.zip please tell me! The Kelvin 64 is not suportted in 1.0.3 or 1.0.5. It is based on the Cirrus 543X, which was not completely stable as of the 1.0.5 release. Our current plans for…
BTW – We have an ADI driver that supports tons of cards, including the Diamond Viper VLB, which works with 3D Studio Release 1/2. Call Vibrant sales at 1-800-937-1711 and tell them that you want an ADI driver for 3D Studio Release 2 and they should be able to give…
>I have, Chuck – unfortunately, none of the *.FLC files were created with the >1.0.4 version, so I don't find anything that applied to me – did I miss it? >(I'll read it again, just to be sure…) I immediately had to go backwards to >the 1.0.3 version becuase of…
>Im using the Graphics Ultra Pro and there are no drivers for 3ds3. I need >details on how to configure the program for regular vga support. The Graphics Ultra Pro should be in the Vibrant Inline driver. Try 3ds vibcfg and see what is under 'ATI'… Chuck Walbourn – Vibrant…
#128902-
#VIB 1.0.5 driver prob
Message #129710
>Well, unfortunately, the VIBRANT 1.0.5 drivers still locks up in *.FL? >playback inside 3DS (v 3) on my S3 805 chip! If I use a (any other) non-3DS >program to play them, all works just fine… My specific card is an Orchid >Fahrenheit VA/VLB w/2MB memory. I never had any…
>Chuck; > We often need to step in and out of 3DS and Windows in order to create >material maps in windows, then use them in 3DS. That is also why the crash >when going into windows after 3DS is such a drag! Understood. We are working on resolving the…
>I understand that. Now, when I type 3DS vibcfg and go through the different >modes, how come you bring the screen immediately? For instance, if I pick >1024x768x8 and say "yes" to test the mode, the graphic screen comes up >immediately. If I go back and select another resolution, you…
>OK, Chuck, thanks. Just to clarify for those folks *thinking* that Liquid >Speed is included in R4. My take: Uh Uh. The hardware lock is STILL >required, but you are using Autodesk to help distribute the R4-compatible >software update, as a convenience to LS users, and as a side benefit…
>for fast >preview ……. as an autodesk developer I feel that force feeding the user to >conform to an 8 bit display, limits the user and sacrifices the very >performance that all of us have been working towards for over four years now. >HSC's product which is in develpment (Kai's…
>Talk about timing….. I downloaded the new Vibrant drivers that have been >recently added and all is well now. What exactly is the difference between >RCPADI and Vibrant? Rendering speed? Display speed? The Inline driver uses a proprietary interface which is functional based instead of packet-based like ADI. The primary…
>Yes, there is. According to Chuck the new (real time preview) will work only >in 8 bits. That's the reason this thing started. If everything worked in >either mode, than we wouldn't have a problem. But if that's true, we don't >have a choice. That's why mode switch is important.…
#128152-
#3DSR4 & LS
Message #128603
>Chuck, > Does Vibrant expect to release an updated Liquid Speed to work with 3D >Studio R4? Version 1.0.3 is already released and supports R4. PS: A copy of Liquid Speed (no hardware lock included) will be shipped with all Release 4's, so once you get a production release, you…
>The chip in my board says: > > Matrox > MGA > Power Graphics > IS-Atlas-R1 > 9421KK719 > >Do you know if this is an Athena chip? >Thanks for your interest. Rafa. Nope. The Atlas is MGA-2. It should work fine. Can you send your 3DS.SET file and a…
>Because I keep having to boot different modes, because I am developing >software and I boot 3D Studio hundreds of times, because I want to. Regardless >my reasons, it should not make any difference I understand. As stated before, I understand this is a long time, but there is not…
>My original question was about the _new_ drivers. They fail to recognize the >(my?) MGA board. And I don't know why, but it is taking too long yo get a >significant reply in either this forum or Matrox'. If you are going to test >the new Vibrant drivers and they…
>We just got a Matrox MGA 4Mb PCI board — you can run it at high resolution in >3D Editor, etc. using the RCPADI driver that is included with the board. >Set 3DS to use RCPADI using 3DS VIBCFG, and if you need to change your RCPADI >setup, delete 3DADI.CFG…
>Your Antivesa TSR has worked flawlessly for my PCI ATI w/4mb about 2–weeks >now. It gets me into 3DS in about 15 seconds vs. 50 seconds >when your TSR is not run. Also, I haven't experienced any destabilization as >The Vibrant people claim might happen. Thanks, for posting the >TSR,…
>The problems that I noted with the ATI Graphics Ultra Pro Turbo (Mach 64) is a >VLB card. I have a TriStar computer 486-66DX2, 64MB memory, and the Mach 64 >has and has been configured for 4MB. I have the same problem of going into >windows after 3ds. I also…
>I posted several messages about trying to get an ATI Mach 64 w/4mb to work on >an Intel pentium 90. This message is one of the latest. I haven't gotten a >lot of response on this problem. Maybe I haven't been checking the forum >often enough. Since this message I…
>Once I got your attention, did you see a message a couple of days ago >suggesting a couple of new features for the drivers? Particularly being able >to switch modes on the fly (specially color depth) and an added ability to >coexist with Windows (through the API I sent you…
>looking for? >> > >They *were* up here til last nite. Vibrant asked us to remove it and we're >looking into it as I type…(?) The latest RELEASED version is 1.0.3. We had given 1.0.4 to Autodesk for testing and I asked them to post it for TESTING by various…
>As to the delay, why don't you disable VESA on the way in and re-enable on the >way out? I assume you mean hook VESA then unhook it, ignoring all calls in between. This sounds like it would circumvent the ATI BIOS's operation which could potentially destablize the product. We…
> >> Have you run the ATI configuration program to ensure this mode is > >> setup? > >I have the same problem and it's pretty obvious I have run the setup. If he or >I hadn't run the setup, we couldn't be using 1280x1024x24 in Windows, which, >by the…
>I just got the card, tried to load it, and can't get past the 3ds vibcfg. At >this point, I'm not sure if it's the card, or the way I'm filling in the >vibcfg. I use vibrant selections for all and use ATI GPT. I even tried the ATI >Mach…
> Maybe you should chat with Gus Grubba. He is the one on the ASOFT forum that >wrote the ANTIVESA.EXE utility which helps get the load time down from 1:15 to >just under 15 sec. Thanks. We have been in contact with him on this issue. Chuck Walbourn – Vibrant…
> I have done some more research into the number of people actually having >problems and it does seem to be pretty wide spread. Although it does seem to >be worse with the PCI cards. We currently believe it to be related to the PCI's location of the video address…
>in this forum. It has been noted that there may be problems playing 320×200 >FLI files with the Vibrant configuration option for Flic-playing. Enjoy! Has anyone here ever had a problem with 320×200? Chuck Walbourn – Vibrant Graphics
#125723-
Latest "Vibrant" beta
Message #126869
>Well, I seem to be having a dickens of a time with the latest VIBRANT graphics >driver update outside of normal use! Anything I do in the 'normal' world >works perfectly, but lemme try and show a .FLC or something, and things go >straight to he… It almost always shows…
>I assume you mean 1 Min. 15 Sec to load 3DS. It takes me the same amount of >time without the ANTIVESA.EXE TSR some wonderful chap put up here on this >forum. It stops all VESA calls from the Vibrant driver and solves the slow >load problem of 3DS. Search…
>I also have that problem, plus starting studio takes a minute or two. Plus I am not sure there is much we can do about this. Does switching modes take 1-2 seconds or a lot more? >after rendering, the view are different. How do you mean 'different'? Chuck Walbourn -…
> I appreciate all you can do in regards to the problems getting into windows >after using 3DS with the ATI mach 64 and also regarding the slow entry into >3DS. > > As far as not being able to reproduce this effect, I find that hard to >believe. I…
>VIBCFG, I tried to have 1280 x 1024 with 16 million colors on my rendering >screen, but I got "Error 1933:BIOS does not support this mode" followed by >the statemet that my board may not have enough memory. It has 4MB, and will >configure to 1280 X 1024 with 65,000…
> But the WORST problem I am having with this ATI card is that after using 3DS >you must reboot the system prior to starting windows. It seems that the >Vibrant drivers leave a mess in the memory of the ATI card (It even fails it >won memory test after…
>I have an additional question that concerns viewing .flc files in 3DSr3. If I >view a 256 x 243 .flc the playback is at 320 x 200 cutting off 43 lines. If I >view a 512 x 486 .flc the playback is at 640 x 480, cutting of 6 lines.…
>Hi, > >Can anyone tell me where I can find 3D Studio drivers for a Matrox MGA II >graphics card ? The Vibrant Inline drivers version 1.0.3 and higher support this card. Look in the libraries of this form for VIB3DS.ZIP Chuck Walbourn – Vibrant Graphics
>I know that there is a "prelease" of the inline drivers ver. 1.0.4c on this >forum. But when will the actual release be out???? The "prelease" works great >as far as the mode switching, I don't have any delays with my ATI Mach 64, >however I still have a problem…
>I am having a strange problem and I'm not sure whether it's 3DS, Vibrant or >hardware related. My old video board (Viper PCI) crapped out and it was >replaced with a Stealth 64 (2MB). I have the most recent Vibrant drivers, ran >3ds vibcfg and all display modes look fine.…
> I have been using the Vibrant 1.0.4.c3 drivers with ATI M64 ISA 2M in a >486/33. 3DSr3 load time is 1 min 15 sec. Moving to and from the Material >Editor or View Image takes almost 4 sec. Is this what I should expect with the >current driver? TIA.…
>Two things: have heard many rumblings about new drivers for 3DS3 > (1.04+? mebbe) but cannot find. Also,and more important: We have two > machines running 3ds, and the IBM with the .5 meg tseng4000w32 pops > up renders(quick)in the Material ED, whereas the 1meg Cl-GC5422 takes >forever. > Otherwise,…
>I just downloaded the "new" vibrant drivers only to find out that they are the >"old" 1.0.3 drivers from last may! Now I have trashed my old copy and the >1.0.4 or 5 or 6 that was up here latest is gone. Help! Also, in case anyone >from Vibrant is…
#Mach 64 Delay FIXED!
Message #121573
Good news! We, with a bit of information from ATI, have been able to fix the delay problems with switching modes in the ATI Mach64! It will be available in the 1.0.4 Inline driver. Basically, for those techies who want to know, the problem was that we jumped to ATI's…
Page 1 of 4