@chrisw99 said in SD card write cycles:

It was more a generic question about the lifecycle of an SD card if it's in a Pi as there always seems to be stuff being written even when idle.

Things get written to logs when events happen - it's not an issue to cause excessive write tearing. Unless you have a problem which gets logged continuously in the logs (such as under-voltage warnings), the normal operation on a Pi will not negatiely impact the negatively the sdcard lifetime.

You could configure logging to RAM instead of persistent storage (with something like Log4Ram) if you wish.

@dankcushions thank you so much for giving me this link... i finally found compatible roms. I am so thankful like, omg, i can finally continue my project. You made my week!

@mitu said in Multiple Default Emulator:

You can probably automate some stuff. The ROM-Emulator association is stored in /opt/retropie/configs/all/emulators.cfg. If you already configured some games to start with specific emulators, then you already have some entries there so you can see how its format and replicate it for other games.

thanks! that did the trick :)

i will now try and get all the names of each system and add that into the list!

will try and figure out an easy way to do this now ;P since i got close to 5k roms lol

@lazaruz A pi4 is faster to handle the more accurate emulators but it also makes some new games playable. Taito F3 games are now full speed. You can play sega system16/18 games on fbneo without slowdown so I don't need to deal with mame2003's buggy bootlegs. You can use mame2010 or 2016 for bug-free system32 games like golden axe 2 and spiderman. 3d games like tekken, etc are still unplayable. If you can run your favorite games in fbneo now then there's no point using a pi4.

@dankcushions I wasn't sure if it'd be worth the hassle of having to reset to head to be able to update again is all. if that's fairly trivial then I'll follow your instructions.

@lochana

Necro, but when you google this problem thread is one of the top results, so I'll add this here.

I was just reading that this emulator can give a performance boost over the LR version, so I decided to try it out and of course my controls don't work. I see the mention of building a config file, but I happen to have a USB keyboard installed and noted the following:

The game recognizes my analog sticks right off the bat, none of the buttons. If I press escape I get the emulator menu, which allows me to redefine the controls. The problem is, the emulator doesn't seem to recognize any button pushes from my controller. It does list it as a recognized input device (generic 360 controller)but when I select that as the device and try to define keys, it just never seems to recognize any button pushes at all. This seems like a much easier way to define the keys if there is a trick to getting it register the button pushes.

Edit: A note to future googlers: In order to configure the button presses from your controller in the configuration you need to use the A or X (PS) button to start configuring things. For some reason when I was pushing return and then trying to push a controller button it wasn't reading the configuring. After I pushed that button and then tried to configure the button it was suddenly registering them.

The only thing it is not registering is my d-pad, so I can't configure the d-pad for up/down/left/right if I want. Not sure why as that works in the lr version just fine.

It's also not registering my triggers for R2/R3

@morugaskorpion general rule is, rpi4 will struggle with emulation tasks at 4k. you should force a 1080p60 mode via raspi-config.

@mitu Thanks!

That happened also in 4.6 and it's not specific to RetroPie.

Since the Pi4 supports 4k, by default it will use the video mode advertised as 'preferred' by the TV. If that's 4k, then this is what it will use. Previous models didn't have this issue, since they didn't support 4k. You can check with tvservice -m CEA what video modes your TV supports and what is the preferred mode.

@mitu said in Dreamcast/Naomi/Atomiswave no longer working.:

There are a few - glaring - errors in your configurations:

there is no /opt/openarena folder in a RetroPie installation, so your emulators.cfg files are wrong. You copied that from your previous installation, it's not compatible to the RetroPie installation, no wonder they don't work. Reicast doesn't support Naomi/Atomiswave ROMs and there is no lr-reicast in RetroPie (it's the former name for lr-flycast).

If you have created custom folder for Naomi/Atomiswave ROMs, then you should install lr-flycast and then copy the emulators.cfg, from the dreamcast system to your new system configuration. Make sure you have a corresponding retroarch.cfg in each config folder, containing

input_remapping_directory = "/opt/retropie/configs/<FOLDER>/" #include "/opt/retropie/configs/all/retroarch.cfg"

Gotcha. That's essentially what I did, since I have my ROMs on a USB drive, I just copied those cfg files. I didnt realize the dingus that had created that previous installation changed the directory structure (yet another plus to abandoning it).

Well I'm on the right path now (get it?) to fix it. Thanks for the help, yet again.

@mitu Not sure but I usually(in Zelda a link to the past) Do the save and quit option then use the hot key combo to exit.

@mitu I haven't noticed anything strange with hdmi1 so I'll stick with that. Thanks for the effort :)

@thd79 said in tvservice not able to change resolution on the fly:

This has definitely worked in the past for me, has support for it been removed recently? The same settings work fine when specified at boot time.

The tvservice and support for video mode switching are not part of RetroPie, but a Raspbian/Kernel+firmware feature - it was certainly not removed in RetroPie. What does 'in the past' mean ? 1 year, 1 week, etc. , before doing any kernel/firmware updates, using a certain RetroPie version maybe ?

What version of RetroPie are you running (specifically) and how it was installed ? Can you post your config.txt configuration file ?

@mitu Thanks for your help. It took me a while to confirm things to get back to you. I was wrong about the save states on the Megadrive Mini. The game saves are there. I thought I had to use the save states lest I lose the data.
I have successfully installed Retropie onto my Linux Mint desktop. Thanks!

I may have found a solution, downloaded diskinternals linux file reader, so I can read the files from the card in windows. Then I will copy the roms off and put them on the new install. Fingers crossed

@mitu okay I will comment out the sections for the patches and see if it will build with the added lines in your above post. If I run into issues I will post back. Thank you so much for your help

@shonee That SD card is probably set up in a way that nobody can possibly predict and therefore support cannot be offered according to the guidelines shown in https://retropie.org.uk/forum/topic/3/read-this-first
Only the creator can help you with it.

The best thing to do is install retropie from the official image and follow the first install guide. All your controllers will be autodetected.

@mitu Thanks dude!