Search Issue Tracker
Fixed
Fixed in 2021.3.39f1, 2022.3.33f1, 6000.0.0b16, 7000.0.0a1
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
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