-
-
Notifications
You must be signed in to change notification settings - Fork 22k
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
Unable to import FBX model in 4.4.dev #96223
Comments
Just as a quick update, I retested this using a default cube exported from Blender as FBX and it fails with the same errors, so this does not seem to be related to the models used in the issue description. |
I bisected it to 7a20ba9. |
This was likely already fixed by #96207, can you confirm? |
Yes, building [f648de1] the issues seems to be fixed for FBX and gLTF! |
Yes, that pr fixes it. May require deleting the cache folder to fix the corrupt scene error. |
Tested versions
System information
Godot v4.4.dev.mono (108c603) - Windows 10.0.22631 - Vulkan (Forward+) - dedicated NVIDIA GeForce RTX 3070 (NVIDIA; 32.0.15.6094) - AMD Ryzen 9 3900X 12-Core Processor (24 Threads)
Issue description
When importing a mixamo character as an FBX in 4.4.dev, its not possible to instantiate it in a scene. The import process itself runs without issues however when attempting to drag the model into the scenes the output log is spammed with the following errors:
To note may be that when importing the same model in 4.3.stable the following warnings are logged:
I don't know if that is relevant, I just wanted to mention it in case there are issues with the model itself.
It was possible to import the character without issues in 4.3.stable. It was also possible to instantiate the model in 4.4.dev when performing the import in 4.3.stable and then opening the project in 4.4.
The models I've tested were the X-Bot as well as the Alien Soldier with both failing with the same errors.
Also I'm using the following props in my custom.py:
Steps to reproduce
Minimal reproduction project (MRP)
N/A
The text was updated successfully, but these errors were encountered: