GL-Slang more of a scripting language?

Well, since the hardware has no idea whether or not the code it is receiving came from unrolled loops, obviously. It just can't deal with very long shaders.

 

I've had enough problems using loops in GLSL shaders on ATI hardware that I stopped using them completely. For example, this code:

Code:

vec4 alpha = texture2D(sAlpha, alpha_texcoord);
vec4 color = texture2D(sTexture[0], texcoord[0]);
for(int i = 0; i < 4; ++i)
   color += texture2D(sTexture[i+1], texcoord[i+1]) * alpha[i];

Would either cause my app to crash, or produce very atrifacted results. Unrolling the loop manually to this:

Code:

vec4 alpha = texture2D(sAlpha, alpha_texcoord);
vec4 color = texture2D(sTexture[0], texcoord[0]);
color += texture2D(sTexture[1], texcoord[1]) * alpha[0];
color += texture2D(sTexture[2], texcoord[2]) * alpha[1];
color += texture2D(sTexture[3], texcoord[3]) * alpha[2];
color += texture2D(sTexture[4], texcoord[4]) * alpha[3];

solved the problem completely. This is damn frustrating

 

Wow, that's just a bad compiler.

 

The hardware isn't capable of doing any compiling BUT as I already said the drivers I'm fairly sure can unroll loops for 9700 as long as they are static loops and as long as the unrolled version stays within the instruction limit.

 

Well, some instructions require multiple slots, so the actual number may end up being less.