No saving state
-
Hello, I'd like to know if there's any news regarding the issue with settings and the engine counter not saving. The problem only occurs in MSFS2024 for me, and it affects every BS product. Every time I launch the simulator, the plane is in its default, first state. This is a major issue that significantly disrupts immersion.
-
No update, since it's been the holiday season. I've been struggling with the recommended techniques for state saving since MSFS 2020, so I'm going to finally use this an an excuse to pressure Asobo to fix the issues once and for all. I apologize that we're going to be waiting for a solution from Asobo in the meantime, but the lack of hobbs time saving is the strong indication that this is a simulator level issue.
-
Is there a chance that state saving will be expanded to other functions/switches? Is it limited by what Asobo provides, or is it limited because it's out of scope for the planned design of the planes?
I love state saving and wouldn't be sad if there would be generally more in Black Square planes.
-
Is there a chance that state saving will be expanded to other functions/switches? Is it limited by what Asobo provides, or is it limited because it's out of scope for the planned design of the planes?
I love state saving and wouldn't be sad if there would be generally more in Black Square planes.
@Tadeus72 I actually have ideas for levels of state saving that I don't think anyone has ever done before within a flight simulator, but the state saving options available to me from the Javascript context are too inconsistent to consider implementing them. Even from WASM, I don't entirely trust the persistence of the files saved within the virtual file system of MSFS, which is unfortunate.
-
I have some other planes with state saving and there it just works (both with new releases and old ones that are multiple years old and were introduced in MSFS 2020), so I'm wondering if they are using Javascript, WASM or something entirely different to make it work. I'm just afraid that just basing on Asobo fixing it might never bring satisfactory results and something more robust and custom might be needed.
That saying, I have no idea how planes are done, so just brainstorming here
Thank you for answering either way.
-
I found a partial solution. After the flight, if I exit the plane with Shift + C, go back to the main menu, change the plane, and re-position it at the airport. Only then do I close the simulator, and the saved data remains. I don't know why this is happening, or why I can't do it the traditional way.
-
Just done some testing among a couple of Black Square planes, it seems like the only part of state saving that still works are failures that were already triggered in the last flights. If I manually fail something and leave, it will be still failed on the next flight. But all of the rest:
- EFB Options and all stuff connected to them
- Hobbs Meter
- Engine Status
- Radios
Are not being saved anymore. It just always shows the same one status from some time ago. From before SU4? Not sure.
I'm wondering if the age of the components is still being counted for MTBF purposes, otherwise the whole failure system is impacted
EDIT: Can confirm the solution above. Avatar mode at the end of the flight > Main Menu > Respawn in the sim seems to be saving data, at least the EFB options, not sure about the rest.
-
Just done some testing among a couple of Black Square planes, it seems like the only part of state saving that still works are failures that were already triggered in the last flights. If I manually fail something and leave, it will be still failed on the next flight. But all of the rest:
- EFB Options and all stuff connected to them
- Hobbs Meter
- Engine Status
- Radios
Are not being saved anymore. It just always shows the same one status from some time ago. From before SU4? Not sure.
I'm wondering if the age of the components is still being counted for MTBF purposes, otherwise the whole failure system is impacted
EDIT: Can confirm the solution above. Avatar mode at the end of the flight > Main Menu > Respawn in the sim seems to be saving data, at least the EFB options, not sure about the rest.
-
Just done some testing among a couple of Black Square planes, it seems like the only part of state saving that still works are failures that were already triggered in the last flights. If I manually fail something and leave, it will be still failed on the next flight. But all of the rest:
- EFB Options and all stuff connected to them
- Hobbs Meter
- Engine Status
- Radios
Are not being saved anymore. It just always shows the same one status from some time ago. From before SU4? Not sure.
I'm wondering if the age of the components is still being counted for MTBF purposes, otherwise the whole failure system is impacted
EDIT: Can confirm the solution above. Avatar mode at the end of the flight > Main Menu > Respawn in the sim seems to be saving data, at least the EFB options, not sure about the rest.
@Tadeus72 said in No saving state:
the only part of state saving that still works are failures
Ah yes, the system where I maintain my own (still cloud based) Javascript avionics state instead of using the recommended technique for aircraft L:Vars, which is now ignored with the rest of the aircraft's state. Thanks for confirming that this is the case. It comports with my current understanding of what's broken in the simulator, and that can be very helpful for explaining things to Asobo.
