Search Issue Tracker
Fixed in 1.5.0
Votes
0
Found in [Package]
1.4.4
Issue ID
ISXB-373
Regression
No
"NotImplementedException" and "Cannot find binding" errors are thrown when binding Usage to Actions
Reproduction steps:
- Open the attached (UnityInputSystemSamples.zip) project
- Open the “Assets/Samples/Input System/1.4.4/Rebinding UI/RebindingUiSampleScene.unity” Scene
- Open the “Assets/Samples/Input System/1.4.4/Rebinding UI/RebindUISampleActions.inputactions” Input Action Asset
- Delete all bindings in the “Interact” Action dropdown menu
- Select the “+” button near the Interact Action and press “Add Binding”
- Change the Binding’s Path to “Submit” (Usages > Submit) and press “Save Asset” in the window’s toolbar
- Select the “InteractRebind” GameObject in the Hierarchy window (Canvas > Keyboard > InteractRebind)
- Observe the Console
- Enter the Play Mode and unpause the Play Mode
- Press the blank button near the “Interact” label
- Observe the Console
Expected result: No errors are present in the Console, and binding works as expected
Actual result: “NotImplementedException: Matching usages inside subcontrols instead of at device root” and “Cannot find binding with ID '50a5adae-36bc-4b42-ac08-266d143e2c62' on 'Gameplay/Interact[/Keyboard/enter]'“ errors pop up in the Console
Reproducible with: 1.2.0, 1.3.0, 1.4.4 (2020.3.43f1, 2021.3.16f1, 2022.1.24f1, 2022.2.2f1, 2023.1.0a24),
Reproducible on: Windows 10 (21H2)
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
- “Screen position out of view frustum...” errors are thrown when zooming out in the Scene view after creating UI GameObject
- CurveTexture is not being released when unloading AssetBundle containing a Scene with ColorCurves post-processing component in Global Volume
- Crash on ExtractActiveCasterInfo when navigating the scene view in a project with specific lighting data
- Build Profile name increments when numeric suffix is removed from duplicate Profile name
- "Unrecognized block header in profiler data file, stopping deserialization" error is shown and no more profiler data is recorded when the Player is connected and profiler recording is enabled/disabled few times
Resolution Note:
Fixed in: 1.5.0
Verified with:
2023.2.0a5.435.2856
Revision: trunk e4a766a8b34d
Built: Tue, 28 Feb 2023 02:17:31 GMT