Search Issue Tracker
By Design
Votes
0
Found in
2021.3.50f1
2022.3.60f1
6000.0.43f1
6000.1.0b11
6000.2.0a7
Issue ID
UUM-100278
Regression
No
Keywords on Material Variants aren't automatically saved when changed on original Material through Shader Graph
How to reproduce:
1. Open the attached “IN-96240_Material Keyword Reproduction” project
2. Open the Project window, navigate to the “Shader” ShaderGraph and open it
3. Navigate to the “Shader” ShaderGraph window and duplicate the existing Boolean keyword
4. Drag the duplicated Boolean keyboard to ShaderGraph Blackboard
5. Connect the duplicated Boolean keyword’s “Out(1)” node to the “Tangent(3)”, “Normal(3)”, or “Position(3)” output in the Vertex Output
6. Ensure no GameObjects are selected in the Inspector, then save the shader file
7. Go to File > Save Project to save the changes
8. Open the corresponding Mat.mat file in a text editor and observe the population of {{m_ValidKeywords:}} list
Expected Results: The Mat.mat file is updated immediately after saving the “Shader” ShaderGraph
Actual Results: The Mat.mat file is not updated immediately after saving the “Shader“ ShaderGraph
Reproducible with: 2021.3.50f1, 2022.1.0a1, 2022.3.60f1, 6000.0.43f1, 6000.1.0b11, 6000.2.0a7
Reproducible on: MacOS 15.3.1 (M1 Max)
Not reproducible on: No other environments tested
Workarounds: If you go to the project again and navigate to Scene View and then save the project, you can populate the {{m_ValidKeywords:}} with duplicate Boolean Keyboard
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
- "Create Empty Child" Option Creates Root Object When No Parent Is Selected
- Freeze/Crash when entering Play Mode in a specific project
- Lack of documentation regarding VFX Ray Tracing support
- Shader properties do not appear on the GameObject when switching ShaderGraphs during runtime in the Player
- Multiple '-' symbols are allowed to appear in a row when inputting '.' into a non-decimal numeric field
Resolution Note:
The material serialization state does not fully reflect the keyword feature capabilities of the entire shader.
Unless this issue results in incorrect material/shader behavior or other issues, I'm closing this As Designed, as there doesn't appear to be any unexpected behavior.