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
- Frame Debugger is not disabled when switching Scenes if the Frame Debugger window is not open during the transition
- Standalone Profiler Targets another Project if a Standalone Profiler was launched in it before when switching between Edit or Play Mode Targets
- Crash on ForwardRenderLoopJob when opening a specific project
- [Android] Memory leak and eventual crash on Snapdragon 8 Gen 1+ devices when a Clear Pass is executed after Framebuffer Fetch
- Crash on EnumerateDisabledKeywordsInVariantsArray or UNITY_XXH32 when rapidly saving ShaderGraph or VFXGraph changes
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.