lr-mame2003 - enter key now crashes emulator, used to be fine. Any ideas?
-
@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.
-
@movisman ok, you're not crazy! :) i get this exact issue. i will investigate now...
-
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
-
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.
-
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!
-
@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).
-
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.
-
Genius - just to confirm that disabling launch art solves the issue completely for me, from what I can see?
Cheers
-
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).
-
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
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.