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
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
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.