CompuServe Thread

#White Bar on Config

6 messages in this thread
#78613From: CHRIS TRUTYJan 24, 1994 10:36 AM
Jack, I have an Ultra Pro w/1MB of RAM. When I try to config RCPADI with 840x680x65,000 or 1024x768x65,000 and then test the video mode, I get a white bar which takes anywhere from 1/4 to 1/3 of the bottom portion of the screen. Rendering moves the top of the image down 1/3 of the screen and prints the bottom third at the top and offset to the left. I hope this is a setting problem that can be solved relatively quickly as I have a client waiting for a final product. As a side note also, 640x480x16,000,000 gives me nothing on the test screen. The VIBCFG config file is ADI3DS.CFG. Thanks, Chris
#78661From: Jonas Ruikis [ADESK]Jan 24, 1994 12:58 PM
Chris, If you have the ATI Ultra Pro, why are you not using the Vibrant Inline Drivers. I would recommend that you try that first. Remove any reference to RCPADI in your autoexec.bat and rerun 3ds vibcfg. See pages 66-74 for details of selecting VIBRANT and the ULTRA PRO. jonas[adesk]
#78677From: CHRIS TRUTYJan 24, 1994 2:35 PM
Jonas, I am still using r2. I don't have the programs that you suggested (not to mention that I have misplaced my installation manual). I am still doing it the "old-fashioned" way; changing the resolutions by erasing the 3dadi.cfg file and then restarting. Chris P.S. If this is something new that is not related to the version of 3DS, please tell me more!! I've had driver problems all of my life 🙁
#78709From: Jonas Ruikis [ADESK]Jan 24, 1994 5:25 PM
Chris, <<3DR2 I've had driver problems all of my life 🙁 >> Yet another reason to upgrade to R3. The video configuration has become much better along with all of the 200+ new features. jonas[desk]
#78725From: CHRIS TRUTYJan 24, 1994 6:57 PM
<< Yet another reason to upgrade to r3. >> I'm well aware of that and believe me it's at the top of my priority list but for now I still have r2 and I have to solve the problem. Any suggestions??? Chris
#78923From: Ralph F. FrantzJan 25, 1994 3:00 PM
Chris, I have seen this happen when the monitor frequency can not support the frequency that the video card is putting out at that resolution. Check the monitor specs against the video card specs. FWIW -Ralph