Search Issue Tracker
Fixed
Fixed in 1.0.7
Votes
0
Found in [Package]
1.0.6
Issue ID
BEHAVB-107
Regression
No
Placeholder nodes overwrite nodes inside the graph and don't revert back
*Steps to reproduce:*
1. Create a graph with custom nodes.
2. Delete the custom nodes back cs files. Wait for domain reload
3. Reopen the graph, see the nodes have been replaced with placeholder nodes
4. Bring back the cs files for the nodes.
*Actual results:*
Graph still contains Placeholder nodes.
*Expected results:*
Placeholder nodes should revert back to the original nodes
*Reproducible with versions:* 1.0.6
*Not reproducible with versions:*
*Can’t test with versions:*
*Tested on (OS):*
*Notes:*
* This can also happen due to bad domain reload that fails to load the nodes correctly.
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
- [Dragon Crashers] Build fails in U6
- [Dragon Crashers] 4 Shader error messages on import
- [Dragon Crashers] Readme text is white on light grey
- Cursor stays in front of the first character when entering text in the TextMeshPro field
- Searching in Hierarchy causes unwanted component calls
Resolution Note (fix version 1.0.7):
Missing nodes will no longer be replaced with placeholder nodes in the file, instead the change will be limited to the UI only. This means it's also easier to recover them once the source files are loaded correctly.
Also added improved error logging when converting from authoring asset to runtime asset to show when such nodes are encountered and exit early without an exception.