Search Issue Tracker
Fixed in 1.1.0-preview.2
Votes
0
Found in [Package]
0.9.1-preview, 1.0.0-preview.3
Issue ID
1207550
Regression
No
[Input System] Action can only be triggered by one of the Action Maps when Action name is identical
Reproduction steps:
1. Open user's attached project "InputSystemBug2" and scene "SceneWithControlScheme"
2. Enter Play Mode
3. Press the Space key
4. Switch to the second Action Map by pressing 2
5. Press Space again
Expected result: Both Action Maps trigger "Jump" Action
Actual result: "Jump" Action is only triggered by the first Action Map
Reproducible with: 2019.2.19f1, 2019.3.0f5, 2020.1.0a20
Could not test with: 2017.4.36f1 (no Package Manager), 2018.4.16f1 (errors)
Reproducible with package versions: 0.9.1-preview, 1.0.0-preview.3
Could not test with package versions: 0.9.0-preview (errors)
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
- NullReferenceExceptions are being thrown when saving a ScriptableObject with an array of a type with a CustomPropertyDrawer that uses TrackPropertyValue
- Applied velocity is inconsistent when using Rigidbody AddForce() with ForceMode.VelocityChange
- Crash on AudioUtil_CUSTOM_HasAudioCallback when exiting Play Mode while the Inspector is displaying a GameObject with an empty script attached
- Scroll offset is framerate-dependent when scrolling with velocity in the Device Simulator
- "Object.FindObjectsOfType<T>() is obsolete" warning is thrown when using "Transitions Plus" asset
Resolution Note (fix version 1.1.0-preview.2):
Addressed by https://github.com/Unity-Technologies/InputSystem/pull/1222.
Fixed in 1.1.0-preview.2 that is available in 2019.4 and above.