CompuServe Thread

#Graphite Pro rendering

9 messages in this thread
#68460From: John TissavaryNov 26, 1993 7:38 PM
Why aren't you using the in-line Vibrant drivers? All you have to do is delete your 3DADI.CFG, then type 3DS VIBCFG. This will put you into the Vibrant in-line loadable configuration program. Just select your card, and the resolutions you want (there is a problem with 800×600 24 bit which is being looked at by Hercules and Vibrant). I have the same card and have no problems. As for getting it running under windoze, did you exclude your base memory addresses from the 386Enh section in the System.ini? John Tissavary (La Luna cie)
#68514From: Bob KeeferNov 27, 1993 11:37 AM
I am using the Vibrant drivers that are included with R3! I followed the exact procedure you described – deleting 3DADI.CFG and selecting the mode for display, rendering, and materials. The 256-color rendering modes work fine, but the 640x480x24bit rendering mode is the one that locks me up after the rendering is completed. I also cannot get the 24-bit mode to work in the Materials Editor either. As for Windoze (I LIKE that), yes I added an EMMEXCLUDE for the same A000-C7FF range that I exclude in the CONFIG.SYS. Running under Windows isn't _critical_, but it would be nice sometimes when running AutoCAD for Windows not to have to exit and reload each program. Thanks for the advice!
#68522From: Angelo Guarino [DTI Inc]Nov 27, 1993 12:30 PM
Bob, >> Graphite, 3DS & DOS Make sure you are running the VESA.COM MYSCREEN.CRT in your autoexec.bat. Also, you shouldn't be defining a RCPADI device driver at all. Run 3DS with the VIBCFG option to get into the configuraiton system. Then choose the "vibrant" drivers and the correct option for the Graphite. >> Graphite, 3DS & Win I believe there is a problem running the vibrant drivers for the Graphite under windows. People are having success selecting the VESA driver though. Ang
#68564From: John TissavaryNov 27, 1993 6:01 PM
Oh yeah… the VESA.COM. Somebody (Vibrant, Hercules) ought to make this clear, because I don't think it's documented anywhere. I had to call Vibrant and beg them to tell me what the problem was after following instructions to the letter everywhere, and still not getting it to work.. John Tissavary (La Luna cie)
#68593From: Carl FinchNov 27, 1993 10:35 PM
>> I don't think it's documented anywhere… I had to… beg << The current Graphite Installation Guide (Ed. 1.3, June 93) _does_ address the need for running vesa.com for DOS-based VESA apps. on page 2-5. Maybe your supplications helped!
#68574From: Bob KeeferNov 27, 1993 6:03 PM
Ahhhh, Bach (sorry – old M*A*S*H reference where Radar appears to understand). I am using a batch file to run 3DS, in which I am running the VESA.COM and setting it to the MYSCREEN.CRT rather than in the AUTOEXEC.BAT, but I will try that. The reason I had it in the 3DS batch file was because I was also doing the following lines: SET RCPADI =…\DLXPRESS\RCDLX067.EXP SET VIBCFG =…\DLXPRESS\VIBRANT.CFG If I understand you, I do not need the SET RCPADI statement if I am using the Vibrant drivers. What about the SET VIBCFG – can I also eliminate that? This is a great idea – I didn't think about that because these were left over from running R2. I'll give it a try immediately! I've been battling this all day – finally found that I can run 1024x768x256 in all 3 modes (Display, Material, Renderer) and everything will work, but any other combination is causing lockups. Thanks for the tips, Ang. I'll let ya know what happens! Bob Keefer
#68579From: Bob KeeferNov 27, 1993 7:12 PM
I tried removing the SET RCPADI and SET VIBCFG statements from the 3DS batch file, but it did not seem to make a difference. Here's the wierd part (all using inline Vibrant drivers): I can run Display, Materials, and Renderer all at 1024x768x256, and everything works. I can even change the Materials to 1024x768x32K. But if I change the Materials to 640x480x256 or 16.7m, it locks up. If I change Display to 640x480x256 it locks up. And, if I change Renderer to 640x480x16.7m, it will render fine, but when I return to the 3D Editor, the cursor is frozen and I have to reboot. I completely reinstalled 3DS, and tried it once with the default 640×480 VESA drivers, and everything worked. Changed ONLY the Display to 640x480x256 Vibrant Graphite Pro driver, and it locked up. I am completely stumped. Thanks again for the suggestion. BTW – I was in a store today Christmas shopping with my wife – she came over and found me staring at a clear canister of Penn tennis balls. I excitedly explained why, waving my arms and rotating the canister to talk about highlights and transparency falloff, etc. Always supportive, she smiled and suggested we move on before someone called security. Nice job, Ang!
#68587From: Bob KeeferNov 27, 1993 9:01 PM
Ang: Hooboy, am I embarrassed…. Great story, wrong guy. I gotta get some sleep. I'll just blame it on hardware hassles. My mistake, and compliments to Alan Iglesias. I'll just crawl back under my desk now.
#68637From: ALAN IGLESIASNov 28, 1993 12:20 PM
Get ye from under that desk, Bob! That *was* a great story. I thank you much for the compliments, and *really* thank you for thinking of my rendering when you saw a *real* can of tennis balls! I hope Ang isn't too insulted, though, for being mistaken for me…-:)<g> It's the times like this that make ya feel so much better when you have one of those days when your machine is up on "jack stands" with parts strewn all over the place! *Never* stop scrutinizing those reflections and highlights, -Alan