Search Issue Tracker
By Design
Votes
0
Found in
2018.4
Issue ID
1280119
Regression
No
Material properties are not correctly setup when assigning a ShaderGraph to a newly created material
Repro steps:
- Create a project with HDRP installed
- Create a new material from the project window, note that the Lit.shader will be assigned to this material
- Create a new HDRP Lit ShaderGraph and change some settings like the surface option to transparent for example
- Assign the ShaderGraph to the material
- Notice that even if the graph was set to transparent, the material is not.
Expected result: the material should have taken the properties from the graph instead of keeping its old ones
Actual result: the material doesn't change any of its properties
Note that we can observe this behavior with ShaderGraph but it, in fact, happens with every kind of shader when we assign them to any material.
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
Resolution Note:
postponed to the material instance system