Search Issue Tracker
Won't Fix
Won't Fix in 2023.3.X
Votes
0
Found in
2022.2.2f1
2023.1.0a24
2023.2.0a1
2023.3.0a3
Issue ID
UUM-27301
Regression
Yes
Input drawn with PropertyDrawer every few frames sets the value to null when changing the input value
Reproduction steps:
1. Open the attached “Test Project” project
2. Open the “SampleScene” scene
3. Select “Main Camera” GameObject
4. Select the “New Behaviour Script (Script)” component
5. Press the “Test” button
6. Change value inside newly appeared input
7. Observe the input while changing the value
Expected result: The input value changes without any interruptions
Actual result: The input value, every few frames, is defined as null
Reproducible with: 2022.2.0a9, 2022.2.2f1, 2023.1.0a24
Not reproducible with: 2020.3.43f1, 2021.3.16f1, 2022.2.0a8
Reproducible with: Windows 10
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
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
- Changing Transform values in Search window Inspector loses focus while dragging and stopping mouse without releasing dragging action
- Saving changes on the dirty VFX Graph during the Play mode throws "The referenced script (Unknown) on this Behaviour is missing!" warnings
- VFX Graph Debug Info overlaps the "Initialize" block debug info by default
Resolution Note:
Can't reproduce in latest 2022.3, 2023.2 and 2023.3. Try upgrading the Editor. If the bug is still present, we're sorry for the inconvenience, it could mean that the reproduction steps needed to be more detailed.
Resolution Note (2023.3.X):
Can't reproduce in latest 2022.3, 2023.2 and 2023.3. Try upgrading the Editor. If the bug is still present, we're sorry for the inconvenience, it could mean that the reproduction steps needed to be more detailed.