Search Issue Tracker
Fixed
Fixed in 1.12.0, 7000.0.0
Votes
1
Found in [Package]
1.11.2
Issue ID
ISXB-1258
Regression
Yes
[Input System] The Editor freezes when pressing 'A' on the controller and using touch input at the same time
Reproduction steps:
1. Open the “IN-89900” project
2. Open the “SampleScene” scene
3. Connect the controller
4. Go to the Simulator view
5. Enter Play Mode
6. Press the button in the middle of the screen with a mouse and a controller’s 'A' button at the same time
7. Observe the Editor
Expected result: The button is pressed
Actual result: The Editor freezes and never recovers
Reproducible with: 1.11.2 (2021.3.45f1, 2022.3.54f1, 6000.0.30f1, 6000.1.0a7)
Not reproducible with: 1.10.0, 1.11.1 (2022.3.54f1)
Testing environment: Windows 11 Pro
Not reproduced on: Windows Standalone (does not simulate touch input)
Notes:
- Also reproducible with Nintendo Switch Player (by user)
- Sometimes the Controller is not required (it freezes when pressing the button with mouse)
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
- Decal Projectors of Prefabs appear less faded in Scene view
- Default Preset application and Reset() method execution order is different when adding a Component via the Inspector versus calling Reset via the Component context menu
- Scene view is not outputting HDR when the "Use HDR Display Output" option is enabled, DX12 is selected as the Graphics API, and URP/HDRP is in use
- Sprite Atlas results in suboptimal packing even when "Allow Rotation" is enabled
- References placed in a UnityEvent change to the same reference when multi-selecting their GameObjects
Resolution Note (fix version 7000.0.0):
Removal of pointers was assumed to always succeed. This assumption meant we were always deprecating a loop index ultimately leading to an infinite loop (when using touch input).
Resolution Note (fix version 1.12.0):
Fixed an editor/player hang in `InputSystemUIInputModule` due to an infinite loop. This was caused by the assumption that `RemovePointerAtIndex` would _always_ successfully remove the pointer, which is not the case with touch based pointers.