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
- Error “Shader error in 'YSCloudCover': call to 'tex3D' is ambiguous at Assets/YSCloudCoverText.shader(606) (on d3d11)“ is present when compiling tex3D shader with DXC
- Placeholder asset is not loaded with Advertisement Legacy sample when using the latest version of the package
- Addressables content build fails but the Player build is successful when building a development build
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
Add comment