I have set core and game overrides. I have made sure to save RA settings without a game open so it saves the settings i have set up.
When i press save state it IGNORES EVERYTHING and sets the save state slot to 106.
How do I stop this so each game starts at 0 and increments? The first image you see is me testing that setting on and off. I can get it to increment with that on BUT IT STARTS AT 106 and not 0. Why? Maddening.
If you move/rename your retroarch.cfg temporarily and test just that setting does it do the same thing? And are you using a stable or nightly build? if a stable, have you tried a nightly?
Thanks for the reply.
I am using stable 1.22. Tried nightly as well, same deal. I went so far as to manually open retroarch.cfg and look for 106 and set it to 0. I tried again and it still grabbed 106 as a save state ignoring settings ignoring overrides. It is just bizzare.
Currently im cutting my lossess and installing RA fresh and slowly transferring settings over bit by bit. the issue is not present (yet) in the fresh install.
Im really curious what is conflicting to override everything im telling it to do. Ive used RA for well over a decade across many installs and configurations, first time Ive had this issue.
One clue is that on another game I do have real save states upto 106. This made me think the save state number is being used across all games for the given core, but me setting it manually to 0 should override this as I set an override for the core AND the game AND configured the retroarch.cfg manually its just weird why its stuck like that. In past installs it would act like it should; every new game added gets its own save state numbers. RA trying to share numbers across games is bad for countless reasons.
yeah, I think there was an issue with it using the same slot across game but it was fixed awhile back, hence the nightly question. Hopefully, it stays fixed as you set up your config. If you find the offending setting, let me know.
I have not found the issue yet but this started to happen again in a fresh install of RA. Ive bearly change any settings. This time its stick on save state 3.
I dont mean to be entitled, but this is kind of ridiculous. Save state numbering has been nailed down for 30 years inside even the most basic emulation. How is this even happening?
Im going to try the nightly again as of today, but stuff like this is …
Okay, on the fresh install, does it go back to working if you move/rename/delete your retroarch.cfg? If so, and you only changed a couple of settings, that should make it even easier to track down.
I understand your frustration, but bugs happen. If you can help us find the cause, they can be fixed.
Alright I have some time to Ill get more into this.
Step1: Rename retroarch.cfg to retroarch.OLD
Issue: Settings that are needed for saves to work how they should have also been reset, so saves dont work properly at all now. Most notably: “Auto Increment Save Stats Index”
.
Step2:
Im on C right now. Ill post images of what im changing exactly
So im going to start from less to more settings just to make it easier on myself. Navigating in RA is a still nightmare lol.
Next post will be more settings and status of if issue present or not present.
Overrides on the core are off (ill show if I change this). I also check if each setting is really changed by quitting RA and relaunching it and checking if its correct each time.
Changes these from OFF to ON
No issueChanged these from OFF to ON
No issueChanged the following
No issueChanged the directory that saves/states are pointed to. This not only results in it saving to a nice orderly directory, but it also remember the number it last left off at. This is a good thing.
Turned shaders on, 2x video filter and 2 keybinds.
No issue.i will do more testing later. This seems to be a more involved conflict than I hoped.
