search

batocera-linux / batocera.linux

batocera.linux
https://batocera.org
Other
1.83k stars 466 forks source link

Batocera PCx64 and MAME "incremental save-load(+1) states" persistent problem #9198

Open madman80 opened 1 year ago

madman80 commented 1 year ago

I came from batocera discord channel, where I've been asked to open a ticket here as it seems to be a bug. From batocera v35, as I can remember, there is a persistent bug that don't get fixed. Each time I try so save state (hotkey+west) in a MAME game this is done in slot 2, then if I load state (hotkey+north) batocera tries to load slot 3 (empty). If I save state again now is done in slot 4, and if I load last state is done is slot 5 (empty). So each time I save or load state is done in "current slot +1" I find this behaviour only happens in PCx64. Batocera S905x3 doesn't have this problem. Is there any way to fix this via config files or anything? Thanks in advice.

nadenislamarre commented 1 year ago

hi, go in options and modify the "incremental savestates" options. this is the default behavior to not erase you saves.

madman80 commented 1 year ago

Yes. that is the first thing that i tried, but the problem persist, Anyway, the default behavior can´t be trying to load a future /still not generated) slot. Is has no sense. As I say this problem only happens in batocera PC x64. SAme batocera in Raspberry and TVBoxes save-load is ok.

nadenislamarre commented 1 year ago

but for me, you didn't describe a problem, but the normal behavior.

joinski1 commented 1 year ago

@madman80 on discord you mentioned, that this issue only exists on mame, on other systems like Neo-Geo or megadrive you do not have this issue, correct?

madman80 commented 1 year ago

@joinski1 yes. Only mame games

madman80 commented 1 year ago

but for me, you didn't describe a problem, but the normal behavior.

If so, why the batocera behavior is different for PC compared with s905x3 or raspberry with the same configuration? While playing MAME games:

Normal behavior. Raspberry pi4, s905x3..: 1.(hotkey+west) Save state to slot 0 2.(hotkey+north) Load state from slot 0 3.(hotkey+west) Save state again to slot1 4.(hotkey+north) Load state from slot 1 ... Wrong behavior PC x64: 1.(hotkey+west) Savestate to slot 0 2.(hotkey+north) Load state from slot 1 (does nothing, slot 1 is empty) 3.(hotkey+west) Save state again to slot 2 4.(hotkey+north) Load state from slot 3 (does nonthing. slot 3 is empty) ...

madman80 commented 12 months ago

Any news for this problem? I invite you all to try the fast save state and fast load state function in MAME games to understand the problem and confirm if it is a bug or not. IMHO is an abnormal behavior.

nadenislamarre commented 12 months ago

in fact, for mame, buttons are slot. if you press the button 4, it will save in slot 4. if you press in button 8, it will save in button 8. this is how mame works.

madman80 commented 12 months ago

in fact, for mame, buttons are slot. if you press the button 4, it will save in slot 4. if you press in button 8, it will save in button 8. this is how mame works.

So If I always save state in the same slot (hotkey+button west) it should save always in the same slot number. And If I always load state with the same button (hotkey+button north) it should load the same slot. And that's not what happens. In MAME it always increment one slot independently if you save or load. Even nothing changes If I disable increment save states. I repeat this only happens in PCx64. S905x3 or pi4 should have the same behavior and they don't.