Search Issue Tracker
Fixed
Fixed in 6000.3.1f1, 6000.4.0a6, 6000.5.0a3
Votes
0
Found in
6000.3.0b9
6000.4.0a4
6000.5.0a2
Issue ID
UUM-127704
Regression
No
Shader build settings un-checking strip toggle does not disable stripping
In the shader build settings there seems to be a bug where enabling stripping (toggling the strip checkbox for a keyword declaration override and toggling off some keywords under that) does work as expected but then disabling the stripping after that does nothing.
Steps to reproduce:
- Create a keyword declaration override and strip some keywords using it.
- Disable the stripping by toggling off the strip checkbox for that override
- Check the variants
Actual results:
Variants are still stripped.
Expected results:
Variants are created without stripping.
Reproducible with versions:
Not reproducible with versions:
Can’t test with versions:
Tested on (OS):
Notes:
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note (fix version 6000.5.0a3):
Removed the "strip keywords" checkbox which removes this issue too.
Resolution Note (fix version 6000.4.0a6):
Removed the "strip keywords" checkbox which removes this issue too.
Resolution Note (fix version 6000.3.1f1):
Removed the "strip keywords" checkbox which removes this issue too.