-
Notifications
You must be signed in to change notification settings - Fork 3.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
Multiple meshes - No indices #4237
Labels
Comments
Thanks for the detailed report, @konashredbiker. @lasalvavida can you please look at this after the glTF 1.0.1 updates? |
Could this be labeled as "bug bash" so someone can take a look at this issue? |
Hi @konashredbiker, we've labeled this issue for the bug bash. It might be a little larger scope than we can get to during the event, but this will at least put it on our radar to look into it soon if we can't get to it then. Thanks! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Storing multiple meshes in one glTF without indices and loading it in Cesium results in an error. Only the first mesh shows up. While debugging Cesium, I can see that multiple meshes are loaded and this error message occurs while rendering:
[.CommandBufferContext]GL ERROR :GL_INVALID_OPERATION : glDrawArrays: attempt to access out of range vertices in attribute 1
When debugging Cesium in Context.js line 934 [context._gl.drawArrays(primitiveType, offset, count);] a different offset is used than defined in the glTF file.
In the example (testMulti.zip) three Cubes are saved, but when loading the file only the first one is rendered.
I already posted an issue in the glTF repo (KhronosGroup/glTF#694), but it seems that the model or the glTF spec is not the problem.
The text was updated successfully, but these errors were encountered: