@ErnieBall Glad to hear you're enjoying it! It's a very special aircraft for me too. I'm always here if you have any more questions!

Nick, an elegant solution wins the day! Excellent news.

I'm watching for the Duke bundle also for the same reason.

Empty Wt: 2355 Fuel: 50-100 gals: 335 - 670 lbs Baggage: 50 lbs Occupants: Pilot + 3 (170lbs ea): 680 TOW (not factoring taxi fuel consumption): 3420 - 3755 lbs (within CG envelope per EFB) Earlier flights in the list were at 50 gals fuel, later flights were longer (100 gals).

Disregard I figured out the issue.... Circuit breaker face palm

After understanding how the damn Reverse Polish Notation works, I managed to configure, using Mobiflight, the prop axis to include the prop feather once the detent is passed. You can program it several ways, even in a single action, but I prefer two actions to keep the expressions simpler. To get these values I used the Mobiflight app "Potentiometer RPN-Tool" which you can find at the link Prop lever: @ -3.2312 / 16383 + 0 max 16383 min (>K:PROP_PITCH_SET) Prop feather: @ 57000 > if{ -16383 (>K:PROP_PITCH1_SET) } The same goes for the flaps. I configured the Mix2 lever as if it were the flaps lever. The configuration is as follows: Flaps 0 > At the top of the lever Flaps 10 > a little lower (value 2000) Flaps 20 > At the detent (between 50000 - 53000) Flaps 30 > In its lowest position (beyond 57000) You can adjust these values to your liking. The four actions I created in Mobiflight are: Flaps up: @ 2000 < if{ (>K:FLAPS_UP) } Flaps 10: @ 2000 > if{ @ 45000 < if{ (>K:FLAPS_1) } } Flaps 20: @ 50000 > if{ @ 53000 < if{ (>K:FLAPS_2) } } Flaps 30: @ 57000 > if{ (>K:FLAPS_3) } For the power and condition lever , I’m still using the configuration I mentioned earlier in this post. I could do something similar to the flaps, but I prefer to keep the beta range configured this way to play with it during taxi. Hope this helps.

I believe I’ve found the cause and it’s related to the issue I mentioned about the COM/MIC buttons in this other post. While I have COM2 and COM2/MIC selected, the GNS430 volumen knob works correctly. As soon as COM1/MIC is active, having COM2 active at the same time, it doesn’t work. In that case only the GNS530 volume works. Occasionally (not always, but it happens sometimes), when all four buttons are selected (COM1, COM1/MIC, COM2 and COM2/MIC), the ATIS selected on COM2 is heard duplicated, as if it were also tuned to COM1.

Ok. I have already verified that by disabling the TCC on FSTraffic, MSFS uses the FS Traffic models. Working very well.

I’m glad there are threads about this - i’m have the same issue with the Caravan Pro and the NDB 345.5 NWI - the KR ADF radio wont input the .5s - so annoying when trying to do NDB approaches at EGSH. I’m going to ask at my old flight training centre to see what they say.

Please let me know when you have a video. Always happy to look.

Thanks for the awnser. You right. I am going to report to MS. Rgds.

Further info here, in that an afternoon spent doing ILS approaches with the freight or Cargomaster variant has been rock solid and a World removed from what I see in the clean, no pod pax version. Solid as a rock and on rails at all speeds down to an improbable 70 knos indicated. There is definitely something odd here, but what it might be, I haven't a clue.

@Black-Square Do you have any interest in looking into this?

My apologies! Everything is working fine now. It was probably an issue on my end with the liveries add-on.

If I understand what you're looking to do, this would be determined solely by the font you include in your package. You should be able to accomplish almost any effect you're looking for, so long as you're willing to edit the font.

I have the same question myself. In the flight_model.cfg file this damaging speed 190 is under the "flaps" section, which makes sense since the max flaps extended speed is 180. Should this really apply to the landing gear as well?