Search Issue Tracker
Won't Fix
Votes
0
Found in [Package]
1.21.1
Issue ID
ADDR-3103
Regression
Yes
AvatarMask changes are ignored when re-building the Default Build Script
How to reproduce:
1) Open the attached user project “TestAvatarMaskBuild“
2) Open Scene “SampleScene“ (Assets/Scenes)
3) Open the Addressables Groups window (Asset Management>Addressables>Groups)
4) Build Default Build Script (Build>New Build>Default Build Script)
5) Select the Avatar Mask (Assets/AnimatorController/UpperMask9085.mask)
6) Expand the Humanoid dropdown
7) Press on the arms and hands (they should turn red)
8) In the Addressables Groups window clear the Build cache (Build>Clear Build Cache>All)
9) Repeat the 4th step
10) Enter Play Mode, observe the arms and hands
Expected: The arms and hands are not animated
Actual: The arms and hands are animated
Reproducible with: 1.21.1 (2020.3.42f1, 2021.3.15f1, 2022.1.24f1, 2022.2.1f1, 2023.1.0a22)
Not reproducible with: 1.20.5 (2020.3.42f1, 2021.3.15f1, 2022.1.24f1, 2022.2.1f1, 2023.1.0a22)
Reproduced on: macOS 12.5 (Intel)
Notes:
- Issue is reproducible in Builds
- It is expected for two 'defaultlocalgroup_assets_player_119_2_*.bundle’s to have different hashes, but they have two identical hashes
Comments (1)
-
Alan-Liu
Apr 01, 2023 01:46
Related forum thread: https://forum.unity.com/threads/sbp-issues.1325760/
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
- "Perform Selected" of Shortcut Manager window does not perform the shortcut in some cases
- Crash on mono_get_hazardous_pointer when running Play Mode tests in a specific project
- [iOS] ‘확인’(Done) and '취소'(Cancel) text is displayed as '...' in the on-screen keyboard when the System preferred language is set to Korean
- No warnings when creating the selector with the duplicate name
- [sw-unity-6-1] Shadergraph panning area size is constant regardless of the size or the zoom level
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.