Search Issue Tracker
Fixed
Fixed in 6000.5.0a7
Under Consideration for 6000.4.X
Votes
0
Found in
6000.0.66f1
6000.3.5f1
6000.4.0b4
6000.5.0a5
Issue ID
UUM-132370
Regression
No
Longer Shader Graph Property Reference names breaks VFX Graph Output Particle Node
Steps to reproduce:
1. Create new Unity project using High Definition 3D Template
2. In project import provided VFX Asset “TestingVFX.vfx” and Shader Graph Asset “TestingShader.shadergraph”
3. Open “TestingVFX.vfx” VFX Asset
4. Observe the Output Particle Shader Graph Node
Actual results: Using longer Property Reference name in Shader Graph, breaks VFX Output Particle Node
Expected results: Using longer Property Reference name in Shader Graph should not break VFX Node, name should be truncated
Reproducible with versions: 6000.0.66f1, 6000.3.5f1, 6000.4.0b4, 6000.5.0a5
Tested on (OS): macOS Silicon Tahoe 26.2 (M1)
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
- MissingReferenceException errors are thrown after entering Play mode when multiple Inspector windows are displaying different objects with Grid Layout Group component
- "Can't change name, category with the same name already exists" Error is logged when renaming a Category to a name with a trailing space in the VFX Graph Blackboard
- Delete does nothing on an in-use Custom Attribute when re-triggered after cancelling the deletion confirmation prompt in the VFX Graph Blackboard
- No Ellipses are used for the Visual Effect Graph Create Context Menu Option
- Crash on LaunchBugReporter when opening a specific project using DirectX 12
Resolution Note:
Fixed in 6000.5.0a7
Resolution Note (fix version 6000.5.0a7):
Fixed in 6000.5.0a7