Loadout changes will not save
Not sure if this is an issue that anybody else has but since yesterday my loadout changes made in-game have not been saving. Changes will only save and appear in-game if I make them in the companion ...
Forum Discussion
Just for the heck of it I repaired my game and there's still no change :/ Really wish more people would chime in :/
ietxmmyrus
EA Staff
EA StaffHey @MrProEastie,
I didn't encounter that particular issue yet - but probably something similar.
Could you check in Origin if cloud save is enabled and if so, disable it? Then launch the game, change your loadout in the menu. Exit to main menu. Go back to the customization screen. Check if your changes are still present.
Exit the game. Relaunch the game. Check if the loadout has been reset. If so, repeat. Let me know if that works.
Repeated a few times, still no change unfortunately ☹️ I would think that that would've worked of all things, seems the most logical :/
could you please try to edit your loadout on the Companion website, just to see if there´s the same problem?
I forgot to mention it but I tried that earlier and it's the same thing with the companion website as it is with the companion app, only changes made there will stay :/
- ietxmmyrus
Hey @MrProEastie,
if I understand that correctly, your loadout is saved when you edit it in the App, but not in game.
Could you do me a favor and check if this affects ALL loadouts or just specific ones? I had someone else reporting a similar issue hat only affected cavalry and the 1st Assault slot. Thanks!
- Checked a few times to make sure and it seems to affect all loadouts (all slots of the 4 main classes, cavalry, and tanker/pilot vehicle loadouts).
- ietxmmyrus
Alright, thank you @MrProEastie, I'll look into this.
I just wanted to add my voice, as I am facing the same problem with Battlefield 1 on PC.
i have the same problem as the others
I've had this issue.
One way I "solved" it was to choose a different loadout (e.g. Support 2), change that loadout for each class, and it saved.
Issue seems to have fixed itself following this months patch.
