Search Issue Tracker
Won't Fix
Votes
0
Found in
2022.3.38f1
6000.0.11f1
Issue ID
UUM-76484
Regression
Yes
Animation Clip selection is reset to the first Clip when changes on imported FBX animations are applied
How to reproduce:
1. Create and open a new 3D project
2. Import the “animation test.fbx” file (or any other file which contains 2 or more Animation Clips)
3. Select the FBX file in the Project tab
4. Select the “Animation“ section at the top of Inspector
5. Change any one Animation Clip (except the first Clip) property in the Inspector
6. Press the “Apply“ Button
7. Observe the Clips section in the Inspector
Expected result: The selected Clip remains the same as before
Actual result: The first Clip is selected
Reproducible in: 2022.3.9f1, 2022.3.38f1, 6000.0.11f1
Not reproducible in: 2021.3.40f1, 2022.3.8f1
Reproduced on: Windows 11 Pro (23H2)
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
- PlayerPrefs get corrupted when a minimized fullscreen Player is closed through the Taskbar
- "To Debug, run app with -diag-job-temp-memory-leak-validation cmd line argument. This will output the callstacks of the leaked allocations." warning is printed when JobTempMemoryLeakValidation switch is enabled
- Main Thread stalling when loading Audio Source asset asynchronously while preloading another Audio Source asset
- Material artifacts occur in the Material Preview window when baked lighting is applied to scenes
- “ArgumentOutOfRangeException” after saving, reseting and re-add Default Tile Palette Tools to the list in Preferences window
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.