Search Issue Tracker
Won't Fix
Won't Fix in 6000.4.X
Votes
0
Found in
6000.0.59f1
6000.2.7f1
6000.3.0b4
6000.4.0a1
Issue ID
UUM-120937
Regression
No
Text overlap and is unreadable in Inspector > Terrain Paint Texture after creating new Terrain Layer
Steps to reproduce:
1. Create new Unity project using Universal 3D Template
2. In Hierarchy window create Terrain GO
3. Make sure Terrain GO is selected
4. In Inspector window > Terrain select "Paint Terrain" mode
5. Change to "Paint Texture"
6. In Terrain Layers press "Edit Terrain Layers..."
7. Press "Create Layers..."
8. Select any Texture to create Layer
9. Select on newly created Layer
10. Observe the "Color Tint" and "Opacity as Density" text in the Inspector window
Actual results: "Color Tint" text is on top of "Texture must have mip maps" warning and "Opacity as Density" text is on top of "Normal Map" text, making it difficult to read
Expected results: Adding new Layers should not create any UI/text issues in the Inspector window
Reproducible with versions: 6000.0.59f1, 6000.2.7f1, 6000.3.0b4, 6000.4.0a1
Tested on (OS): Windows 11, macOS Silicon, Tahoe 26.0 (M1)
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
- Specular lighting visible in a camera with Path Tracing when Preserve specular lighting is disabled in observed material
- Cinemachine package throws CS1061 errors in the Console when installed in a project that has HDRP and URP installed
- Editor.log file size grows rapidly when a scene exceeds the "Maximum Shadow on Screen" limit setting in the HDRP Asset
- Player build freezes after calling Application.Quit() when the scripting backend is set to IL2CPP
- Texture is not applied on a Custom Render Texture when a Cubemap is selected as the texture
Resolution Note:
Thank you for reporting this issue and helping us identify potential areas for improvement. After careful evaluation, we have determined that this bug has a low impact on functionality or user experience and does not currently align with our immediate priorities. We are unable to address this issue at this time as we are focusing our efforts on higher-priority bugs and improvements that affect core functionality. Thank you for your understanding.
Resolution Note (6000.4.X):
Thank you for reporting this issue and helping us identify potential areas for improvement. After careful evaluation, we have determined that this bug has a low impact on functionality or user experience and does not currently align with our immediate priorities. We are unable to address this issue at this time as we are focusing our efforts on higher-priority bugs and improvements that affect core functionality. Thank you for your understanding.