Search Issue Tracker
Won't Fix
Won't Fix in 6000.0.X
Votes
0
Found in
6000.0.68f1
Issue ID
UUM-134362
Regression
No
Terrain Component and Overlay Text Rendering is broken when using Bitmap Text Rendering Mode
Steps to reproduce:
- Open any Project
- Switch the Preference for "Editor Default Text Rendering Mode" in the General Tab of the Preferences Window to "Bitmap"
- Create a Terrain Game Object in a Scene and select it
- Observe the Terrain Overlays in Scene View
- Observe the Buttons under the Terrain Component in the Inspector
Actual results: Button Text is not rendered correctly in Terrain Overlays and Terrain Component in the Inspector when using Bitmap Rendering of Text in the Editor
Expected results: Both Rendering options render text correctly
Reproducible with versions: 6000.0.1f1, 6000.0.68f1
Not reproducible with versions: 6000.0.0f1 (No Text Rendering Mode Preferences)
Fixed in: 6000.3.9f1, 6000.4.0b9, 6000.5.0a7
Tested on (OS): Windows 11
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
- Play Mode Scenario selection/highlight is too long and out of its bounds when the Play Mode Scenario window is opened after maximizing
- Duplicated groups and incorrect grouping in UI Builder when using UxmlElementAttribute: libraryPath
- Asset name is not shown in the Undo History window when a sprite is modified
- Moving a Tab to a floating window fails when floating windows are docked next to each other
- Crash on UNITY_FT_Render_Glyph_Internal when Generating Font Atlas in the Font Asset Creator Window
Resolution Note:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.
Resolution Note (6000.0.X):
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.