Search Issue Tracker
Fixed
Fixed in 2021.3.36f1, 2022.3.20f1, 2023.2.10f1, 2023.3.0b5
Votes
1
Found in
2021.3.30f1
2022.3.8f1
2023.1.11f1
2023.2.0b7
2023.3.0a3
Issue ID
UUM-48008
Regression
No
[Windows] Context menus can display in incorrect position in triad monitor layout
When using a laptop with a certain scale connected to two external monitors of a different scale in a configuration like this (two external monitors side-by-side with the laptop display below them situated halfway between):
display2 | display3
display1
*and* the scale of the laptop display is a different scale than the external displays, context menus on display2/display3 can show up in the wrong position. Whether the issue reproduces on display2 or display3 seems to depend on which display *logically* comes first when Windows enumerates displays.
My repro:
MacBook Pro Intel
Display 1: Internal Retina display @ 250% scaling
Display 2 and 3: 4k monitors of the same model @150% scaling
# Lay out the monitors with the external monitors side-by-side and the laptop display underneath them halfway
# Open Unity and try both of the following (only one will repro):
## Put Unity in monitor 2 with hierarchy in the *right pane* and right-click on the hierarchy view close the the *right edge* of the display
## Put Unity in monitor 3 with hierarchy in the *left pane* and right-click on the hierarchy view close to the *left edge* of the display
Result: In one of the two scenarios, the context menu pops on the wrong monitor
Expected: Should pop up wherever the mouse pointer is
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
- “[Worker0] Could not generate preview image“ error when opening macOS native plugin in the Inspector with Architecture to build for set to ARM 64-bit
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
- [Rendering Debugger] [NewInputSystem] Debug Overlays in Play mode throws InvalidOperationException when using New Input System
Resolution Note (fix version 2023.2.10f1):
Verified fixes, looks good!
Resolution Note (fix version 2021.3.36f1):
Looks good!