No saving state
-
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.
@Tadeus72 said in No saving state:
I'm wondering if the age of the components is still being counted for MTBF purposes, otherwise the whole failure system is impacted
It's percentage based, not tracked hour based, adjusted by your failure rate.
-
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.
-
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.
@dejw6 This works, thanks for the tip!
Tested this few times. It work without exiting plane (Shift+C), and also no need to change plane, you can load same flight again after ending previous flight.
I had Notepad++ and TBM's state.cfg file open in background. Only time Notepad++ offered updated state.cfg file was when I loaded a new flight after I made some changes to planes tablet. -
@dejw6 This works, thanks for the tip!
Tested this few times. It work without exiting plane (Shift+C), and also no need to change plane, you can load same flight again after ending previous flight.
I had Notepad++ and TBM's state.cfg file open in background. Only time Notepad++ offered updated state.cfg file was when I loaded a new flight after I made some changes to planes tablet.@Zwoop68
Thanks for the tip about clicking "restart" once I finish my flight. It seems to fix the Save State issues on my end and also save engine hours and tablet settings.I just registered to this website to say this!
Also a big thanks to Nick and amazing work on his Baron/Bonanza! Can't wait for the Caravan. My wallet is ready! Thanks again for your work.
-
@Zwoop68
Thanks for the tip about clicking "restart" once I finish my flight. It seems to fix the Save State issues on my end and also save engine hours and tablet settings.I just registered to this website to say this!
Also a big thanks to Nick and amazing work on his Baron/Bonanza! Can't wait for the Caravan. My wallet is ready! Thanks again for your work.
-
B Black Square referenced this topic on
-
Hi everyone,
I might be doing something wrong, but trying to follow the steps from @Zwoop68 and @dejw6. When I land from a flight:- Shift + C
- ESC and restart flight?
- Exit.
And my engine - panel state should save like it used to?
Thanks guys, any chance this will be fixed properly in future? As it stands, its quite the downgrade from what it used to be. Any way of having a button to save current state so that it can be loaded again on the next flight. Every single flight is now a chore, as I have to set everything back to the way I want it as it seems to have a saved a state mid-checklist...
-
Shift + C was found to not be needed.
When you are finished with your flying just open the MSFS menu and select Restart. It will restart you in your departure airport with the properly saved state from the finished flight. Now you can do whatever you want to, exit the sim, start a new flight, whatever.
Works for me every time in different BKSQ planes.
-
Shift + C was found to not be needed.
When you are finished with your flying just open the MSFS menu and select Restart. It will restart you in your departure airport with the properly saved state from the finished flight. Now you can do whatever you want to, exit the sim, start a new flight, whatever.
Works for me every time in different BKSQ planes.
-
Dragging up a slightly aged thread, is there still no improvement on state saving following SU6? I guess not based on recent (pre-SU6) posts in the Caravan sub-forum here.
I just came here looking for information on how to transfer my 2020 aircraft persistence data over to 2024, since I now get satisfactory VR performance in 2024 after a modest computer upgrade. I know where the state.cfg files are, but they don't seem to contain any failure-related information. Just engine hours, payloads and tablet settings in a nutshell. So, there must be another file. Some aircraft store data in the "...\LocalState\packages<aircraft-name>\work" directory, but the BlackSquare aircraft don't.
I'm not sure where else to look. Any clues? Is it even transferable?
Why is it important to move over?
On a recent Duke flight I spotted a fuel leak prior to take off. I chose to fix it, but on doing so I saw that I had two other active failures on the tablet... I decided not to check what they were, so I don't (yet) know what perils are ahead and I prefer to keep it that way! But I would like to transfer my slightly 'broken' Duke over to 2024 to carry on flying it there.But if the state-saving isn't working properly in 2024 still (other than with the reload-a-flight trick), then I will stick to 2020 until it's sorted. Flying a persistent aircraft from the last place I landed at is important to my immersion in pretending to be a pilot!
-
Dragging up a slightly aged thread, is there still no improvement on state saving following SU6? I guess not based on recent (pre-SU6) posts in the Caravan sub-forum here.
I just came here looking for information on how to transfer my 2020 aircraft persistence data over to 2024, since I now get satisfactory VR performance in 2024 after a modest computer upgrade. I know where the state.cfg files are, but they don't seem to contain any failure-related information. Just engine hours, payloads and tablet settings in a nutshell. So, there must be another file. Some aircraft store data in the "...\LocalState\packages<aircraft-name>\work" directory, but the BlackSquare aircraft don't.
I'm not sure where else to look. Any clues? Is it even transferable?
Why is it important to move over?
On a recent Duke flight I spotted a fuel leak prior to take off. I chose to fix it, but on doing so I saw that I had two other active failures on the tablet... I decided not to check what they were, so I don't (yet) know what perils are ahead and I prefer to keep it that way! But I would like to transfer my slightly 'broken' Duke over to 2024 to carry on flying it there.But if the state-saving isn't working properly in 2024 still (other than with the reload-a-flight trick), then I will stick to 2020 until it's sorted. Flying a persistent aircraft from the last place I landed at is important to my immersion in pretending to be a pilot!
@Mustang As I imagine you've heard, I have completely redesigned the state saving system in my new aircraft, which will be coming to all my pervious aircraft too. This uses the same technique as my failure system always has. Unfortunately, in order to use this vastly superior system, all of its data is stored in The Cloud. Perhaps there is some trick to link your MSFS 2024 state to your 2020 state, but I haven't heard of one anecdotally.
-
Thanks Nick. Yes, I read about the new approach and appreciate your efforts there. Look forward to seeing the retrofit updates as and when!
So if I infer correctly, at present the failure state of your aircraft is already cloud-stored on the MSFS side as part of each user's profile? Then it's perhaps not so easy to migrate to 2024, though I'm sure there's a local cache somewhere.
I auto-backup the aircraft state.cfg files and 'work' directories for both sims so I don't lose my hours if the computer dies, but seems it's more tricky than I expected to back up everything - and I don't 100% trust Microsoft's cloud (though ironically I'm using OneDrive for my own backups). I had to reset my 2024 cloud profile with SU3 as the sim wouldn't reach the main menu despite reinstalls/resets. If it has happened before it could happen again...
So, now I have a new idea... an 'export/import' feature on the tablet to save/load state files locally. Belts & braces... probably overkill but you can never have enough backup copies, riiight?!
-Martyn
-
Thanks Nick. Yes, I read about the new approach and appreciate your efforts there. Look forward to seeing the retrofit updates as and when!
So if I infer correctly, at present the failure state of your aircraft is already cloud-stored on the MSFS side as part of each user's profile? Then it's perhaps not so easy to migrate to 2024, though I'm sure there's a local cache somewhere.
I auto-backup the aircraft state.cfg files and 'work' directories for both sims so I don't lose my hours if the computer dies, but seems it's more tricky than I expected to back up everything - and I don't 100% trust Microsoft's cloud (though ironically I'm using OneDrive for my own backups). I had to reset my 2024 cloud profile with SU3 as the sim wouldn't reach the main menu despite reinstalls/resets. If it has happened before it could happen again...
So, now I have a new idea... an 'export/import' feature on the tablet to save/load state files locally. Belts & braces... probably overkill but you can never have enough backup copies, riiight?!
-Martyn
@Mustang said in No saving state:
an 'export/import' feature on the tablet to save/load state files locally
I feel the same way, and don't trust anything stored anywhere I can't keep on my desk. Unfortunately, the MSFS architecture purposefully makes it impossible to save files locally from JavaScript. The "work" folder is exclusively for WASM instruments, I believe, but don't quote me.
