Search Issue Tracker
Fixed
Fixed in 6000.3.4f1, 6000.4.0b3, 6000.5.0a4
Votes
0
Found in
6000.3.1f1
6000.4.0b1
6000.5.0a3
Issue ID
UUM-129553
Regression
No
Entering the double-space between characters in the Shader Build Settings creates the empty keywords
How to reproduce:
1. Create a new Unity project
2. Go to Edit -> Project Settings -> Graphics -> Shader Build Settings
3. Add an item under the "Keyword Declaration Overrides"
4. Enter any character, double-space, and another character
5. Expand the keywords list and observe the results
Expected results: Only two keywords are on the list
Actual results: There are three keywords on the list, one of which is empty
Reproducible with: 6000.3.1f1, 6000.4.0b1, 6000.5.0a3
Can't test with: 6000.0.64f1, 6000.2.15f1, 6000.3.0f1, 6000.4.0a5 (No expandable list)
Reproducible on: Windows 11 Pro
Not reproducible on: No other environment tested
Note: Empty keywords are not removed when deleting everything from the field, list item should be readded
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:
Shaders: Fixed shader keyword declaration override UI in shader build settings getting confused by multiple whitespaces.
Resolution Note (fix version 6000.5.0a4):
Shaders: Fixed shader keyword declaration override UI in shader build settings getting confused by multiple whitespaces.
Resolution Note (fix version 6000.3.4f1):
Fixed in 6000.3.4f1