Gamepad joystick movement question

To explain a little, phase transitions on an action are primarily driven from interactions. If there's no interaction on an action, "performed" is the only thing that you will see. The action will simply trigger "performed" every time a bound control changes state (meaning also when it goes back to its default value) and then will go back to waiting. If one or more interactions are present, then the phase transitions are entirely driven by them.

I don't think we have an interaction out-of-box ATM that does exactly what you want for the stick. The ones that are in there so far are pretty much all focused on button interactions and mostly won't have very useful behavior on a stick.

The Press interaction indeed only triggers Performed. PressAndRelease triggers Started and Performed.

One way would be to do this manually in the performed callback by storing the last value. If the last value is non-zero and the current value is zero, the stick has gone back to its deadzone.

Ideally, there should be an interaction for this. Will have a look.

 

You can do a read value in the callback like so:

Code (CSharp):

1. myAction.performed +=
2.     ctx =>
3.     {
4.         var value = ctx.ReadValue<Vector2>();
5.         //...
6.     }

This will read a 2D vector from the control that triggered the action. Will also work if, say, you've bound a WASD key combination to the move.

I'm looking at adding a "StickInteraction" that would give you a "started" when the stick goes out of its deadzone, a "performed" while the stick moves around outside the deadzone, and a "cancelled" when the stick moves back into the deadzone. Something like that.

 

Took a stab at it here: https://github.com/Unity-Technologies/InputSystem/commit/430b36e2f603cf32ed6cce6ca1b35003264dbe92. Putting this on a stick binding should give you the behavior of started/performed/cancelled when the user starts moving the stick and then lets it go.

That's great to hear Especially at this still relatively early point.

The action portion of the system is still pretty rough and has a lot of holes but hopefully within the next 3-4 months, we'll see some great progress there. Other than that, barring any surprise findings, I think the system just needs a lot of stabilization and a couple features here and there (plus of course plenty of docs) and then we should be good to go.