Search Issue Tracker
Won't Fix
Votes
0
Found in
2021.3.56f1
2022.3.66f1
6000.0.57f1
6000.2.4f1
6000.3.0b1
Issue ID
UUM-117139
Regression
No
Baked Lightmap ”View” button text is aligned incorrectly
Reproduction steps:
{}{}1. Create a new project
2. Create a 3D GameObject
3. Enable Contribute GI Static status in the Inspector
4. Open Lighting window (Window > Rendering > Lighting)
5. Press “Generate Lighting” button
6. Click on 3D GameObject in the Hierarchy
7. Observe Baked Lightmap “View” button in the Inspector (Mesh Renderer > Lightmapping > Baked Lightmap)
Actual result: “View” text is positioned on the right side of the button
Expected result: “View” text is positioned in the center of the button
Reproducible with: 2021.3.56f1, 2022.3.66f1, 6000.0.57f1, 6000.2.4f1, 6000.3.0b1
Reproduced on: Windows 11, macOS Sequoia 15.4 (M4)
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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
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.