Search Issue Tracker
Fixed in 5.4.1
Votes
0
Found in
5.4.0b9
Issue ID
778814
Regression
No
EditorJsonUtility doesn't serialize same UnityEngine.Object after reloading scene
Repro steps:
1-Open the Bug scene.
2-Select the Bug GameObject
3-Link a reference to any UnityEngine.Object in the "Reference" field
4-Press the "Serialize" button
5-Save and reload the same scene
6-Press the "Deserialize" button
7-Notice how the "Reference" field has changed - sometimes it gets empty, sometimes it references to absolutely different game object
Expected behaviour: after deserialization it references the same object
Actual: serialization drops after reloading the scene
Reproduced on: 5.4.0b21; 5.3.5p3;
No EditorJSONUtility on 5.2 and earlier
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- "Attempting to use an invalid operation handle" error is thrown when stopping Play Mode after loading an Addressable scene using LoadSceneAsync
- Arabic separator character (066B) is treated as a full-width character when Duospacing is enabled on a TMP text component
- Crash on CheckDeviceStatus when converting materials from built-in to URP and using DX12
- Higher CPU frame time on Android devices with Cortex-A510 efficiency cores (vs Cortex-A55)
- Alt+click on List header does not recursively toggle child foldouts when items use a UI Toolkit CustomPropertyDrawer
Add comment