Save State is not persisted after exiting the sim (only works when switching flights in-session)

  • Sim Version: 1.6.34.0

  • Frequency: Consistently

  • Severity: Blocker

Bug Description:
Save State does not persist when the user ends a flight and exits Microsoft Flight Simulator 2024. After re-launching the sim, the aircraft loads without the previously saved state (systems state, accumulated flight hours, and other developer-defined Save State values are lost).

The only scenario where Save State reliably works is when the user exits the current flight and loads another flight within the same simulator session (without closing the sim). This behavior is inconsistent with Microsoft Flight Simulator 2020, where Save State persists across a full sim shutdown/restart.

This is a blocker because it prevents users from maintaining continuous aircraft ownership/usage data (such as flight time accumulation) and breaks developer Save State persistence workflows that are expected to survive closing and re-opening the sim.

2 Likes

I can confirm the same type of behaviour in our Airvan. States aren’t saved when exiting the flight, as if the plane stays “loaded” while you are in the menu.

Hi Alex,

It does save the state when you return to the main menu (it’s written to the persistence database). The problem is that it only gets loaded when you start a new flight—and if the user closes the sim, that persisted data can be lost the next time they launch it.

Because of this, I had to implement a WASM-based save-state system instead. The WASM approach stores the state data in the user’s WASM AppData aircraft folder, so it survives sim restarts reliably.

Hopefully Asobo fixes the persistence issue soon, but we can’t wait on it. In the meantime, I can set up the WASM solution for you based on the product name.

1 Like

Hello @Flysimware,

I can also confirm this issue occurs on my 2024-native EMB-110. I am relying on this for the aircraft and EFB settings, but with this issue occurring, now I have to implement a persistent settings system on WASM instead.

Thank you for posting the bug report. Happy holidays BTW, guys (@Flysimware and @SWS-AlexVletsas)!

Regards,
Carlos Daniel González Gómez
NextGen Simulations

2 Likes

Hello @Flysimware

A fix is already on the way to have state.cfg saved when returning to the main menu, following your other bug report: Aircraft load with 50% fuel no matter what - [MSFS 2024] Bug Reports / SDK: Tools/Samples/Documentation - MSFS DevSupport

The case where the player would quit the game directly without going back to the main menu will be reviewed as well.

Regards,
Sylvain

1 Like

Around 20 users have reported the same issue.

One user said the state.cfg is only updated when starting the flight, but never updated during or at the end of the flight.

Another user said he presses “restart flight” when ending the flight to save the progress.

This is new to SU4 and no similar fs20 issue exists.

User reports:

Every time I start the DA42, it’s like the first time. I also noticed the state.cfg file time stamp is not updated upon sim exit. (AppData\Roaming\Microsoft Flight Simulator 2024\SimObjects\Airplanes\COWS_DA42VI\state.cfg). Suggestions please?

same here, MSFS 2024, COWS_DA42VI, with beta, my `state.cfg` timestamp gets updated, but update date/time is when I started a session, not when finished it. the values in there are not what i had in the plane when finishing the session (fuel levels, hobbs and so on). it used to work before su4.

I’ve had similar issues, but found that after a flight,if I go back to the main menu and put the aircraft on another airport it seems to save okay.

All I do is turn the battery on check the service hours before switching off again.

Then shut down my Xbox.

Just FYI, the current easier solution is to click Restart in the menu after the flight. At least it works for planes from other devs that have the same problem after the update so might be worth checking.

In SU4, the only way to force a state.cfg save is to reload the aircraft. So typically, this will happen if you back to main menu and start a new flight with the same aircraft.

Will EFB/JS SetStoredData be affected as well by the fix?

I’m finding inconsistent states between sessions in my EFB app
(Maybe similar to @cdgonzalezgo ?)

1 Like

They’re separate mechanisms so it would be better to track those issues in a separate bug report.

1 Like

This statement was not part of my bug report. But also would be fixed if you get the behavior to work like MSFS20. I was stating that if you go back to the main menu then close the flight you do not save anything. This was a huge shock as this tricked many users. That is why MSFS2020 saves the save state the minute you exit the flight or close the sim from the flight.