Matrox – Vibrant vibcfg
13 messages in this thread
I just downloaded the beta release Vibrant drivers for 3ds r3 from Matrox for
my MGA Impression 3mb board. I put the 2 files (vib3ds.vlm and vibrant.res) in
my
\3ds directory and run "3ds vibcfg". I choose Vibrant for the Display driver
and
pick my board from the list. When I run the test I get a black box in the
middle of my screen and I have to reboot to get out.
Should 3dadi.cfg be deleted for r.3 (matrox requires it deleted for r.2)?
What i'm I doing wrong?
Where can I download the latest drivers from Vibrant Graphics?
Tom,
<< I just downloaded the beta release Vibrant drivers for 3ds r3 from Matrox
for my MGA Impression 3mb board. >>
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.
<< I put the 2 files (vib3ds.vlm and vibrant.res) in my \3ds directory and run
"3ds vibcfg". I choose Vibrant for the Display driver and pick my board from
the list. When I run the test I get a black box in the middle of my screen and
I have to reboot to get out.
Should 3dadi.cfg be deleted for r.3 (matrox requires it deleted for r.2)?
What i'm I doing wrong? >>
Well, you can always delete that file and it will get recreated upon startup.
Do you possibly still have your "set R*PADI=c:\….. " in your autoexec.bat? If
so, remove it.
jonas[adesk]
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 640x480x16M renderings to screen, there is a
multicolored line down the right edge of the screen.
– Doug Wolfgram/GRAFX, Written 02-Jun-1994 @ 07:46:59
Using: Windows NavCIS PRO 1.2
Doug,
<< 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 640x480x16M renderings to screen, there is a
multicolored line down the right edge of the screen.
– Doug Wolfgram/GRAFX, Written 02-Jun-1994 @ 07:46:59
Using: Windows NavCIS PRO 1.2 >>
My docs state that the latest vib3ds.zip in the 3ds section of the lib supports
the Number 9. For the best results you can post this to Chuck
Waldbourn[VIBRANT] 71673,2500 or to Nik Grant{ADESK] who collects and forwards
vibrant issues to Vibrant.
jonas[adesk]
>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 640x480x16M renderings to screen, there is a
>multicolored line down the right edge of the screen.
Verison 1.0.2 (on the system now) does support the GXE PCI. There are some
various minor bugs that are fixed in S3 for 1.0.3, but I think the 'line'
problem may be BIOS related… 1.0.3 should be out soon, please try it and get
back to me… Meanwhile, I'll ask around…
Chuck Walbourn – Vibrant Graphics
Jonas,
There's no RCPADI statement in my autoexec.bat.
I reinstalled MGA's software and Vibrant's beta release, but still black-out.
I know beta releases may have some problems, but I should be able to get
past step #1.
I spoke with Vibrant Graphics today and they say the new release of drivers
(not beta) will support my Impression board, and should be ready for
downloading
by this Saturday! VG BBS:#512-918-3411, but what can I do untill then?
VGA & VESA modes work in Display, but won't Render.
Tom,
<< , but what can I do untill then?.. >>
What's the behaviour when you choose driver=Vibrant and graphics board=VESA
Compatible?
Jonas,
When I choose Vibrant w/VESA comp. I get "ERROR # 1404 : Vesa function 0
or is not supported. A required VESA function to query the VESA BIOS either
failed or is not supported. Most likely, a VESA compliant BIOS is not present,
or the VESA system is corrupted. You may have installed the incorrect VESA VBE
for your VGA."
Tom,
<< When I choose Vibrant w/VESA comp. I get "ERROR # 1404 : Vesa function 0
or is not supported. A required VESA function to query the VESA BIOS either
failed or is not supported. Most likely, a VESA compliant BIOS is not present,
or the VESA system is corrupted. You may have installed the incorrect VESA VBE
for your VGA." >>
Try downloading VESADR.exe from the hware/opsys section of the library. Install
it as a TSR before going into 3ds vibcfg. Try it and let me know.
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.
> 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 forum list both MGA-1 and
MGA-2 based boards. The MGA-1 (MGA Impression and MGA Pro) don't work reliably
in all cases (single screen seems to have problems without their BIOS loaded).
Verison 1.0.2 release therefore doesn't list any MGA-1 boards. Version 1.0.3,
which is now in testing, resolves these problems and lists the MGA-1 boards
once again.
Chuck Walbourn – Vibrant Graphics
>Version 1.0.3, which is now in testing, resolves these problems and lists the
>MGA-1 boards once again.
Is there any possibility to get the beta of 1.0.3 driver ? I am asking because
I am developing the realtime hardware preview IPAS for MGA cards and I woul
like to test my module as soon as possible.
PavelK
>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 support. MGA-1 support was pulled because
it did not work correctly under 3D Studio. The MGA Impression 3mb is an MGA-1
and therefore DOES NOT work in all cases with 1.0.2. Version 1.0.3, which is
in testing now, will work in all cases with MGA-1 and MGA-2.
The 1.0.2 Beta that Matrox has lists MGA Impression, MGA-1 boards, but it is
NOT listed in 1.0.2 release because of the problems we found. 1.0.3 will list
the MGA Impression.
Chuck Walbourn – Vibrant Graphics