Search Issue Tracker
Won't Fix
Votes
0
Found in
2020.3.38f1
2021.3.9f1
2022.1.15f1
2022.2.0b7
2023.1.0a9
2023.2.0a1
Issue ID
UUM-14887
Regression
No
Errors do not contain the name of the file with the issue when FBX assets are imported to the Editor
How to reproduce:
- Create a new project
- Import user-attached “Dome.fbx” and “01_Frank_Whip_Equip_All.FBX” assets to the project
- Observe the errors
Expected result: The name of the file which has the problem is displayed in the Error messages.
Actual result: The name of the file is not displayed.
Reproducible on: 2020.3.38f1, 2021.3.9f1, 2022.1.15f1, 2022.2.0b7, 2023.1.0a9
Reproducible with: macOS 11.6.5 (Intel)
Errors:
Framerate was set to 0.00, it's been reset to 1.0.
transform.localRotation assign attempt for 'Sword_Blade12' is not valid. Input rotation is { NaN, NaN, NaN, NaN }.
Take/AnimStack 'Take 001' contains animation curves with invalid numbers (NANs) on these nodes (R - rotation): 'Sword_Blade12' (R), 'Sword_Blade13' (R), 'Sword_Blade14' (R). The invalid numbers will be replaced by default numbers from default pose.
This error indicates corrupt FBX file. In some case this error can be caused by having 0 scales in animation. 0 scales are not supported in FBXSDK. Use very small scales (like 1e-5) instead.
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Editor crash on "PPtr<Shader>::operator Shader*() const" when checking in changes with a very long comment in Unity Version Control window
- [Ubuntu] Toolbar and menu items for Version Control lack spaces in text on Linux
- Unity Version Control window Pending Changes tab’s Item checkbox is unresponsive when clicked and the item list is empty
- Audio stuttering occurs when heavy processing is performed while OnAudioFilterRead is in use
- Inconsistent Node search results in VFX Graph
Resolution Note:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.