Search Issue Tracker
Fixed
Fixed in 2023.2.10f1, 6000.0.0b11
Votes
0
Found in
2023.2.2f1
6000.0.0b11
Issue ID
UUM-57757
Regression
Yes
A Script Component that has a serialized custom class is not detecting changes in the first boolean variable when entering the Play mode with the Script Components GameObject opened in the Inspector
How to reproduce:
1. Open the “SerializibleBug“ project
2. Open the “SampleScene“
3. Open the “Testing“ GameObject in the Inspector
4. Enter the Play mode
5. Observe the Console window with the Collapse option
6. In the “Test“ Script Component drop-down the “Unit“ array and toggle on the “Boolean 1“ check box
7. Observe the Console window with the Collapse option
Expected result: When only the “Boolean 1“ check box is toggled on a message “1 True; 2 False; 3 False“ is displayed in the Console window
Actual result: When only the “Boolean 1“ check box is toggled on a message “1 False; 2 False; 3 False“ is displayed in the Console window
Reproducible with: 2023.2.0a18, 2023.2.2f1, 2023.3.0a16
Not reproducible with: 2021.3.33f1, 2022.3.14f1, 2023.2.0a17
Reproducible on: macOS 13.5.2 (Intel)
Not reproducible on: No other environment tested
Note: The issue is only reproducible when entering the Play mode with “Testing“ GameObject already open in the Inspector
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
- UnityLinker causes crash when outputting snapshot data for very large projects
- Camera Preview does not detect multiple cameras with same GameObject name
- Crash on TypeTreeIterator::Children() when renaming a corrupted asset while Asset Serialization is set to Mixed
- Cameras (Camera.targetDisplay) render only to Display 0 in the Player when Multi-Display setup is used and DX12 API is set
- [Vulkan] _CameraOpaqueTexture produces a feedback effect on Android Adreno devices when using Vulkan
Resolution Note (fix version 6000.0.0b11):
This was fixed in 6000.0.b7 through an internal bug.
Resolution Note (fix version 2023.2.10f1):
This was fixed in 2023.2.10f1 through an internal bug.