No persistance after SU4
-
Perhaps I should have done this years ago, but I'm finally going to bring this to Asobo's attention this week. The method recommended in the SDK should not be working with a less than 50% success rate at this point...
-
-
Nick, if it matters persistence was working fine for before SU4- it broke after. Also, after a flight in one of your planes, there is a new timestamp on the state.cfg, so it’s trying to access the file but it’s not successfully writing to it. Manually editing the state.cfg does affect the sim, so it’s still able to read just fine.
-
For what it’s worth, FlySimWare recently escalated the state saving bug to Asobo too. There’s definitely something broken with it after SU4 which Asobo has to fix. FSW implemented a temporary workaround for the Learjet but they use WASM.
They mentioned another workaround (before their custom fix was implemented) is to end your flight, start a new flight, then exit the game once loaded in and that may cause things to save correctly. That trick may work for the Baron/Bonanza too but I haven’t had a chance to try it.
-
For what it’s worth, FlySimWare recently escalated the state saving bug to Asobo too. There’s definitely something broken with it after SU4 which Asobo has to fix. FSW implemented a temporary workaround for the Learjet but they use WASM.
They mentioned another workaround (before their custom fix was implemented) is to end your flight, start a new flight, then exit the game once loaded in and that may cause things to save correctly. That trick may work for the Baron/Bonanza too but I haven’t had a chance to try it.
@Iconography said in No persistance after SU4:
end your flight, start a new flight, then exit the game once loaded in and that may cause things to save correctly. That trick may work for the Baron/Bonanza too but I haven’t had a chance to try it.
Thanks bud!
-
For what it’s worth, FlySimWare recently escalated the state saving bug to Asobo too. There’s definitely something broken with it after SU4 which Asobo has to fix. FSW implemented a temporary workaround for the Learjet but they use WASM.
They mentioned another workaround (before their custom fix was implemented) is to end your flight, start a new flight, then exit the game once loaded in and that may cause things to save correctly. That trick may work for the Baron/Bonanza too but I haven’t had a chance to try it.
@Iconography said in No persistance after SU4:
They mentioned another workaround (before their custom fix was implemented) is to end your flight, start a new flight, then exit the game once loaded in and that may cause things to save correctly. That trick may work for the Baron/Bonanza too but I haven’t had a chance to try it.
This does appear to work on the Bonanza (so probably also for the Baron). Thanks for posting!
-
I'm finding the weight and fuel is now saving. I am not seeing any decline in engine health though... I don't know how fast it should decline, but I've put quite a few hours on it now.
-
I'm finding the weight and fuel is now saving. I am not seeing any decline in engine health though... I don't know how fast it should decline, but I've put quite a few hours on it now.
@AngleofDangle engine health shouldn’t decline unless you’re being mean to the engine, so you’re probably fine
-
@AngleofDangle engine health shouldn’t decline unless you’re being mean to the engine, so you’re probably fine
@Iconography Thanks, that makes sense! I treat them gently.
