@mitu welp, you solved my problem. So emulationstation if launched from c:\programfiles\emulationstation\emulationstation.exe it is v2.9.0RP-DEV which works fine. I originally set it to install in D:\emulationstation so the exe in that location launches v2.0.1A which I just realized I accidentally deleted my desktop exe and then went to that location to grab it again. Dont know why there are 2 locations but v2.0.1A is what causes a problem. Somehow when typing this I went to 2.9.0 without thinking to check the version and then just closed it but every time I tried to use a controller I was launching v2.0.1. Sorry and thank you ._.

Going to leave this up unless mods wanna delete it cause maybe others might make a dumb mistake like me.

@mitu Noted. Thanks ;)

@mitu So when I got home I took the microSD card that was in the raspberry pi zero W that I think is faulty. And just moved it over to the new raspberry pie zero w that arrived in the mail today. And it seems to be working a lot better. It booted up just fine to EmulationStation and I’m not getting any of the button issues that I was having when I had it in the Retroflag GPi case. It occasionally gave input configuration crashes too.

I tested only one Atari game on it and it seems to be working (where as before I could never keep it from crashing long enough to run a game). However I’ve only started transferring games over and havent tested any others. Either way it’s not freezing like it was just a few seconds after loading up emulation station. And it has yet to crash. Which means so far that’s a really good sign.

When I’m done transferring the files over, doing a scrape for the game images, and can actually spend some time playing games on it. I’ll be glad and certain of what the issue was. But based on all the trouble I was having and I’m using the exact same microSD card with everything that was installed before. So far I’m convined that I had a faulty raspberry pi zero W.

Thanks @mitu I thought it looked and sounded familiar! :)

Just managed to figure out!! I SSH'ed into the box running retropi and ran emulationstation from that console . When i did that, emulationstation appeared on TV (great). When i ran game, i saw a menu that says to press a button to configure, and there I've seen to run with verbose logging. When game exited, i opened up /dev/shm/runcommand.log file and saw that umk3-u2.bin file was missing. So I've kept on looking for 0.78 romset mk3 files until i found that there is umk3-u2.bin file in one of them ! When i found it, I've copied that one to arcade dir and ran it without issues!!!

I love mk3 ! Now all i have to do is find my notebook with special moves written on it for every character which i collected during old days ! Ahhhh, that takes me back!

Thank you, all of you for assisting ! Would not have done it without you!

I love the search function.

Just wanted to say this helped me get my Windows 10 build scraped! Thank you! 🥂

That worked for me! Thanks a lot!

I'm not an expert in overvclocking, but if the same values have been working without issues, on the same PI, they should be ok with the new version.

@mitu said in Removed emulationstation-dev help:

@paffley Just install Emulationstation (the regular package) from the core packages section.

Thanks @mitu

I installed a fresh ES from binary then had to re-add es_systems.cfg content from an old backup I had (modified).

All working now thank you! keep up the super work!

Looks like a permissions problem or a funky named controller that's not saved or possibly other problems (disk full ?) that prevent Emulationstation to save the controller configuration.
My advice is to start with a clean image and work from there - https://retropie.org.uk/docs/First-Installation/.

Running the update appears to have fixed the problem for me. Tested real quick with Super Bomberman 3 on SNES and Crash Team Racing on PSX and all four controllers are working. Powering off a controller while EmulationStation is running no longer causes it to crash or freeze.

I'll keep an eye on this and report back if anything changes.

@cainkirisgai your Zelda theme for ES is absolutely perfect for a project I'm working on! Where can I get it!?!?

Thanks for the reply. Not the expected answer, but at least some clarification on the status quo.

Works for me. I will pay respect to what is found as formatting in a file (and not procject atm) and will format my edits accordingly.

And also pledge to other PR issuers to do the same (if they haven't done so in the past).

However, if the maintainers ( @herb_fargus , @petrockblog @psyke83 @BuZz ... ) have a informal list of format styles ready (or want to discuss/collect them here) I am more than willing to transform them in a formal formatter config with a formatting tool is easily available for the Linux and Windows platform.

Cheers,

@mitu @GoldManSex778 - Thanks for the advice. I converted with handbrake, basically opened the video in h/b and ran it through without messing around with the settings.
Now both the portrait and landscape videos display with the correct aspect ratio and work with omxplayer
Thanks so much.

I know it is an old topic, but I really like Space Oddity theme and I cant disable OMXplayer, so I changed some values at the theme file and this was the result:
WhatsApp Image 2019-05-20 at 18.12.25.jpeg

I changed pos and origin values, and replaced maxSize for size. You can see the file and change it by yourself, or just download and overwrite it

Changes:
Screenshot_1.png

Link:
https://github.com/Ephastus/space-oddity-theme.xml-OMX-Fix-

Sorry, this isn’t my first language, feel free to correct me.

@mitu That worked. Thank you!

@quicksilver It might be... However it's connected to an hdmi monitor. As I mentioned, the hiss is slightly more audible when I use, CRT for an example, when the metadata is scrolling. It was less audible when I switched to the Pixel theme.