David Spilling
10-12-2005, 06:53 AM
Dear All,
I have recently (today) upgraded my drivers from Catalyst 5.2 to 5.9 and experienced unfortunate behaviour with a shader that previously worked fine under 5.2. The application now slows to a virtual halt (presumably because the shader is now in software).
I've isolated and simplified the offending line to a rather innocuous :
vec4 a = texture3D( TextureMap, vec3(0.0,0.0,0.0));
so it's not an indirection issue or anything similar.
Without this line, the shader works fine. With Catalyst 5.2 and with this line, the shader works fine. With this line with Catalyst 5.6 or 5.9, I seem to drop back to software.
3DLabs' GLSL Validate is completely happy with the shader. Card is a X800.
What's changed since 5.2 which might be upsetting this? Any ideas appreciated!
Dave
I have recently (today) upgraded my drivers from Catalyst 5.2 to 5.9 and experienced unfortunate behaviour with a shader that previously worked fine under 5.2. The application now slows to a virtual halt (presumably because the shader is now in software).
I've isolated and simplified the offending line to a rather innocuous :
vec4 a = texture3D( TextureMap, vec3(0.0,0.0,0.0));
so it's not an indirection issue or anything similar.
Without this line, the shader works fine. With Catalyst 5.2 and with this line, the shader works fine. With this line with Catalyst 5.6 or 5.9, I seem to drop back to software.
3DLabs' GLSL Validate is completely happy with the shader. Card is a X800.
What's changed since 5.2 which might be upsetting this? Any ideas appreciated!
Dave