#Vibrant 1.0.5 p1 busted!
7 messages in this thread
I've been playing with 1.0.5 p1 w/ both R3 and R4 with my Matrox MGA
Pro 4.5 Z/V. The driver is 'slightly' flaky under R3 with this card,
but with R4, it is a disaster! Even the video tests under vibcfg are
trashed. I reinstalled both 1.0.3 and 1.0.4 and no problems in either
R3 or R4. Any hints on when we might get a new version which is
healthy. Vibrant seems to have been having troubles with quality
lately…I noticed they pulled the first version of the release after
less then a week in the library section.
If anyone (especially Jonas) has any ideas on this situation I'll take them! I
know versions 1.0.3 and 1.0.4 are not officially supported with R4, but at this
point I have no choice.
mikey
Hi Mike,
<< If anyone (especially Jonas) has any ideas on this situation I'll take them!
>>
We don't have this card in product support. I'll make sure Nik sees this
message.
jonas[adesk]
<< If anyone (especially Jonas) has any ideas on this situation I'll take them!
>>
We don't have this card in product support. I'll make sure Nik sees this
message.
Jonas,
While your at it ask them to take a long look at the Mach 32 cards from ATI.
After I work in Studio for a short time, I get garbage across the screen when
play a preview.
Thanks,
Scott Lunsford
Tennessee Production Center, Inc.
I take that back. I double checked, and they are actually MGA ultimas. My
mistake. Sorry.
Scott, I also run the Mach32 and have had garbled screen problems when running
preview after rendering. Also, when leaving 3-DS, will get garbled screens in
other applications. There seems to be a problem in how Vibrant Drivers use the
card and don't give up settings. I tried a number of things, including excludes
and what not, but nothing seemed to help. THE FIX: Before leaving 3-DS, or when
encountering the garbled preview or running a 320×200 fli, I render to a blank
screen with the VIBRANT 320×200 option selected. Clears the card just fine.
Note: Right after R3 was installed, I contacted Jonas and Nik and was unable to
get any sort of fix. After updating the drivers the problem continued, but the
320×200 render satisfied me, more or less. I suppose R4 will give me the same
problem, hopefully not more, and perhaps, just perhaps, the problem will be
gone. Tech side note: Nik and Jonas, if you still want to contemplate this card
problem: If I leave 3-DS without clearing the card and go to windows, my
windows apps are fine. However, if i run a DOS app in windows it is fine until
I Alt-ESC. When going back into the app, then the screen is garbled. If I leave
3-DS without doing the 320×200 blank render, and go into Anim-Pro or Fractal
Dev (both running Supervga 800×600) that is while staying in DOS, I get the
garbled screen and have to go back into 3-DS and do the Vibrant 320×200 render.
Hi Jeffrey,
<< Tech side note: Nik and Jonas, if you still want to contemplate this card
problem: If I leave 3-DS without clearing the card and go to windows, my
windows apps are fine. However, if i run a DOS app in windows it is fine until
I Alt-ESC. When going back into the app, then the screen is garbled. If I leave
3-DS without doing the 320×200 blank render, and go into Anim-Pro or Fractal
Dev (both running Supervga 800×600) that is while staying in DOS, I get the
garbled screen and have to go back into 3-DS and do the Vibrant 320×200 render.
>>
Thanks alot!!
This is the kind of documentation that really helps the engineers involved
track down a problem.. thanks again.
jonas[adesk]
I hate to break this to you, but we have two of these cards in the shop, and
neither one of them are acting flaky. I suggest you start scrutinizing your
autoexec.bat and config.sys and stripping them down to bare bones and try
running 3ds again. I have run 1.03, 1.04 and 1.05 vibrant drivers on these
machines with nary a problem to be found.