Search Issue Tracker
Fixed in 7.2.0
Votes
1
Found in [Package]
7.1.6
Issue ID
1204827
Regression
No
[HDRP][Shadergraph] Adding a boolean keyword to an HDRP Lit Shader makes material features not work
Reproduces in any version with Keywords.
Repro steps:
1. use a project with HDRP
2. Create a lit shadergraph
3. Click the settings button and change the material type to "Anisotropy"
4. Change "Anisotropy" input to 0.9
5. Add a boolean keyword
Expected result: the material feature continues to work
Actual result: the material feature doesn't work anymore
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Phantom_X
Jan 14, 2020 20:56
Adding a keyword also break a lot of other things like scene color node, scene depth node, cast shadows.... basically breaks the whole shader.