Search Issue Tracker
Won't Fix
Votes
0
Found in
5.3.1
Issue ID
UUM-132375
Regression
No
"Terrain Tools" shortcut conflicts with the Overlays shortcut by default
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, in the Scene view, press the "S"key
5. Observe the results
Expected results: The shortcut doesn't have any conflicts
Actual results: "Shortcut Conflict" pop-up opens
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
- “FMOD failed to set the software format to the custom sample rate…” warnings are thrown as System Sample Rate value is being changed in Audio section of Project Settings window
- VFX Marquee selection does match the visual indicator
- “Invalid AABB aabb” errors are spammed when “Infinity” value is entered in Collider Component fields
- Editor Role does not sync with the MPPM Play Mode Scenario Role when entering Play mode
- Long asset names cause overlap with the “Find” function in search result tabs
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.