146 State Saving Not Working?
-
Most of the configuration options listed above are intentionally not included in the state-saving logic, as each livery has its own custom configuration based on the real aircraft. This affects all exterior equipment, as well as the KG/LBS units on the EFB.
For third-party liveries, livery creators can include a custom livery configuration file for their liveries, which will set the desired external equipment configuration for that livery. Further details on that are listed here: https://support.justflight.com/en/support/solutions/articles/17000124988-146-professional-msfs-paintkit
For all other State Saving related feedback, it is possible for the state saving to get confused between updates, especially updates as large as v2.4, as the aircraft may be attempting to load a state that was only possible in a previous version of the product. One thing I'd recommend trying is deleting the StateSave.ini file from the following file directory, and it'll then regenerate the next time a flight is loaded with the 146 with the correct state saving options available.
MSFS 2020 - MS Store:
C:\Users*USERNAME*\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe
LocalState\packages\justflight-aircraft-146\work\PanelSaveMSFS 2020 - Steam:
C:\Users*USERNAME*\AppData\Roaming\Microsoft Flight Simulator\Packages\justflight-aircraft-146
work\PanelSaveMSFS 2024 - MS Store:
C:\Users\USERNAME\AppData\Local\Packages\Microsoft.Limitless_8wekyb3d8bbwe\LocalState\WASM\MSFS2024\justflight-aircraft-146\work\PanelSaveMSFS 2024 - Steam:
C:\Users*USERNAME*\AppData\Roaming\Microsoft Flight Simulator 2024\WASM\MSFS2024\justflightaircraft-146\work\PanelSaveHope that helps.
Mark - Just Flight
-
I will talk with the livery creator for my VA; I don't know that he cares as much about the antennas (that's a personal preference), but I'll beat on him until he fixes the EFB unit default.
I will try deleting the .ini file and see if that fixes the system state, at least.
EDIT: what would happen if there was no livery configuration .ini file? It would just load the plane's default settings and equipment?
-
Most of the configuration options listed above are intentionally not included in the state-saving logic, as each livery has its own custom configuration based on the real aircraft. This affects all exterior equipment, as well as the KG/LBS units on the EFB.
For third-party liveries, livery creators can include a custom livery configuration file for their liveries, which will set the desired external equipment configuration for that livery. Further details on that are listed here: https://support.justflight.com/en/support/solutions/articles/17000124988-146-professional-msfs-paintkit
For all other State Saving related feedback, it is possible for the state saving to get confused between updates, especially updates as large as v2.4, as the aircraft may be attempting to load a state that was only possible in a previous version of the product. One thing I'd recommend trying is deleting the StateSave.ini file from the following file directory, and it'll then regenerate the next time a flight is loaded with the 146 with the correct state saving options available.
MSFS 2020 - MS Store:
C:\Users*USERNAME*\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe
LocalState\packages\justflight-aircraft-146\work\PanelSaveMSFS 2020 - Steam:
C:\Users*USERNAME*\AppData\Roaming\Microsoft Flight Simulator\Packages\justflight-aircraft-146
work\PanelSaveMSFS 2024 - MS Store:
C:\Users\USERNAME\AppData\Local\Packages\Microsoft.Limitless_8wekyb3d8bbwe\LocalState\WASM\MSFS2024\justflight-aircraft-146\work\PanelSaveMSFS 2024 - Steam:
C:\Users*USERNAME*\AppData\Roaming\Microsoft Flight Simulator 2024\WASM\MSFS2024\justflightaircraft-146\work\PanelSaveHope that helps.
Mark - Just Flight
-
@paulC I think I might have an idea now.
I suffered from the same issue, with 1 eternal load - back then load again, and it spawns, but either with every switch in a very odd state (examining the state save file, everything was set to 0.0) with all switches in silly positions and the tablet not fully working, or the WASM crashed state withe the yoke deflected and the orange error message.
Finally got it working for a flight tonight, when I only set a starting point and no ending point for my flight.
Normally I would set my starting stand and select the arrival airport (as it could supposedly improve performance with preloading more stuff from the destination - not sure it actually matters though!). Every combination failed when I loaded with a destination already in, despite deleting the statesave and restarting etc. but worked first attempt without a destination and again deleted statesave.ini
Too late for me today to try examine more today, but it might help you.
If you want to use the built in ATC, it should be possible to send a route to ATC with the MSFS tablet after loading in. -
@paulC I think I might have an idea now.
I suffered from the same issue, with 1 eternal load - back then load again, and it spawns, but either with every switch in a very odd state (examining the state save file, everything was set to 0.0) with all switches in silly positions and the tablet not fully working, or the WASM crashed state withe the yoke deflected and the orange error message.
Finally got it working for a flight tonight, when I only set a starting point and no ending point for my flight.
Normally I would set my starting stand and select the arrival airport (as it could supposedly improve performance with preloading more stuff from the destination - not sure it actually matters though!). Every combination failed when I loaded with a destination already in, despite deleting the statesave and restarting etc. but worked first attempt without a destination and again deleted statesave.ini
Too late for me today to try examine more today, but it might help you.
If you want to use the built in ATC, it should be possible to send a route to ATC with the MSFS tablet after loading in. -
Wow, that was unexpected.
I deleted both the JF_146.ini file and the StateSave.ini file from the WASM folder. I ended up deleting both because I forgot to when I started MSFS after the SU4 drop today, and when I applied AC power to the aircraft every single bell, whistle, and alarm started screaming at me, the wipers freaking out, the whole airplane was possessed. Scared the hell out of me because of the sudden onslaught of alarms and flashing lights. Oh, and the EFB had disappeared.
After deleting both and restarting the sim, I loaded in, set the EFB to LB, and just started up the APU and the FMS to see if there were any funky WASM errors happening. I hit End Flight shortly after getting her partially powered up, then loaded back in.
To my surprise, she was quiet from the outside, but on entering the aircraft proper I was greeted to the same light state, the APU running, the master switches all on, and pretty much everything how I left it except the FMS/Radar was off and the handful of things covered by the livery options Mark mentioned above. It even kept the EFB set to LB this time.
I was a doubter but so far so good for me.
-
More testing after the b update today. First load gets stuck and generates a failed state save file with zeroes in every variable. Press back and don't even exit the sim. Simply go out in the file system and delete the state-save file found as described in Mark's post above.
Now load in again, and it loads quickly and properly without starting in some bad state with switches in stupid positions and the tablet not working or with a WASM crash.With wasm already built on 2nd load and no corrupt panelstate everything seems to load quickly and functionally.
