Search Issue Tracker
In Progress
Under Consideration for 2021.3.X, 2022.3.X
Fixed in 6000.0.0b16
Votes
8
Found in
2021.3.36f1
2022.3.21f1
2023.2.14f1
6000.0.0b11
Issue ID
UUM-66099
Regression
No
Additive Blending does not consider the difference between animation properties when using Additive Reference Pose
How to reproduce:
1. Open the “additiveBlending“ project
2. Open the “AdditivePropertyTest“ Scene
3. Open Window → Animation → Animator
4. Enter Play Mode
5. Select the “WithReferencePose“ GameObject
6. On the Animator window select Parameters
7. Observe “TestValue“
Expected result: “TextValue“ changes between 1 and 2
Actual result: “TestValue“ changes between 2 and 3
Reproducible with: 2021.3.36f1, 2022.3.21f1, 2023.2.14f1, 2023.3.0b10
Reproducible on: Windows 10
Not reproducible 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
- [XR] Input is not registered and headset view is headlocked after entering Play Mode with Meta XR SDK on 6000.0.0b16 and higher
- Crash on RtlLookupFunctionEntry when using 10 or more GameObjects with Articulation Body component in the scene
- Polygons are created on the opposite side of the Sprite when the Sprite boundaries are above the edge of the Texture
- Render Graph Viewer Resource list becomes shrunk after using a filter that yields no results
- [Android] [Vulkan] "VK_IMAGE_USAGE_TRANSIENT_ATTACHMENT_BIT" not added on some Android devices to "2D Colour Attachment"
Resolution Note (fix version 6000.0.0b16):
Fixed an issue where the additive reference pose frame would not be evaluated for curves not in the source clip. Shows an error message when selecting additive reference pose outside of the clip range with additional curves