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
- Opening Terrain Prefab in Prefab Editing Mode throws "NullReferenceException" error
- [Search] Dragging query pills put them behind the search text field
- A CustomPropertyDrawer that returns a PropertyField for a property named the same as a child field will not render all child fields
- Graphics Settings shows default values instead of the real values in the Rendering Debugger when Volume.profile is assigned via script
- Deleting multiple Tags throws “NullReferenceException”, and "Retrieving array element that was out of bounds" errors when holding the Enter key
Add comment