Search Issue Tracker
By Design
Votes
1
Found in [Package]
1.6.3
1.7.0
1.8.0-pre.2
Issue ID
ISXB-712
Regression
No
Two separate Input Actions triggered in separate Action Maps when another similar but Composite Binding exists
Reproduction steps:
1. Open the “ReproProject“ project
2. Open the “Assets/InputTest/InputTestScene“ scene
3. Enter Play Mode
4. Press the “Q“ button on the keyboard
5. Observe the Console Window
Expected result: “Received action trigger for Player/QBindingInPlayerMap“ and “changed action map to UI“ messages are seen in the Console Window
Actual result: “Received action trigger for Player/QBindingInPlayerMap“, “changed action map to UI“, and “Received action trigger for UI/QBindingInUIMap“ messages are seen in the Console Window
Reproducible with: 1.6.3, 1.7.0, 1.8.0-pre.2 (2021.3.33f1, 2022.3.15f1, 2023.2.4f1, 2023.3.0a18)
Reproducible on: Windows 11 Pro (22H2)
Not reproducible on: No other environment tested
Note: Changing the Binding Path from “AnotherBindingWithQPlusModifier“ Action in the “UI“ Action Map to a different button, or deleting it from the “Assets/InputTest/PlayerControls“ fixes the issue.
-
jlfreund
Dec 16, 2024 05:50
I have the same problem and was wondering why this was closed as "by design"?
I can understand if there were 2 action maps active before the input was given then both action maps consuming that input would be called. But in this case, there was only 1 action map active at the time of input, but somehow, when that action enabled a second action map, the input triggered new action map as well.
In my case, adding any breakpoints along that path would prevent the second action map from being called.
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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Resolution Note:
Currently, actions on one action map don't prevent it firing in another action map
There is some documentation here under the "Multiple input sequences" section:
https://docs.unity3d.com/Packages/com.unity.inputsystem@1.7/manual/ActionBindings.html#conflicting-inputs
The mechanism described here only applies to Actions that are part of the same InputActionMap or InputActionAsset.