Search Issue Tracker
Fixed in 6.5.0
Votes
0
Found in [Package]
6.4.0
Issue ID
1132342
Regression
Yes
[ShaderGraph] Multiply Bug. Zeroing components in code generation
Generation of multiply code is zeroing out some components
1. Create a new ShaderGraph
2. add a Color node
3. feed that into a multiply node's A Slot
4. Set the w component of the default input binding for Slot B to 0
The reproduction of this bug is not limited to this permutation of input binding values. You can set any of the other components to any other value to get some odd behavior.
I added the generated shader code and added a note where the bad code is generated. Ctrl-F for "NOTE(wyatt)" or "@matt"
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