@Heclak Splitting off a single variant like that would be almost as much work as splitting them all out, so that doesn't gain me much, unfortunately. I will also add that MSFS 2024's LOD system also makes this much more difficult for developers, because I must now export at least four or five models for every one in MSFS 2020. Lastly, I will agree with you that I understand WT's decision, the same way that I would hope anyone would understand my design decisions, but at least from my perspective, hot-swapping works perfectly well with all the 3rd party avionics my aircraft support, including my own (KNS RNAV and Starship). The hot-swapping system in the GNS 530 does not allow for all the options supported by 3rd party avionics, but it still works well enough for me and my users, so it's definitely sad to see that system abandoned for these new avionics. Between my users and I, I will do my best to think of interesting places I could use the IFD's in the future, even if that's not alongside all the avionics options in my current aircraft.

On the first point, you're correct, the engine won't fail completely. You can consider this either a severe clog of both fuel lines, or another type of "acceleration schedule" failure on the part of the FCU. The engine driven fuel pump failures are coded correctly, but it's possible I fixed this recently and just haven't published it in an update yet. It's hard to tell from your video, did the column pusher really activate, driving the yoke into the panel? Looking at the code, that is definitely dependent on both circuits being energized.

I was able to get it working. It was one of the following: activating VLOC before swapping the ILS frequency, or arming APR before the LOC needle started moving I have gotten used to how the PMS50 GTN behaves, which is not completeliy aligned to the actual Garmin GTN 750. I'm moving to the TDS because the PilotWorkshops GTN training uses it, and I can understand why ... as pilots in training in real life need to learn exactly how the real device operates.

@Black-Square thank you for the quick response and clarification.

Hobbs saving is entirely on the simulator side, unfortunately. Asobo introduced a state saving bug in SU4, which was supposed to be fixed in SU5, but apparently is not entirely fixed. The current workaround is to reset the flight before exiting the flight and quitting the simulator. Sorry we all have to deal with this right now!

@SenaCE I would recommend contacting Just Flight support. There is a link on their website at www.justflight.com

Nick, tried to mail you. Can we still hope for this to come out? Thanks for a short reply.

Since everything in my aircraft is saved via the MSFS cloud service, your state should be retained. I've never done this, however, so hopefully someone here might have the definitive answer for both of us.

@Black-Square Yea no problem, your welcome, great work with v1.2 !

@Black-Square @BorisAudio Caravan v1.2 is awesome, thank you, love the sounds, way better than v1.1

The lack of response leads me to suspect that the answer is "no".. too bad. In the real airplane, you can correct your mistake if you act quickly (or so I have been told..)

Not flight model rated - works perfectly here. Identical turn rate and aileron deflection to both sides. Probably a joystick calibration problem.

Yes, there will be good to make it possible with lvars

L:var_trueAirspeedRing, number should really do the trick. The position of the ring is directly tied to that variable. I will double check it myself later.

Thanks for looking into it. Has to be incredibly frustrating for you! At least in this case there's an easy workaround for now - turn em off lol.

@Black-Square thankyou. I can see the changes added in v1.2: Sounds for all exterior interactions, like opening and closing doors, are now audible during walkarounds.