Search Issue Tracker
Fixed
Fixed in 6000.0.71f1, 6000.3.12f1, 6000.5.0a9, 6000.6.0a1
Votes
1
Found in
6000.0.68f1
6000.3.9f1
6000.4.0b9
6000.5.0a7
Issue ID
UUM-134691
Regression
No
Project Settings Search Highlights misaligned when using Bitmap Text Rendering Mode and Standard Text Generator
Steps to reproduce:
- Open any Project
- Open up the Preferences Window's General Tab
- Set "Editor Default Text Rendering Mode" to "Bitmap"
- If "Editor Text Generator Type" setting is available, make sure it's set to "Standard"
- Open up the Project Settings Window and type any Setting String into the Search Field at the top of the Window
Actual results: Blue selection highlights are misaligned, a searched for character's selection highlight is as wide as 3 characters
Expected results: No misalignment happens when using the different Text Rendering Mode
Reproducible with versions: 6000.0.68f1, 6000.3.9f1, 6000.4.0b9, 6000.5.0a7
Cannot test with versions: 6000.0.0f1 ("Editor Default Text Rendering Mode" is introduced only in 6000.0.1f1)
Tested on (OS): Windows 11, Windows 10
Notes:
- Issue doesn't reproduce on newer versions when "Editor Text Generator Type" is set to "Advanced"
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:
Fixed in 6000.5.0a9
Resolution Note (fix version 6000.6.0a1):
Fixed in 6000.6.0a1
Resolution Note (fix version 6000.5.0a9):
Fixed in 6000.5.0a9
Resolution Note (fix version 6000.3.12f1):
Fixed in 6000.3.12f1
Resolution Note (fix version 6000.0.71f1):
Fixed in 6000.0.71f1