Search Issue Tracker
Won't Fix
Won't Fix in 1.5.X
Votes
0
Found in [Package]
1.5.0
1.5.1
Issue ID
ISXB-460
Regression
No
EnhancedTouch.Touch.activeTouches Method displays incorrect display index value when using more than one touch-screen monitor
How to reproduce:
1. Open the “IncorrectTouchDisplayIndex” Project
2. Open the “SampleScene”
3. Build And Run
4. In Player, on two touch-screen displays, simultaneously touch the Player viewport
Expected result: the Display Index is different for each monitor
Actual result: the Display Index is the same for all monitors
Reproduced with: 1.5.0 (2020.3.47f1), 1.5.1 (2020.3.47f1, 2021.3.23f1, 2022.2.16f1, 2023.1.0b13, 2023.2.0a11)
Could not test with: 1.1.1-1.4.4 (2020.3.47f1) (TouchControl does not contain a definition for ‘displayIndex’)
Reproduced on: Windows 11
Note: Also reproducible in the editor
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
- Redoing creation of Sub Scenes and Cube GameObjects in Hierarchy throws “Assertion failed on expression: 'targetScene != nullptr’” error in Console window
- Selecting “New Sub Scene” after assigning “New Scene” in Sub Scene Script Component throws “Destroying GameObjects immediately is not permitted” in the Console window
- Group Selection title text size is smaller in renaming than the actual font size
- Rich Text is not correctly highlighted when searching through Debug Logs in the Console window
- Shader warning in 'Hidden/Core/DebugOccluder' thrown after building High Definition 3D Sample Template
Resolution Note:
There are no fixes planned for this Bug
Resolution Note (1.5.X):
There are no fixes planned for this Bug