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
- Crash on ShaderLab::ShaderState::ApplyShaderState when entering Play Mode and calling ShaderWarmup.WarmupShaderFromCollection with a shader that has dynamic_branch
- Crash on operator delete[] when a serializable structure in the System namespace is serialized by a MonoBehaviour
- [macOS] forward and backward mouse buttons are recognized as middle mouse button
- NavMeshModifier.OnEnable/OnDisable gets progressively slower when called repeatedly
- "System.Net.CookieContainer" throws an "ArgumentException" error when using a non-UTF-8 machine locale and hostname
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.