Search Issue Tracker
Fixed
Votes
0
Found in
2020.3.48f1
2021.3.32f1
2022.3.12f1
2023.2.0b15
2023.3.0a12
Issue ID
UUM-14038
Regression
No
Touch input generates mouse input when the build is in windowed mode
Reproduction steps:
1. Open the user’s attached project
2. Open “Assets/TouchTestScene.unity”
3. Click File > Build Settings > Add Open Scenes
4. Click Build
5. Open “DesktopTouchTest.exe”
6. Make the window fullscreen and touch & move everywhere
7. Observe the “Mouse 0” input and notice it stays false
8. Make the window width 1/4 the size (press alt+Enter to leave fullscreen) and touch everywhere
9. Observe the “Mouse 0” input becomes True when moving the finger
Expected result: “Mouse 0” input is False
Actual result: “Mouse 0” input is True
Reproducible with: 1.3.0, 1.4.1, 1.4.2 (2020.3.39f1, 2021.3.8f1, 2022.1.14f1), 1.4.2 (2022.2.0b6, 2023.1.0a9), 1.6.1 (2021.3.46, 2023.2a19)
Reproducible on: Windows 10 Pro 21H2
Notes:
1. Press Alt + Enter, to change build from fullscreen to windowed mode
2. Also reproducible with Legacy Input System
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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- Crash with “Fatal Error! The file ‘MemoryStream’ is corrupted!” when adding a large number in Font Character Rects Size field
Resolution Note:
Fixed by another internal issue: UUM-92144: Input System: Windows Touchscreen sends mouse events