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
⚠️Issues not using this template will be systematically closed.
Describe the bug
When loading a model with two face corner byte color attributes, Filament crashes with PreconditionPanic in the VertexBuffer::Builder::build function.
We are not correctly handling gltf models with multiple color
attributes. Filament doesn't allow for more than one color
attribute. So we just set the additional attributes as
VertexAttribute::CUSOM(N).
Also properly clean up dummy buffer.
Fixes#8396
We are not correctly handling gltf models with multiple color
attributes. Filament doesn't allow for more than one color
attribute. So we just set the additional attributes as
VertexAttribute::CUSOM(N).
Also properly clean up dummy buffer.
Fixes#8396
We are not correctly handling gltf models with multiple color
attributes. Filament doesn't allow for more than one color
attribute. So we just set the additional attributes as
VertexAttribute::CUSOM(N).
Fixes#8396
Describe the bug
When loading a model with two face corner byte color attributes, Filament crashes with PreconditionPanic in the VertexBuffer::Builder::build function.
To Reproduce
Steps to reproduce the behavior:
Use React Native Filament 1.6.1 which wraps filament @ 3ca9b9c. In theory this should also apply to directly using Filament.
Load attached model which has two face corner byte color attributes
Observe crash
Expected behavior
The model should load and be displayed.
Screenshots
Inspecting the model using Blender we can see the two Byte Color attributes.
Logs
Crash as observed from iOS Simulator:
Desktop (please complete the following information):
Additional context
Testing file attached. Removing one of attributes solves crash. Import/Export via Blender 4.3.2
avatar_armature_only.glb.zip
The text was updated successfully, but these errors were encountered: