If you are using the FSHUD traffic injection, we would recommend contacting FSHUD support via the following link: https://www.fshud.com/site/knowledge If you are using the FS Traffic traffic injection, we would recommend contacting Just Flight Support via the following link: https://www.justflight.com/support Mark - Just Flight

The exact file path for flight plan imports using locally stored files varies depending on which version of the simulator is being used (2020/2024) and which store version is being used (Microsoft Store/Steam). The relevant file paths are listed in the following FAQ under Method 1 CO ROUTE (Company Route): https://support.justflight.com/en/support/solutions/articles/17000142837-gnlu-910a-fms-how-can-i-import-a-flight-plan-from-simbrief- A direct Simbrief import was also added to the GNLU-910A in a recent update to the RJ that doesn't require locally saved flight plan files. The process of directly importing a Simbrief flight plan into the GNLU-910A is covered under Method 3: SimBrief Import: https://support.justflight.com/en/support/solutions/articles/17000142837-gnlu-910a-fms-how-can-i-import-a-flight-plan-from-simbrief- If either of those two options isn't available/aren't functional, we would recommend reinstalling the latest version of the RJ Professional to ensure that you have the latest version. If you continue to have any issues with the flight plan import, we would recommend opening a support ticket at Just Flight Support via the following link, and one of our support team will be able to assist with further troubleshooting: https://www.justflight.com/support Mark - Just Flight

Thanks again for this! I went through the new file, and everything looks perfect. It's those SetSimVarValue calls that really seem to affect performance when in great number, so the simple conditional is usually better. I will include this in my next updates, and I've already updated the manuals with the new variables. You're more than welcome to share the profile! Usually I worry about conflicts later down the line when a mod is made incorrectly, but in this instance, since you will be overwriting only the one file, and with the exact same code that will be in the next update, I think it's mostly safe. You're welcome to make your own package, or wait a month or two until my usual round of summer updates for all my aircraft. There are lots of little new features for all of them, so this will be a nice addition too! Thanks again.

I am using the TDS and getting this problem quite frequently. But this only happens when coming out of HDG mode. When using an RNAV procedure to get myself onto the ILS, it never happens. So far, I only encountered this when using Black Square aircraft. And yes, it might be a problem with the standard autopilot but still it’s quite an annoying bug. I love the Black Square aircraft but the autopilot implementation is really a weak point. A2A for example does a custom autopilot implementation for the Comanche and Aerostar and it shows. Much more realistic behaviour and one can actually operate the autopilot using the original manual. It’s quite a pity that Black Square uses highly customized systems for almost everything but then uses the standard autopilot.

Excellent! Thank you.

Do you think you could record a video for me to look at? Since you have the Analog Caravan, I assume you are familiar with starting procedures, so you're waiting until the gas generator reaches its maximum speed before introducing fuel?

Is it possible to automatically swap the SL40 COM radio for the SL30 NAV/COM radio in slot 2 when the NAV OBS 2 option is turned on, to solve the issue of it only being usable with two GPS units or one GPS as it is now?

@Black-Square Thanks for the feedback Nick. BTW loving the Caravan - its my go-to aircraft these days!

@Black-Square OK that seems to work well. It appears to be simply "slowing down the animation" which works fine for me. @Black-Square said in Customizing the Prop Animation: If you also want to delay the transition to the blurred propeller disk, then change the first line to (A:PROP RPM:1, RPM) 286 > I'm not super concerned, but this didn't seem to affect anything that I could see. I even increased it to the prop's maximum RPM and I still got the blurred disc effect. Also, I think initially I was getting hung up on this final line, thinking that I could somehow multiply the visual RPM by 0.5 as it relates to the engine RPM: (L:bksq_VisualPropRpm, RPM) (>L:BKSQ_CARAVAN_PROP_RPM, RPM) Thanks again!

@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.