[MSFS 2024] No tablet state saving between flights
-
Hi,
the settings I made in the tablet are not saved after a flight, even if I end flight to main menu, wait several minutes and then properly close MSFS (not through the "x"). Upon next flight everything is re-set to default and I have to start all over again.
However the pressure altitude preset is saved.
For me the 2024 state saving option is faulty. What can I do?
Regards,
Stefan
-
State saving is faulty for a lot of us, and worse in MSFS 2024, it seems. There are lots of conversations about it online, but no conclusive fixes for everyone, from what I've seen. Some say that virus checker settings were responsible, some say it's firewall/network settings, recently someone reported that changing the default registration of the aircraft might cause it to break. Trust me, I would love to get this fixed as much as you, or I suspect much more!
-
Wouldn't it be possible to save the tablet setting in a local .ini file?
-
I wish it were, but we cannot write to any files from JS. Only WASM can write to local files, and there are many reasons why I don't use WASM. The best reason for my users is that WASM is more prone to CTD and performance degradation issues.
-
Ah, didn't know that. Thanks!
Also understand the decision not to go for WASM.
-
I've had the opposite experience: state saving is working fine for me, even on the GeForce Now service where the state isn't preserved at all for most third-party aircraft (likely due to WASM saving to a local file that is deleted post-session). I now understand from Black Square's post that this is because the TBM 850 does not use WASM, which is actually excellent news for cloud simmers like me.
-
I've had the opposite experience: state saving is working fine for me, even on the GeForce Now service where the state isn't preserved at all for most third-party aircraft (likely due to WASM saving to a local file that is deleted post-session). I now understand from Black Square's post that this is because the TBM 850 does not use WASM, which is actually excellent news for cloud simmers like me.
@VT I'm glad to hear that there's some benefit, because it's been an unfortunate struggle to deal with Asobo's sometimes-working/sometimes-not native state saving. Unfortunately, I suspect you are in the minority, but I appreciate you sharing. There are so many ways that people use my aircraft on so many different platforms, the only way I can learn about these things is if you share them with me!
-
@Black-Square You are absolutely right! For example, after MSFS 24 became available on the GeForce Now service, and in addition, they upgraded the GPUs to the 5080 this year, MSFS has become quite popular there because it runs so incredibly well on it.
However, GFN is very restrictive regarding what exactly is saved between gaming sessions. For this reason, there are constant issues with saving state or even basic settings in custom EFBs for most third-party aircraft. But, despite these problems, I still purchased the TBM 850 after it appeared on the Marketplace, and I was very pleasantly surprised that state saving works perfectly! Looks like this is yet another, albeit non-obvious and very specific, advantage of not using WASM.
