Search Issue Tracker
Fixed in 2022.2.9f1
Fixed in 2022.2.X, 2023.1.X, 2023.1.0b7, 2023.2.X
Votes
0
Found in
2022.2.3f1
2023.1.0a26
Issue ID
UUM-24730
Regression
Yes
Canvas GameObject Component does not change its Additional Shader Channel value when "Everything" is selected
Reproduction steps:
1. Open the attached “My project (35).zip“ project
2. Select Canvas GameObject
3. In the Inspector window attempt to change the Additional Shader Channel value to “Everything”
Expected result: Additional Shader Channel value changes to “Everything”
Actual result: Additional Shader Channel value stays as "Nothing"
Reproducible with: 2022.1.0a3, 2022.2.3f1, 2023.1.0a26
Not reproducible with: 2020.3.44f1, 2021.3.17f1, 2022.1.0a2
Reproduced on: macOS Monterey 12.6 (Intel)
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
Add comment