Search Issue Tracker
Won't Fix
Votes
1
Found in
2021.3.9f1
Issue ID
UUM-24660
Regression
No
Imported Blender animations have gitches
Reproduction steps:
# Open the attached “Repro” project
# Select the “Assets/Models/Entities/MainCharacters/Heroes/UtilityAnim/HimikoMasaki_UtilityAnim1.blend” Model in the Project window
# Switch to the “Animation” tab in the Inspector window
# Select the “Himiko_Motion_Decelerate1” Animation in the Clips list
# Observe the 18th and 19th frames of the Animation in the Preview window
Expected result: The character's left leg doesn’t stretch towards the outside
Actual result: The character's left leg glitches, the left leg stretches outwards for 2 frames
Reproducible with: 2021.3.9f1
Reproducible on: Windows 10 (21H2)
Note:
* This issue is hard to reproduce and it occurs very rarely, randomly and can occur to any of the .blend files according to the user
* This project has been sent with the captured inaccuracy, reimporting the .blend file, rebuilding the libraries will force the model with its animation to be reimported and most likely the issue won’t be seen anymore on this particular animation
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
- Shader warning after building a project with URP Sample
- MissingReferenceException after clicking "Fix now" on NormalMap settings
- The "UniversalRenderPipelineGlobalSettings.asset" is creating noise in the git diff when building a Player
- Scene is marked as dirty when opening the project with Vertical Layout Group added as a Component
- Crash on UnityEngine::Animation::SetGenericFloatPropertyValues when keyframing the RigBuilder component to Enabled and Disabled
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.