Search Issue Tracker
Fixed in 2020.2.X
Votes
0
Found in
2020.1.0a20
Issue ID
1218558
Regression
No
Avatar Mask ignores RM when both Humanoid & Transform masks are defined
Issue happens with Animator Controller Layers & Timeline Track Layers.
This is only repro with Humanoid.
This only happens when BOTH Humanoid & Transform masks are defined in the same Mask.
When only the Humanoid Mask is defined, everything is evaluated as expected.
When both are defined, the resulting RM is incorrect.
repro:
- open RM_controller scene
- play... notice that the Sprint motion is playing on the lower body including RM (expected result)
- select DefaultMale and open Animator window
- select the Sprint Layer, open option gear and replace "MaleMask" with "MaleMask_withTransforms"
note: this is the same Humanoid Mask, but also has a Transform definition
- play...
bug: notice that the Sprint motion is playing on the lower body BUT the RM is from the Walk clip, not the expected Sprint clip.
expected: RM is applied from the Sprint clip.
Although the Transform part of the Mask should not affect the RM of the Humanoid mask, it does. The two Masks in the project "should" give the same result on a Humanoid character.
The "RM_Timeline" scene reproduces the same issue on Timeline tracks.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- APV data is sometimes incorrectly loaded from multiple baking sets when loading a scene
- GC Alloc spikes occur when calling UnityEngine.Resolution and UnityEngine.RefreshRate with Equals() and GetHashCode()
- Type error is thrown when a new ComputeShader is instantiated after destroying previous ComputeShader
- APV data becomes incorrect when reselecting the currently active Baking Set
- Launch screen image exceeds the screen bounds on IPad when building for iOS
Add comment