I dont really know what i did, but rebooted and copied the exact same config file (literally made a copy deleted it rebooted and then put it back) and now it is working

I remapped the controls of almost every core because of my joystick layout. I'm gonna buy a new controller with a different controller and default mappings are more fitting.

I need to have the cores just like if I never remapped their controls

This forum is not for general purpose emulation, but it's targeted specifically at RetroPie, a Linux based solution for installing and configuring emulators. Unfortunately, the emulator you're trying to use is not one of the RetroPie supported emulators.

Update your Retropie setup script first, then install from source.

@stoney66 Thanks for the advice. I've got a config for /opt/retropie/configs/all/retroarch-joypads/USB\ Gamepad\ .cfg that looks reasonable, but still nothing is working. I have remapped them all repeatedly, and still no love. Any other ideas?

@240pnoob said in 240p Over Composite to CRT Problems:

any easy guides on how to do this? Keep in mind I have only had a raspi for about 24 hours, with 20 of them being me fighting it.

You really should read on about the Raspberry Pi and RetroPie in general before trying to customize your installation. Themes can be installed from the RetroPie setup script - https://retropie.org.uk/docs/Themes/.

@dsstrainer Thanks for sharing your find. I just tested it and it works fine, but only if the file is created (by touch in your example) when ES is already running. ES seems to delete the file at start up, because it's actually meant for ES' restart option, as I understand it.

Thus, to use it as an everyday fail-safe in case ES crashes you'd have to find a way to create it automatically after ES has already started (edit: and to manually delete it if you want to shut down ES for good).

Just an addition to your advice, since you don't need it yourself anymore. :)

@meynti The backup image contains 2 partitions, one for boot and one for the system itself. The 2nd partition is formatted with the Linux ext4 filesystem and cannot be read by Windows. You'll need a Linux system to be able to read it - either try a live linux distro (that you can run from an USB drive on your Windows PC) or find a Linux installed pc to read the image.

A big thanks from me. I never thought to do it this way either.

Pi Model or other hardware: (A+ 512mb.)
Power Supply used: (5v, 3A)
RetroPie Version Used (retropie 4.4):
Built From: (Pre made SD Image on RetroPie website,)
USB Devices connected: usb hub
Controller used: ps2 for pc(only the usb out)
Error messages received:none
Emulator: (don't know)

@windale interesting. I'll keep it in mind. thank you :)

@mitu that did it, thanks!

so just the pi/raspberry login then? well that was easy. odd that didn't come up in my search. thanks :)

ALl I had to do was move the NV files as well as all emulator named folders under roms\arcade over and all is great!

rbaker! WoW thanks. It some mucking around, trial and error but I got it mostly to work, actually it works I maped the joystick and fire button and that akk you need in lots of 2600 games. I need to figure out the other keyboard maps and Im done.

Thanks again.

Alan

@mitu said in Build my own retropie image with buildroot:

Recalbox project

will do, thanks.

Just tried that and still get the same error as before

lv10: System "steam"is missing name, path, extension, or command!

Edit:

Solution found

<system>
<name>steam</name>
<fullname>Steam</fullname>
<path>~/RetroPie/roms/moonlight</path>
<extention>.sh .SH</extention>
<command>bash %ROM%</command>
<platform>steam</platform>
<theme>steam</theme>
</system>

extention is incorrect

<system>
<name>steam</name>
<fullname>Steam</fullname>
<path>~/RetroPie/roms/moonlight</path>
<extension>.sh .SH</extension> -------------------- change here to extension like its meant to be
<command>bash %ROM%</command>
<platform>steam</platform>
<theme>steam</theme>
</system>

What a noob mistake guess I just didn't notice.

The menu has appeared now so sweet..

@somguy The problem is that you're using BerryBoot and the partition layout is different from the layout expected by the resize2fs_once service (the normal Raspbian sd-image layout with 2 partitions).
You either disable this service or ignore the error.