Search Issue Tracker
Won't Fix
Won't Fix in 6000.0.X
Votes
0
Found in
2022.3.24f1
2023.2.18f1
6000.0.0b14
Issue ID
UUM-70610
Regression
No
Data is not serialized correctly on time when OnValidate is used to retrieve the data
How to reproduce:
1. Open the “ScriptableSaveBug.zip“ project
2. Observe the Console
Expected result: The serialized data value is the same as the expected value
Actual result: The serialized data has the value of the previous state
Reproducible in: 2022.3.24f1, 2023.2.18f1, 6000.0.0b14
Could not test in: 2021.3.37f1 (Unsolvable script compilation errors)
Reproduced on: Windows 11 Pro (23H2)
Not reproduced on: No other environment tested
Notes:
- To reproduce the issue the second time, the “Value: “ in the “Test Scriptable Object.asset“ Asset has to be changed to 0 before opening the project
- Workaround is to change the “Value: “ in the “Test Scriptable Object.asset“ Asset to 1 before opening the project
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
- Assets are created in the Package folders when creating assets via custom buttons in the Inspector window or other windows
- “Select” windows are named differently on Windows and macOS
- [Windows] No minimum “Select” window size
- Enabling “Editor Extension Authoring” in UI Builder doesn’t dirty the document and saving with shortcut doesn’t persist the state
- WebRequest.Create() function fails with "URI prefix is not recognized" errors when the project is built for Linux Standalone or Windows Dedicated Server
Resolution Note:
Since the OnValidate method can be called from a separate thread or process, relying on the timing of changes made in this method is unreliable. Triggering the editor update callback from this method is also inadvisable since that callback is specifically for after an inspector refresh, which will not happen in the importer process.
Resolution Note (6000.0.X):
Since the OnValidate method can be called from a separate thread or process, relying on the timing of changes made in this method is unreliable. Triggering the editor update callback from this method is also inadvisable since that callback is specifically for after an inspector refresh, which will not happen in the importer process.