Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

THREE.WebGLProgram: shader error #7035

Closed
mangust404 opened this issue Aug 22, 2015 · 5 comments
Closed

THREE.WebGLProgram: shader error #7035

mangust404 opened this issue Aug 22, 2015 · 5 comments

Comments

@mangust404
Copy link

Three.js revision: 71
Firefox: 39.0, Firefox 40.0, Ubuntu 12.04 LTS x86_64, NVIDIA GeForce 7300 GT

So the error is:
THREE.WebGLProgram: shader error: 0 gl.VALIDATE_STATUS false gl.getPRogramInfoLog Statically used varyings do not fit within packing limits. (see GLSL ES Specification 1.0.17, p111)
(see screenshot)

The problem occurs with MeshPhongMaterial, the MeshBasicMaterial is working fine.

The previous version of firefox worked fine, the last version of Chrome is also works.
Looks like only Firefox of the versions 39+ are affected.
screenshot 2015-08-23 01 04 29

@benaadams
Copy link
Contributor

What does the output of this say? http://webglreport.com/?v=1

@mangust404
Copy link
Author

Wow. Incredibly fast :-)
Here we go:
http://awesomescreenshot.com/04956avhf5
http://awesomescreenshot.com/08556avia3

@mangust404
Copy link
Author

Hooray!
With the webgl.bypass-shader-validation=true in about:config I can see the broken scene now.
But there is a really HUGE message in the console:
http://paste2.org/VCkh27dk

@benaadams
Copy link
Contributor

Its reporting a Max Varying Vectors of 0; which means the vertex shader won't be able to pass any data to the fragment shader; which is definitely a problem.

Its a firefox bug; but I can't see anything in the bug tracker for it.

Could you raise a bug in the Firefox bug tacker? https://bugzilla.mozilla.org/ Include the detail here with screenshot and screenshot for WebGL 1 that you have from the webglreport?

@mangust404
Copy link
Author

Ok, here it is: https://bugzilla.mozilla.org/show_bug.cgi?id=1197525
Can I leave this issue until guys from mozilla will handle the problem?

@Mugen87 Mugen87 closed this as completed Apr 7, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants