Search Issue Tracker
Won't Fix
Votes
1
Found in
2021.3.45f1
2022.3.52f1
6000.0.27f1
6000.1.0a4
6000.2.0a1
Issue ID
UUM-87333
Regression
No
Root GameObject behaves differently when blending animations with and without keyframes and using AnimationPlayable
Reproduction steps:
1. Open the attached project "ReproProj"
2. Open the “/Assets/Scenes/Test1.unity” Scene
3. Enter the Play Mode
4. Press the Button with the text “Play()“
5. Observe the Transform of “CubeL1”, “CubeL2”, and “CubeL3” GameObjects
Expected result: All cubes reach 90 degrees of local rotation simultaneously
Actual result: GameObject “CubeL1” rotates locally only to 45 degrees while other cubes rotate to 90 degrees
Reproducible with: 2021.3.45f1, 2022.3.52f1, 6000.0.27f1, 6000.1.0a4
Reproducible on:
Play Mode
Windows Standalone Player
VLNQA00318, Oneplus OnePlus 7 Pro (GM1913), Android 11, CPU: Snapdragon 855 SM8150, GPU: Adreno (TM) 640
Testing environment: Windows 10 Enterprise 21H2
Not reproducible on: No other environment tested
Notes:
- The “TestComponent.cs” script has an animation curve set for “clip1”, but no animation curve is set for “clip without keys”. When blending these clips with a weight of “1.0f”, only the root GameObject (CubeL1) behaves differently, and even the clip without keys affects the blend unexpectedly
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
- Memory leak when a lot of UI elements are spawned and despawned
- Warnings are not logged in the Console window when using external code analyzers
- Errors “TLS Allocator ALLOC_TEMP_TLS, underlying allocator ALLOC_TEMP_MAIN has unfreed allocations, size 288“ appear constantly when Prefab is open
- Crash on PPtr<Shader>::operator or NullException errors spammed in console when calling Dispose() on null GraphicsBuffer with baked Reflection Probes
- “EndRenderPass: Not inside a Renderpass” and other Render Graph errors in the Player when Render Graph is enabled and Overlay UI is used
Resolution Note:
Thank you for bringing this issue to our attention. We acknowledge that this behavior is incorrect, and it is also not a regression in our code. Unfortunately, after careful consideration we will not be addressing your issue as the risk and impact on existing projects and users has been evaluated as high. This issue can be avoided using the following workarounds:
* Avoid using the Animation Mixer Playable with empty or incompatible clips by disconnecting the empty input or setting its weight to zero
* Make sure any animation sources used in the Animation Mixer Playable have curves specified for the root object being animated.
We appreciate your input and understanding, and please let us know if you have any other concerns or issues you would like to report in the future.