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
- Deleting AudioMixer asset throws MissingReferenceException and breaks the Audio Mixer window
- Crash on ScheduleGenerateTilingShape when modifying PolygonCollider2D path count and setting path vertices
- Crash when a scene is created with LocalPhysicsMode::Physics3D
- [HDRP] Light doesn't bounce off terrains
- Unity Hub opens instead of the Unity Editor when launching a project from a Windows command line if a backslash is added to the end of the project path
Add comment