Genoa 8500VL w/CL-GD5428
15 messages in this thread
Does anyone know if there are VIBRANT drivers for this chip??? The 542x setting
doesn't recognize the board. I'm using RCPADI currently but would like to see
the difference.
Same board, same problem. Tried VESA too. I will try RCPADI now.
RCPADI works really well, just be sure to follow the instructions carefully.
The mention editing a couple of lines in 3DS.cfg, do just as it says and you'll
be set.
I tried it and screwedit up. I will give it another shot. Thanks.
>>Does anyone know if there are VIBRANT drivers for this chip??? The 542x
setting doesn't recognize the board. I'm using RCPADI currently but would like
to see the difference.<<
Richard,
I have been using this card with the Vibrant drivers for around a year. I use
the Genoa 8500 setting in vibrant and it works fine. What problems are you
experiencing?
Terry Gilbert
Forcade & Associates
>> I have been using this card with the Vibrant drivers for around a year. I
use the Genoa 8500 setting in vibrant and it works fine. What problems are you
experiencing? <<
Well, it doesn't even acknowledge that the card it there. It gives me a
message that I've selected the wrong driver for my card. If I let it auto
detect it reads Unknown….
>> it doesn't even acknowledge that the card it there.
I'm afraid this won't help too much, but I'm running the same card with no
problem. However, I do remember running into an occasional problem when I
first got the card. Since I didn't document the problem, ("Oh, good, it works.
I'll remember that for next time!" – Yeah, right…) I don't remember what the
problem was. I'd say check 4 things.
1. Make sure you have the most recent Vibrant drivers.
2. In your memory manager, exclude the ROM addresses for your video bios.
3. Make sure no VESA TSR is being loaded (from your old card, for instance)
4. Try the SYNC program on your Genoa disk to initialize the card.
Just some ideas… Like I said, mine works now, but there was a time that it
occassionally didn't. Good luck!
Thanks for the ideas! I don't think I have the latest drivers so I'll grab them
from here and take it from there.
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?
Thanks to those who responded!
>> all is well now.
Excellent. Glad to here it all worked out. Re: differences between RCPADI and
Vibrant, I'm not sure of all the specifics. I'd better let someone else
comment.
Richard,
<< What exactly is the difference between RCPADI and Vibrant? >>
RCPADI uses a packet style interface initially conceived for ACAD. The Vibrant
In-Line drivers use hooks that are integrated deeper into the 3DS core and I
believe use a more robust method of data passing.
Maybe Gary will elaborate a bit here..?
jonas[adesk]
>> RCPADI uses a packet style interface initially conceived for ACAD. The
Vibrant In-Line drivers use hooks that are integrated deeper into the 3DS core
and I believe use a more robust method of data passing. <<
So in other words the Vibrant drivers are better optimized for 3D Studio
operation. Sounds good to me….
>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 reasons/advantages are –
(1) ADI has no support needed by the FLIC playing module. The
R1/R2 releases of 3D studio had 'auto-detecting' code for
this which resulted in LOTS of problems because the
'auto-detect' code couldn't properly recognize and use
many of the video boards on the market. (Those of you who
remember know that this was a BIG deal for users of boards
like the Diamond Speedstar 24… The only resolution flic
that could be universally played back was 320×200).
(2) 24-bit color access was not supported by ADI for anything
other than 'RENDERING' devices. This means that using Vibrant
allows a true 24-bit color Materials Display. Users of ADI
will notice that even in 24-bit color modes, switching the
active material viewport remaps the palette.
(3) Performance. ADI's packet structure is slower than direct
calls. Also, ADI drivers reside in their own segment, resulting
in 'FAR' calls and memory access. Vibrant resides in the same
memory segment as 3D Studio, so all calls and data-passing is
'NEAR'. This makes for a much faster interface.
(4) Robustness. ADI was bascially 'adapted' for 3D Studio and
is primary driven to support AutoCAD. There are lots of
weird nuances with the way AutoCAD uses ADI, so 3D Studio
couldn't duplicate them all. Making an ADI driver FULLY
work with 3D Studio is not a trivial matter–we spent a year
of work keeping our ADI driver up with R1 and R2's usage.
The Inline is a simple, clean interface for 3D Studio and
there are no hidden problems with the operation of the
driver. Also, our draw-code is being used by drivers for
AutoCAD, 3D Studio, Microstation, Cadkey, and Animator Pro,
and most of it has been in production for years.
(5) Configuration. ADI's configuration was dependant upon the
vendor who developed it and many were VERY difficult to get
setup correctly. Vibrant's Inline driver has an integrated
configuration which covers 90% of all users.
(6) Support. The Vibrant Inline Driver supports hundreds of cards
out of the box with 3D Studio with very extensive resolution
and color-depth support.
Chuck Walbourn – Vibrant Graphics
Very well said, Chuck. Thanks.
– G
Richard,
I suspect that David is correct. It sounds like there may be some outside
conflict that is preventing the vibrant driver from accessing the card. do any
other programs with drivers specific to this card work? What version of the
vibrant driver do you have?
Terry Gilbert
Forcade & Associates