Search Issue Tracker
Fixed in 1.1-pre.6
Votes
0
Found in [Package]
2019.4
2019.4.13f1
2020.1
2020.2
2021.1
Issue ID
1292754
Regression
No
MultiTapDelayTime does not influence MaxTapSpacing in Input Action assets
How to reproduce:
1. Open attached project ".zip"
2. Open Input Action Asset "prototype1" (in "Settings" folder)
3. Expand "RotateDouble" InputAction
4. Click on "Open Input Settings"
5. Change the value of "MultiTapDelayTime"
6. Hover the mouse pointer over Input Actions Window to update the window
Expected result: "MultiTapDelayTime" influences "MaxTapSpacing"
Actual result: "MultiTapDelayTime" does not influence "MaxTapSpacing"
Reproducible with (Input System 1.0.1) - 2019.4.15f1, 2020.1.17f1, 2020.2.0b14, 2021.1.0a10
Could not test with - 2018.4 (no Input System package functionality)
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
- [Web] VideoPlayer.frameReady event fires only once in a video when the Player Graphics API is set to WebGPU
- Hierarchy V2 Reset Columns leaves empty space and does not resize to fit when removing the columns
- Unexpected changes are made to the main asset when cloning and adding root objects with AddObjectToAsset in AssetPostprocessor
- [RenderGraph] Outputs from camera stack override each other when using OpenGLES3 with a custom renderer feature
- An "RefreshInternalV2 is called before InitialRefresh" error is thrown when opening a project where a build profile with Player settings added is selected
Resolution Note (fix version 1.1-pre.6):
Fixed in 1.1-pre.6