Hi,

found a strange bug which doesnt occur when I precompile my shader using the fxc.exe from the DX SDK. The following expression should never become true but it actually does:
(x>=1) != (x>1 || x==1)

Just make simple pp effect using COL as output with these lines:


You´ll get white vertical stripes over the screen.
Compiled with fxc the screen stays black as expected.

V8.10.1

Regards

PS: Besides, when compiling complex shaders with big loops the fxc compiler is much faster. Why?

Better never compare nonzero floating point variables with "==". As you see, some compilers just don't like this. And we're not going to fix the compiler.

But it's interesting. Which DirectX SDK version were you using for the external compiler?

Must have been a quite old one but actually I dont know the exact SDK version the exe is coming from. The fxc.exe file version is 9.26.952.2844.

This could explain the different behavior. The engine uses the August 2009 SDK. I don't know if shader compiling with a different version causes a problem, but better use the August 2009 fxc.exe to get consistent behavior. Or compile fxo files with the engine - fxc.exe won't work for library shaders anyway.