RetroPie forum home
    • Recent
    • Tags
    • Popular
    • Home
    • Docs
    • Register
    • Login
    Please do not post a support request without first reading and following the advice in https://retropie.org.uk/forum/topic/3/read-this-first

    Can't make same inputs between USB and GPIO controller

    Scheduled Pinned Locked Moved Help and Support
    inputsfighting gamesgpio controllerretroarch contr
    4 Posts 2 Posters 581 Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • G
      Garell
      last edited by

      Hi,

      I recently setup my 2P arcade cab with a PI4 and GPIONext. In most games/emulators everything works fine.

      My issue is with fighting games like Marvel vs Capcom where you need to make a joystick input + pressing 2 buttons simultaneously. The in game combo isn't triggered while playing with my GPIO controller. But the same inputs work flawlessly with an USB arcade controller.

      As a counter example, a simple shoryuken works on both controllers (joystick input + 1 button).

      Now I'm not sure were to look at, is it an issue from GPIONext ? (haven't found anything on their github about this) Or is it a configuration issue in the Retroarch controller setting ? (tried to modify controller driver there, but most times it breaks the GPIO controller)

      Hopping someone can shed some light on this.

      Cheers !

      1 Reply Last reply Reply Quote 0
      • mituM
        mitu Global Moderator
        last edited by mitu

        Most likely a GPIONext issue. You can easily test if all your inputs are processed with jstest - just run jstest /dev/input/js0 with only the GPIO controller connected and press the neessary buttons/joysticks for the combo(s).

        1 Reply Last reply Reply Quote 0
        • G
          Garell
          last edited by

          Thank you for your quick reply !

          I already did this test, but I didn't see anything unexpected though.

          1 Reply Last reply Reply Quote 0
          • G
            Garell
            last edited by

            Finally found the solution:

            The default configuration of GPIONext is not optimal for those inputs.

            What fixed it:

            gpionext set combo_delay 0 # was 50
            

            Hope it helps someone else !

            1 Reply Last reply Reply Quote 1
            • First post
              Last post

            Contributions to the project are always appreciated, so if you would like to support us with a donation you can do so here.

            Hosting provided by Mythic-Beasts. See the Hosting Information page for more information.