@Fabioborsoi said in RetroStats Web Application: Weekly Activity works for a while ( first 6 days ) then disappear, if i check the /schedule it seam populated properly. I see what you mean. There was an indexing error, not sure if or when I might have introduced it. Should be fixed in 0.0.7. Edit: I rushed the fix and it is not complete in 0.0.7, 0.0.8 should work.

I've seen that there's a Python front-end for Mupen64 that has a GUI where you can select different cheats, but I'm guessing it just loads them before starting the emulator the same as the CLI you posted. https://github.com/mupen64plus/mupen64plus-ui-python

@hostolis Yes, vnc works, I just tried.

@ziggurat I got carried away by looking at neofetch and got this It's a bit large though for a 64x80 standard Linux console.

I forgot to say, I found these command lines in the /opt/retropie/configs/emulatorname/emulator.cfg for each emulator and removed the %ROM% parameter.

@buzz As I said above "I had to unplug and repower it up, then Retropie won't reboot?" Therefore, getting any kind of log is not possible. This person seems to have the exact same issue I'm having so I didn't think it would hurt to jump on the thread. I'm trying again today, with a new Retropie, and I'm repeating the same issue. I'm taking your advice and being very patient a giving it plenty of time... Yes,,, I think it's doing something.... I got a black screen now.... I'm being patient... it's not doing anything except being a black screen for a few minutes.... SUCCESS! I hit the "b" button and Retropie is there. Thanks for your help.

This is very interesting idea, if some one could get this to work it would be much clever :)

@dosch said in Back to ES from CLi: I launched the RetroPie-Setup script from the CLI. In there I went to script>>Configuration / tools>>autostart and changed it back to Start EmulationStation at Boot. I just did this again, but then used the option in the same menu to reboot the system, instead of doing a reboot from the CLI. Now it boots back into ES. Thank you for your help @obsidianspider, but I guess it fixed itself ;-)

@Pawka Had the same issue and this fixed it. Thanks!

...