@windg thank you, I will try that asap.

Are the savestates of the different systems always stored in the rom folder?

For RetroArch based emulators, yes. Other standalone emulators may choose to save to different locations, depending on their implementation and it's not always in the system's folder (e.g. Mupen64plus, PPSSPP, etc).

How about dos games, are the savegames always in the folder of the respective game?

Most likely yes, by default the game folder is set-up in Dosbox as C: driver by default, so saves should go there.
If you're using a different set-up to start the games (using .conf file and/or a separate folder for PC games), then this may vary.

I'm not that big of a shell expert, the only thing that comes to mind right away is to copy the savegames and states by hand before mirroring them again so that they don't get lost. Does anyone have a more elegant way that is easy to do?

Use a NAS to share the ROM folders between the 2 systems ?
You can also use the roms share from one of the Pis as the network share for the 2nd Pi, using the same guide referenced above.

@Ashpool said in rgui - load/save state option missing:

May I ask(/wonder) why update_packages_gui_setup() calls updatescript_setup(), but basic_install_setup() ain't doing that?

Not sure I fully understand.
Basic setup is meant for a new installation, which assumes you are doing a manual installation. This means you just cloned the RetroPie repository, so there's no need to update again the script.

Hm, save states are not portable also between emulators, so as a starting point you should use the same emulators when testing.

But since you're using a Pi 0, the same emulator from the Pi3 may not be available or perform well enough to be a viable alternative on a lower spec system.

@br23z please fill out https://retropie.org.uk/forum/topic/3/read-this-first

including relevant config files (/opt/retropie/configs/all/retroarch.cfg and the one for the system in question) and verbose log.

@mitu Yep, exact same name, cut and pasted to avoid any errors. I think this is a hopeless case tbh, the saves I'm using behave extremely weirdly and I suspect there's just no chance of transferring them over but it never hurts to ask in case someone knows of a conversion tool or the like.

@Zangdaarr Another Late Reply - I came across this while trying to figure out why Hi Scores were not being saved while trying to write using ROMS on a network share. I had given the User I had created access rights, however, I believe that the rw (read/write) and the file/dir mode of 777 (read, write and execute (I believe)) is the secret sauce. Glad that this is in the User Guide...but, just overlooked by me until today.

@mitu That was indeed the problem, using the same emulator fixed everything! Thank you so much, I was going crazy there for a while. Merry Christmas to all of you!

Thanks for the reply!

You can launch discs for supported cores by starting any rom for the system in question first (which avoids having you to load up a core first before launching a disc) and then selecting "load disc" from the retroarch menu.

You're right, defining a per-system folder for the savefiles is a good idea, but it doesn't help with the save states, which is indeed a retroarch problem.

@mitu Thanks that did solve it, was able to save emulator settings. Just uninstalled and then update retropie setup script =D

@deskjobo

@deskjobo said in SAVE STATE STUCK AT 0% ISSUSES:

@theotherdan Thank you so incredibly much for your response. I followed both sets of steps you gave, and my results are as follows:
After using df -h my available storage is shown to be 785M out of 3.3G size.
For the command ls -al /home/pi/RetroPie/roms/ all the emulators appear to have 'pi' in both the user and group, as well as all the correct modebits.

Is 785M enough of an available storage or could that be the cause of the problem?

ps. All my roms are stored in a usb drive instead of in the sd card with the image.

@deskjobo
785M will be 785 Megabytes, so a decent amount of space. For save states, I would say that space is not an issue..
Now, since you are not using the default location for saving, you will need to adjust the process a bit.
You can look at /opt/retropie/configs/all/retroarch.cfg by running 'cat /opt/retropie/configs/all/retroarch.cfg'. This file should show you where the save states and saves games are stored:

#Save all save files (*.srm) to this directory. This includes related files like .bsv, .rtc, .psrm, etc ...
#This will be overridden by explicit command line options.
savefile_directory = "/media/usb0/savefile" <--

#Save all save states (*.state) to this directory.
#This will be overridden by explicit command line options.
savestate_directory = "/media/usb0/savestate" <--

Based on the output, and where the USB device is loaded, you will have to append the command to meet it:

sudo chown -R pi:pi /media/usb0/<emulator>

Let me know how that turns out.

Ok thanks for the reply. I will do that. Thanks

Maybe @jandalf81 gots a script solution in his pocket: [SCRIPT] Setup script to sync saves to cloud services

@mitu I'm going to look at it thank you very much !

@jandalf81 Interesting..thanks!

again.... playstation games..... and the snes9x2010 emulator lol i figured i wouldnt find a answer on here im pretty sure the official power supply is enough

just posted a issue with re3 having load issues.... the guy wanted to know what kinda power supply i was using LMFAO outa 166 games why does the type of controller i use a issue at all.....

@rmigd it depends on the emulator, if not handled properly, size of savestates can be different between 32 and 64 bits. Most likely your android device is using arm64 retroarch while your rpi is using arm32 retroarch.

Hi Mitu,
Sorry about not posting that information, must've missed that post. I started collecting the data, but while I was running through it I decided to run the following commands:

sudo apt-get update
sudo apt-get upgrade
sudo apt-get install alsa-utils

After that my save states worked normally even with auto-login enabled. When I originally updated the device was when the save states stopped working, but I guess now that has been figured out :)

Sorry for the late reply... ;-(

@joelkolb I'm glad you like this. I did this more as a "proof of concept" since I don't really use save states. There will very likely be a whole batch of errors in this scripts... ;-)
Nevertheless, I corrected the script to work with games with dots in their names. If you install the script now, this should work out of the box.
As for the timer, that can be changed from inside RetroPie. The setup added a configuration script to the main RetroPie menu

@cyperghost Thanks for helping with the quick fix!

@robertybob I have no intention of adding any of my scripts to the "official" RetroPie setup. This is more of a side project or hobby to me. Having more users means having more problems as my scripts have not been thoroughly tested. This would create frustrations on all sides. Now, if someone were to fork my projects and take over support for that fork... I wouldn't have a problem with that.

@ExarKunIv You either need to manually activate the setting to create a thumbnail on saving states or the first savestate won't have one. If you use my script to start a ROM with a savestate that setting will be set to TRUE by the script. This will be done per system, as @joelkolb said

@montecore >Sounds like there's nothing that can be done

Well, you could manually recompile it from an earlier version to get back to where it was but as far as converting the savestates I'm not aware of any method