@737Cowboy Hell yeah. I mean, based on Nick's statement, I wouldn't be surprised. However, I also assume he's working on some slick TPE331 stuff for the Commander, so in my mind a B100 is also possible. Speculation is fun.

This has been reported by many developers. I'm really hoping Asobo figures this out soon, because it's affecting many 3rd party aircraft clickspots in ways that don't seem logical based on the model (there is nothing occluding the VR cursor that might interfere with the clickspot in the model).

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?

As you probably know, the lighting itself has nothing to do with the low voltage light. The annunciator illuminates when the bus voltage is being dragged down by electrical loads (of which the lights are one), and the engine's RPM is insufficient for the alternator to boost the bus voltage above the trigger level. Which GTN are you trying to use? The PMS50 GTN? I haven't heard about any issues lately, so I just suggest making sure your GTN is up-to-date. Let me know if there is anything else I can help with.

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

@Chotter why dont you use mousewheel for zoom or maybe try headtracker

By the way @Black-Square, would you be happy for me to share the altered KAS297B.js file along with my Stream Deck profile on flightsim.to with appropriate caveats? Caveats like "no support from Black Square for this" and "backup the original file!" If not, I'll see what I can do to make a semi-functional dial, but without exposing the "armedVS" value it makes it a bit clunky on the Stream Deck.

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

@Akknk Hi everyone, I have one question regarding the cruise profiles. SimBrief offers the following options: MCR-1600 / MCR-1750 / MCR-1900 LRC-1600 / LRC-1750 / LRC-1900 Is there any documentation or table showing the actual performance values behind these profiles? I am especially interested in the expected cruise data by altitude, such as: RPM torque TAS fuel flow ISA assumptions differences between no cargo pod, cargo pod, cargomaster and amphibian I would like to better match the SimBrief profile in the Black Square Caravan during cruise. For example, if SimBrief plans LRC-1900, I would like to know what torque / fuel flow / TAS I should aim for in the aircraft. Are the profiles based on the Black Square manual tables, the real Cessna POH, or custom SimBrief performance data? Any help or pointers would be appreciated. Thanks!

Hi gazdav787... Thanks... I'm using MDFS2020... And as I noted, the .RTE file(s) are in the correct location for my sim... Rob

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.