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
Comments (1)
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
- Keywords on Material Variants aren't automatically saved when changed on original Material through Shader Graph
- Light Probes get baked when calling LightProbes.Tetrahedralize
- Shadows flicker and cause visual artifacts when modifying a GameObject's bounds using Swizzle (Y Mask) and Sine Time nodes
- [WebGL] Frame rate drops by 5-20 fps when moving cursor or touch input in the Player
- Light bleeds when using box shaped spotlight with specific Emission Range values
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.