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

    N64 controller ordering woes

    Scheduled Pinned Locked Moved Help and Support
    retropiemupen64pluscontroller
    4 Posts 2 Posters 320 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.
    • stattmoneS
      stattmone
      last edited by

      Hi all, pulling my hair out on this one:
      I want the N64 controller on port 2 to be player 1, for Mupen64plus only.
      I have followed the retropie and mupen64plus instructions, and read all posts i can find on this topic.

      No matter what I try, Mupen64plus STILL loads with input device 0 as player 1.

      Any help/guidance gratefully received 🙏


      Device: Pi 3B+
      retropie version: 4.14.98-v7+ (pre-made SD)
      Power supply: HN-538 5V 3A


      USB Devices:
      /dev/input/js0 - Joystick/button controller (reads as DragonRise)
      /dev/input/js1 - Joystick/button controller (reads as DragonRise)
      /dev/input/js2 - N64 USB controller (reads as SWITCH_CO._LTD)
      also connected:
      USB Hub, with keyboard connected, as well as USB-powered LED strips (not addressable, just power)


      /opt/retropie/config/all: (default controller order, as plugged in to pi)

      ...
      input_player1_joypad_index = "0"
      ...
      input_player2_joypad_index = "1"
      ...
      input_player3_joypad_index = "2"
      ...
      

      --> https://paste.c-net.org/PeeledCheating


      /opt/retropie/config/n64: (configure joypad index 2 to be player one for N64)

      input_player1_joypad_index = "2"
      input_player2_joypad_index = "0"
      input_player3_joypad_index = "1"
      

      --> https://paste.c-net.org/SuspectSinger


      /opt/retropie/configs/all/autoconf.cfg: (hotkeys disabled)

      
      # this file can be used to enable/disable retropie autoconfiguration features
      8bitdo_hack = "0"
      es_swap_a_b = "0"
      disable = "0"
      mupen64plus_audio = "1"
      mupen64plus_compatibility_check = "1"
      mupen64plus_hotkeys = "0"
      mupen64plus_texture_packs = "1"
      
      

      dmesg: https://paste.c-net.org/TanksDeedee


      lsusb

      Bus 001 Device 006: ID 2563:0575
      Bus 001 Device 007: ID 0dc6:3401 Precision Squared Technology Corp.
      Bus 001 Device 004: ID 214b:7250
      Bus 001 Device 008: ID 0079:0006 DragonRise Inc. PC TWIN SHOCK Gamepad
      Bus 001 Device 005: ID 0079:0006 DragonRise Inc. PC TWIN SHOCK Gamepad
      Bus 001 Device 009: ID 0424:7800 Standard Microsystems Corp.
      Bus 001 Device 003: ID 0424:2514 Standard Microsystems Corp. USB 2.0 Hub
      Bus 001 Device 002: ID 0424:2514 Standard Microsystems Corp. USB 2.0 Hub
      Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
      

      ls -l /dev/input/by-path

      lrwxrwxrwx 1 root root 9 Jun 27 14:05 platform-3f980000.usb-usb-0:1.1.2:1.0-event-joystick -> ../event2
      lrwxrwxrwx 1 root root 6 Jun 27 14:05 platform-3f980000.usb-usb-0:1.1.2:1.0-joystick -> ../js1
      lrwxrwxrwx 1 root root 9 Jun 27 14:05 platform-3f980000.usb-usb-0:1.1.3:1.0-event-joystick -> ../event3
      lrwxrwxrwx 1 root root 6 Jun 27 14:05 platform-3f980000.usb-usb-0:1.1.3:1.0-joystick -> ../js2
      lrwxrwxrwx 1 root root 9 Jun 27 14:05 platform-3f980000.usb-usb-0:1.2.2:1.0-event-kbd -> ../event1
      lrwxrwxrwx 1 root root 9 Jun 27 14:05 platform-3f980000.usb-usb-0:1.3:1.0-event-joystick -> ../event0
      lrwxrwxrwx 1 root root 6 Jun 27 14:05 platform-3f980000.usb-usb-0:1.3:1.0-joystick -> ../js0
      
      1 Reply Last reply Reply Quote 0
      • mituM
        mitu Global Moderator
        last edited by

        You haven't mentioned which emulator are you using - the settings you applied are effective only when using a libretro core - either lr-mupen64plus or lr-mupen64plus-next.
        If you're using RetroArch and one of the 2 cores, you can check (and change) the controls assignment from the RGUI - in the Controls section. You may have a game/core override that overwrites the controls order.

        1 Reply Last reply Reply Quote 0
        • stattmoneS
          stattmone
          last edited by

          Thanks for the response

          I’m trying to use non-libretro mupen for the superior performance. I’d understood from the pi fork docs that it still took controller configs from those files, but maybe that’s where I’m going wrong!

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

            @stattmone If you're using the standalone emulator, then the configuration you've done have no effect. Look in the /opt/retropie/configs/n64/mupen64plus.cfg file and re-arrange the controllers there (look for [Input-SDL-Control1], [Input-SDL-Control2], etc.). The same file is available at \\retropie\configs\n64, if you're using file shares to access your Pi.

            1 Reply Last reply Reply Quote 0
            • 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.