-
-
Notifications
You must be signed in to change notification settings - Fork 21.1k
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
Invisible geometry importing glTF with more than 4 bone weights #56705
Comments
Can confirm. Photo is with the fix. The bug happens when the skeleton is at the root. Attached fixed bird. |
Well, I tried the model and got this error:
This error means this model is not supported in Godot 3.4, because it uses more than 4 bone weights per vertex. During the development of the glTF module, I remember that it was decided that models with more than 4 bones could not be reasonably imported (based on some chat conversations I had with @fire and others), because some pathological cases exist which require more than 4 bone weights to function. My opinion is that the top 4 bones could be selected and renormalized, but I would need to understand more to know if this is a viable approach. I don't actually know how Godot <=3.3 dealt with models with >4 bone weights, such as JOINTS_0 and JOINTS_1. it's possible it just ignored JOINTS_1, but did it renormalize the remaining bones? |
My last attempt at normalizing bones is here. #48360 |
I can also confirm this. Either some rotation values are added into some bones (usually spines). After reimporting the gltf a few times, all meshes disappear. |
Fixed by #61912. |
Godot version
v3.4.3.rc.custom_build [dd00219]
System information
windows 10, gles3
Issue description
When importing the attached glb, the geometry is invisible, seems to be empty, no vertices, When importing in 3.3 or 4.0, it loads correctly. The model has a skeleton and some animations, both seem to load fine
Steps to reproduce
import glb into project, load scene
Minimal reproduction project
bird.zip
The text was updated successfully, but these errors were encountered: