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
- 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
Resolution Note:
Fixed in 6000.5.0a7
Resolution Note (fix version 6000.5.0a7):
Fixed in 6000.5.0a7