Search Issue Tracker
Fixed
Fixed in 1.4.14
Votes
0
Found in [Package]
1.4.12
Issue ID
UVSB-679
Regression
No
Bolt deserialization error and nodes missing after pressing Undo when Update Coroutine with Wait node is present in graph
How to reproduce:
1. Open attached project "BoltUndoLostData_stripped6.zip"
2. Enter Play mode
3. In Hierarchy select "directional Light"
4. In Inspector press "Edit Graph"
5. In "Flow Graph" window, create and enter into "Super Unit" node
6. Delete the Output node
7. Press Ctrl+Z (or do undo in any other way)
8. Observe the Console window and the main Flow Graph
Expected result: no errors are thrown, the Output node is present
Actual result: "\[Deserialization]" error is thrown, Output node is not coming back, the main graph has nodes missing
Reproducible with: 2019.4.0f1, 2020.1.0b12, 2020.2.0a14 (Bolt 1.4.12)
Could not test with: 2018.4 (unrelated errors), 2019.4.0f1, 2020.2.0a14 (Bolt 2, was unable to find 'Super Unit' node)
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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Resolution Note:
Graph rebuild has been delayed to the frame after deserialization to avoir the StopCoroutine issue while in deserialization.
Resolution Note (fix version 1.4.14):
Graph rebuild has been delayed to the frame after deserialization to avoir the StopCoroutine issue while in deserialization.