Hours/Hobbs reset to Zero on next startup. 2024
-
Same here with me. Same with all other aircraft (but not A2A). I think it's still a MSFS 2024 bug.
-
There’s still an unresolved bug ticket for the Hobbs, it affects all aircraft for me as well: https://forums.flightsimulator.com/t/regression-hobbs-meter-not-saving-in-the-last-few-beta-versions/747013
It’s still tagged as bug logged and so far not fixed in SU6 beta either.
Nick has mentioned before that he uses the native Hobbs meter logic and nothing custom so it’s still on Asobo to fix. -
There’s still an unresolved bug ticket for the Hobbs, it affects all aircraft for me as well: https://forums.flightsimulator.com/t/regression-hobbs-meter-not-saving-in-the-last-few-beta-versions/747013
It’s still tagged as bug logged and so far not fixed in SU6 beta either.
Nick has mentioned before that he uses the native Hobbs meter logic and nothing custom so it’s still on Asobo to fix.@Iconography said in Hours/Hobbs reset to Zero on next startup. 2024:
Nick has mentioned before that he uses the native Hobbs meter logic and nothing custom so it’s still on Asobo to fix.
That's correct. Since the hobbs time is stored in state.cfg, this is part of the ongoing state saving failures of MSFS 2024 that have prompted me to create my own system for this aircraft. I haven't included the hobbs, however, since I know the native variable is often used by 3rd party career applications and alike.
-
There’s still an unresolved bug ticket for the Hobbs, it affects all aircraft for me as well: https://forums.flightsimulator.com/t/regression-hobbs-meter-not-saving-in-the-last-few-beta-versions/747013
It’s still tagged as bug logged and so far not fixed in SU6 beta either.
Nick has mentioned before that he uses the native Hobbs meter logic and nothing custom so it’s still on Asobo to fix.@Iconography said in Hours/Hobbs reset to Zero on next startup. 2024:
There’s still an unresolved bug ticket for the Hobbs, it affects all aircraft for me as well: https://forums.flightsimulator.com/t/regression-hobbs-meter-not-saving-in-the-last-few-beta-versions/747013
It’s still tagged as bug logged and so far not fixed in SU6 beta either.
Nick has mentioned before that he uses the native Hobbs meter logic and nothing custom so it’s still on Asobo to fix.Thanks for the heads up. I have been on the A2A's until now the past few months so didn't even notice it.
Guess I will stick with 2020 for now until Asobo fixes this new mess. -
@Zacke They're saved right next to each other in the same file by the simulator itself.
-
Thanks, Nick!
It's sad MSFS 2024 doesn't handle that in a adquate manner. But I'm extreme thankfull for your new state saving system (and the other important things (payload, fuel ect.) are saved since SU5 (?) with your other planes). And I'm very happy with all your excellent, innovative and fascinating work!
-
I had no idea this was happening to so many people. It saves this info in a text file, so it's strange that it keeps getting reset for some people and not others. I had somehow had a failure to save on my first flight in the Commander, but going forward it hasn't reoccurred, and I don't think I've EVER had it fail in any other aircraft in 2024.
-
Okay now this IS happening to me. I started flying the Turbo and saw the hours at 0, which I assumed is because it counts as a separate plane. Gained 1.2 hours. Exited that flight and started another in the same airframe to confirm it was still there. Then exited the game, fire it up the next day and load into the NA version, and now ITS hobbs also says 1.2, whereas the last time I flew it, it was around 2.5. So at the very least we have an issue here where the two versions are overwriting each others hours.
-
Ok so my hours were saving just fine but today they've reset, it may be self inflicted as I went to the Configure Screen where you select the aircraft which if that is the case then I'll have to avoid doing that in future. Reading above though are they saved externally by the Commander itself? (bit confused)
-
I know I've said this countless times, but pretty please, I think you guys have enough information now for Asobo to take a serious look at this. I've moved on with my new state saving system, but there are still several simulator functions that rely on the state.cfg method. I recommend finding/creating a post on the official forums, and focusing on what you've found that forces state.cfg to save.
While the state.cfg method was very inconsistent with L:Vars for some users since 2020, this new behavior where not even the hobbs saves is new since SU4 for MSFS 2024.
