[Bug] Shader doesn't compile on FPS example (Linux/Chrome)

[jackdalton]

The FPS example is broken on several Linux distributions. Attached is a console log.

[jackdalton]

Chrome v47.0.2526.106 (Official Build) (64-bit)

[jackdalton]

Kubuntu 15.10 x64.

[jackdalton]

Same happens with Arch Linux x64.

Specific error message:

error: sampler arrays indexed with non-constant expressions are forbidden in GLSL 1.30 and later

[jackdalton]

Related to mrdoob/three.js#6115.

[jackdalton]

Happens on http://chandlerprall.github.io/Physijs/examples/jenga.html as well.

[jackdalton]

Confirmed by another user here.

[jackdalton]

mrdoob/three.js#6929

[jackdalton]

spite's suggestion yielded nothing, composer size is set here.

[Mugen87]

See WebGL shader fails to initialize. The bug will be fixed with Chrome 49.

The dev-build of Chrome already contains the fix. All my test cases work properly.

[Mugen87]

Besides, the error doesn't occur with the latest dev version of three.js.

[sasha240100]

@Mugen87 Thanks! Is that version stable now?

[Mugen87]

@sasha240100 No, it's just the latest build of the three.js dev branch. I don't recommend to use it in production. This commit fixes the issue. If you need a hotfix, you can implement it in a custom build of three.js.

[sasha240100]

@Mugen87 Will this one support this fix?(dev channel)

[Mugen87]

@sasha240100 Well, if you use this version of Chrome (dev channel), you won't get the error even in older three.js revisions.

If you can't upgrade your browser, you can implement the mentioned fix for three.js. Or just wait until everything lands in production...

[jackdalton]

@Mugen87 Thanks for taking the time to help us out with this, not being able to see some of our demos has been driving me crazy. I grabbed google-chrome-dev out of the AUR, and everything works. I've just been using google-chrome-beta, I never thought to test with Chrome's dev build.