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

    How to setup run ahead with controller and keyboard?

    Scheduled Pinned Locked Moved Help and Support
    run aheadhotkeyscontrollerkeyboardretroarch
    12 Posts 2 Posters 1.0k 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.
    • J
      jedcooper
      last edited by

      I'm using RetroPie with ES the usual way. Xbox 360 or PS3 Gamepad with Hotkey on the "Power on controller" button. All fine.
      Now as it comes to run ahead, I cannot use the RetroArch keys on my USB Keyboard (which is working fine in other circumstances).
      Only if Hotkey on controller is pressed at same time. It's unusable that way. I need the P (pause) and K (frame advance) key at least.
      So the controller Hotkey config interferes with the keyboard keypresses. Not sure where I could (temporarily) turn the hotkey stuff off and handle RetroArch hotkeys the normal way (as on Windows f.e.)
      So how?

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

        @jedcooper said in How to setup run ahead with controller and keyboard?:

        So the controller Hotkey config interferes with the keyboard keypresses. Not sure where I could (temporarily) turn the hotkey stuff off and handle RetroArch hotkeys the normal way (as on Windows f.e.)

        Unplug the controller(s).

        J 1 Reply Last reply Reply Quote 0
        • J
          jedcooper @mitu
          last edited by jedcooper

          @mitu
          When? If I'm in RetroArch and unplug controller it isn't working that way.
          I set the p and k key in the RetroArch Input settings ofc. They were not set by default.
          I can move with cursor keys and x, z etc. are fire buttons. Yes. But no RetroArch hotkeys work.

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

            Is you keyboard input configured with a Hotkey Enable key ? If no, then the normal hotkeys should work by pressing the key directly (P/Space/etc.).

            J 1 Reply Last reply Reply Quote 0
            • J
              jedcooper @mitu
              last edited by jedcooper

              @mitu said in How to setup run ahead with controller and keyboard?:

              Is you keyboard input configured with a Hotkey Enable key ?

              Nope Keyboard input isn't configured at all, it's just plugged in. Only controller(s) are configed by the ES controller UI with hotkey (PS3 button/Xbox button) ofc for convenience.

              @mitu said in How to setup run ahead with controller and keyboard?:

              If no, then the normal hotkeys should work by pressing the key directly (P/Space/etc.).

              Yes, I thought the same, but it unfortunately isn't :(

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

                @jedcooper said in How to setup run ahead with controller and keyboard?:

                Nope Keyboard input isn't configured at all, it's just plugged in. Only controller(s) are configed by the ES controller UI with hotkey (PS3 button/Xbox button) ofc for convenience.

                Post your retroarch.cfg to pastebin.com just to check.

                J 1 Reply Last reply Reply Quote 0
                • J
                  jedcooper @mitu
                  last edited by

                  @mitu

                  /opt/retropie/configs/all/retroarch.cfg: https://pastebin.com/YDkFCiLF

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

                    @jedcooper You do have a hotkey enable set:

                    input_enable_hotkey = "space"
                    
                    J 1 Reply Last reply Reply Quote 0
                    • J
                      jedcooper @mitu
                      last edited by jedcooper

                      @mitu
                      i.e.?
                      ok, set to this in the very same file /opt/retropie/configs/all/retroarch.cfg to input_enable_hotkey = "nul" nothing changed. with or without controller plugged in. RetroArch hotkeys still don't work. with controller plugged in it's the same, controller hotkey (PS3/Xbox button) has to be pressed to have reaction on USB keyboard for RetroArch hotkeys.

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

                        @jedcooper If you have enabled 'Save Configuration on Exit', then modifying /opt/retropie/configs/all/retroarch.cfg might not help.
                        Check the system's retroarch.cfg and see if you have a hotkey set there - the system's config should be in /opt/retropie/configs/<system>.

                        J 1 Reply Last reply Reply Quote 0
                        • J
                          jedcooper @mitu
                          last edited by jedcooper

                          @mitu
                          My global retroarch.cfg has not set "Save Configuration on Exit".
                          /opt/retropie/configs/all/retroarch.cfg:
                          config_save_on_exit = "false"

                          For example ColecoVision

                          My system /opt/retropie/configs/coleco/retroarch.cfg is:

                          # Settings made here will only override settings in the global retroarch.cfg if placed above the #include line
                          
                          input_remapping_directory = "/opt/retropie/configs/coleco/"
                          
                          core_options_path = "/opt/retropie/configs/coleco/retroarch-core-options.cfg"
                          #include "/opt/retropie/configs/all/retroarch.cfg"
                          

                          My system /opt/retropie/configs/coleco/retroarch-core-options.cfg is:

                          bluemsx_auto_rewind_cas = "ON"
                          bluemsx_cartmapper = "Auto"
                          bluemsx_msxtype = "ColecoVision"
                          bluemsx_nospritelimits = "OFF"
                          bluemsx_overscan = "disabled"
                          bluemsx_vdp_synctype = "Auto"
                          bluemsx_ym2413_enable = "enabled"
                          

                          No other .cfg or .opt files for the emulator, system or game.

                          System folder:

                          pi@crtpithree:/opt/retropie/configs/coleco $ ll
                          total 2.3M
                          drwxrwxrwx  2 pi pi 4.0K Feb 24 16:43 .
                          drwxrwxrwx 94 pi pi 4.0K Feb 22 00:05 ..
                          -rw-rw-rw-  1 pi pi  459 Feb 13 08:52 emulators.cfg
                          -rw-r--r--  1 pi pi 2.3M Feb 13 12:28 launching.png
                          -rw-------  1 pi pi  302 Feb 13 08:51 retroarch.cfg
                          -rw-r--r--  1 pi pi  217 Feb 24 13:45 retroarch-core-options.cfg
                          

                          emulators.cfg:

                          lr-fbneo-cv = "/opt/retropie/emulators/retroarch/bin/retroarch -L /opt/retropie/libretrocores/lr-fbneo/fbneo_libretro.so --subsystem cv --config /opt/retropie/configs/coleco/retroarch.cfg %ROM%"
                          default = "lr-bluemsx"
                          coolcv = "/opt/retropie/emulators/coolcv/coolcv_pi %ROM%"
                          lr-bluemsx = "/opt/retropie/emulators/retroarch/bin/retroarch -L /opt/retropie/libretrocores/lr-bluemsx/bluemsx_libretro.so --config /opt/retropie/configs/coleco/retroarch.cfg %ROM%"
                          

                          blueMSX folder:

                          pi@crtpithree:/opt/retropie/configs/all/retroarch/config/blueMSX $ ll
                          total 16K
                          drwxr-x---  2 pi   pi   4.0K Feb 13 12:29 .
                          drwxrwxrwx 45 root root 4.0K Feb 15 09:54 ..
                          -rw-r--r--  1 pi   pi    157 Feb 24 13:15 blueMSX.cfg
                          -rw-r--r--  1 pi   pi     92 Feb 13 12:32 coleco.cfg
                          pi@crtpithree:/opt/retropie/configs/all/retroarch/config/blueMSX $ cat blueMSX.cfg
                          custom_viewport_height = "240"
                          custom_viewport_width = "1360"
                          run_ahead_enabled = "true"
                          run_ahead_secondary_instance = "true"
                          video_crop_overscan = "false"
                          pi@crtpithree:/opt/retropie/configs/all/retroarch/config/blueMSX $ cat coleco.cfg
                          custom_viewport_height = "240"
                          custom_viewport_width = "1360"
                          video_crop_overscan = "false"
                          
                          1 Reply Last reply Reply Quote 0
                          • mituM
                            mitu Global Moderator
                            last edited by

                            Then I have no idea. I routinely use a keyboard - without a hotkey set - and don't experience the behavior you're describing.

                            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.