Modify Control Usages

This docs page makes reference to 'Control Usages' and I'd like to modify / create my own. Most notably, I'd like to remove certain controls from a usage.

I believe that these are causing control conflicts. I've bound the space bar to a jump control, however with a specific combination of inputs (two arrows + space), the jump control is not triggered. This combination does work is the jump control is replaced with something else (i.e. z). I can confirm that this is not an issue with my code; no triggers are coming in at all. Space is probably conflicting with the default UI controls, which use the Submit usage.

 

Or it could just be a ghosting problem if you have a "basic" keyboard ?

 

Could you explain what you mean by that, and how I might fix it?

 

https://www.maketecheasier.com/what-is-keyboard-ghosting/

 

Just looked at the input debugger, and the space bar input is not being registered. The space bar is not detected when the left and up arrows are held, but is being detected when the right and up arrows are held (weird). The bindings are standard as far as I know, I've got one control for Jump, bound to z and space (both without processors or interactions). This weird behaviour only arises when using space, and the z control works as expected.

 

I have the reverse issue where Space does not Submit in my menu, only Enter does. I want to make Space also bound to the Submit usage. However, the UI usages in the Input Actions Asset don't behave like other actions. Adding the Space input below "Submit [Any]" doesn't make Space submit, like Enter.

I've read the doc and tried a few things, but it led to nowhere (the example with Player1 seems very hard to adapt; Player1 is a tag to indicate a controller, but they use it as a usage? What do I do with the creation action object?)

Could you give a complete code snippet to:

1. Add Space as alternative input to the Submit "usage" action in menus (what I need)
2. Remove Enter from the list of Submit inputs (or Space if it has been added) (may be useful for users with a similar issue as the OP, where the existing input conflicts with game input)

Thank you

 

Oops, I was still pointing to the Default Input Actions on my Event System's Input System UI Input Module, instead of the custom Input Actions asset I created.

Using the custom asset, and adding Space as alternative binding to Submit, makes it work as expected.

 

If I understand this correctly, if for example, the southButton has the usage Submit there is no way to change that in a script.

In other words, I can rebind the keys for actions but the UI will not respect the rebinding?

Yes?

In an example if I have these actions:
N
S

And these bindings:
N -> <Gamepad>/southButton
S -> <Gamepad>/northButton

Even thought the N and S actions fire correctly the UI will still be using the south button on the gamepad as Submit.

If so how can I get the UI to respect rebinding such that pressing the north button on the gamepad is the submit button?