@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.
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.
@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.
@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
@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
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.