[PC]Possible solution for loadout resets and other Issues connected to the saved data.

#1

It seems like I’m onto something here, I just tested it succesfully and it could be a viable solution for some people that are being haunted by loadout resets and other Issues where deleting the saved data is the only solution.

This process should result in having only to restart the game instead of deleting your files and re-creating your complete loadouts and configuration.

I went to %localappdata%\SpaceFish\Saved\SavedGames and set the properties of UserSettings.sav to read-only. <-- This is basically all you need to do. You can just copy/paste this path into your Windows Explorer.

Then I opened the game and messed around with my profiles, changed names, switched weapons, etc.
Started a match, everything like I just changed it.
Closed the Match, Loadout is still like I just changed it.
Then I restarted the game, and now the Loadouts are again just like they were when switching the files to read-only!

The awesome thing is that I was still able to change the Loadouts in-game and play with the recent changes, but restarting the game would revert the loadouts and configuration back to their initial state that I saved.

You still need to change the file properties again to make permanent changes to your loadouts, but first tests showed it actually seems to prevent those Loadout Resets!
So it should offer a convenient and time-efficient solution against any loadout-related Bugs by just restarting the game.

I would need other people to verify this method, especially people who frequently need to delete their saved data because of bugs.

@OldKingHamlet and @Courier:
Maybe this could be also helpful for your Developers!
They could change the code so that the Loadouts are only able to change while being in the Customization Menu.

[Disclaimer]: I have no coding background and cannot say this is safe to do!

The file UserSettings.sav seems to be responsible for the Loadouts and controller Options, this is also the file you can backup if you want to save different loadout profiles.
The other file in the folder called PlatformSettings.sav seems to be responsible for your Graphics Settings.

5 Likes
#2

Little Update: A friend of mine tested it, and it actually even prevented his Loadouts from resetting.
It was reproducible in his case, since his Loadouts always reset when he has leftover equipment points and leaves the 3rd equipment slot open.(Both Pred and FT)

But he is then stuck with his loadouts from before, when restarting the game, which is what I also experienced.
Now we just need to find out how to save his Loadouts after repairing.

He also sent me his file and I noticed that his is 2KB smaller while we both have the same Shaders and DLCs. (16 KB opposed to 18 KB)

#3

I’m not as pc friendly , so forgive me if this is a stupid question . Why would that certain file not be read only anyway? If it was read only from the start would that mean you couldn’t customise you’re loadouts in game at all? , ah I done another read over , so with read only you can change loadouts etc but if the game is closed it reverts back to the base setup?

#4

Yes right.
So if you have regular problems with loadout resets you can create a base-set of loadouts you will always play and make those read-only.
That way this base-loadout will always reappear when restarting the game.

This can be especially convenient for players like me who don’t change their loadouts much often.

1 Like
#5

The explanation for this behaviour might be, that, at the start of the game, said UserSettings.sav is loaded into memory and from then on, the data in memory is taken. If you change your loadout, the loadout in memory is changed. At the end of the game one would expect said memory data to be written back to the hard disc (means to said UserSettings.sav file) - so that the next time, the game is started, the user data is up to date. By making said UserSettings.sav file read-only, you prevent (just) that last step of saving - which then just fails - which leads to “resetting” data to the time point, when said file has been changed to read-only.

If this prevents the system from the resetting of the loadout bug, then the underlying error probably can be found in the routine exporting the memory data to the hard disc and obviously corrupting said user settings file.

1 Like
#6

Exactly!
I also noticed there are several points where the file is being read/saved where we get those reset bugs, though the game seems to temporarily save the loadouts somewhere else(like you said) even while it is read-only which makes playing with recend changes possible

The points that I found so far are:

  • Opening upon opening the Customization Menu
  • Opening and saving(point where it produces reset bug) when opening and closing a specific Loadout
  • Opening and saving(point where it produces reset bug) after closing the Loadout and going back to Customization
  • Opening and saving(point where it produces reset bug) joining a Lobby

I personally get most Loadout resets upon joining a lobby, and iirc that would also be the point where the game sometimes validates if the chosen loadout is possible or not.
For example when I’m using an impossible loadout from a previous patch, it would usually then reset on purpose, maybe this validation process also happens on other points and produces the bugs, since I would just override it by making the file read-only.

That my friends file is smaller, while we have the exact same stuff and produces bugs even for me if I use it proves your point.

Another Interesting(and disturbing) thing I found out in this process is that also the Shaders and DLCs seem to be saved in one of the local files, what makes those also prone to exploitation…
While testing and discussing the Loadout File I met somebody who was able to transfer his DLCs and Shaders to a Lvl 1 account and play with all perks, classes and weapons unlocked, even special classes like DLCs.

But the Player Level, Veritanium, Field Lockers and Bonus Tapes are saved on Illfonics servers.
They should probably move the rest there too, then the -1 Bug would affect that too, but that wouldn’t change anything regarding that bug. lol