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
- Render Pipeline Converter selected asset counter reports one fewer item when using manual selection
- [Android] [Adreno] [WebGL] A light cookie is not rendered with shader compile error when WebGL build is launched on a device with Adreno GPU
- Rigibody sliding over a flat surface that is made of several GameObjects detects false collisions when Collision Detection is set to "Continuous" or "Continuous Dynamic"
- UI Toolkit Label height is incorrectly calculated when using max-width with percentage value
- Visual Effect Material causes Scene view to update continuously when both Scene and Game views are open, despite "Always Refresh" being disabled
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.