Update . . . I went back into the simulator and did a complete overhaul on the tablet. It worked. I was able to adjust the altimeter and got airspeed and altitude working. Unfortunately, on my very next flight, the same behavior has repeated itself and the overhaul didn't work.

EDIT: So I tried using my old Honeycomb Alpha Yoke and had zero problems. Nice smooth engagement of the autopilot whether I was trimmed out for level flight or climbing. It must have to do with the Moza Yoke not being in the correct "position" regardless if the aircraft is trimmed for straight and level flight.

Not true I know that the Twin Otter Float and Amphibian have those (Also PT6 engines). The SWS Kodiak 100 also feature these. The reason is that if the props would startup feathered, once unfeatherd the "surge" would make the Aircraft start moving. So You want to latch them at zero angle blade pitch during startup (which is opposite being feathered).

Hi Tyler! I appreciate this post, and maybe you can confirm some things regarding the Power Management in the Caravan Pro. I Really enjoy the BKSQ aircraft, and see them as some of the best for the game. I have the whole steam gauge series, 2020 version of BKSQ 208, and the 2024 version of the TBM850, and those aircraft wrongly do not stay in feather during start-up when the prop lever is in Feather. Looking at the blades both from inside and outside views, one can see that they immediately go to their low pitch stop (FI), which is wrong as I understand the system and remember from all operations of PT6A engines in general. Does the Pro Caravan still have these issues? I Also wonder how the power management and prop governing / Beta mode is, compared to the real thing. Are the sound scapes correct for the modes etc? Thanks! David.

@Pistenpaule Just for reference I am using Axis-and-Ohs, I do not know if or how this works in Spad Just try this: Left Tank: On 19·(>K:FUEL_SELECTOR_SET) Off 0·(>K:FUEL_SELECTOR_SET) Xfeed 20·(>K:FUEL_SELECTOR_SET) Right Tank: On 20·(>K:FUEL_SELECTOR_2_SET) Off 0·(>K:FUEL_SELECTOR_2_SET) Xfeed 19·(>K:FUEL_SELECTOR_2_SET)

The pressurized Baron is a great round the world plane :). I've done trips around the world in both the Starship and the Baron 58P.

To make things clearer, of course, external lights are On, landing (both side) On, and NAV lights (flash - so rotating beacon) are On. In this situation, you can't connect NAV lights steady, and the description in the callouts is landing, nav, and beacon On. [image: Bez-tytulu.jpg]

Ok, I'll wirite it, thx!

@Black-Square To add more information, I am also experiencing consistent CTDs with the BS Caravan Pro under very specific conditions. I am running the MSFS 2024 Store Version (1.6.34.0 / SU4) on Windows 11. My Specs: * CPU: i5-13600KF | RAM: 32GB GPU: RTX 3080 Ti (Driver 591.86) Troubleshooting performed: Clean Community folder (only the BS Caravan Pro installed). Repaired MSFS 2024 installation. Deleted Rolling Cache and Shader Cache. Full system restart. Shut down all unneccessary applications including the Nvidia App. The Issue: Even after completing the above steps, I still experience a CTD every single time I attempt a "second load" involving the Caravan. Specifically: Aircraft Swapping: Switching to the Caravan Pro in the Free Flight menu after previously flying a different aircraft. Starting a New Flight: Ending a flight in the Caravan and attempting to start a new flight (same or different airport) without restarting the sim. Restarts: Attempting to "Restart" a current flight while in the Caravan. Summary: The Caravan Pro functions perfectly only if it is the very first aircraft selected and loaded immediately after a fresh launch of MSFS. To fly a second leg or change locations, I must completely restart the simulator. I do not experience this with any other aircraft, including your TBM 850. I have no expertise on the subject, but could this possibly be caused by how Caravan handles memory during the sim's "End Flight" or "Reload" transitions? I hope this can be sorted in a future update.

I was reminded of this topic and just got done poking around in the sim. Using the Behavior tool I can see the LVars, but not anything that would be useable inside the sim. I didn't see the AP Pitch Reference, either, which tells me that it's probably wired in under the hood and not tied to the switch/animation, so this likely wasn't a good test anyway. If you think you've exhausted the list of possible sim bindings, and I'm sure you have because I just searched "reference" and I didn't see one I thought would fit, either, I would give someone official from JF a few days to pitch in here, or maybe open a support ticket. At least then they can log it for potential inclusion into a future patch.

Thanks for your continued attention to this issue. Looking forward very much to it being fixed.

Agree. And the reason why my hanger includes every plane available on Xbox. You certainly do have a lot of consumer confidence with JF.

@ButterSausage Your best bet would be to contact Just Flight Support and they can advise on any problems you are having with the aeroplane.

@RealPax Thanks, and yes XD

You bet. I have been using it since the FS2004 or maybe before that. It is wonderful.

Hi Mark, I tried a repair from the installer and it was just the same. I'll try and make time to remove and re-add the Vulcans again over the next couple of days. regards Steve