Search Issue Tracker
By Design
Votes
0
Found in
2023.1.10f1
2023.2.0b6
Issue ID
UUM-47252
Regression
No
Default shader values are not set for existing materials
Blackboard variables with default values are not set if a material is already created even if that variable was never included in the initial setup of the material
# Create a new shader graph (any type)
# Create a material using this new shader
# Add a new blackboard variable to the shader: blackboard => '+' => any type
# Set the default value. Select the new blackboard var => Graph Inspector => Default
# Select the material created in step 2
Expected result: The default value is applied to the existing material
Actual result: The new value is set to the type's default value- integers 0, colors white, e.t.c
!Unity_bnvDKjGGPb.gif|width=1544,height=773!
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
- The text below Orientation Gizmo does not change when the Scene viewing direction changes
- CPU is overused and the usage cannot be limited for Runtime when the Editor is not rendering anything
- Recorder Texture Sampling does not record Canvas images correctly when the Camera projection is Orthographic
- [HDRP] HDAdditionalLightData.RequestSubShadowMapRendering on directional lights breaks cascade shadows rendering
- Memory leaks when Instantiating Objects with SerializeReference
Resolution Note:
Default value propagation from ShaderGraph to Materials isn't well supported after the material has already been created. This isn't something we will address as a bug in the near term, so I'm closing this out for now. We're aware and are keeping it in mind for any opportunities we have to address it in the future.