Search Issue Tracker
Active
Under Consideration for 6000.2.X, 6000.3.X, 6000.4.X
Fix In Review for 6000.5.X
Votes
0
Found in
6000.2.0f1
Issue ID
UUM-120444
Regression
No
[VFX Graph] Updating custom VFXType doesn't refreshed previously created nodes.
Steps to reproduce:
- Import the provided package.
- Open the VFX inside named VFXG_BugRepro_CustomVFXType.
- Open the C# script named MyCustomVFXDataType.
- In the script, uncomment line n°9 and save the script.
- Observe the changes in the VFX editor window.
Actual results: After saving the script, the VFX editor refreshes its window and data.
The previously created node that uses the VFXCustom Type is not correctly refreshed, and its field slots are not refresh.
Newly created nodes are correct.
To refresh a previously created node, the user needs to switch between data types and will lose connections to the node.
Expected results:
Upon refresh, the nodes should be refreshed:
-New slots should be created for the added fields in the struct.
-Slots should be deleted for the removed fields in the struct.
-Slots names should be updated for the updated names in the structs.
Regarding connection:
Already connected slots should see their connection broken if the data type changes.
Already connected slots should see their connection broken if the struct field has been deleted.
If the Order has changed but the names are the same, it would be nice to keep the connections.
If the names have changed without order changes, it might be nice to also keep the connection.
[^VFXG_BugRepro_VFXCustomType_Refresh.unitypackage]
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Add comment