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
- Some UXML Template Asset foldouts appear enabled when all fields inside are disabled
- URP Terrain Demo crash on burst_signal_handler after Generating lighting
- Project window button icons are poorly visible and their shades differ in Light theme
- GC.Alloc called by HDRenderPipeline.LensFlareMergeOcclusionDataDrivenPass() when playing the default HDRP Sample Template project
- Automatic LOD fails and SRP Batcher incompatibility occurs when using spline-based quad-topology meshes
Add comment