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

    lr-mame2003 - enter key now crashes emulator, used to be fine. Any ideas?

    Scheduled Pinned Locked Moved Help and Support
    mame2003
    16 Posts 4 Posters 4.5k 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.
    • M
      movisman
      last edited by

      Thanks for the response. It doesn't appear to be anything like this - everything is all ok in the other retroarch emulators, they all use the same config. Hotkeys are enabled and everything else works. Pressing enter essentially crashes / terminates the emulator, it doesn't exit in the same way my actual exit button does (hotkey+escape).

      I am still investigating/troubleshooting where the issue might lie, it's very strange.

      Cheers

      dankcushionsD mediamogulM 2 Replies Last reply Reply Quote 0
      • dankcushionsD
        dankcushions Global Moderator @movisman
        last edited by

        @movisman retroarch configs can be per-core. your issue must be in one or more of the following files:
        /opt/retropie/configs/mame-libretro/retroarch.cfg (there will be a retroarch.cfg.rp-dist backup of the default settings you can replace it with)
        /opt/retropie/configs/all/retroarch-core-options.cfg (harder to revert, as this is shared with all RA cores.. look for mame2003 and delete anything that looks related)
        /home/pi/RetroPie/roms/mame-libretro/mame2003/cfg/default.cfg (you say you've already deleted this)

        (these are all assuming your roms are in the mame-libretro folder, not arcade)

        M 1 Reply Last reply Reply Quote 0
        • M
          movisman @dankcushions
          last edited by

          @dankcushions

          Cheers for that. Actually this evening I have done all those things already but it still crashes the emulator when pressed.

          I renamed my rp-dist config to retroarch.cfg temporarily so it uses the original skeleton file, and renamed my core options file so it used the defaults, but still no difference. Indeed I did already remove my default.cfg.

          My specific core config file (retroarch.cfg) doesn't have any customisations in it at all.

          It's really quite strange that it only happens in mame2003 though and not the other emulators.

          I have even replaced the .so file with an older one from a backup (end of August) just to rule out any commits and it still crashes.

          FBA, Mame4all and all my other emulators are all good though. Such a bizarre thing.

          dankcushionsD 1 Reply Last reply Reply Quote 0
          • mediamogulM
            mediamogul Global Moderator @movisman
            last edited by mediamogul

            @movisman said in lr-mame2003 - enter key now crashes emulator, used to be fine. Any ideas?:

            everything is all ok in the other retroarch emulators, they all use the same config.

            It's really quite strange that it only happens in mame2003 though and not the other emulators.

            Could you have inadvertently mapped an exit function in the native MAME menu that is invoked by the 'Tab' key?

            Edit: Just noticed that you've ruled that out.

            RetroPie v4.5 • RPi3 Model B • 5.1V 2.5A PSU • 16GB SanDisk microSD • 512GB External Drive

            1 Reply Last reply Reply Quote 0
            • dankcushionsD
              dankcushions Global Moderator @movisman
              last edited by

              @movisman ok, you're not crazy! :) i get this exact issue. i will investigate now...

              M 1 Reply Last reply Reply Quote 0
              • M
                movisman @dankcushions
                last edited by

                @dankcushions

                Phew! I was running out of ideas so i'm glad you have seen this too.
                I knew it was a bizarre thing, because my configuration hasn't changed for such a long time now. I deliberately make sure all my config is clean and tidy. I don't have any old config hanging around because I started again from a fresh 4.0 a while back, and manually copied the necessary config across to cut down on any mess left from previous versions.

                Like I say, it was working ok but i'm not exactly sure when the issue started. I just happened to notice it.

                Let me know if you want me to do any testing if you manage to find anything...

                As you will notice, it crashes the emulator (it doesn't quit), and then the terminal is knackered afterwards - anything related to it like the RetroPie-Setup GUI doesn't refresh and if you quit emulationstation there is a lot of nonsense output in the terminal window.

                Cheers

                1 Reply Last reply Reply Quote 1
                • dankcushionsD
                  dankcushions Global Moderator
                  last edited by

                  ok this is interesting. what it looks like is happening is that the keyboard is still issuing commands to the terminal (or script) running in the background. if i run mame2003 directly (or through GDB) it doesn't react to pressing enter, but if i run it via the runcommand (specifically, via emulationstation) it quits out:

                  /opt/retropie/supplementary/runcommand/runcommand.sh: line 855:  1257 Quit                    /opt/retropie/emulators/retroarch/bin/retroarch -L /opt/retropie/libretrocores/lr-mame2003/mame2003_libretro.so --config /opt/retropie/configs/arcade/retroarch.cfg "/home/pi/RetroPie/roms/arcade/88games.zip" --appendconfig /dev/shm/retroarch.cfg

                  however, if i run it directly from the terminal (/opt/retropie/emulators/retroarch/bin/retroarch --config /opt/retropie/configs/all/retroarch.cfg --appendconfig /opt/retropie/configs/arcade/retroarch.cfg -L /opt/retropie/libretrocores/lr-mame2003/mame2003_libretro.so /home/pi/RetroPie/roms/arcade/88games.zip), it doesnt quit but i can see my various keystrokes being logged within the terminal, which doesn't seem right. perhaps this is conflicting with the runcommand script, which is treating 'enter' as quit? it looks to me like the script itself is terminating mame, as there's neither a standard libretro core shut-down in the log, nor a segfault. paging @BuZz :)

                  i'm not sure why this only affects lr-mame2003, though.

                  BuZzB 1 Reply Last reply Reply Quote 1
                  • M
                    movisman
                    last edited by

                    Yes, I was going to mention something about the keyboard as some of the output I spotted in the terminal when closing emulationstation was related to keystrokes / keymaps etc - this doesn't get logged in other emulators and never used to happen in 2003. I was just waiting until I got home later so I could do a copy/paste of some of the information rather than guessing the content, but you have already spotted it.

                    The terminal and any launching of scripts are also screwy after the emulator terminates via pressing enter. I guess this is maybe related to the runcommand script or something not being cleared, but i'm not too sure how that functions so don't want to cause more confusion.

                    Hopefully Jools will have some idea how to resolve!

                    1 Reply Last reply Reply Quote 1
                    • BuZzB
                      BuZz administrators @dankcushions
                      last edited by BuZz

                      @dankcushions terminal output happens when stdin isn't correctly attached to a tty. However runcommand should do this.

                      Do either of you have box art displaying on launch ? Try disabling that. I suspect it could be due launching FBI in the background, which is interfering (In which case I am going to have to revert to how it was before - launching just before we launch retroarch).

                      Alternatively it could be related to the upstream plymouth changes as they affect the ttys. Please make sure retropie-setup is up to date along with retroarch and lr-mame2003 emulators (and reboot).

                      To help us help you - please make sure you read the sticky topics before posting - https://retropie.org.uk/forum/topic/3/read-this-first

                      1 Reply Last reply Reply Quote 0
                      • BuZzB
                        BuZz administrators
                        last edited by

                        Yeah looks like it is due to running FBI in the background - but please confirm if everything is fine disabling launch art and then reboot.

                        To help us help you - please make sure you read the sticky topics before posting - https://retropie.org.uk/forum/topic/3/read-this-first

                        M 1 Reply Last reply Reply Quote 1
                        • M
                          movisman @BuZz
                          last edited by

                          @BuZz

                          Genius - just to confirm that disabling launch art solves the issue completely for me, from what I can see?

                          Cheers

                          1 Reply Last reply Reply Quote 0
                          • BuZzB
                            BuZz administrators
                            last edited by

                            I will revert the backgrounding of the fbi call so it will be the old behaviour (the art show for 2 seconds, then the game loads).

                            To help us help you - please make sure you read the sticky topics before posting - https://retropie.org.uk/forum/topic/3/read-this-first

                            M 1 Reply Last reply Reply Quote 0
                            • M
                              movisman @BuZz
                              last edited by

                              @BuZz

                              Updated my script, re-enabled art and all is good now. Thanks a lot for your help as always, both @BuZz and @dankcushions.

                              I feared people were going to assume it was a configuration issue my side, so i'm glad you guys checked it out.

                              Cheers

                              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.