Search Issue Tracker
Fixed
Fixed in 6000.5.0a6
Won't Fix in 6000.4.X
Votes
0
Found in
6000.4.0b4
6000.5.0a4
Issue ID
UUM-132187
Regression
No
Tool Tips are redrawn with every cursor movement when moving it above Converter Labels in the Render Pipeline Converter
Steps to reproduce:
- Open any URP Project
- Open the Render Pipeline Converter (Window > Rendering > Render Pipeline Converter)
- Hover cursor over any of the Converter Labels
- Move the cursor horizontally along the label and observe the Tool Tip
Actual results: Tool Tips are redrawn at the cursors location with each movement making them flicker
Expected results: Tool Tips are drawn a single time until the cursor leaves the label like everywhere else in the Editor
Reproducible with versions: 6000.4.0a3, 6000.4.0b4, 6000.5.0a4
Not reproducible with versions: 6000.0.66f1, 6000.2.15f1, 6000.3.4f1, 6000.4.0a2
Tested on (OS): Windows 11
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:
Fixed in 6000.5.0a6
Resolution Note (fix version 6000.5.0a6):
Fixed in 6000.5.0a6
Resolution Note (6000.4.X):
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.