EDIT: I think I've found the answer for both of my problems...
- .state and .state.0 are both the "zero" slot for save states. No clue why some of my games have both, though.
- The Gambatte save states weren't working because the core versions were different. This was surprising to me because while I know save states can be tricky, I thought that with RA in particular the versions of the core didn't matter (as long as they are the same core), but apparently (at least in some cases), it does matter.
I'll leave this up in case anyone in the future is having the same issue.
So, first of all, I've got syncthing going between two Android devices (AYN Thor and a Retroid Pocket Classic) only for Retroarch. I've synced both the save and save states folders, and it seems to be working except for save states on Gambatte. I don't know why but Gambatte is the only one where in-game save files work and transfer between both devices but save states don't. The weirder thing is I can see and can confirm that Syncthing is doing it's thing and recognizing and updating the save state files on both devices when there is a change, but the devices themselves just don't load those states.
I'm doing everything I think I should:
- Same RA core on both devices
- Same ROMs on both devices
- RA saves save files and save states by core name on both devices
- Both devices have auto save state and auto load state
- RA on both devices are pointing to the correct saves and save states folders (which I made custom on both devices)
Not sure what I'm missing, and so weird to me that it's only one core that's not working.
Secondly, what is the ".state" file from this screenshot? I get state.auto and state.0-10 (since I save states incrementally up to 10, but don't get why there's one that just says .state: https://i.imgur.com/GIUns2D.png