Caravan Professional

@AlpraziTech I have now exactly the same issue as you, never happened before. The GTN 750 is not working at all, and the 530 is "working" but without GPS signal, so unable to use any of the maps. It shows as well the "NO GPS POSITION" message, and it doesn't go away at all. Playing on Xbox Series X.

A small update on where we're going with this. Still very much work in progress, but it gives an initial overal picture on the project. We hope you like it. [image: b3bd6a73-2bc9-4381-a111-d248c4d24779.jpg]

Ok, simple testing complete. Active pause will not stop failures from triggering, whereas esc pause does. That suggests tay esc pause does indeed stop the code from executing, but of course does continue to allow the passage of time. It even automatically turns off active pause, which means my workaround doesn't work. Still, good to know where we are! Edit: but wait, if one manually locks time with the flow widget, then it will stay locked during an escape pause! So true pause does seem to be available with msfs2024. A bit annoying that you need a piece of (paid) third party software to do it, but it does seem to work.

Ok Any idea on how long that would take ? To release the fix ? Remember - MSFS2020 Marketplace

Hey, want to by this plane. Is visible passenger loading fixed? can i load the maximum passenger size in the plane, not only 5 ?

Daft thought, but to satisfy all, could a toggle br built into the EFB? At least, that way you can have high confidence that you can satisfy everyone.

Thanks for your reply. the problem was i juste re-use the gtn750 from my new cessna caravan since months. with over gtn750 all worked fine, but for the cessna none. it was simply my map oriented north instead of heading. i was a bit confused. It was just nothing... Sorry, thanks again.

I've figured out where things went wrong. I used the Contrail store to check the version installed, and that indicated wrong. So now I have the latest version installed. I checked the changelogs of the last 2 versions, and indeed all these issues I have were actually incorrect and fixed in those later versions which I did not have. So when I reinstalled suddenly the plane behaved differently than I remembered, simply because I had an outdated version before I was used to. Mods feel free to remove or close this topic if necessary.

@Sunshine_db Yay! Glad I could help, and glad you were able to figure out the last bit on your own too! Indeed, I can't imagine doing those myself without the help of the debugger. Good luck, and you know where to find me if you need anything else

@Black-Square is the update coming soon?

Nope! You're the first one to notice! All fixed, thanks. Thank you for telling me now, instead of the day after I release a Caravan update, haha.

I’m interested as well

@Black-Square said in State Saving: This has come up more recently, as it seems that state saving has never been the same since SU4, and it was never particularly reliable to begin with. There are some workarounds that you can read about, and possible causes. Particularly, restarting the flight before quitting to desktop, and disabling anti-virus seems to be the most commonly cited solutions. I've become increasing frustrated with this myself, which is why I have recently invested my time in creating a whole new full state saving feature, which will hopefully provide better consistency, and save nearly every variable in the aircraft. You can read about it here, if you like. Is this new system coming to the previous aircraft, from the Bonanza Professional and upwards, among the other improvements? If yes, do you have a rough time schedule for patches to come? (i.e. before the end of summer...)

My Hobbs meter is reset back to 12ish every time I fly. I am using the same livery every time. I read in a different topic that it might have something to do with the way Asobo calculates it. @Black-Square With the advanced state saving added in the Commander, do you think it would be possible to backport that to the hobbs meter in the Caravan?

Solved! I had to unistall it and reinstall it in a custom folder and then move it to the Community. The installer put everything in a JustFlight folder that my fs2024 does not recognize in the game. @Black-Square [image: e6c0ced4-b49c-402f-b328-7ca4d92b62d6.png]

Update - Just went through everything again, made sure my physical default control positions matched the proper pt6 “just started” state and everything worked as expected, no abnormal issues. I restarted everything and went through it a few more times and everything worked correctly. For now the problem now seems resolved for me.

Thanks, I finally later found the solution by using simconnect flaps_incr but I have to add 16384 in the parameter field. I don't know why! [image: 4309032e-3be2-4e58-8706-d384da46b97a.png]

I just sent another request to bother Asobo about this again... I'll see if we can get any traction this time.