Search Issue Tracker
Won't Fix
Votes
0
Found in
5.3.1
Issue ID
UUM-132369
Regression
No
"Brush Attributes" menus have no padding
How to reproduce:
1. Create a new Unity project
2. In the Hierarchy, right-click -> 3D Object -> Terrain
3. Install the "Terrain Tools" package (Window -> Package Management -> Unity Registry)
4. With the Terrain GameObject selected, make sure to have the "Brush Attributes" Overlay in the Scen view
5. Click the "arrow" button near the "Opacity" Attribute and observe the menu
Expected results: The menus have a padding from above
Actual results: The menus have no padding
Reproducible with: 5.3.1 (6000.0.64f1, 6000.3.3f1, 6000.4.0b5, 6000.5.0a5)
Reproducible on: macOS Tahoe 26 (M1)
Not reproducible on: No other environment tested
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
- Texture generator reference image fails despite valid size
- Agent mode can enter infinite execution loop
- AI Gateway responses contain duplicated sentences
- Texture 2D asset is created when promoting a generated Cubemap to a new asset
- Unable to copy multiple paragraphs from Assistant responses
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:
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.