I have e eyesight issues too and simply look at the needle angle initially for a rough guide and then fine it up when the opportunity arises, hence another plus for steam over glass, but I used to also use a free app called spacedesk to run out stuff to another screen or tablet. You might find that useful if it is still around for your Apple paperweight

After understanding how the damn Reverse Polish Notation works, I managed to configure 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.

Whats the TOW?

@sputman101 Unless you're referring to an issue with the frequency spacing in the simulator that I'm unaware of, this might be of interest to you from the manual: A secondary click on the power knob will increment the standby frequency by 0.5 kHz, indicated with a dot to the left of the frequency.

@pieroni All will be told when we publish an update article soon. As several of you noted above, I did have the opportunity to record sounds from the King Air and Turbo Commander last week, as well as the privilege of flying both. It took me several weeks of contemplation to choose the specific King Air variant, with competing interests among my users. I think my final decision will deliver the best of both worlds, and I look forward to hearing your thoughts soon.

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

Apologies for the thread resurrection but this appears to closely relate to the issue I am seeing. In the latest version in MSFS2024, I am seeing fuel burn numbers in the simulator approximately 50% lower than the Simbrief estimates. I am using the Just Flight 146 Simbrief profiles and I believe they are accurate, I believe the issue is on the MSFS side. Is anybody else experiencing this? Is it potentially a regression of an earlier fix, either with the product or MSFS2024 itself? I am using Kgs as the units, in case this has any bearing.

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.

Don't suppose you are using an FFB yoke or similar? Is the software running externally to the sim? I know mine does (CLS60) and there can then be a mismatch between stick or yoke settings and the sim settings, which can catch you out on occasion with trim forces.

Hi RobSys, If your using MSFS2024 ... I've just had a quick look at my RJ setup (I'm using the store version) and I have the following location for my downloaded Simbrief flight plans: .. \AppData\Local\Packages\Microsoft.Limitless_8wekyb3d8bbwe\LocalState\WASM\MSFS2024\justflight-aircraft-rj\work\JustFlight\FlightPlans With the Simbrief flight plans downloaded and saved in the above folder - was able to load my EGFFEGJJ01.RTE file into the FMS, as seen in the picture below. From memory the folder used was changed when making the MSFS 2024 native versions of the RJ Pro [image: 78ca6913-9c86-4131-9304-63f9f007aa5b.png]

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.

No apology necessary at all! In the meantime I also had ChatGPT analyze the propeller code above, and it came to much the same conclusion. I just haven't had a chance to try it out yet. Thanks so much, Nick! The FedEx Cargomaster in particular is my jam, and I've been greatly enjoying making short cargo runs in it. 🥰

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.