KhronosGroup/WebGL

unexpected result after a for loop in a shader

Closed this issue · 1 comments

here are 2 links leading to WebGL code. Both should give the same result, one has a "for" loop, the other has a copy paste of statements into this loop. What intrigues me is that the code with the "for" loop does not give the expected result on my laptop. I would like to know the cause

https://jsfiddle.net/56jey9mf/

image

https://jsfiddle.net/nk2Lb1xh/

image

You should report it to the browser vendor bug tracker. Also remember to report which hardware the failure occurs.
For current Mac Safari, it appears that both cases work.

This might also be an issue with the underlying hardware or drivers.

The PointSize of 300 might be too big for some GL drivers for some cases.