state.cfg settings

Wothan

Are You sure You are looking into the right Stat.cfg ?

My path is:
C:\Users[user]\AppData\Local\Packages\Microsoft.Limitless_8wekyb3d8bbwe\LocalCache\SimObjects\Airplanes\bksq-aircraft-caravanamphibian

And the content:
[LocalVars]
var_radio1Mode=0
var_radio2Mode=0
var_globalFailureRate=1
var_engineDamage=0.561118
SAVED_FUEL_QTY_L_pct=48.327589
SAVED_FUEL_QTY_R_pct=51.672298
SAVED_PAYLOAD_PILOT_lbs=170
SAVED_PAYLOAD_COPILOT_lbs=170
SAVED_PAYLOAD_1_PAX_lbs=0
SAVED_PAYLOAD_2_PAX_lbs=0
SAVED_PAYLOAD_3_PAX_lbs=0
SAVED_PAYLOAD_4_PAX_lbs=0
SAVED_PAYLOAD_5_PAX_lbs=0
SAVED_PAYLOAD_6_PAX_lbs=0
SAVED_PAYLOAD_7_PAX_lbs=0
SAVED_PAYLOAD_8_PAX_lbs=0
SAVED_PAYLOAD_CABIN_CARGO_lbs=0
SAVED_PAYLOAD_CARGO_POD_1_lbs=0
SAVED_PAYLOAD_CARGO_POD_2_lbs=0
SAVED_PAYLOAD_CARGO_POD_3_lbs=0
SAVED_PAYLOAD_CARGO_POD_4_lbs=0
var_OxygenPressure=1850
var_RadarMode=3
var_Visor_L=0
var_Visor_R=0
BKSQ_UnrestrictedBeta=1
BKSQ_NewStrobeEffect=1
BKSQ_ShowCopilotInterior=1
BKSQ_VatsimClientMonitorBoth=0
BKSQ_ShowBetaAnnunciator=1
BKSQ_LoadWithCovers=1
BKSQ_StaticTabletPosition=0
BKSQ_InstantBetaOnTouchdown=0
BKSQ_TabletPayloadUnitKg=1
BKSQ_RealisitcYokeMovement=1
[engine.0]
accumulated_time=1.431383
accumulated_time_hobbs=1.841092

pbrad74

@Wothan Yep, that's the path. Thank you for posting that! I'm editing now to see if it'll work.

pbrad74

ok, so I just added:

var_OxygenPressure=1850

and started the sim and Oxygen is still at 0.

pbrad74

I just uninstalled, rebooted, reinstalled, rebooted, and I'm still only getting:

[LocalVars]
var_radio1Mode=0
var_radio2Mode=0
var_globalFailureRate=0
var_engineDamage=0
SAVED_FUEL_QTY_L_pct=49.999997
SAVED_FUEL_QTY_R_pct=49.999997
SAVED_PAYLOAD_PILOT_lbs=170
SAVED_PAYLOAD_COPILOT_lbs=170
SAVED_PAYLOAD_1_ZONE_lbs=0
SAVED_PAYLOAD_2_ZONE_lbs=0
SAVED_PAYLOAD_3_ZONE_lbs=0
SAVED_PAYLOAD_4_ZONE_lbs=0
SAVED_PAYLOAD_5_ZONE_lbs=0
SAVED_PAYLOAD_6_ZONE_lbs=0
SAVED_PAYLOAD_CARGO_POD_1_lbs=0
SAVED_PAYLOAD_CARGO_POD_2_lbs=0
SAVED_PAYLOAD_CARGO_POD_3_lbs=0
SAVED_PAYLOAD_CARGO_POD_4_lbs=0
[engine.0]
accumulated_time=0.000068
accumulated_time_hobbs=0.000722

this is for the super cargomaster.

With the amphibian version, I have this:

[LocalVars]
var_radio1Mode=0
var_radio2Mode=0
var_globalFailureRate=0
var_engineDamage=0
SAVED_FUEL_QTY_L_pct=49.999997
SAVED_FUEL_QTY_R_pct=49.999997
SAVED_PAYLOAD_PILOT_lbs=170
SAVED_PAYLOAD_COPILOT_lbs=170
SAVED_PAYLOAD_1_PAX_lbs=0
SAVED_PAYLOAD_2_PAX_lbs=0
SAVED_PAYLOAD_3_PAX_lbs=0
SAVED_PAYLOAD_4_PAX_lbs=0
SAVED_PAYLOAD_5_PAX_lbs=0
SAVED_PAYLOAD_6_PAX_lbs=0
SAVED_PAYLOAD_7_PAX_lbs=0
SAVED_PAYLOAD_8_PAX_lbs=0
SAVED_PAYLOAD_CABIN_CARGO_lbs=0
SAVED_PAYLOAD_CARGO_POD_1_lbs=0
SAVED_PAYLOAD_CARGO_POD_2_lbs=0
SAVED_PAYLOAD_CARGO_POD_3_lbs=0
SAVED_PAYLOAD_CARGO_POD_4_lbs=0
var_OxygenPressure=1850
var_RadarMode=3
var_Visor_L=0
var_Visor_R=0
BKSQ_UnrestrictedBeta=0
BKSQ_NewStrobeEffect=0
BKSQ_ShowCopilotInterior=1
BKSQ_VatsimClientMonitorBoth=0
BKSQ_ShowBetaAnnunciator=1
BKSQ_LoadWithCovers=1
BKSQ_StaticTabletPosition=0
BKSQ_InstantBetaOnTouchdown=0
BKSQ_TabletPayloadUnitKg=0
BKSQ_RealisitcYokeMovement=1
[engine.0]
accumulated_time=0
accumulated_time_hobbs=0

pbrad74

I have manually edited the Cargomaster state.cfg adding only var_OxygenPressure=1850, and it doesn't recognize the change when I load the sim.

pbrad74

In MSFS 2024, Caravan Professional persistence appears inconsistent by variant on my system.
Amphibian writes advanced state entries such as var_OxygenPressure=1850, BKSQ_LoadWithCovers=1, var_RadarMode, and visor variables to state.CFG, but those states do not restore on reload.
Cargomaster writes only the minimal persistence block (radios, fuel, payload, engine/Hobbs) and does not generate the advanced Black Square keys at all.
Reinstalling did not change behavior. Manual edits to existing cfg values are read, so the file path itself appears correct.

pbrad74

Why would the amphibian have all of the data in state.cfg but not the cargomaster?

Black Square

@pbrad74 Because I made a mistake Thanks for pointing me in the right direction. The configuration files care about sequential numbering in some places, and not others...

pbrad74

@Black-Square said in state.cfg settings:

@pbrad74 Because I made a mistake Thanks for pointing me in the right direction. The configuration files care about sequential numbering in some places, and not others...

Ah, ok, so next update? I was worried I had something wrong on my end.

Thank you!

qqwertzde

Some related issues: I like to start with pitot and engine covers, and chocks in place. Changing that on the tablet was never saved. I then edited the state.cfg file and that work two thirds: the covers are now in place, but the chocks are still missing.

I am dreaming of a BlackSquare airplane in the future where thinks like this are saved from the previous flight, and where your engines might suffer animal-induced issues or the likes if you don't put on the engine covers at the end of a flight

Black Square

@qqwertzde said in state.cfg settings:

the covers are now in place, but the chocks are still missing.

This has been discussed numerous other times, unfortunately. The aircraft loading sequence in MSFS 2024 is terribly confused, with the aircraft being thrown up and down while the terrain is loading, while temperatures and wind are loaded from the camera position in low earth orbit. This means that aircraft is still moving so much when it's loaded that the chocks are automatically disengaged. I haven't found a fix for this yet, because I was hoping that Asobo would fix some of these significant regressions from MSFS 2020, but it seems like that's becoming very unlikely.