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

@thomas-ap said in SAVE STATE STUCK AT 0% ISSUSES: @pokevania I checked my SD and it's at 4 gbs so I know it's not a storage issue How large is your SD card ? Depending on the size, 4Gb might be under 5% of its capacity and you might have issues writing to is, since - by default - 5% from the formatted capacity is reserved for the root user. Do an experiment and remove one of the larger disc images from the your ROM set, freeing up some more space. See if you can save.

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

@radiusxe The best you can hope for is to load the save state from the previous core version and work your way to an area that allows for a normal memory save. Afterwards, update the core load the save and make a new save state. I realize this wouldn't be possible for all games and it's a major hassle, but it's really the only option. It's best to only utilize save states for very casual use and at no time when it's crucial to keep them for long periods of time. Save state formats can change at any time depending on development. You might see an emulator/core keep its format throughout its lifespan, or you might see it change several times a year.

@rustymg Ooh, that's odd. I just use the joystick, if that doesn't work I have no idea what to suggest.

Thanks @dankcushions I didn't knew that I needed the parent rom. Problem solved. It's up and running. Now I can save my progress in Pacman. Thank you all. @mitu and @jonnykesh You've been a great help.

Maybe your changes messed up your retroarch.cfg files. It might help if you give us your configuration for savestate_directory. Can you run this and give us the output: cd /opt/retropie/configs grep -r 'savestate_directory' ./

I fixed my problem with the Y cable. The savestate are more faster, but it long.... So I have mounted my external hard drive manually by editing the fstab. All works but with Y cable only.

@matthimself no worries :) now get raising chocobos and cry when [REDACTED] ... or whatever happens on disc 2 (i forget!)

@BuZz said in RetroArch (Pi) Save Slot Issue (always #0): @zoop see my post above. You can't update automatically to include that fix currently. You need to wait until I update retroarch, eg for v1.4.2 - the module doesn't build the bleeding edge code anymore. I got fed up fixing things over and over again. Yeah, sounds like a reasonable approach. Thanks for the update. I will eagerly anticipate 1.4.2 :)