Having trouble with trigger axis mapping.

This is a READ-ONLY snapshot of the Godot Community Forums when TwistedTwigleg was the owner, which is hosted for archival reasons only. The current Godot Community Forums can be found here.

Some links may point to external websites, including the current Godot Community Forums. These websites are not associated with TwistedTwigleg.

Having trouble with trigger axis mapping.

the_eclectic_dyslexic

I am currently trying to get my game working using a controller, but I am noticing that L2 and R2 are axis events and not button events, and seemingly because of that the function is_action_pressed and is_action_released don't seem to activate when expected.

Is there a way for me to work around this without having to put a wrapper around every single input event to handle the special case that an event is InputEventJoypadMotion instead of a InputEventJoypadButton. I absolutely can just write a special case for every time this occurs, but I would prefer not to if I can get away with it... as the player has the option of remapping events, and I would prefer not to have to effectively create a wrapper for handling InputEvent.is_action_pressed() and InputEvent.is_action_released()

The sort of solution I am hoping for is to register the triggers as buttons instead of axis events, and then just forget about them. Is there a way for me to sneakily do this (maybe when binding the event to an action) and just have godot treat them as button events instead of axis events?

the_eclectic_dyslexic

edit: this sort of works... but it shouldn't be considered a perfect answer as it means you can't use the _input(event: InputEvent) function. To make this properly work, the code must be put inside of _process(), otherwise you will get unusual behaviour (given that the Input Singleton only seems to update once per frame.)

In 3.5 it is possible to simply set the triggers as buttons and there will be no issue. However I am using 4.0 beta (5-16 so far) In the 4.0 beta, it seems that the best option is to do the following...

While InputEvent.is_action_pressed will be called multiple times,
Input.is_action_just_pressed will be called once.

So, instead of

func _input(event):
	if event.is_action_pressed("action_name"):
		do_something()

do the following

func _process():
	if Input.is_action_just_pressed("action_name"):
		do_something()