State saving in the A36 doesn't work
-
I'm having trouble making the state saving system work.
I've read the manual, and both the radios and the fuel should sync when the sim is properly shut down through the main menu quit command (not Alt-F4).
Whenever I hop into the A36, while both making sure the default fuel is loaded and without going to the fuel panel, the aicraft loads with a fresh configuration: radios reset, engine wear always reset, and fuel at half (I've only managed to make it work once).The radios go back to 124.85 (COM1/2, both standby and active freq), VOC 110.5/113.9 (active/standby on LOC1/2), but surprisingly the channel spacing hasn't been reset the last time I tried (remained on 8.33 as I've selected last time on the GNS 430), but it did get reset once.
This is quite frustrating, any way I can fix this?
It could be related to https://community.justflight.com/topic/8915/a36-bonanza-fmc-does-not-register-menu-flight-plan-automatically
-
-
This is also a known bug with the simulator. I have also wasted countless hours trying to understand why state saving does not work for a small number of users, but to no avail. This is a major limitation for me too, because I would do many more and interesting things with my aircraft's state saving and memory if it was more consistent. Since this is an issue experienced by many across many aircraft, you might be able to find hints elsewhere that apply to your specific system. If you do, please let me know so that I can include your findings in my manuals for everyone to see.
-
I have tried multiple actions, to no avail.
I deleted the A36 folder from the Community, then Repaired the installation (all with an empty community folder). Nothing worked except a couple of things that got saved from time to time for no apparent reason, like the Active Failures multiplier and current failures.Funnily enough, I decide to use the installer to remove the package and install it again: it's been the only time I actually saw a save state ever since I formatted months ago, retaining fuel and engine wear (I expedited its wear on the ground) right AFTER reinstallation. The caveat? It was the state of around three attemps prior (which was common, when the feature actually worked). The engine had definitely been fully repaired at some point, instead it displayed exactly the percentage I had before repairing it.
What's funny is that after I quit the game (Avionics off, battery off, Exit button -> Main menu -> Quit game), and then respawned without manually reselecting the aircraft (hence, not changing fuel neither)... it was back as freshly installed: cockpit temp in °F, GNS 750, Failure Rate on 1x (which was often not saved, reverting back to a previously selected one).
The very only thing unchanged was an indicator in the GNS 530: I changed the bottom left indicator to display Cross Track Error (XTK) instead of the default Ground Speed.
So, it looks like when it works, it picks up the state of some sessions prior.
I will keep examining the matter, this time surfing the Internet for more general users. Let me know if I can be of any help.
-
Y Yosyp referenced this topic
-
I manged to get it working somehow reliably two times.
I disabled my VPN as I've read in another forum that State Saving is actually saved onto Microsoft's servers (truly horrible choice), so I figured NordVPN might be a problem.
The same post also told about the importance of choosing the same livery, as SS is tied to that also. This is not on the manual.I noticed that sometimes the livery is pre-selected, some other times it reverts back to the default one. In the first case, I've found it's good to actually select another livery, then select the previous one manually, and some of the variables are recalled: engine health, active failures, fuel on board, windowed open, cabin thermometer. The rest is always reset (including the radios).
