Search Issue Tracker
Won't Fix
Votes
0
Found in
6000.0.49f1
6000.1.3f1
6000.2.0b1
6000.3.0a1
Issue ID
UUM-105722
Regression
Yes
FBX Resamples Curves incorrectly when importing FBX files
How to reproduce:
1. Open the attached “IN-101924” project
2. Open the "SampleScene"
3. Click on the "Vehicle A.fbx" item in the Hierarchy
4. Double click the "Take 001" Animation clip in the Inspector
5. Select the Curves option in the Animation window
6. Select the "wheel_lf : Rotation” in the Animation Hierarchy
7. Observe the result of the Animation curves
8. Repeat steps 2 - 5 for "Vehicle A Corrected.fbx" in the Hierarchy
9. Observe the result
Expected Result: Y rotation is not trimmed to the Z rotation
Actual Result: The Y rotation of the curve is trimmed to the Z rotation
Reproducible with: 2022.3.42f1, 6000.0.0b15, 6000.0.49f1, 6000.1.3f1, 6000.2.0b1
Not reproducible with: 2022.1.0a1, 2022.3.41f1, 6000.0.0b14 (a038ffb60cdd)
Reproduced on: Windows 11, Windows 10 (user reported)
Not reproduced on: No other environment tested
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
- Popup windows spawn on the incorrect monitor when the Editor is placed near the boundary of scaled monitor next to a monitor with different scaling
- Hidden Tabs do not shift into empty space after closing visible Tabs
- [Android] Application not deployed on a device when "activity-alias" is used in the AndroidManifest
- Shader compile process adds shader ID to the constant buffer name when the word "Globals" is being used in Vulkan
- Audio Mixer Snapshot link to the documentation isn’t working
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.
After some investigation, we deduced that your problem was caused by the latest version of the FBX sdk.
Sadly, we cannot revert to a previous version, as doing so would deprive us of critical security updates.
In the event that Autodesk releases a new version that fixes this bug, we will consider an update.
We will close this case today.
Thank you again for taking the time to report this issue, and please let us know if anything changes that affects its impact or severity.