Search Issue Tracker
Postponed means that the issue was either a feature request or something that requires major refactoring on our side. Since that makes the issue not actionable in the close future we choose to close it as Postponed and add it on our internal roadmaps and technical debt pages instead.
Postponed
Votes
4
Found in [Package]
1.3.0
Issue ID
ISXB-122
Regression
No
Custom Input Binding Processor disappearing during and after Play Mode
How to reproduce:
1. Open the attached project (InputProcessorTest.zip)
2. In the Project panel select the "New Controls" asset and press "Edit asset" in the Inspector
3. In the "Input Actions" window in the "Actions" section expand: New Action > One Modifier (If the option is missing press the plus button on the right of the "New Action" entry and add a binding with one modifier)
4. Select the "Binding: <No Binding>" entry
5. In the "Binding Properties" section press the plus on the right side of the "Processors" sub-section title
6. Find the "Binary Cardinal" option in the dropdown
7. Enter playmode
8. Repeat steps 3 to 6 and note the missing "Binary Cardinal" option
Expected result: the custom "Binary Cardinal" processor option always appears in the dropdown
Actual result: the custom "Binary Cardinal" processor option is not present after entering Play Mode
Reproducible with Input System: 1.3.0 (2019.4.38f1, 2020.3.34f1, 2021.3.2f1, 2022.1.0f1, 2022.2.0a12)
Reproducible on Ubuntu 20.04 and Windows 10
Note: the "Binary Cardinal" processor option reappears after recompiling scripts
-
huulong
May 06, 2022 11:11
Note that in my original bug report, I followed instructions in https://docs.unity3d.com/Packages/com.unity.inputsystem@1.0/manual/Processors.html
Forum thread: https://forum.unity.com/threads/new-input-system-processors-not-appearing-always.911015/
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
- [Mobile] Developer Console does not appear when an error is thrown
- [HDRP] Game view renders artifacts when Camera's Component "Post Anti-aliasing" is set to "TAA" and Dynamic Resolution's "Forced Screen Percentage" is changed
- A deactivated Prefab's name color becomes white when a GameObject in the scene is deactivated
- The Game view becomes blank when using Frame Debugger with MSAA and Texture binding enabled in Play Mode
- NullReferenceException is thrown when changing the Inspector preview selection
Resolution Note:
Posteponed for now until we redo the action editor