Search Issue Tracker
Fixed
Fixed in 2022.2.22f1, 2022.3.16f1, 2023.1.0a25, 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
- Mono Windows Builds don't produce full log callstacks when generating logs
- AssetBundles fail to load when running in Built Players for Mobile Devices
- UI elements with text gets bigger and grey when Player window is moved to another screen with different resolution
- System name accepts multiline text but crops it on confirmation, duplicates input, and shrinks the field when empty
- UI element scale and position are wrong in project build when DRS is changed with HDR and Software Dynamic Resolution enabled
Flavelius
Nov 14, 2023 12:00
Same for UI, 2022.3 needs this fix