@Bradyadams
Which configure file? The mupen configure "mupen64plus.cfg" or the autoconfig file "InputAutoCfg.ini"? I recently ran into same / similar. No matter how much I edited the mupen config controller sections no changes. Even if I set the controller to manual config but no luck. The global buttons like escape I could changes.

I then found an old auto config file that had info for keyboard already setup. I copied this into the config folder and was good to go. Reading the wiki it made it sound like the auto config should be generated when you first start retropie, but I am guessing if you only config keyboard it might not.

@Gusgmb does it happen on all emulators or just some? Are you sure you're using the libretro version? Also what's your config in RetroArch-joypads? Please format it properly as described on the read this first page

@Ikyrus You could use something like jslisten to monitor for inputs, and invoke a script to switch config files.

https://github.com/workinghard/jslisten

@d8thstar Just a thought. . .What about the possibility that you are modifying the gamelists while Emulation Station is running? Have you tried putting the file into your ROMs directory while ES is not running? Then starting up and seeing if it picks up the list?

Also, where exactly are you putting the XML file? Notes above have suggested "the ROMs folder" but for you, since you are mounting an external volume, that probably means /mnt/MAME106/roms/ right?

Ok, so reinstall with 4.1

removed the hash from in front of hdmi_drive2 (now that I can see the config file) and that seemed to do it. That berryboot was the main cause like you said @rbaker , I will say this though: the config file looks way different than a regular raspberry pi one. But Ill see about any other changes in another thread. Moral of the story is skip berry boot if you can.

I tried placing syscard3.pce in the same folder as the rest of the .pce, .bin, and .cue files. I'm still getting the same result. There is probably an issue with the commands I used to launch the emulator. I had to unzip my TG16 files because they were not loading when I left them in .zip format. Perhaps I should use the same commands I used for that emulator (/opt/retropie/emulators/retroarch/bin/retroarch for the Executable and
-L /opt/retropie/libretrocores/lr-beetle-pce-fast/medafen_pce_fast_libretro.so --config /opt/retropie/configs/pcengine/retroarch.cfg "[romfilename]" for the Command Arguments). I'm still scratching my head trying to figure this out :-(.

@Nwoodward yeah i havent had time to yet. I was too busy lately. Please do report it to them. If you post a link to the thread you post in i will probably comment when i get a chance too

@BuZz

Thankyou!

im using a media pi plus. it has a converter inside

@Darix i would try sega cue maker. .ccd should work with it. Not sure about the other two. You can also try renaming it to .bin then running sega cue maker if it doesnt work the other way. Yes i know its a different format but i have gotten several games to work that way in the past.

Please let me know if this is enough information -- as mentioned, super new to this...

Pi Model: v 3
RetroPie Version Used: v4.1
Built From: downloaded file from retropie site and followed instructions to extract with 7-zip and used Win32DiskImager
USB Devices connected: tried once with just the USB SNES style controller RetroLink and once with both Controller and Keyboard (logitech k400)
Controller used: same as above
Error messages received: no error messages, it just loses controller mapping and essentially requires a reboot
Log found in /dev/shm/runcommand.log (if relevant):
Guide used: many different online guides tried / youtube videos / this forum /
File:
Emulator: Tried with NES / SNES / Genesis
Attachment of config files: how do i copy these out of the device?

Thank you again!

@edmaul69

good to know

I was wondering the same but until I get the time to really fix this issue I do the following:

Create whatever file you need on your Pi in Windows (or any other OS) Copy the file(s) to your Pi in one of the shared folders in \Retropie SSH into the Pi Copy the files to the right location on the Pi

Not the most user friendly way, but this way I got my Pi to boot showing the PsOne boot sequence.

@ebtalk as found here, you can use gparted for this:

*"So the best way I have found is to use GParted (you can either use a Linux-based OS, or boot from a GParted Live USB). It is simple enough to find detailed instructions on how to do each of these steps in detail, but here is the general method I have found to work:

Run GParted, find your SD card in the device list and shrink the main partition to as small as it will go.
Take the value of the last sector of this partition and multiply this by the sector size (512 for me; I presume this is standard, although you can check this in GParted settings for your device): this will give you the total size in bytes to copy.
Divide the total number of bytes by 4096 (round up if you need to - better to take a bit more space than not enough), and this will give you the 'count' to then enter into the following command at the terminal in a Linux environment (You can probably do this from the GParted Live USB operating system terminal or in Cygwin without sudo so long as you are running it as an administrator):
sudo dd if=/dev/mmcblk0 of=/path/to/your/file.img bs=4k count=<count>

Change the input device location if you need to. This should give you a final image file that is the smallest that it can be, omitting empty space."*

@matalog Alright, I think i can give it a go at the weekend.
I'll post my testings in here and let you know if it works.

@fastfalcon94 use the search function on this forum. It's been answered at least 5 times already

Nice - thank you Petrtopie

@Forlife said in Optimal way to shut down RetroPie? (also other questions..):

...or actually go to menu, quit, shut down?

Disco!

Does it make a difference?

You risk corrupting your SD card otherwise.

Also, is it necessary to have a usb keyboard?

It's not absolutely necessary, but I would highly recommend keeping one handy for maintenance.