You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Some of my controllers - like OUYA Controller or Razer Kishi - on triggers have assigned 2 actions at once (verified in joy.cpl): axis and button, what is not letting me properly assign buttons in GamepadPhoenix because application sometimes catches button (and then my triggers are working like digital triggers), and sometimes catches negative axis, so my trigger button is always pressed and is "getting unpressed" when I am really pressing it.
I think if undo button would catch every pressed action I would be able to come back to proper button action undoing assignment of negative axis and button press, reaching first action registered - positive axis.
Alternatively I was trying to edit config file as well, and assign proper actions manually, but codes are not readable like it is in SDL mappings (b1,+a1,-a1), so it's not possible to fix mappings in this way. Maybe making these codes more user-friendly would help too resolving my problem.
The text was updated successfully, but these errors were encountered:
Some of my controllers - like OUYA Controller or Razer Kishi - on triggers have assigned 2 actions at once (verified in joy.cpl): axis and button, what is not letting me properly assign buttons in GamepadPhoenix because application sometimes catches button (and then my triggers are working like digital triggers), and sometimes catches negative axis, so my trigger button is always pressed and is "getting unpressed" when I am really pressing it.
I think if undo button would catch every pressed action I would be able to come back to proper button action undoing assignment of negative axis and button press, reaching first action registered - positive axis.
Alternatively I was trying to edit config file as well, and assign proper actions manually, but codes are not readable like it is in SDL mappings (b1,+a1,-a1), so it's not possible to fix mappings in this way. Maybe making these codes more user-friendly would help too resolving my problem.
The text was updated successfully, but these errors were encountered: