RetroArch (Pi) Save Slot Issue (always #0)

zoop

I am using a kit I ordered from Amazon for my PI setup. The details may be found here: https://www.amazon.com/gp/product/B01LWURJMI/ref=oh_aui_detailpage_o01_s00?ie=UTF8&psc=1

Pi Model or other hardware: PI 3 Model B
Power Supply used: 5V/2.5A Power supply charger for Raspberry 3B
RetroPie Version Used (3.6, 3.8.1, 4.01 etc.. - do not write latest): 4.1
Built From: Pre made SD Image on RetroPie website
USB Devices connected: Buffalo Classic Super NES USB, USB Keyboard
Controller used: Buffalo Classic Super NES USB
Error messages received: No error messages

When I save my game state on my raspberry pi from within any game it always displays a message indicating that it is 'saving to slot #0". Even when I change the save slot to 1 or 2 it always says it is saving to slot #0. The game is correctly saving to the slot I have selected, and I am able to load the states of the games I have saved. This appears to be a purely cosmetic issue, but it drives me crazy and I am always nervous I have saved my state to the wrong slot.

This issue started seemingly at random. I don't recall making any changes. The only changes I have made to my Pi are as follows:

Uncommented the disable_overscan=1
Copied my splashscreen videos to the Pi splashscreens directly so I could use the built in randomizer with my splashscreen video connection.
Overclocking my Pi.

Does anyone have any ideas on what might be causing this issue, and more importantly how to fix it?

bmn001

I can confirm I'm seeing this as well with 4.1.14 in all cores.

You can change state slots as many times as you want, and loading/saving works from each of them. However the visual feedback will always say slot #0, regardless of which slot is being used.

This feels like a Retroarch bug to me. Unless the Retropie team says otherwise, you may want to consider reporting it to them:
https://github.com/libretro/RetroArch/issues?page=2&q=is%3Aissue+is%3Aopen

(I did a quick search and didn't see anything in the open issues about it.)

zoop

@bmn001 said in RetroArch (Pi) Save Slot Issue (always #0):

I can confirm I'm seeing this as well with 4.1.14 in all cores.

You can change state slots as many times as you want, and loading/saving works from each of them. However the visual feedback will always say slot #0, regardless of which slot is being used.

This feels like a Retroarch bug to me. Unless the Retropie team says otherwise, you may want to consider reporting it to them:
https://github.com/libretro/RetroArch/issues?page=2&q=is%3Aissue+is%3Aopen

(I did a quick search and didn't see anything in the open issues about it.)

Well at least I am not alone then :p. Thanks for the response. I will submit an issue later.

TitQuentin

Same problème for me ;)

zoop

@bmn001 said in RetroArch (Pi) Save Slot Issue (always #0):

I can confirm I'm seeing this as well with 4.1.14 in all cores.

You can change state slots as many times as you want, and loading/saving works from each of them. However the visual feedback will always say slot #0, regardless of which slot is being used.

This feels like a Retroarch bug to me. Unless the Retropie team says otherwise, you may want to consider reporting it to them:
https://github.com/libretro/RetroArch/issues?page=2&q=is%3Aissue+is%3Aopen

(I did a quick search and didn't see anything in the open issues about it.)

Opened an issue here. Anyone else experiencing this issue please add your details to the issue:

https://github.com/libretro/RetroArch/issues/4663

Thanks everyone!

bmn001

Looks like the bug's already been fixed! That was quick.

However when I update RetroArch from source in the RetroPie menu, I'm still seeing the original problem...

Xyb0t

I have the same issues
https://retropie.org.uk/forum/topic/8329/psx-savestates-always-0

Although, it feels like it really does only load save from slot #0 .... i have to investigate some more this evening

zoop

@Xyb0t It appears the issue I opened has been fixed and marked as closed.

Not sure what that means in terms of an ETA to be able to install it though...

Maybe someone who knows more can fill us in...

On my end the issue is entirely cosemetic. Tfwiw.

BuZz

@zoop update retroarch from source and you will get the fix (and other changes since the last binary was built - including any new bugs of course)

Xyb0t

I updated from sourceand did a reboot, but the problem persists. Someone in a post above had the same experience..

BuZz

@Xyb0t ah sorry. I locked down retroarch version as it broke too often. Will need to wait for me to update (without making code changes).

zoop

@BuZz I tried updating RetroArch from binary earlier today and after rebooting the same issue is present, so I just assume the changes haven't been pushed/released yet? Or am I doing something incorrectly?

To be clear, I am going in to the retropie setup and choosing to update from binary on RetroArch from the GUI.

Thanks all!

BuZz

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

zoop

@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 :)