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
- Texture Import Warnings are obscured by other Terrain Layer options in the Inspector
- Burst Inspector middle divider is jittering when resized with the Burst Inspector window docked
- JsonConvert conversion fails trying to call GetCallbackMethodsForType when [OnDeserialized] is used in a class
- Different text alignment in the column header in Entities "System" window
- Objects with Universal Render Pipeline/Particles/Lit shader are always lit up when changing their Rendering Layer Mask
Resolution Note:
postponed to the material instance system