cannot recharge battery and other issues after update to 1.3
-
After updating I hopped in the Tomahawk today and I noticed during the walkaround that my battery was low, at 0.0v. Everything else was fine, at 100% except for the engine which was around 99%.
I tried to recharge the battery but nothing happened. I then tried replace the perfectly good spark plugs and I heard the sound of tools "fixin' things"
I then went inside again and turned on the battery, assuming it needed to be switched on for it to be recharged.When again in the walkaround mode, it still did not charge, but I did notice that my spark plugs were suddenly at 39%. I then checked my engine condition and it also was 39%, while it was closer to 99% before.
I disabled state saving, overhauled the aircraft, switched to random state, disabled wear & tear and failures but nothing seems to allow me to recharge the battery.
If the battery was broken at least the overhaul should have fixed it but it didn't.I will try and delete the actual profile of the aircraft within the MSFS files and see if that fixes things but I shouldn't have to.
Any idea what went wrong?
-
I deleted the files in the "LocalState...\JF_PA38_Tomahawk" and "LocalCache...\justflight-aircraft-pa38\work folder, except for the userinfo.txt, which I thought might contain the licence info and could cause issues when removed.
After that I started MSFS again and loaded up a flight and did the walkaround.
I noticed that the flaps and ailerons were moving, which they did not do in the previous walkaround. I know they did before the update.The battery issue is now fixed. I will need to check whether all the files I have removed have been recreated automatically. I have the original files backuped just in case.
Since my Tomahawk is in a brand-new state now I hope the gremlins from after the update are gone. I'm now taking it for a flight to enjoy the update.
-
We aren't able to reproduce any of these issues on our end with v0.1.3, but with the 'State Saving' option having been enabled on the EFB and with how deleting the state saving folder fixed the issues, we suspect this may have been a quirk with the State Saving logic being enabled between updates. For instance, some of the parameters that the aircraft had saved in v0.1.2 may have been changed/removed/updated in v0.1.3, and that may have prevented the aircraft from correctly loading the save state on that first load after the update. I'll log this on our internal bugs/feature request tracker to investigate further and to see if we can prevent this from occurring in future updates.
If this does occur again, try disabling "State Saving" on the EFB and then restarting the flight. That should load the aircraft in the default state and will still retain all of your other wear/tear/engine hours. You should then be able to reenable "State Saving" and continue to use it as you did prior to the update.
Mark - Just Flight
-
