Search Issue Tracker
Fixed
Votes
0
Found in
2022.1.8f1
2022.2.0a12
Issue ID
UUM-8469
Regression
Yes
VFX Graph's Operator Subgraphs are turned into Empty Subgraph Operators when renaming an asset
How to reproduce:
1. Open the attached “VFX Test” project
2. Open the “New Graph” asset in the Assets folder
3. Rename the “RenameMe” asset to anything else in the Assets folder
4. Observe the VFX Graph
Expected result: There are no changes in the VFX Graph
Actual result: The “New Graph_Subgraph Operator_1” subgraph gets turned into an Empty Subgraph Operator
Reproducible with: 13.1.1 (2022.1.0a16), 13.1.8 (2022.1.8f1), 14.0.2 (2022.2.0a12)
Not reproducible with: 10.9.0 (2020.3.37f1), 12.1.7 (2021.3.6f1), 13.1.0 (2022.1.0a15), 14.0.2 (2022.2.0a13), 14.0.3 (2022.2.0a15, 2023.1.0a1)
Reproducible on: Windows 10
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
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
- Changing Transform values in Search window Inspector loses focus while dragging and stopping mouse without releasing dragging action
- Saving changes on the dirty VFX Graph during the Play mode throws "The referenced script (Unknown) on this Behaviour is missing!" warnings
- VFX Graph Debug Info overlaps the "Initialize" block debug info by default
Resolution Note:
Fixed by another internal issue: UUM-5081: [Backport] Renaming a VFX Graph loses all subgraph references