#3D Studio R3
7 messages in this thread
Matthew,
The error you are receiving, as you may have surmised, is being generated by
the Vibrant Graphics driver that ships with 3D Studio. First, are you using the
latest version of the Vibrant Drivers? That would be version 1.05 and you can
get it by downloading VIB3DS.ZIP from the forum library.
2nd, a .VDC file is something that the Video Card or manufacturer would
provide. Since you already checked the disks that shipped with the card, you
might try going ATI a call to see if they have any further info.
In the meantime, I will forward this information to Vibrant, to see if they can
recreate your problem, and if so, offer a possible solution.
-Brian
Brian:
>The error you are receiving, as you may have surmised, is being generated >by
the Vibrant Graphics driver that ships with 3D Studio. First, are you using
>the latest version of the Vibrant Drivers? That would be version 1.05 and you
>can get it by downloading VIB3DS.ZIP from the forum library.
Thanks for the quick response! I did download VIB3DS.ZIP prior to contacting
you for help. I extracted the following files:
VIB3DS.VLM 10/07/94 16:32 413,020
VIBRANT.RES 10/07/94 16:34 388,986
VG940124.RLM 01/24/94 14:16 12,394
I even downloaded VIB3DS.ZIP again tonight, and I received the same files as
listed above. Per your suggestion; though not reprinted here, I have contacted
ATI regarding this problem as well.
Thanks,
Matt
<< Per your suggestion; though not reprinted here, I have contacted ATI
regarding this problem as well.>>
If they can't help you, let us know and we will see what other options we may
have.
-b
I had the same problem with the Graphics Ultra Pro Mach32, and no one
could help me so here is the answer to your question. The vibrant
drivers dont do jack, what u have to do is add the PAN switch to the
vvesa command. For more info type in at the dos prompt vvesa /? and
then everything should be allllright.
Thanks for the tip. Will check into it. Part of the problem I had
arised for OE (Operator Error) on my part. I renamed the old
drivers, thinking the program would look for the name only. After
realizing that 3-D Studio was accessing both the old an new drivers,
hence becoming schizoid, did I rename the extensions on the old
drivers as well.
Have you had a chance to eliminate the "schizoid" driver issue? Does this work
for you? I have no reports of this card failing with the latest Vibrant
drivers.
Nik:
Thanks for checking up on my progress. I resolved the schizoid driver issue,
as I was apparently loading both the old and new drivers at the same time. I
needed to rename more than the just the driver name, but the extension as well.
Preliminary tests look good so far.
Matt