Remember me

Lost Password?

Register now!


Who's Online
75 user(s) are online (51 user(s) are browsing Forums)

Members: 0
Guests: 75


Support us!

Recent OS4 Files

Report message:*

Re: Warp3DNova shader bugs thread

Subject: Re: Warp3DNova shader bugs thread
by Hans on 2020/6/3 7:09:48


Is it mean that Nova need to deal with unitialized variables again ? Like, "vec3 col;" is unitialized, and optimizer fail to see that it used in the "if" later? But then, if should't work at all then, but it works. Just live vec3 have different value ?

Not in the case of that shader. Try setting col = vec3(1.0) on Windows, and see what happens.

The shader is taking advantage of GLSL implementations zeroing uninitialized variables. section 5.9 of the GLSL spec (using version 4.50) says: Reading a variable before writing (or initializing) it is legal, however the value is undefined.

At present, I have no intention of setting uninitialized variables to 0. I'll consider it if too many programs need it.


Powered by XOOPS 2.0 © 2001-2016 The XOOPS Project