Search Issue Tracker
Won't Fix
Votes
0
Found in
6000.2.0b2
6000.3.0a1
Issue ID
UUM-105156
Regression
No
Converting VFX to Subgraph Context breaks property connections
Steps to Reproduce:
- Import the attached VFX package
- Double-click Flames.vfx to open it
- Observe its appearance in the Scene view
- Press {{Ctrl/Cmd+A}} or manually select all nodes in the workspace
- Right-click any context and choose Convert to Subgraph from the context menu
- Observe the change in appearance of the Flames effect in the Scene view
- Open the newly created subgraph and inspect the exposed properties and connections
Actual results:
- Some property connections are lost or incorrectly assigned in the subgraph
- For example, the Flipbook Size property is incorrectly connected to the Soft Particle Fade Distance slot instead of the Flipbook Size slot
Expected results:
- All property connections should be preserved and correctly assigned during the conversion process
- No unintended remapping or loss of property-slot links should occur
Reproducible with versions: 6000.2.0b2
Not reproducible with versions:
Can’t test with versions:
Tested on (OS): macOS
Notes:
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:
This "convert to subgraph" contextual meny entry has been removed for nested VFX. This issue is therefore redundant