Search Issue Tracker
Fixed in 2022.2.22f1
Fixed in 2022.2.X, 2022.3.X, 2023.1.X, 2023.3.X, 2023.3.0a15
Votes
2
Found in
2020.3.40f1
2021.3.11f1
2022.1.19f1
2022.2.0b8
2023.1.0a12
2023.2.0a1
2023.3.0a3
Issue ID
UUM-16464
Regression
No
[Input System] Collider OnPointerDown event not registering on second display
Steps to reproduce:
1. Open the attached user's project "ColliderMultiMonitorSizeIssue.zip"
2. Go to the Build Settings window and press Build And Run
3. Click on the red square on the first screen
4. Click on the green square on the second screen
Expected result: the green square detects clicks and turns blue momentarily while being clicked
Actual result: the green square does not detect clicks and does not show the blue color
Reproducible on: 2020.3.40f1, 2021.3.11f1, 2022.1.19f1, 2022.2.0b8, 2023.1.0a12
Environment: Windows 10 21H2 & MacOS 12.6
Notes:
-On Windows, when a game has two displays (or more) and the displays have different display resolutions, the camera for one of the non-primary displays will not register collider OnPointer events correctly.
Comments (1)
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
- Play Mode framerate drops significantly when moving the mouse cursor with high polling rate
- Create workspace does not update the Unity Version Control and Branch Explorer windows leading to multiple clicks on “Create workspace” which throws an “already exists” error when Creating a workspace with the Branch Explorer window open
- Default and Result encoding properties have blank dropdowns by default when opening the Unity Version Control Settings
- Crash on "StoredGraphicsBuffer::GetGfxBufferID" when activating VFX via extention of Activation Track in Timeline window
- [Linux] Stack trace file path and line number information is missing when IL2CPP Stacktrace Information is set to "Method Name, File Name, and Line Number"
Flavelius
Nov 14, 2023 12:00
Same for UI, 2022.3 needs this fix