Windows+ATI star and nebula display bug solution.
Moderators: winston, another_commander
Windows+ATI star and nebula display bug solution.
Windows players whose ATI video cards display stars and nebulae as ugly translucent squares
there seems to be an OpenGL driver error in ATI's EXT_texture_lod_bias implementation.
this has not been fixed in Catalyst 9.1 drivers. ( edit .. ) or 9.2
edit: Ahruman has made a good code workaround for Oolite version 1.73
if you want to compile oolite.exe from source edit trunk/src/Core/Materials/OOTexture.m changing ..
if (sTextureLODBiasAvailable) glTexEnvf(GL_TEXTURE_FILTER_CONTROL_EXT, GL_TEXTURE_LOD_BIAS_EXT, _lodBias);
to
if (sTextureLODBiasAvailable) glTexEnvf(GL_TEXTURE_ENV, GL_TEXTURE_LOD_BIAS_EXT, _lodBias);
the resulting oolite.exe should work for Windows + ATI video cards. even with recent Catalyst drivers ( including 9.1 )
it is not necessary to update drivers first.
this apparent OpenGL driver error has been reported to ATI recently.
glTexEnvf(0x8500,0x8501,_lodBias); ( should work .. but does not )
glTexEnvf(0x2300,0x8501,_lodBias); ( should not work .. but does )
is there anybody out there with experience reporting graphics bugs to ATI ?
there seems to be an OpenGL driver error in ATI's EXT_texture_lod_bias implementation.
this has not been fixed in Catalyst 9.1 drivers. ( edit .. ) or 9.2
edit: Ahruman has made a good code workaround for Oolite version 1.73
if you want to compile oolite.exe from source edit trunk/src/Core/Materials/OOTexture.m changing ..
if (sTextureLODBiasAvailable) glTexEnvf(GL_TEXTURE_FILTER_CONTROL_EXT, GL_TEXTURE_LOD_BIAS_EXT, _lodBias);
to
if (sTextureLODBiasAvailable) glTexEnvf(GL_TEXTURE_ENV, GL_TEXTURE_LOD_BIAS_EXT, _lodBias);
the resulting oolite.exe should work for Windows + ATI video cards. even with recent Catalyst drivers ( including 9.1 )
it is not necessary to update drivers first.
this apparent OpenGL driver error has been reported to ATI recently.
glTexEnvf(0x8500,0x8501,_lodBias); ( should work .. but does not )
glTexEnvf(0x2300,0x8501,_lodBias); ( should not work .. but does )
is there anybody out there with experience reporting graphics bugs to ATI ?
Last edited by Solas on Tue Feb 24, 2009 2:03 pm, edited 4 times in total.
- JensAyton
- Grand Admiral Emeritus
- Posts: 6657
- Joined: Sat Apr 02, 2005 2:43 pm
- Location: Sweden
- Contact:
It should be noted that the change Solas made above has not been added to “official” Oolite because it goes against the EXT_texture_lod_bias specification.
For 1.73, I’ve added a setting to disable all use of EXT_texture_lod_bias, which should avoid the glitch. (See Hidden Settings in Oolite.)
For 1.73, I’ve added a setting to disable all use of EXT_texture_lod_bias, which should avoid the glitch. (See Hidden Settings in Oolite.)
E-mail: [email protected]
We'll still have to do a few more bugfixes before releasing 1.73, which might take a while...Baza wrote:any idea how long?
In the meantime, you can try and build your own version of Oolite from trunk. That way you can get to play with the latest developments!
The most up to date instructions to do so on a PC are in
https://bb.oolite.space/viewtopic.php?p=69755#69755
A word of warning: sometimes things that work ok in 1.72.2 may be temporarily broken in trunk...
Hey, free OXPs: farsun v1.05 & tty v0.5! :0)
I also have other failures which appear sometimes (including bugs appearing after some play time)...and that's definitely only happening with my Vista ATI configuration.Baza wrote:Theres one thing I cannot understand..why is it that I get the nebula and point stars etc occassionally. Surely if this is a driver problem then I should get consistently problems? Cannot wait for 1.73 with the fix...any idea how long?
When I tested the modified version, I didn't experience the nebulae problems anymore with Vista...
Other issues had been solved with other driver versions, but those introduced other problems.
It's easy to implement bugs that don't happen everytime. For example, reading memory from an uninitialized variable. Good development tools can show such things, but often are not used because they slow things down while testing.
Screet
after reporting this bug on AMD Game » AMD Technology » ATI Radeon Graphics
http://forums.amd.com/game/messageview. ... erthread=y
I have received a response indicating that the problem has been located and a solution found ..
"This has been implemented ready for a future driver and will probably take a few months to appear in the drivers that the public get."
http://forums.amd.com/game/messageview. ... erthread=y
I have received a response indicating that the problem has been located and a solution found ..
"This has been implemented ready for a future driver and will probably take a few months to appear in the drivers that the public get."
MONTHS !?!Solas wrote:I have received a response indicating that the problem has been located and a solution found ..
"This has been implemented ready for a future driver and will probably take a few months to appear in the drivers that the public get."
If they found and fixed it as they say, why not supply that with the next driver release? It sounds like they may have found something but are afraid that they messed things up?!?
I did write to the vendor and asked them to send me a bill for the price difference of a GTX 295 compared to the 4870x2...as my card definitely suffers from other problems, too. Same OpenGL speed as an X1550 which uses the mainboards RAM! There must be something seriously wrong. No wonder that I have been missing a performance kick when I tried to play other OpenGL games in the past. Asus support completely stopped replying and ATI tech support simply closed the case as "solved" without ever writing any suggestions on what might be wrong - after asking me for a system report which includes my Vista keys (which I did blank out). Oh...and the driver feedback form has simply been disabled!
Screet
- JensAyton
- Grand Admiral Emeritus
- Posts: 6657
- Joined: Sat Apr 02, 2005 2:43 pm
- Location: Sweden
- Contact:
Yes.Screet wrote:If they found and fixed it as they say, why not supply that with the next driver release? It sounds like they may have found something but are afraid that they messed things up?!?
This is an entirely reasonable attitude when writing drivers.
E-mail: [email protected]
- DaddyHoggy
- Intergalactic Spam Assassin
- Posts: 8515
- Joined: Tue Dec 05, 2006 9:43 pm
- Location: Newbury, UK
- Contact:
So my plan to stop using ATi cards ten years ago was the right one...
From my friends who still have ATi cards they say Customer support has gotten worse since they were taken over by AMD - is this true? Shocking if it is!
From my friends who still have ATi cards they say Customer support has gotten worse since they were taken over by AMD - is this true? Shocking if it is!
Oolite Life is now revealed hereSelezen wrote:Apparently I was having a DaddyHoggy moment.
Or any complex software!Ahruman wrote:This is an entirely reasonable attitude when writing drivers.
Screet, I'm sorry you got burnt by ATI's broken drivers: however, as someone older & wiser told me many a time: It ain't worth it! walk away, man, walk away & don't look back, life is too short!
Hopefully the nvidia card will go some way to make you forget all this hassle...
Hey, free OXPs: farsun v1.05 & tty v0.5! :0)