I’m pretty sure this is the default action Unity provides out of the box, how do they intend that you work with this? I haven’t been able to figure out how to differentiate between bindings and use those for different things because the context.ReadValue doesn’t seem to allow me to point to a specific binding. I did have luck completely bypassing the callback param and doing two seperate Gamepad.current.rightStick / lightStick, but I want to use the provided callback so I have access to rebinding etc later.
Any tips? Currently I just have one action per action, the above image looks to me like two actions in one, so you could XZ move the character and rotate the camera with the other stick. I can’t figure out how to do with though with context.readvalue, and haven’t seen this done in any samples provided by unity either. I did look at their warriors sample project, and they have a InputProvider component on their Cinemachine FreeLook camera, but that just hooks it up automagically and I want to know how it works, or how they intend for us to do it typically without cinemachine’s help.
No. The input system is a layer of abstraction between the action and the inputs that correspond to it. Namely, it means you don’t need to care about the specific inputs, and only have to care about the action they handle.
So an InputAction refers to one action, and can (and often will) have multiple inputs that trigger it. You should only care about registering to the actions, and not care about the individual buttons.
I’m fairly certain you’re looking at the UI action map of the default input action map asset. Which is, unsurprisingly, set up for simple UI navigation, not game-play.
@spiney199 thanks! Yes likely, I took their LStick & RStick under one navigation action as twin stick, not two options to do the same thing, navigate through menus… but I guess that is fine for demonstration purposes on their end.
