Increment / Maximum Save States issues

[jayare5]

I'm using 2 options:

• Increment Save State Index Automatically
• Maximum Auto-Increment Save States to Keep

This has the following issues:

1. Setting a maximum number of savestates is meant to delete the savestate with the lowest number, but it does not delete the corresponding screenshot. I expect it to delete that too, or else the menu will show screenshots with non existent savestates, and there could be tons of files occupying space.
2. It can go beyond 999, which is the limit selectable savestate. You can access savestates over 999, but only the first time as the menu will appear with a value over 1000 selected. If you go back below 1000, the limit will be 999 again and the next value is Auto and then 0, as if there weren't savestates with 1000+ value. I expect to be able to select a value above 999 if the savestates exist.
3. I would prefer if it went back to the lowest existing savestate and replace it instead of deleting and continuing to increase the number. For example if we limit it to 3 states, I expect it to go like this: 1-2-3 - 1-2-3 - 1-2... instead of 1-2-3-4-5-6-7-8... I guess that would make the first issue pointless if reprogrammed this way :P but the way it works currently, you can limit it to 3, but if you made 500 save states, the only 3 save states available will be 498, 499, 500. While having all 500 screenshots in the folder but only those last 3 save states. It's kind of messy, but specifically bad if we go over 999.

These things probably apply to replays / auto increment replays too.

I'm using the latest version of RetroArch.

Thanks!

[Lolight2]

This has been a huge issue for me too, I hope your voice gets heard here since this is the biggest problem Retroarch currently has for me.

[zoltanvb]

Thanks for the heads up. Yes, #16836 + #16845 covers 1., while #16947 covers 3., and prevents 2. to happen in the future.