Error in ThreeJS examples: gl.getProgramInfoLog() (66,6): warning X3557: loop only executes for 1 iteration(s), forcing loop to unroll

[ximreh]

After updating our project to ThreeJS ver 66 and 67 we came across the following error:
gl.getProgramInfoLog() (66,6): warning X3557: loop only executes for 1 iteration(s), forcing loop to unroll. There is no error with version 65.

The error can be reproduced also in the original threejs examples on
http://threejs.org/examples/#webgl_geometry_colors
http://threejs.org/examples/#webgl_geometry_convex

Browser versions : FireFox 28, 29, Chrome 33, 34

[satori99]

I get this error on windows with both Chrome and firefox too. I figured it was an Angle related warning, as it does not seem to affect the demos even though it is presented as an error.

[mrdoob]

It's not an error, it's a warning.
Before 66 we were not showing gpu warnings in the console.

[Nimanf]

@mrdoob This is reported as console.error(), which causes some issues, and displayed multiple times.
Other than reporting, isn't that because max(xxx, 0) was removed from pow() in shaders recently?

one example:

• Now:

pow( 1.0 - dot( lVector, pointHalfVector )

• Before :

pow( max( 1.0 - dot( lVector, pointHalfVector )

Thanks
Exocortex

[Nimanf]

Error:

"(71,64-116): warning X3571: pow(f, e) will not work for negative f, use abs(f) or conditionally handle negative values if you expect them

[WestLangley]

isn't that because max(xxx, 0) was removed from pow() in shaders recently?

Recently? It was? Which shader and when?

[Nimanf]

I reviewed the git history.. It seems max() was never added for all cases, it only gets reported after getProgramInfoLog.

This commit 183eacb only added max() condition for some parts.
Shaders of lights might still be negative. pow( 1.0 - dot( xxx )) ?

For example, adding a few hemisphere lights generates negative f error in pow().

[Gassepouille]

Hi,
I'm sorry to invite myself here, but I had the same problem :

gl.getProgramInfoLog() (45,6): warning X3557: loop only executes for 1 iteration(s), forcing loop to unroll (75,6): warning X3557: loop only executes for 1 iteration(s), forcing loop to unroll

So I tried to see where that came from, I isolate the problem, and it seems that it comes from the shadow casting method on the mesh which has the property : receiveShadow=true

At first I thought I did something wrong, but I just browse your examples and "warnings" appear in the console too :
http://threejs.org/examples/#webgl_shadowmap

I tried with the receiveShadow=false, the warnings are still there for your examples, but they are shortened. For my project : the error disappears. But no more shadow :'(

I hope it helps.

[bhouston]

Maybe the solution is to have a debug mode flag that shows the warnings? They are useful when debugging, but they scare users if they see them in production?

[mrdoob]

Hmm, yeah... Well, by now I've changed it to be a console.warn() instead I should have done in the first place.

[mrdoob]

Shaders of lights might still be negative. pow( 1.0 - dot( xxx )) ?

Could you do a PR fixing the remaining ones?

[Nimanf]

Could you do a PR fixing the remaining ones?

Sure, I can do that on Monday