Save files getting corrupted (Frankische Symphonie campaign)

[SchDerGrosse]

First of all, amazing game.

Completed the Czech and the Big Red One campaigns without any issues.

Jumped into the West German campaign and my save files are constantly getting corrupted, due to which i have to roll back 1-2 cycles.



Is there any way to prevent it? Is this campaign specific?

I also observed some weird behaviour, not present in other campaigns, like unit not moving despite being ordered to, artillery not firing although a barrage order was put in place.

[SgtZdog]

Can you upload one of the corrupted saves here please for us to inspect (and ideally the last good save you have for it too, bonus points for a save that is corrupted and then 1 order phase earlier is good).

[SchDerGrosse]

Sure, there you go.

The 0739 hrs save works, the 0802 and anything past that (made multiple saves during the cycle) doesnt.

[SchDerGrosse]

Got a another corrupted save file on mission 3.

Any update on whats causing it and how can it be prevented?

It is really taking away from the enjoyment that I have rigorously make manual saves to minimaze the chance of appearance of this bug.

Thank you,

[CapnDarwin]

I'll ask on today's Dev call and see if there is an answer to the problem. Thank you for your patience.

[Zumwalt_446]

Hi all,

I have encountered the same issue in Scenario 1 of the Canadian campaign. Saves are attached for 44% progress (which loads successfully) and 52% (which does not).

Hopefully this helps somewhat in diagnosing the problem.

[CapnDarwin]

Thanks for the info and save. I alerted the team to this issue, @Zumwalt. We are looking into it.

[SgtZdog]

Sorry for the delay getting back to this.

@SchDerGrosse, the saves you attached load just fine for me. I'm not sure if you uploaded the wrong ones by mistake, or perhaps it is some other problem that we have already fixed.

@Zumwalt_446, your issue is one I've created a ticket for already as we got a report of it on discord, it is FPSS-7177 and I will add your saves to the ticket as additional test data. Thank you for your help.

[SchDerGrosse]

Thank you for your answer.

I do multiple saves per cycle. After the save I exit the game and check whether it loads.

Now I have encountered the 4th failed save load state.

1. MIDGAME_33 260805_2036 @ 27_pct__1241_hrs" -> loads fine

2. MIDGAME_33 260805_2036 @ 31_pct__1306_hrs -> loaded fine when i 1st made it

3. MIDGAME_34 -> issued some orders, made the save, exited the game then it failed to load AND made save 2. corrupted too.

Already verified the the game files integrity.

[WildCatNL]

Yesterday, we found and fixed a problem causing the campaign scenario not to load.

A potential (non-confirmed) work-around is to first load another, non-campaign scenario (all the way to seeing units on the map), exiting to the main menu and then resuming the campaign scenario.
If you try this, please let us know if this avoids the problem.

[SchDerGrosse]

Yesterday, we found and fixed a problem causing the campaign scenario not to load.

A potential (non-confirmed) work-around is to first load another, non-campaign scenario (all the way to seeing units on the map), exiting to the main menu and then resuming the campaign scenario.
If you try this, please let us know if this avoids the problem.

Thank you again for the quick response.

Tried it with the "Hunting in the woods" scren. Loaded the scren up, messed around a little, went to main menu, tried the faulty save, but unfortunately got the same "access violation etc." error message.

Just a quick clarifying question, the files that I have uploaded in this topic do load properly for everyone else? (see SgtZdog's post)

Thank you,

[SchDerGrosse]

And another one...

1440 loads 1503 doesnt.

[SgtZdog]

@SchDerGrosse, I loaded your last 2 batches of saves in my Steam copy of the game and got the same results as you. Then I loaded them up in my local dev build and they all loaded just fine, so I think whatever the exact problem your experiencing is, is now fixed and should not be a problem whenever we release the next patch. Apologies for the inconvenience.