-
-
Notifications
You must be signed in to change notification settings - Fork 35.5k
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
WebGLBindingStates setupVertexAttributes BUG #20196
Comments
Hi, thanks for the report! Would you mind if making an example which can reproduce the error at jsfiddle? It helps us investigate the problem. (Note to Three.js core devs. If I'm right, it doesn't sound like a VAO related problem. It seems to have existed even since before we introduced VAO) |
Before joining the instancematrix, my program is working well, so a judgment should be added here |
Duplicate of #17701. |
There is also a PR for fixing this issue: #20135 |
Another user in the forum has run into this bug: https://discourse.threejs.org/t/mixed-use-of-mesh-and-instancedmesh-r120-version-reports-an-error/18281/2 |
When I use the scene with both InstancedMesh and normal Mesh, and set the scene.overrideMaterial =Depthmaterial; then object.instanceMatrix Is the undefined value, because normal Mesh does not have this property. In the setupVertexAttributes method of WebGLBindingStates, const attribute= attributes.get(object.instanceMatrix) On line 386, an exception is thrown. It is suggested to modify the get method of WebGLAttributes and add judgment:
The text was updated successfully, but these errors were encountered: