Search Issue Tracker
Fixed in 2022.2.0f1
Fixed in 2022.2.X, 2023.1.X, 2023.1.0a23
Votes
0
Found in
2022.2.0b7
2023.1.0a10
Issue ID
UUM-13824
Regression
Yes
GameObject is not visible when is assigned to a custom layer and the layer is not marked in Opaque Layer Mask
To reproduce:
1. Open the user’s project
Expected result: The GameObject “Fog of Exploration (2)“ is visible in the Scene
Actual result: The GameObject “Fog of Exploration (2)“ is not visible
Reproducible with: 14.0.2 (2022.2.0a14), 14.0.3 (2022.2.0b7), 15.0.1 (2023.1.0a10)
Not reproducible with: 10.10.0 (2020.3.39f1), 12.1.7 (2021.3.9f1), 13.1.8 (2022.1.16f1), 14.0.2 (2022.2.0a13)
Reproduced on: macOS Monterey 12.5.1 (Intel)
Workaround: Mark the layer in Opaque Layer Mask
Notes:
- It throws two same warnings in the Console when selecting the GameObject in 2022.1.16f1 (“CommandBuffer: temporary render texture not found while executing“)
- It throws two errors in the Console when selecting the GameObject in 2022.2.0a18 (“ArgumentNullException: Value cannot be null Parameter name: value” and “Assertion failed UnityEngine.GUIUtility:ProcessEvent”)
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 2022.2):
There was an issue where the bound RenderTarget was not correctly tracked after some post-process situations. This issue has now been resolved.