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

    Intel NUC 8i5BEK

    Scheduled Pinned Locked Moved Help and Support
    intel nucupgradehardware
    22 Posts 7 Posters 10.4k 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.
    • YFZdudeY
      YFZdude @A Former User
      last edited by

      @daragon said in Intel NUC 8i5BEK:

      Thanks, that's what I wanted to hear. I will have to do some research how to do that, because dolphin is not listed in Retropie packages, but that's another topic...

      The package lists vary depending on the platform on which you have installed RetroPie. I'm not familiar with RetroPie on the NUC line, but it is definitely on the list somewhere for x86 builds. I think it was in experimental.

      I'm not sure if I'm reading this correctly but based on the github page it may be for 64-bit OS only.
      https://github.com/RetroPie/RetroPie-Setup/blob/master/scriptmodules/emulators/dolphin.sh

      It says

      rp_module_id="dolphin"
      rp_module_desc="Gamecube/Wii emulator Dolphin"
      ...
      ...
      rp_module_section="exp"
      rp_module_flags="!all 64bit"
      
      1 Reply Last reply Reply Quote 1
      • ?
        A Former User
        last edited by

        @mitu @YFZdude

        Yup, that should be the problem. I couldn't find it on my Odroid XU4, so I thought it needs to be installed somehow from terminal, but now I know, thank you.

        1 Reply Last reply Reply Quote 0
        • George SpiggottG
          George Spiggott @A Former User
          last edited by

          @daragon I have the exact same SSD and one stick of 16GB of 2400Mhz RAM. I also have a 2.5"/7mm 2TB HDD installed.

          Currently running:
          Retropie 4.8.9 on a Pi Zero 2W (Overclock Settings: CPU 1400Mhz)
          ES-DE on a GMKtec K6 (Windows 11, 32GB RAM)

          1 Reply Last reply Reply Quote 0
          • ?
            A Former User
            last edited by A Former User

            Hello, so I finally installed Retropie on my NUC, also installed dolphin emulator from Retropie packages and everything seems to work like a charm. The only one problem is, that the input is from a keyboard.

            I tried to map my controller (8Bitdo SF30 Pro) in dolphin-emu GUI. The controller is working here, I can start games from this GUI and play all of the games. The problem is that the controller that I set up still does not work in Retropie - Retropie has a keyboard as an input. After closing emulation station and opening a dolphin-emu located in opt/retropie/emulators/dolphin/bin I can see my configuration there and I can play the games. Also graphical settings are applied only in dolphin emu, but not in Retropie.

            Am I missing something? It is still the same emulator. It does not make a sense to me...

            Thanks

            George SpiggottG YFZdudeY 2 Replies Last reply Reply Quote 0
            • George SpiggottG
              George Spiggott @A Former User
              last edited by

              @daragon Am I right in thinking you are using the standalone Dolphin emulator in EmulationStation?

              I found a copy of the Dolphin Libretro core and I'm not having any issues with controls. It won't load .GZ games but it runs my test .ISO, Soul Claibur 2, just fine. I've also found an early version of the PCSX2 Libretro core and that works reasonably well also.

              Have you overcome EmulationStation showing both discs for Gamecube games? If you have please share.

              Dolphin: https://github.com/hunterk/libretro_builds
              PCSX2: https://github.com/aliaspider/pcsx2/releases/tag/v0.1-libretro

              Currently running:
              Retropie 4.8.9 on a Pi Zero 2W (Overclock Settings: CPU 1400Mhz)
              ES-DE on a GMKtec K6 (Windows 11, 32GB RAM)

              1 Reply Last reply Reply Quote 0
              • YFZdudeY
                YFZdude @A Former User
                last edited by

                @daragon
                If you setup your controller while using dolphin, then RetroPie won't have that information. You need to setup the controller in RetroPie. If it doesn't prompt you, you can press START to access the menu and look for Configure Input in the menu.

                The disconnect is because the dolphin package listed in the RetroPie setup is a standalone emulator and not the libretro/RetroArch version. Only the lr- emulators can pull controller configs and settings from RetroPie.

                ? 1 Reply Last reply Reply Quote 0
                • ?
                  A Former User @YFZdude
                  last edited by A Former User

                  @George-Spiggott @YFZdude
                  Just to be clear...

                  Yes, I am using the dolphin standalone emulator. I downloaded it through package management in Retropie->Retropie Setup->Manage Packages->exp->dolphin. My Retropie is installed on Ubuntu 20. When I start Retropie app/EmulationStation I can see Wii and GameCube games in the list. My controller is working in every console except of Wii and GC. When I start a Wii/GC game and press A button I can choose two emulators -> dolphin or dolphin-gui. In dolphin option the input is from a keyboard and in dolphin-gui option nothing works.

                  From searching in Retropie Docs I found out that it needs to be mapped individually in dolphin-emu GUI. I opened a terminal and started the ./dolphin-emu. A dolphin app appeared and I changed a controller from keyboard to 8Bitdo. I mapped all the buttons and started a game from standalone dolphin emulator not Retropie (I press the play button, select the game and it started). Voala, the dolphin recognizes my new input and everything works fine.

                  Unfortunatelly this input is still not working in Retropie. I can play games only with keyboard.

                  I do not know what to do, because it is the same dolphin emulator and it should work I suppose.

                  EDIT: Also any graphics or audio configuration does not apply in Retropie. Only in dolphin from terminal. It is still the same emulator, isn't it?

                  YFZdudeY 1 Reply Last reply Reply Quote 0
                  • YFZdudeY
                    YFZdude @A Former User
                    last edited by YFZdude

                    @daragon
                    Ah I see. So if you launch the standalone it works but when launching from within RetroPie it doesn't.

                    Odd, I pretty much did the same as you to configure the controllers when I set mine up on my Lubuntu 20.04 build on my old PC. The only thing I do differently is I have changed the emulator choice from runcommand to be the dolphin-gui since that is the only way I could get it to use the hotkey for exiting the emulator and returning to RetroPie.

                    When I launched the standalone GUI to map controls, I didn't launch a game from there but I can't see how that would break the controller config. It sounds like there is some trouble saving the controller config where RetroPie expects to find it. It should be launching the same standalone emulator so this isn't making sense to me.

                    EDIT: Maybe you can check out the guide at https://dolphin-emu.org/docs/guides/configuring-controllers/ and see if there is anything that stands out as something that may have been missed. It does appear there are multiple screens for picking the controls and which controller gets used.

                    ? 1 Reply Last reply Reply Quote 0
                    • ?
                      A Former User @YFZdude
                      last edited by A Former User

                      @yfzdude

                      Thanks for your reply.
                      Yes, that's the site I followed during my controller mapping. As I said, it is working in standalone dolphin and input is saved here - when I close it up the config remains. Only Retropie has a problem with it and do not see those mappings.

                      I am doing a deep search in Retropie configs. I found the file "GCKeyNew.ini" located in /opt/retropie/configs/gc/Config . First lines of this file:

                      [GCKeyboard1]
                      Device = XInput2/0/Virtual core pointer
                      Keys/HOME = Home
                      ...

                      Below that there is whole keyboard mapping and after that nothing. I tried to change the Device to "evdev/0/8Bitdo SF30 Pro" which is my mapped controller in standalone dolphin and also mapped some buttons, but it does not work - it is still the keyboard :D .

                      EDIT: I found it! I have to customize manually the file "GCPadNew.ini" in GameCube config files. But I can't understand why it does not work automatically...

                      EDIT2: I left that file opened to see what will happen. I reset the mapping and configure buttons again, now it is working. I can't tell where did I go wrong, but looks OK.

                      EDIT3 (and the last): NEVER and NEVER run an emulator using sudo command, that's why I could not properly configurate my controller - Retropie runs emulators without sudo I suppose...

                      I hope it will be allright for this time. I'll leave a comment after some time...
                      THANK YOU!

                      YFZdudeY 1 Reply Last reply Reply Quote 1
                      • YFZdudeY
                        YFZdude @A Former User
                        last edited by

                        @daragon said in Intel NUC 8i5BEK:

                        EDIT3 (and the last): NEVER and NEVER run an emulator using sudo command, that's why I could not properly configurate my controller - Retropie runs emulators without sudo I suppose...

                        Ah yes, this might make some sense after all. If you ran it with sudo the first time, the configuration file probably got saved with root ownership or permissions. Then when it runs as the regular pi user from ES, it doesn't have ownership or permission to edit the file most likely. I've seen the Windows version of this snafu before.

                        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.