Search Issue Tracker
Fixed
Fixed in 1.8.0
Votes
0
Found in [Package]
1.8.0-pre.2
Issue ID
ISXB-769
Regression
Yes
Actions with Control Type "Any" lose the ability to add Positive\Negative Bindings when Control Type is switched to "Axis" and then back to "Any"
How to reproduce:
1. Open the attached "inputsystem_add_binding_issue" project
2. Open the "example" Input Actions Asset from the Assets folder
3. Right-click the “test” Action and verify that “Add Positive\Negative Binding” is a selectable option
4. Select the Control Type dropdown menu and select “Axis” (or any other, as the option selected here likely does not matter)
5. Select the Control Type dropdown menu again, and set it back to “Any”
6. Right-click the “test” Action
Expected result: The “Add Positive/Negative Binding” option is still available
Actual result: The “Add Positive/Negative Binding” option does not appear
Reproducible in: 1.8.0-pre.2(2022.3.18f1, 2023.2.8f1, 2023.3.0b4)
Not reproducible in: 1.7.0, 1.8.0-pre.1, 1.8.0-pre.2(2021.3.34f1)
Reproducible on: Windows 11, macOS 13.6.3 (Intel)
Not reproducible on: No other environments tested
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Screen Space Ambient Occlusion is ignored when toggling "Post Processing" visibility in the Scene window overlay
- “RenderTexture.Create failed: requested size is too large.” errors are thrown and the Inspector window is black when selecting a CubemapArray texture
- Crash on AMDUnityPlugin.DLL in specific built project when using FSR2 upscaler
- RenderObjects does not have any Depth texture bound when Event is set to AfterRenderingPostProcessing
- Prefab override popup is cropped/positioned incorrectly when more than one display is used and a higher display Scale is set
Add comment