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
- [UWP] Mouse movement re-triggers stale <Mouse>/scroll value after the scroll wheel is used once
- "Shutdown worker was forced killed because it kept running. Worker ..." errors are thrown after building a blank HDRP project
- [UI Toolkit] USS materials in AssetBundles break due to InstanceID referencing a material that no longer exists when a Scene is loaded through Addressables for the second time
- Help button leads to a missing documentation page when clicked on a Font Import Settings in the Inspector
- TextMeshPro Text Component reads bottom-to-top instead of top-to-bottom when using RTL Editor
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.