Search Issue Tracker
By Design
Votes
0
Found in
6000.0.62f1
6000.2.12f1
6000.3.0b10
6000.4.0a5
6000.5.0a1
Issue ID
UUM-126738
Regression
No
Shader graph node does not update to red when there is a precision mismatch between the base graph and the subgraph
How to reproduce:
1. Open the “IN-119523” project
2. In the Project window find and open the “Unity_Hand_Noise.shadergraph”
3. Ensure that “Precision“ mode is “Half”
4. Observe the “All Finger Highlights” node is blue
4. Double-click the “All Finger Highlights” node to open the subgraph
5. Ensure the “Precision” mode is set to “Single” and save the “All Finger Highlights” subgraph
6. Go back to the “Unity_Hand_Noise” base graph
Expected result: The “All Finger Highlights” node is red
Actual result: The “All Finger Highlights” node is blue
Reproducible with: 6000.0.0b13, 6000.0.62f1, 6000.2.12f1, 6000.3.0b10, 6000.4.0a5, 6000.5.0a1
Could not test with: 6000.0.0b12 (Compilation errors due to outdated packages)
Reproducible on: macOS Tahoe 26.1 (M1 Max), Windows 11 (by user)
Not reproducible on: no other environments tested
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:
Upon further review, this is by design. There are many places where the precision can be modified. In the provided case, the resulting precision lines up with what we'd we expect.