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

    Anyone know how to set up N64 raphnet adapter with the "raphnetraw plugin" on RetroPie??

    Scheduled Pinned Locked Moved Help and Support
    raphnetn64raphnetrawpluginraw
    19 Posts 2 Posters 2.7k 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.
    • A
      ALinkToTao
      last edited by

      I have some raphnet adapters, and some sweet custom rebuilt stock N64 controllers. I want the full experience with these controllers with the raphnetraw plugin that raphnet includes with the adapter which allows 0 latency with the emulator. I'm assuming I will need the mupen64plus raphnetraw plugin, but I have no idea where to go from there. I'm assuming I need to do something with terminal, but I'm definitely not a terminal wizard. And from there, how would I choose the plugin in RetroPie? I'm assuming I'll have to do it through RetroArch, but I have no idea.

      If anyone has done this, please enlighten me. I would be so happy.

      Many thanks.

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

        I think you need to compile the plugin first and the install it so it's available for Mupen64Plus - https://github.com/raphnet/mupen64plus-input-raphnetraw.
        Mupen64plus is installed by the RetroPie scripts in /opt/emulators/mupen64plus, you'll need to copy the resulting plugin there (into /opt/emulators/mupen64plus/lib/mupen64plus). After copying the plugin, you should add the --input mupen64plus-input-raphnetraw parameters to the start-up command for Mupen64plus in /opt/retropie/configs/n64.

        1 Reply Last reply Reply Quote 0
        • A
          ALinkToTao
          last edited by

          Thank you! I'll give it a try, and let you know how it goes!

          1 Reply Last reply Reply Quote 0
          • A
            ALinkToTao
            last edited by

            I tried to "make" the plugins I guess (sorry I'm a total noob). Here's what happened in terminal: pi@retropie:~/Downloads/raphnetraw/projects/unix $ make all
            Makefile:179: *** Mupen64Plus API header files not found! Use makefile parameter APIDIR to force a location.. Stop.

            1 Reply Last reply Reply Quote 0
            • A
              ALinkToTao
              last edited by

              Okay, after a long go at it, I've made progress. I compiled the plugin with help from a post on github: https://github.com/raphnet/mupen64plus-input-raphnetraw/issues/9#issuecomment-685300745

              Now to try to do what you said. I don't know what the name of the startup file actually is. Would you know it's name?

              1 Reply Last reply Reply Quote 0
              • A
                ALinkToTao
                last edited by

                @mitu
                "After copying the plugin, you should add the --input mupen64plus-input-raphnetraw parameters to the start-up command for Mupen64plus in /opt/retropie/configs/n64."

                How, specifically do I do this? Do I add that line, --input mupen64plus-input-raphnetraw to a specific file? If so, which file? Or do I do this via terminal, and if so, what commands would I specifically input?

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

                  @alinktotao The file is emulators.cfg. Find the entry for mupen64plus-GLideN64and add the input parameters at the end of the command used to start the emulator.

                  1 Reply Last reply Reply Quote 0
                  • A
                    ALinkToTao
                    last edited by

                    @mitu Thanks for your help so far, I've gotten farther than I thought I would. However, when I add the input parameters you mentioned earlier such as --input mupen64plus-input-raphnetraw to the end of any of the entries, it will either make the emulator act as though there is no controller or it will simply close immediately after loading a ROM. I tried many different ways to add the input parameters. I tried by including the path and the .so extension with it, and still it didn't work. Any suggestions?

                    The .so file is in its proper place.

                    mituM A 2 Replies Last reply Reply Quote 0
                    • mituM
                      mitu Global Moderator @ALinkToTao
                      last edited by

                      @alinktotao Can you get the log file from running the emulator (/dev/shm/runcommand.log) and post it on pastebin.com ?

                      A 1 Reply Last reply Reply Quote 0
                      • A
                        ALinkToTao
                        last edited by

                        @mitu Thanks. I will do that next time I get a chance, probably Friday. So grateful for your help. This would have fallen flat on its face without your help. Many thanks.

                        1 Reply Last reply Reply Quote 0
                        • A
                          ALinkToTao @mitu
                          last edited by

                          @mitu said in Anyone know how to set up N64 raphnet adapter with the "raphnetraw plugin" on RetroPie??:

                          @alinktotao Can you get the log file from running the emulator (/dev/shm/runcommand.log) and post it on pastebin.com ?

                          Here is my config text the way you told me to put it in. I put it in under two different emulators to try it on both of them:
                          mupen64plus-GLideN64 = "/opt/retropie/emulators/mupen64plus/bin/mupen64plus.sh mupen64plus-video-GLideN64 %ROM% %XRES%x%YRES% 0 --set Video-GLideN64[UseNativeResolutionFactor]=1 --input mupen64plus-input-raphnetraw"
                          mupen64plus-GLideN64-highres = "/opt/retropie/emulators/mupen64plus/bin/mupen64plus.sh mupen64plus-video-GLideN64 %ROM% %XRES%x%YRES% 0 --set Video-GLideN64[UseNativeResolutionFactor]=2"
                          mupen64plus-gles2rice = "/opt/retropie/emulators/mupen64plus/bin/mupen64plus.sh mupen64plus-video-rice %ROM% %XRES%x%YRES%"
                          mupen64plus-gles2n64 = "/opt/retropie/emulators/mupen64plus/bin/mupen64plus.sh mupen64plus-video-n64 %ROM%"
                          lr-mupen64plus-next = "/opt/retropie/emulators/retroarch/bin/retroarch -L /opt/retropie/libretrocores/lr-mupen64plus-next/mupen64plus_next_libretro.so --config /opt/retropie/configs/n64/retroarch.cfg %ROM%"
                          default = "lr-mupen64plus"
                          lr-mupen64plus = "/opt/retropie/emulators/retroarch/bin/retroarch -L /opt/retropie/libretrocores/lr-mupen64plus/mupen64plus_libretro.so --config /opt/retropie/configs/n64/retroarch.cfg --input mupen64plus-input-raphnetraw %ROM%"

                          1 Reply Last reply Reply Quote 0
                          • A
                            ALinkToTao @ALinkToTao
                            last edited by ALinkToTao

                            @mitu

                            Here it is with the parameters put in the way you wanted me to originally: https://pastebin.com/Qx7tmfT2

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

                              The plugin you compiled works only with Mupen64plus - you've added the parameter to all emulator entries, I said to add it just to first entry (mupen64plus-GLideN64) and use just that emulator to run the game.
                              The log file shows you're starting the X server (xorg) and there's no emulator log there. Are you running RetroPie from the desktop ? This is not a supported configuration on a Pi. You need to get the file after you've run the N64 emulator and get the error, otherwise the file will not contain the correct log.

                              1 Reply Last reply Reply Quote 0
                              • A
                                ALinkToTao
                                last edited by

                                After what you said, I realized that running the emulator, then going to the desktop overwrote the log of running the N64 emulator. You're good at looking at the logs! Instead this time, I used file manager to copy the file into desktop to be able to post it on pastebin.

                                I've also corrected the config file per your recommendation to only modify the Glide64 version of mupen64plus.

                                Here is the log file, sorry for my noobiness: https://pastebin.com/byAkVaaV

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

                                  Looks like the input plugin is detected and loaded, but the plugin errors out while opening the controller:

                                  ...
                                  Opening device path: '/dev/hidraw2'
                                  Input Error: Could not open gcn64 device serial '109634'. Skipping it.
                                  Input Error: No adapters detected
                                  

                                  Maybe there's a permission error ? Check if the /dev/hidraw* devices are available to the pi user, by running the command:

                                  ls -l /dev/hidraw*
                                  
                                  1 Reply Last reply Reply Quote 0
                                  • A
                                    ALinkToTao
                                    last edited by ALinkToTao

                                    @mitu Something interesting to note: running the glide64 version without the raphnetraw plugin leads to the same issue not recognizing the raphnet adapter, whereas the lr-mupen64plus works but bypasses the plugin.

                                    1 Reply Last reply Reply Quote 0
                                    • A
                                      ALinkToTao @ALinkToTao
                                      last edited by ALinkToTao

                                      @mitu said in Anyone know how to set up N64 raphnet adapter with the "raphnetraw plugin" on RetroPie??:

                                      Looks like the input plugin is detected and loaded, but the plugin errors out while opening the controller:

                                      ...
                                      Opening device path: '/dev/hidraw2'
                                      Input Error: Could not open gcn64 device serial '109634'. Skipping it.
                                      Input Error: No adapters detected
                                      

                                      Maybe there's a permission error ? Check if the /dev/hidraw* devices are available to the pi user, by running the command:

                                      ls -l /dev/hidraw*
                                      

                                      pi@retropie:~ $ ls -l /dev/hidraw*
                                      crw------- 1 root root 244, 0 Aug 7 18:58 /dev/hidraw0
                                      crw------- 1 root root 244, 1 Aug 7 18:58 /dev/hidraw1
                                      crw------- 1 root root 244, 2 Aug 7 18:58 /dev/hidraw2
                                      crw------- 1 root root 244, 3 Aug 7 18:56 /dev/hidraw3
                                      crw------- 1 root root 244, 4 Aug 7 18:56 /dev/hidraw4
                                      crw------- 1 root root 244, 5 Aug 7 18:56 /dev/hidraw5
                                      crw------- 1 root root 244, 6 Aug 7 18:56 /dev/hidraw6
                                      crw------- 1 root root 244, 7 Aug 7 18:56 /dev/hidraw7

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

                                        Looks like the /dev/hidraw* devices are read/write only by the root user.
                                        You could add a new udev rule to allow the input group to access them. Just create a file (/etc/udev/rules.d/86-hidraw-input.rules) containing

                                        SUBSYSTEM=="hidraw", MODE:="0660", GROUP="input"
                                        

                                        then reboot your system and try to see if the permissions are changed and the emulator is able to access the controller.

                                        1 Reply Last reply Reply Quote 0
                                        • A
                                          ALinkToTao @ALinkToTao
                                          last edited by

                                          @alinktotao said in Anyone know how to set up N64 raphnet adapter with the "raphnetraw plugin" on RetroPie??:

                                          @mitu said in Anyone know how to set up N64 raphnet adapter with the "raphnetraw plugin" on RetroPie??:

                                          Looks like the input plugin is detected and loaded, but the plugin errors out while opening the controller:

                                          ...
                                          Opening device path: '/dev/hidraw2'
                                          Input Error: Could not open gcn64 device serial '109634'. Skipping it.
                                          Input Error: No adapters detected
                                          

                                          Maybe there's a permission error ? Check if the /dev/hidraw* devices are available to the pi user, by running the command:

                                          ls -l /dev/hidraw*
                                          

                                          pi@retropie:~ $ ls -l /dev/hidraw*
                                          crw------- 1 root root 244, 0 Aug 7 18:58 /dev/hidraw0
                                          crw------- 1 root root 244, 1 Aug 7 18:58 /dev/hidraw1
                                          crw------- 1 root root 244, 2 Aug 7 18:58 /dev/hidraw2
                                          crw------- 1 root root 244, 3 Aug 7 18:56 /dev/hidraw3
                                          crw------- 1 root root 244, 4 Aug 7 18:56 /dev/hidraw4
                                          crw------- 1 root root 244, 5 Aug 7 18:56 /dev/hidraw5
                                          crw------- 1 root root 244, 6 Aug 7 18:56 /dev/hidraw6
                                          crw------- 1 root root 244, 7 Aug 7 18:56 /dev/hidraw7

                                          OH MY GOOODNESS!! THAT DID IT! THANK YOU SOOOO MUCH!!!

                                          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.