Search Issue Tracker
Fixed in 2021.1.X
Fixed in 2020.3.X
Votes
0
Found in
Issue ID
1176077
Regression
No
[ShaderGraph] Enum Keywords: Number of displayed enum options on material doesn't update
2020.1.0a1, sg/keywords (soon to be in master) of 8/12/19
Basically when you change the number of keyword options in a SG using a enum keyword and save, the material still contains the # of keywords before. Even if you create a new material after the save.
Repro:
1) Create a blank SG
2) Create an Enum keyword
3) Change the number of the entries in the keyword to 4 - 8
4) Save the SG
5) Right click on the SG > Create Material
> It will have the right # of options in the drop down menu
6) Go back to the SG, and delete or add some enteries, then save again
> Still has the dropdown options from before
Reproduces even if you create a new material!
Bonus:
It should also be noted that when you first add a new Boolean keyword to a shader that's already in use in the scene, and you set the default to set (after making sure the reference ends with _ON), it will frequently not have the keyword set right. Fixing this requires set & setting the keyword in the material. This will reproduce again if you change the keyword's reference.
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
- "Debug Assertion Failed!" error when launching Windows Dedicated Server Player with Script Debugging enabled
- [Cinematic Studio][3D HDRP] Shader warnings thrown in the Console window when creating a new project with Cinematic Studio template
- Autoplay is triggered on Audio Assets when changing Asset Bundle tags
- Inspector Asset Bundle section has no indication for Variants, AssetBundle is written without a space, and Variant dropdown menu is available without setting the Asset Bundle first
- Graphics.DrawProceduralIndirect and Graphics.DrawProceduralNow silently dropped on DX12
Resolution Note (fix version 2021.1):
Fixed in: 2021.1.18f1 (11.0.0)
Resolution Note (fix version 2020.3):
Fixed in: 2020.3.18f1