Search Issue Tracker
Fixed in 12.x (bdff332)
Votes
0
Found in [Package]
Master/12.x (ae93ea04e4)
Issue ID
1325934
Regression
Yes
[Shadergraph] Custom function node thinks graph precision is half when created
Bug regressed in https://github.com/Unity-Technologies/Graphics/pull/3360 according to Chris Tchou
Repro steps:
1. Use a project with shadergraph
2. Bring the attached hlsl file into the project
3. Make a shadergraph
4. Add a custom function node
5. Set the file to the attached hlsl file
6. Name the function "customfunc"
7. Observe the error on the custom function node
Expected result: the custom function looks for the "_float" version of the function
Actual result: the custom function's error indicates it can't find the "_half" version of the function despite the fact that the custom function's precision is float due to inheritance
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