State Saving not working
-
I have had so many more people report this to me since my aircraft were updated for MSFS 2024 than ever before, and suddenly, so I am left believing that this is a simulator problem. The best evidence for that is that people are reporting that the Hobbs time is not being saved, which I have absolutely nothing to do with. It's been a core feature of MS Flight Sim since at least the 80's. There are some suggestions online about clearing caches or changing firewall settings that might make a difference. If you can learn anything, please let me know!
-
I have had so many more people report this to me since my aircraft were updated for MSFS 2024 than ever before, and suddenly, so I am left believing that this is a simulator problem. The best evidence for that is that people are reporting that the Hobbs time is not being saved, which I have absolutely nothing to do with. It's been a core feature of MS Flight Sim since at least the 80's. There are some suggestions online about clearing caches or changing firewall settings that might make a difference. If you can learn anything, please let me know!
@Black-Square Just to clarify, does that mean there’s currently no state saving implemented for MSFS2024? I don’t want to sound like I’m just comparing developers, but I’ve noticed that some others have managed to get full state saving working in 2024 (I think we all know which ones!).
I really do appreciate all the support and communication you’ve been providing here on the forum and it means a lot. That said, I feel like saying it’s purely a sim issue might not fully explain the situation, especially since this feature was mentioned in the manual and a specific feature i was really looking forward to.
I completely understand that state saving might not be at the top of the priority list right now, but would it be possible to take another look at it and see if there’s any way to make it work in the future?
Thanks so much for your time and for all the effort you’re putting into this project!
-
It should be working in MSFS 2020 and 2024. I use two methods for state saving, one for avionics, and one for general aircraft variables. Both are recommended by Asobo, and both save to their cloud servers. Unfortunately, neither have been perfectly consistent since the release of MSFS 2020 for 100% of users. However, it appears that something suddenly got significantly worse in MSFS 2024 since about SU3. Now I have people reporting that Hobbs time is not saving, and neither is the last used livery, both of which are entirely unrelated to my aircraft. There is a third method for local state saving, which is probably what other developers are using, but it is only accessible via Web Assembly, while I program in JavaScript. I prefer JS over WASM for many reasons, but for my users, the biggest difference is that WASM is much more prone to CTD and performance degradation over time. I will see if we can renew conversation with Asobo about state saving given this apparently recent regression.
-
To confirm, I find that nothing is being saved. Not the avionics, Not the fuel, Not the state of the chocks etc. And this is after diligently and gracefully ending the flight and closing the sim. Where is this data supposed to be saved? I'd like to do some investigation, I wonder if it's a os permission issue..
-
It must be something local, because it seems to be consistently inconsistent for only come users. Unfortunately, as with most things in 2025, the data is saved to the cloud.
-
Similarly, whenever I exit the game, the fuel data is not saved.
-
It must be something local, because it seems to be consistently inconsistent for only come users. Unfortunately, as with most things in 2025, the data is saved to the cloud.
@Black-Square maybe there's a thread with a problem on the MSFS2024 forum? I think we could be more active. because it's very important to many people
-
State saving makes a huge difference to the feeling of ownership and continuity. Doing multi-day trips where not even the fuel is saved is very immersion-killing. I can understand the developers frustration as well since it is a platform api that's unreliable. I'm going to use 3rd party addon to save the basics in the meantime.
