Search Issue Tracker
Not Reproducible
Votes
0
Found in
6000.0.62f1
6000.2.13f1
6000.3.0f1
6000.4.0a5
6000.5.0a1
Issue ID
UUM-127506
Regression
No
Properties synchronize with each other when changing in the Shader Graph or Material Inspector
Reproduction steps:
1. Open the attached project "ReproProj"
2. Open the “/Assets/Materials/Cloud.mat” Material in Inspector
3. Change Secondary Color
Expected result: Each property instance is independent
Actual result: Each Secondary Color property synchronizes with each other
Reproducible with: 6000.0.62f1, 6000.2.13f1, 6000.3.0f1, 6000.4.0a5, 6000.5.0a1
Testing environment: Windows 10 Enterprise 21H2
Not reproducible on: No other environment tested
Note:
- In the Shader Graph “Assets/Shaders/Cloud.shadergraph”, see the many properties with the same name that are synced with each other (as they share properties of their original property)
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:
It looks like your shader graph asset is in an invalid state. I'm not sure how that would happen, possibly a bad merge- but somehow the many duplicate blackboard entries all refer to the same corresponding references. I can recreate this graph and the issue doesn't reproduce.
If you can provide reproduction steps as to how a shader graph asset ended up in this state, we could investigate a solution.