Search Issue Tracker
Fixed in 9.0.0
Votes
0
Found in [Package]
7.1.1
Issue ID
1216760
Regression
No
[Shadergraph] Changing the default value of a boolean keyword causes the associated node's input to switch to a bugged vec4 mode
Repro steps:
1. Create a PBR shadergraph
2. Add a boolean keyword
3. Drag it onto graph
4. Toggle the keyword's default value
Expected result: the inline inputs remain vec1s
Actual result: they become bugged vec4s. The "off" slot will be reset to 0, 0, 0, 0 when the default is toggled on the property, and in the compiled shader, when a material is made of it, the inputs will act like vector1s, with only the X value considered.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Skinned Mesh Renderer with multiple Animator Components does not render when "Optimize Game Objects" is enabled
- [iOS]Certain characters are not displayed when using iOS devices with 18 OS and newer
- Trees do not render in 'Unity Terrain - URP Demo Scene'
- Silent crash when clicking in Scene View in a specific project
- The Player renders black on a Quest headset when MSAA, Post Processing, and Spacewarm depth submission are enabled
Add comment