Search Issue Tracker
Fixed
Fixed in 2022.3.63f1
Votes
0
Found in
2022.3.62f1
Issue ID
UUM-113087
Regression
Yes
Inspector Components temporarily lose some fields when recompiling the code
How to reproduce:
1. Extract and open the attached “IN-108998.zip“ project
2. Open the “DepthShadowDemo.unity“ Scene
3. In the Hierarchy tab, select the “ShadowPlane“ GameObject
4. In the Inspector tab, open the “DepthShadow.cs“ Script
5. At line 65, comment out the “ValidateAll()“ function
6. Tab back into the Editor
7. Observe the Inspector tab
Expected result: “Depth Shadow“ Component has all the fields present
Actual result: “Depth Shadow“ Component loses some of its fields
Reproducible with: 2022.3.62f1
Not reproducible with: 2022.3.61f1 (6c53ebaf375d), 2022.3.65f1, 6000.0.54f1, 6000.1.14f1, 6000.2.0b12, 6000.3.0a3
Fixed in: 2022.3.63f1
Reproducible on: Windows 11
Not reproducible on: MacOS 15.5 Silicon
Workaround: Switching to a different GameObject and then switching back to the “ShadowPlane“ GameObject reveals the previously lost “Depth Shadows“ Component field
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