@drog1998 whether a rom runs with a particular core ain't depending on the folder (that would decide which (if installed) emulators are available to choose from for the roms therein; for lr-mame-cores those would be arcade and mame-libretro.), but of its content (dumped information within the archive). You need a dump matching the cores requirements (defined/queryable within its dat/xml). Take a look at RetroPies Docs and the libretro docs about romsets. In short you need to aquire or build a rom that matches the core requirements (and don't ask for it, as that would be violating the forum rules).

@zoner said in Booting to the default Raspbian desktop.:

I may have misspoken.

I don't think so.

Do I understand you correctly that after installing RetroPie on Raspbian my desktop environment will remain the same?

Yes. You can configure how the system boots and what's started in the autostart configuration - by default no configuration is performed, so the current boot configuration is not modified.

@mitu okay, thank you for bringing that up to me.

Ah great, that put me down the right path. I did have the .info, and my retroarch.cfg for NES was pretty bare bones, but looking for other .cfg files I found this:
Turns out I had a really old config file under ~/.config/retroarch/config/FCEUmm/FCEUmm.cfg

Renaming that file so it wasn't loaded fixed the issue - now I can use save states in nes games again :)

Thanks!

Just wanted to leave this last message here for anyone that finds themselves in a similar position.

I ended up using the below github to get this situation sorted out. I used the "remove orphans" feature after using notepad ++ to change all of the paths of the directory that I wanted to get rid of to "remove.zip"

The gameslist editor linked below then saw these xml entries as "orphans" and allowed for easy removal of the entries without messing with anything else in the gameslist.xml file.

https://github.com/NeeeeB/GameList_Editor/releases

Thank you @ getupor for leading my mind down this path.

@mitu Omg, shame on me. All the time i used the wrong patch for my GPi Case. Instead of GPi Case 2 Patch i used GPi Case 2W Patch.

I installed the correct patch and retropie boot as it should and works immediately. Thank you for the help anyway...

And sorry for double post^^

@mitu Completely agree. As usual, I mess with stuff too much sometimes. It is hooked up as you have said, the primary display is hooked up to the HDMI directly beside the USB-C power port.

i reset my router and it was possible to change my email, sorry for the inconvenient.

@djdq13 Apologies for the delay here, hadn't seen this. This should be fixed in emulatiostation-dev now, if you want to try and confirm? Thanks.

@mitu This worked! I was surprised, because after formatting the flash drive it looked like the drive had a single partition taking up the whole volume. I wasn't able to create partitions on Windows 10, so I used the Disk Utility on macOS to create two exFAT partitions (screenshots of the volume in Disk Management before and after below). After that I was able to follow the instructions to create the proper directories and transfer the ROMs!

Thanks!

Screenshot 2023-12-14 212355.png

Screenshot 2023-12-14 212425.png

Screenshot 2023-12-14 214455.png

@AdamBeGood Hey old topic I know, but if you've still got those Naomi and PC-98 artworks I'd be very interested please

@windg said in Time Crisis in MAME?:

It has been removed due to disagreements between the duckstation developer and RetroArch.

It doesn't make much sense to me, there are disagreements between the MAME team and the libretro project (more like one-sided bashing, just the same as duckstation), but retropie still includes all the MAME libretro cores.

I'm haven't noticed any issues other than the not-centering. I haven't done any research, so I don't know what issues can be resolved with the analog deadzone.

I solved it, was looking through some of the old documents i had written and came across an old Retropie.txt file i created years ago which i had written myself an old guide on how to set up the network rom shares. In the fstab i had used the following.

//IP/Gaming/RetroPie /home/pi/RetroPie cifs username=pi,password=***********,uid=3001,gid=3001,nounix,noserverino,rw,user,exec 0 0

I had totally forgot that i just had to give the pi read/write access to the Gaming dataset and then in fstab i just needed to drop in the uid, gid and rw and it now saves.

Cheers

Ok habe es selbst nun gelöst bekommen.

Habe wohl Cut Trace on Pin #18 nicht richtig durch geführt

Ok, I got it solved myself now.

I probably didn't carry out the cut trace on pin #18 correctly