that link here was very helpful:

https://github.com/libretro/libretro-fceumm/blob/a8fcbf1410aeccb9c29907874a5ed33cfda87ed9/src/ines.c#L797-L802

I guess lr-nestopia handles it the same way fceumm does on the retropie (checking for file name and then setting region).

Is there any way to find something similar about pocketsnes and the snes emulator on retropie, too?

thank you so much, that seems to have completely fixed it! is there any other way i can force screen settings without getting this error?

Ya I didn't really want to mess with kid mode for the sake of a handful of roms, but thanks

Right I have sorted the screen out (run command) and the controls now work on 0.4 so thanks.

What is strange though is UAE4Arm works on the Xbox analogue stick fine in all directions and the d-pad works but left doesn't work and I'm not sure where it get's this setting from. Any ideas?

@cyperghost You mean this post? I used the Adafruit retrogame software for the GPIO to keyboard stuff. It was easy.

What about crt-hylllian-glow and crt -easymode?
Thanks

@BuZz ok sorry about that I didn't realise the post was against the rules. Please just delete it.

yes. /etc/emulationstation/es_systems.cfg is managed automatically when adding / removing packages.

@igmothemagus this. Both controllers are not the same- the architecture of the new controller was moved to bluetooth because it was a simpler and faster band than the one they were apparently using for the original. There was a distinct attempt to brand this new controller as "Bluetooth", even at their E3 conference.

Of course, that didn't stop them from attempting to keep it as exclusive to their platform as they possibly could. The Linux kids are having all sorts of problems using it wireless via Bluetooth on their PC's. It's a mess.

It now works, thanks.

@AndersHP

It's been a while and I have since uninstalled Reicast, but if memory serves, I did have the res as low as possible. I might give it another day in court sometime soon.

HI there

I am having exactly the same problems. I've trawled the internet with no luck... did you manage to fix your problem in the end? I'd love to know how if you did!

Thanks...

Thanks!

@davej ok sorry dint realise

@mccu7pj2

You don't really create an .srm file. The .srm files are created automatically when you save in game, using the original save method intended on the console (such as selecting Save after a castle in Super Mario World). These are created by the emulators to emulate this function of the original cartridge. Save states are different and are specific to emulation, the emulator dumps a copy of the memory to a file to reload, these are what you get when you press HOTKEY + R to save and these are .state files.

If you are playing a game that saves your progress automatically as you go along (Zelda, Super Mario World, Super Mario All Stars, Uniracers, etc.) it will create an srm file for you at the appropriate point when the game would save on a physical console.

Si

I installed Ubuntu 16.04.1 64-bit , installed RetroPie via script, and everything seems just fine.
this is a different laptop than last time, but I am happy as can be.

thank you very much

@Shadowfax

Have you by chance altered the video mode, resolution, or frame buffer display settings in the run Runcommand menu?