Search Issue Tracker
Fixed
Fixed in 2022.3.61f1, 6000.0.46f1, 6000.1.0b13, 6000.2.0a8
Votes
3
Found in
2020.3.0f1
2021.3.0f1
2022.3.0f1
6000.0.0f1
Issue ID
UUM-99077
Regression
Yes
Touch Input is not registered correctly when using multiple displays
How to reproduce:
1. Make sure that 2 displays are arranged side to side
2. Make sure to have a touchscreen display as the second (non-primary) display
3. Open the “IN-83006_repro“ project
4. Select FIle → Build and Run
5. In player touch the secondary display
Expected result: The display index is shown as 1
Actual result: The display index is shown as 0
Reproducible with: 1.7.0 (2021.3.43f1, 2022.3.44f1), 1.9.0 (6000.0.17f1), 1.10.0 (6000.0.17f1)
Reproducible on: Windows 10
Not reproducible on: No other environment tested
Notes:
- Should not be reproducible in 2019.4. 40f1
- Could not find FAV due to the issues when upgrading from 2019.4.40f1 version
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
- Crash on JobQueue::HasJobGroupIDCompleted when closing the Editor while in Play mode on a specific project
- In "Preferences" section the “SpriteShape” menu item, the details page title “SpriteShape”, and “ControlPoint” entries are displayed as code strings rather than formatted UI strings
- Errors thrown constantly when Virtual Offset Debug is enabled and lighting was baked on AMD machine
- Persistent Memory Leak when reloading domain and using Distance-based Ghost Importance
- HDRP project doesn't render in standalone player when using High stripping
Resolution Note (fix version 6000.0.46f1):
Touch positions now match mouse positions when multiple displays and windows are concerned (Windows Operating System).
Resolution Note (fix version 2022.3.61f1):
Touch positions now match mouse positions when multiple displays and windows are concerned (Windows Operating System).