Search Issue Tracker
Fixed in 1.1.0-pre.5
Votes
1
Found in [Package]
1.0.0
Issue ID
1255580
Regression
No
[Input System] Mouse and Touchscreen control schemes are ambiguous when using Touch Simulation in Editor
Reproduction steps:
1. Open the attached project ("case_1255580-TouchSchemes.zip")
2. Open the repro scene ("SampleScene")
3. Enter Play Mode
4. Try clicking around in the Game View
5. Select "Main Camera" GameObject
Expected result: "Touch" is the active Control Scheme and "Clicked" logs are printed in the Console
Actual result: "Keyboard&Mouse" is the active Control Scheme and no logs are printed
Reproducible with: 2019.4.3f1, 2020.1.0b16, 2020.2.0a18
Couldn't test with 2018.4 (minimal required package version is not supported)
Reproducible with package versions: 0.9.0-preview. 1.0.0
Comments (1)
-
H4ppyTurtle
Mar 18, 2021 12:25
I've got the same issue in 2020.3
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note (fix version 1.1.0-pre.5):
Fixed in: 1.1.0-pre.5
Mouse now disabled while touch simulation is active.