Search Issue Tracker
Won't Fix
Won't Fix in 6000.0.X
Votes
0
Found in
2022.3.49f1
6000.0.23f1
Issue ID
UUM-83773
Regression
No
Greyed out Icon for Tool Context is misaligned in the Tools Overlay in the URP 3D Sample Template
Steps to reproduce:
- Create a 3D URP Sample Project
- Open Scene View and select a GameObject in the Hierarchy
- In Scene View, in the Tools Overlay observe the Top Tool Icon (The Cube) that explains what Tool Context is
Actual results: Icon has a margin of 1 on its right side, Icon is misaligned with other Icons
Expected results: No misalignment or icons is not shown to users
Reproducible with versions: 2022.3.49f1, 6000.0.23f1
Can’t test with versions: 2021.3.44f1 (No Sample Project)
Tested on (OS): Windows 11, Ubuntu 24.04
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
- Required SpriteMask class (ID 331) is stripped when "Strip Engine Code" is enabled
- “Maximized serialized file backup not found” error is thrown when minimizing a window in a newly opened project
- Build stack trace contains invalid lines when building with IL2CPP using scripts with delegates containing generic types in the signature
- Entities Systems window has a “Show Full Player Loop” dropdown which does nothing when clicked after enabling “Show Full Player Loop”
- Entities Hierarchy Search “Show/Hide” button’s Lens Icon is blurry when the Editor is on an external monitor
Resolution Note:
Thank you for bringing this issue to our attention. Unfortunately, after careful consideration, we will not be addressing your issue now, as we are committed to resolving other higher-priority issues. Our priority levels are determined by factors such as the severity and frequency of an issue and the number of users affected by it. However, we know each case is different, so please continue to log any issues you find and provide any general feedback on our roadmap page to help us prioritize.
Resolution Note (6000.0.X):
Thank you for bringing this issue to our attention. Unfortunately, after careful consideration, we will not be addressing your issue now, as we are committed to resolving other higher-priority issues. Our priority levels are determined by factors such as the severity and frequency of an issue and the number of users affected by it. However, we know each case is different, so please continue to log any issues you find and provide any general feedback on our roadmap page to help us prioritize.