#Material-edit prob
11 messages in this thread
I tried using vibcfg today and had some success but still not right.
Using vibcfg I got one more selection of 640×480 x 35k colors and that
gave me the result of being able to switch sample boxes without grey scale but
it left mouse trails. So that won't do besides I like 800×600 but at least it
shows me it can be done. I think I need a driver installation program that's
for orchid drivers and 3dsr3 or a custom set file or something to tell the high
preformance driver to perform in the material display screen becouse it's the
same driver for everything including rendering 16m colors. rcfadi42.exp ?
Any ideas? -Mike-
Mike,
if the in-line vibrant drivers don't give you the colour depth option you need
then I'm out of ideas. The latest drivers (vib3ds.zip in lib9) may have
additional support for your card, but I wouldn't swear on it.
Can you please describe your card? It is an Orchid P9000… We have the VLB
version working here. I'll send a note to our QA guys to make sure it still
works–I assume you are using 1.0.2 of the Inline driver?
You will not be able to get true-color materials with any driver other than the
Vibrant driver. ADI doesn't support true-color materials modes–some drivers
support the modes, but 3D Studio uses it as a 256 color device.
Chuck Walbourn – Vibrant Graphics
The card is a freinheit 1280 plus with the new 3.0 bios chip. And it's
using the rcfadi42.exp driver installed with finstall. I got some
success with vibrant driver 640×480 x 65kcolors (? or 35k), in that
the colors wouldn't greyscale out but the mouse would leave
trails.the finstall prog. is actually for 3ds3r2 not r3 and it also
installs acad and other program drivers. This is what Inside
3d-studio says (pg.959) the material editor supports 24-bit color. If
your board will not support 24-color at this res. try 15 or16-bit
color. If your board will not run at a higher number of colors, you
can run the editor with 256 colors, but you can only see one sample
in color at a time; all others are turned to greyscale. I'm just a
novice but it seems to me that my board should be working right.
-Mike-
How come aren't you using the Vibrant in-line drivers? ADI drivers are really
not that good for 3D Studio.
John Tissavary (LUNA cie)
Well I'm using WIN/OS2 and from what little understand, to have 3ds3
run seamless under os2 you need s3 drivers. I swear it's hard being a
novice and trying to sort this out. But I can run 3ds3 minimized or
suspend it minimized or run two sessions at once. But as far as
what's best I havn't found anyone willing to tell me. What's the
difference between a adi and a vibrant driver and do vibrant drivers
work better than Orchid drivers with a Orchid card? I should be
getting some answers finally from Orchid in the next couple days but
any input is appreciated. Thanks Mike
ADI drivers are Autodesk Device Interface drivers, really created for
AutoCad more that 3DS. They are limited in 3DS to 8bits. Vibrant is
the company that has written the in-line driver module for 3D Studio
that supports just about every card out there, including the Orchid
Farenheit. The installation guide gives you a step by step on the
setup procedure, but basically you delete your 3dadi.cfg, then type
"3ds vibcfg" at the dos prompt. This'll get you into the vibrant
setup, then you choose your card and resolution from the lists.
It's pretty straighforward. The Vibrant drivers are much better than
3rd party ADI drivers.
Yes it is straight forward I'll say that as long, as everything goes
right. The trick to make everything go right this time was to NOT
choose my board, but to choose my chip. When I chose the s3 801/805
chip set from vibcfg, I had 1/3 again more choises and it works
great! The board I have is orchid 1280 PLUS but the board offered is
only 1280 and it uses the s3 805 chip. But want to thank you guys for
the input at least I didn't feel ignored. Thanks again. -Mike-
The 801/805 are pretty much the same draw code… Can you send me a
list of which modes worked in the Orchid Faharenheit and the S3
801/805 listings and I'll put the correct listings into the next
driver…
PS: We rewrote *ALL* of the S3 drawcode recently, 1.0.3 inline will
have brand-new S3 drawcode, which should resolve some of the
problems and give a general performance increase.
Chuck Walbourn – Vibrant Graphics
This is what Vibrant inline offered for the s3 801/805 chip set. What
does the at&t mean? If you need what orchid's rcpadi42.exp driver
offered let, me know and I'll pass it along.
main display;
640 x 480 – 16, 256, 32768, 65536, 16777216 colors
800 x 600 – 16, 256, 65536 at&t
1024 x 768 – 16, 256, 65536
1024 x 1024 – 256
material editor;
640 x 480 – 256, 32768, 65536, 16777216
800 x 600 – 256, 65536 at&t
1024x 768 – 256, 65536
1028 x 1024 – 256
render
640 x 480 up to 16777216
800 x 600 up to 65536
1024 x 768 up to 256
This is what VIBRANT offered for the 1280 (there is no 1280 plus option)
main
640 x 480 up to 32768
800 x 600 " 256
1024 x 768 " 256
1280 x 960 " 16
1280 x 1024 " 16
material editor
640 x 480 – 256,32768
800 x 600 – 256
1024 x 768 – 256
render
640 x 480 – 32768
800 x 600 – 256
1024 x 768 – 16
1280 x 960 – 16
1280 x 1024 – 16
The rcpadi installer that came with the card only offered 256 for the material
editor. Let me know if you need more detailed info. -MIKE-
>This is what Vibrant inline offered for the s3 801/805 chip set. What does the
>at&t mean? If you need what orchid's rcpadi42.exp driver offered let, me know
>and I'll pass it along.
AT&T RAMDAC… Various S3 cards have different RAMDACs and therefore slightly
different hi/true-color initialization.
> main display; >640 x 480 – 16, 256, 32768, 65536, 16777216
colors >800 x 600 – 16, 256, 65536 at&t >21024 x 768 – 16, 256, 65536 >1024 x
1024 – 256 > material editor; >640 x 480 – 256, 32768, 65536,
16777216 >800 x 600 – 256, 65536 at&t >21024x 768 – 256, 65536 >1028 x 1024 –
256 > render >640 x 480 up to 16777216 >800 x 600 up to
65536 >1024 x 768 up to 256
>This is what VIBRANT offered for the 1280 (there is no 1280 plus option) > >
main >640 x 480 up to 32768 >800 x 600 " 256 >1024 x 768 " 256 >1280 x
960 " 16 >1280 x 1024 " 16 > material editor >640 x 480 –
256,32768 >800 x 600 – 256 >1024 x 768 – 256 > render >640 x 480
– 32768 >800 x 600 – 256 >1024 x 768 – 16 >1280 x 960 – 16 >1280 x 1024 – 16
What, if any, of these modes work on your card? 1.0.3 has a rewritten S3, so
some of these may work correctly…