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
- “FMOD failed to set the software format to the custom sample rate…” warnings are thrown as System Sample Rate value is being changed in Audio section of Project Settings window
- VFX Marquee selection does match the visual indicator
- “Invalid AABB aabb” errors are spammed when “Infinity” value is entered in Collider Component fields
- Editor Role does not sync with the MPPM Play Mode Scenario Role when entering Play mode
- Long asset names cause overlap with the “Find” function in search result tabs
Add comment