Wow, I have been struggling forever to figure out what was going on with this issue! I was pretty sure I was doing everything right, but then I stumbled in here, and sure enough, I have the 2 cfg file issue too!

Since it's been quite a while since this post was last active, I chose to copy the entry to
/opt/retropie/configs/all/emulationstation/es_systems.cfg, rather than delete the apparently-redundant one, as who knows what's changed since then! :)

<system> <name>dreamcast</name> <fullname>Dreamcast</fullname> <path>/home/pi/RetroPie/roms/dreamcast</path> <extension>.cdi .chd .cue .gdi .sh .zip .CDI .CHD .CUE .GDI .SH .ZIP</extension> <command>/opt/retropie/supplementary/runcommand/runcommand.sh 0 _SYS_ dreamcast %ROM%</command> <platform>dreamcast</platform> <theme>dreamcast</theme> </system>

Incidentally, a lot has certainly changed on the hardware side too. If you've got a RPi4, install the Flycast core instead of Reicast. Holy moly it's so very close to the original experience now!

Thanks to all involved for bringing up and solving this issue; I can finally play around with some of these games instead of tweaking settings endlessly now!

Had a similar issue with my kidzplay racingwheel.
For that i just mapped the analog control as D-pad without using the "Analog to Digital" option for the individual games i used it with.

Since your controller is broader, you can save the button mapping for entire systems, that do not use analog buttons at all.
Only the systems that do use it you'd still have to do it per game for.

Not really a solution, but its a workable workaround.

@akamming said in What tests to use to make sure an overclock is sustainable?:

on a hint of another user on the forum i did a test a few weeks ago of
...

Thanks for the info and cmds! I'll start doing some tests after I get my retropie image backed up.

@Crush said in What tests to use to make sure an overclock is sustainable?:

@TheBattleMaster I justed added the SEGA Naomi system to my retropie and figured you'd like to know that Marvel vs. Capcom 2 runs perfectly smooth on that.

Neat! Time to check some on some setup tutorials for Naomi system :D

As @dankcushions said, it's a percentage, so it depends on the total size of the file system.

This line of commands prints the reserved space in MB for the root file system:

sudo tune2fs -l $(df | grep -E '/$' | cut -d\ -f 1) | egrep "Reserved block count|Block size" | paste -sd\ | awk '{print ($4 * $7 / ( 1024 * 1024 ) ), "MB"}'

source: https://superuser.com/questions/444269/display-filesystems-free-space-available-to-the-root-user

edit: I just found out that it has to be modified to work on RetroPie.

sudo tune2fs -l /dev/mmcblk0p2 | egrep "Reserved block count|Block size" | paste -sd\ | awk '{print ($4 * $7 / ( 1024 * 1024 ) ), "MB"}'

/dev/mmcblk0p2 should be the root device of RetroPie on a Raspberry Pi. You can change it to any block device with an ext FS to see its reserved space.

I know this is an old post but it's the only one I can find that has a similar issue especially with SNES. I'm assuming it has to do with I have donkey Kong rev a and the the image for the bezel doesn't have that name

)Raspbian 5.4.51c71 armv71
Raspberry pi 4 4GB model
Retropie 4.6.7
Retroarch 1.8.8
Snes9x2010

@MISTERHOLLYW00D said in Text Rotate:

Is it possible to rotate retroarch menu? When I bring retroarch up it’s still sideways

No, that's a RetroArch's limitation - even if it can rotate the emulator video, the menu's orientation can be rotated only when using the desktop display driver and it will not work on RetroPie.

You're using a PI3, so you can use the rotation offered by the firmware.

In general, I have no idea what it was, but ... I once again updated the retropie setup script, and once again uninstalled and installed amiberry from the sources. And (magic) everything finally worked as it should ... amazing (sarcasm)

There isn't one, unfortunately. I can delete your account, your posts will remain anonymized. Is that OK ?

@mitu said in Issue configuring PowerA Fusion wired XBox One controller:

@AdamBeGood You should have opened a new topic instead of bumping 2 years old topics.

I'm sorry, I should have started a new topic and referenced this thread. Apologies.

Let me know if I am okay to carry on posting here now, or if the best route is to still open a new topic.

Your issue is probably caused by the usage of rpi-update, which overwrote the xpad driver with the stock Linux kernel version. As explained throughout the topic, RetroPie includes a patched version, which modifies the default driver behavior and maps the triggers as buttons instead of axis.
Don't use rpi-update as a regular update mechanism - it's not intended to be used as such. RetroPie uses dkms to install additional Linux kernel drivers, so that any normal Linux kernel update (via apt) will automatically re-install the drivers. When using rpi-update, this is not possible and causes issues if you rely on a certain driver to be installed and working.

I wouldn't normally use rpi-update but I wanted to try out the KMS change to see how that affected N64 emulation.

Any idea how I resolve this issue now? I looked at amending the line mentioned in the thread but that line doesn't seem to be present in my script, and there is a reference to the trigger issue also so I think the script has been updated since the above was written.

dkms install -m xpad -v 0.4 -k "$kernel" dkms install --force -m xpad -v 0.4 -k "$kernel"

I tried re-installing xpad from Source but that hasn't changed anything.

The below line is also present in "xpad.conf"

options xpad triggers_to_buttons=1

My controller is connected by a USB lead, I'm not using Bluetooth.

Later Edit: it is especially strange as it is only my Elite Controller that is having this issue. Standard XBox One Controller is perfect.

@MargoProxy said in Retropie not booting after trying to change resolution:

“Error parsing XML file /home/pi.emulationstation/gamelists/gbc/gamelist.xml No document found“ not sure if it has to do with the problem before or not

That's usually a sign that the gamelist.xml file is corrupt or not in the correct format. You can try deleting/renaming that file and then re-start:

rm /home/pi.emulationstation/gamelists/gbc/gamelist.xml

Try using append for the Gamelist option, so that existing entries will not be re-scraped/overwritten. That only works when scraping for new ROMs, but if you re-scrape your existing ROMs, try using rom name for the ROM Names option, instead of the default (No-intro).

Thank you for your reply. That's my standard setting, everything from the Retroarch at the settings. Maybe a re-install can sort it out?

You could rename the folder /opt/retropie/emulators/ppssppto something else and then modify the /opt/retropie/configs/psp/emulators.cfg and make a new entry for your copy. Retropie will ignore it then and won't touch it.

Generally doesn't matter as long as you map them correctly in emulationstation and/or the emulator itself.

Probably should fill out the information from the link below first for better help. I think some of the cheaper usb controllers out there that support 2 player sticks/buttons have to be setup exactly the same as each other and maybe that is causing your issue.

https://retropie.org.uk/forum/topic/3/read-this-first

You need to start a game first, the file doesn't exist until a game has been run. Make sure you toggle verbose logging when starting the game; after you exit the game you should have a log file in /dev/shm.

@thestarglider Alan-1 available right now. Google it:)

@BrtsZ said in Retroarch Quick Menu Inconsistency Between Emulators:

I'm using a rPi 4b with retropie version 4.6.7 on an old CRT TV. Because certain menus can be challenging/impossible to read in Retroarch with the default theme (XMB I think?), I've changed the theme style to RGUI, as it's large, clear, and legible with my limited resolution.

RGUI is the default in retropie. did you delete any .cfg files? please fill out https://retropie.org.uk/forum/topic/3/read-this-first?

but then in the following emulators it appears as the default that I can't read (XMB I think?):
-SNES (lr-snes9x)
-NES (lr-fceumm)

again, suspect you've deleted or messed with .cfg files. please provide a verbose log for these, as per my above link.