ATI Radeon 9700 not displaying in 32-bit colour
by Elum Vector · in Hardware Issues · 03/22/2003 (1:52 pm) · 20 replies
Hello,
I recently just installed a new ATI radeon 9700 pro and it seems that I cannot get the TGE to run in 32-bit colour. I set the video driver to direct3d and the game DID display in 32-bit. But as far as openGL I cannot run 32-bit colour for the life of me. Has anyone else ran into this problem? And fixed it?
Thanks in advance for any help.
-Elum
I recently just installed a new ATI radeon 9700 pro and it seems that I cannot get the TGE to run in 32-bit colour. I set the video driver to direct3d and the game DID display in 32-bit. But as far as openGL I cannot run 32-bit colour for the life of me. Has anyone else ran into this problem? And fixed it?
Thanks in advance for any help.
-Elum
#2
Thanks Eric.
-Elum
03/22/2003 (3:31 pm)
Yes, I allready tried that. The display options say that it's running in 32-bit.. but trust me it's definitly not. I even tried the latest realm wars build and the same problem happens.. you choose 32-bit colour and it still displays 16-bit. I'll try some older drivers.Thanks Eric.
-Elum
#3
"The display options say that it's running in 32-bit.. but trust me it's definitly not."
That seems to indicate you have something that can detect the bitdepth the card is running in, and it's telling you something different from Torque?
d
03/22/2003 (7:39 pm)
I've been running torque stuff on a 9700 in 32bit. Can you explain:"The display options say that it's running in 32-bit.. but trust me it's definitly not."
That seems to indicate you have something that can detect the bitdepth the card is running in, and it's telling you something different from Torque?
d
#5
I know the difference between a 32-bit screen and a 16-bit one. I run the level under D3D (32-bit), look at the sky and there is NO banding. All the gradients are smooth. I look at the sky under openGL (32-bit), and there is visible banding.
If it's not too much trouble David, please post your current version of driver you are using for your card.
I am using..
Card: ATI Radeon 9700 Pro 128
Driver version: 6.14.1.6292
-Elum
03/22/2003 (8:29 pm)
Ok, let me explain this in more detail.I know the difference between a 32-bit screen and a 16-bit one. I run the level under D3D (32-bit), look at the sky and there is NO banding. All the gradients are smooth. I look at the sky under openGL (32-bit), and there is visible banding.
If it's not too much trouble David, please post your current version of driver you are using for your card.
I am using..
Card: ATI Radeon 9700 Pro 128
Driver version: 6.14.1.6292
-Elum
#8
That completly solved my problem.
Thank very much Melv along with everyone for the information and help.
That was spot on. Wonderful!
-Elum
03/23/2003 (8:19 am)
Wow,That completly solved my problem.
Thank very much Melv along with everyone for the information and help.
That was spot on. Wonderful!
-Elum
#10
d
03/24/2003 (8:30 pm)
Yeah. People don't seem to realize that all the driver battles for performance have caused the OGL drivers to default toward speed, and D3D to default toward quality.d
#11
i have the same problem with elum i turned texture quality up high but i still have the color bandin problem in OGL programs.It all started after i loaded the latest driver but now going back to the older drivers doesnot seem to fix my problem
Im really desperate :[
09/13/2003 (2:59 pm)
Well i have r9700 pro too with the latest driver from atis site.i have the same problem with elum i turned texture quality up high but i still have the color bandin problem in OGL programs.It all started after i loaded the latest driver but now going back to the older drivers doesnot seem to fix my problem
Im really desperate :[
#12
Just double-check that during your driver battles, the display depth hasn't moved down to 16-bit, check that you've changed the OpenGL settings and not the D3D ones and check that Torque is running under OpenGL.
If this problem is there under D3D and OpenGL then you've got a more fundamental problem.
If putting the older driver (which worked) back on doesn't revert back to a working system then I would question whether the un/installation programs are completely cleaning the driver files correctly from your system. Did you remove the existing driver before putting the next one on? Sometimes things like this can cause headaches. If so, then try reinstalling the later driver, removing it correctly then reinstalling the older one. Note that after removing the older driver and rebooting, if the system detects the card and automagically installs a driver then reminents of it are being left by the installation package. The only way to solve this is to remove the driver files manually. :(
Not sure what else this can be as I've not using a 9700 anymore.
Hope some of this helps,
- Melv.
09/14/2003 (12:02 am)
BSU,Just double-check that during your driver battles, the display depth hasn't moved down to 16-bit, check that you've changed the OpenGL settings and not the D3D ones and check that Torque is running under OpenGL.
If this problem is there under D3D and OpenGL then you've got a more fundamental problem.
If putting the older driver (which worked) back on doesn't revert back to a working system then I would question whether the un/installation programs are completely cleaning the driver files correctly from your system. Did you remove the existing driver before putting the next one on? Sometimes things like this can cause headaches. If so, then try reinstalling the later driver, removing it correctly then reinstalling the older one. Note that after removing the older driver and rebooting, if the system detects the card and automagically installs a driver then reminents of it are being left by the installation package. The only way to solve this is to remove the driver files manually. :(
Not sure what else this can be as I've not using a 9700 anymore.
Hope some of this helps,
- Melv.
#13
I hope they fix it in 3.8 :|
Thnx for the help.
09/14/2003 (1:01 am)
Yes the problem was in the drivers version 3.7 i uninstalled them and installed 3.5 drivers and control panel then increased ogl texture quality and it worked.I hope they fix it in 3.8 :|
Thnx for the help.
#15
09/14/2003 (7:46 am)
Our testers have implied that the 3.4 drivers are best, can anyone confirm?
#16
EricF
09/16/2003 (7:31 am)
Edward, I've had no problems with the 3.5 drivers. Haven't even tried the 3.7.EricF
#17
09/30/2003 (10:29 am)
Hmmm. I'm glad I found this posting. I had the same issues with the 3.7 drivers on my radeon 9200. I reverted to the drivers that came with the card (3.4) and the color is working fine again. As a side note, does D3D work with Torque at all? On my old nVidia card and now on my Radeon card, I've had flashing and artifacts with D3D (in the menus, etc.) ... ?
#18
10/02/2003 (9:33 am)
ATI sent us some information on the problem. The Torque engine downloads 32 bit textures as "GL_RGB". The GL_RGB type implies 32 bits, but actually leaves the stored bit depth at the discretion of the driver and driver settings. We recently checked a change into cvs which explicitly informs the driver we want RGB 32 bit textures. This appears to fix the problem :)
#19
10/02/2003 (11:12 am)
Will the demo executable be updated to reflect this fix?
#20
10/02/2003 (11:20 am)
There have been a few recent fixes we'd like to have in the demo. We will put a new release out.
Torque 3D Owner Eric Forhan
My 9500 is running great.