Search Issue Tracker
Duplicate
Votes
0
Found in
2019.2
2019.2.3f1
2020.1
Issue ID
1182325
Regression
No
Input.GetTouch() is not detected on non-Primary Displays
Touch class, returned by Input.GetTouch() doesn't return touches performed on non-primary display (Windows > Settings > System > Display > Make this main display).
Setup:
have at least 2 touch-capable monitors. In this case, HP Omen 15 Laptop with touch screen and Dell P2418HT monitor was used.
Steps:
1. Open user's attached project ("augmentedretail2.zip")
2. Build and Run
3. Try to touch different screens
Expected: touches are registered on both screens and coordinates appear on the top left corner.
Actual: touch is detected only on screen which is set as Primary Display in Windows Settings
Reproduced with: 2019.2.4f1, 2020.1.0a11.
Not reproduced with: 2017.4.0f1 (due to errors in the Console).
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
- Previous model to world matrix is not correctly set for ASW
- More calls are made to GC.Alloc in an HDRP Sample Template when compared to the 2022.3 stream
- Generating Light Probe lighting returns inconsistent results on a specific mesh
- Two Warnings appear for every Soft Delete Operation when Deleting Sub Assets in the Project Browser
- “Item m_LightProbeSystem not found” warning is thrown when pressing the “Open” button multiple times in the Adaptive Probe Volume component warning
This is a duplicate of issue #1120839