You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When GLB parser creates an index buffer, it passes a typed array to the constructor, instead of an array buffer. This results in view being a storage in the index buffer, instead of array buffer.
I am generating a mesh collider. To avoid copying the indices, I don't use Mesh API, but use the index buffer directly. In order to avoid copying the buffer when sending to web worker, I am sending the underlying Array Buffer. This bug makes it accessing the buffer differently, depending on if the mesh was generated by procedural.js or from GLB parser:
When GLB parser creates an index buffer, it passes a typed array to the constructor, instead of an array buffer. This results in view being a storage in the index buffer, instead of array buffer.
engine/src/framework/parsers/glb-parser.js
Line 835 in dc20e8e
The text was updated successfully, but these errors were encountered: