I know this topic is pretty old but I just had this happen to me. It happened because of a conflict in RetroPie auto start. I had manually entered a command line to auto start and then later chose the auto start option in RetroPie setup. Seems the two didn’t work well together. I resolved it by getting back to RetroPie setup in command line and deleted the auto start line. I’m definitely a noob so I apologize if my terminology is wrong. But I’m learning. Hope this helps someone else.
@TomoS Emulationstation must be launched from the terminal, it's not going to work from an existing X.org/Desktop session. You'll also have to turn off/stop your login manager/display manager if you have one started.
If there's interest, I can "reconvert" my port to move away from their small-screen focus [...] and plug into libretro to benefit from all the different types of controllers available.
I would aprreciate this. The best "game" in this collection is snake. I like puzzeling but I'm totally new to play this with keypads. I've installed the android version on my eBook-Reader and on my smartphone for casual gaming.
@mr_smt That seems to look like a warning, but it might indicate that your installation does not have hardware accelerated graphics (maybe due to running in a vm) and the emulator needs it in order to run.
I'd suggest to use something that's native to your os (macOS) like OpenEmu or RetroArch. You could also use AttractMode as a frontend, in combination with RetroArch, if the default RetroArch interface is not enough.
@buzz The main reason I wasn't using the official image is so that I can use the box for multiple purposes--I can launch mate desktop with startx or launch retropie after I've logged in. I'm building a palmtop/portable emulator. If it's pretty easy to set up the official image to do so, maybe I will just use the image--sure beats installing and compiling all the packages.
Despite libSDL1.2-dev being a dependancy the Makefile actually doesn't use USE_SDL=1 so it's built without it anyway! So much for my original question.
I've tried using the "update from source" option in Retropie-Setup and the newer version it builds is buggy in a similar way to my Vero4K builds. I guess the Reicast devs have a commit somewhere that's broken it a bit. So again it would be very useful to know when the Reicast binary was built? so I can pull from that time to compare.
Incidentally if the Retropie devs are reading this there is a Reicast commit "6ae93b3" which breaks it to the point of segfaulting at startup. This affected the the Vero4K and as it shares a CPU with the RPi3 it will likely break on their too, so be aware should you pull in anything newer from their repository.
Hey @chipsnblip thanks for the positive feedback! I'm glad you are having fun with this game :)
I've been a bit busy so sorry for the delay replying.
one small request, if possible, could gore be enabled by default (nogore = 0)? it's been a while, but i believe having gore on might be the game's standard default (at least on the linux build).
Yes, the game upstream has gore enabled by default. I decided to disable this in the scriptmodule by default thinking that RetroPie might be used by kids (due to its "cute bunnies" premise). However I might have over-thought it too :)
If @BuZz doesn't have any particular opinion about it, I can send a PR to not force gore on first-install.
Did you ever figure out how to set/unset the framebuffer settings after launching advmame?
Unfortunately no. I reported the issue back in April of this year, but unfortunately the same behavior still exists in the latest AdvanceMAME 3.9. Currently, I believe the only solution is to reboot RetroPie after AdvanceMAME has been launched during a session to reset the framebuffer.
Like any big project with limited contributors, bug reports known to affect more users are often prioritized. That being the case, it might help for those affected here to add a comment to the thread. Nothing pushy of course. Just a simple "same here" type statement would do the job.