

You can link an action to any of these values if you want, for example, so the weapon only shoots a bit late but not so late, let's say, at 0.3. going through 0, until you fully release the trigger and it rests at -1. In your example, once you release the trigger after shooting your weapon, the trigger will decrease its axis from 1 to 0.9, 0.8. Just like a car's accelerator pedal.Īs you press for the first time, and keep pressing further, it will start the linear progression of the axis, -1, -0.9, -0.8.

On the moment you start pressing the trigger, it will become the range -1 to 1. Slog - for pointing out the problem of the 0 start state - Īlmost. Notes included.Īlex Chouls - For confirming what I was suspicious about the loop problem. From here, you can work your way to the solution, the images should be enough for a clear explanation of the logic. So why? Here lies the problem - The triggers are parked at 0 by default. The solution: The Axis range are -1 to 1. The problem: Even though you can get the Axis, how do you solve the acceleration? Why it starts in a already fired state? Microsoft made the Triggers to be sensible, therefore, they're Axis, not Buttons, in order to allow acceleration. So, if you're using playMaker, and the XBOX 360/One Controller is the main input device for your game, and you're wondering why you can't get the Triggers to work, this is for you. When I needed this community to help me, it did it in a blink, time to give back some love : )

Finally got to solve it after intensive research. I've been struggling with this logic problem for 17 hours now in total.
