Piston & Turbine Dukes

@SebAvi Yep that's the current plan.

That's exactly correct. The yellow band would allow you to fly the aircraft faster in smooth air, but in a turboprop aircraft, there is no such band, meaning that VNO and VNE are the same speed. Unfortunately, I have been unable to locate the logic behind this regulatory decision, but there are several accident reports of structural failure in turboprop conversions flown beyond VNO in turbulent conditions.

Again, I'm not an expert, and I might be wrong about this, but I think you are approaching this in an overly difficult way. That's not a criticism (I seem to approach everything in my life from a difficult angle too), but there are numerous applications that should allow for very easy L:Var manipulation. I'm sure FSUIPC can do it too, but I'm not sure that it requires register manipulation. The B:Var is the new MSFS interaction system, which can be very useful, but it's also incredible abstract and convoluted for developers to set up, so it tends to be underutilized. Not all 3rd part applications have access to B:Vars, so I would try to avoid them wherever possible.

That's correct. Here's a snipped from my manual with an interesting tidbit: Unlike the reciprocating engine version of this aircraft, the combustion heater does not provide any heating to the aircraft, and will never be activated by the temperature controller. The heater has been disabled, because it is not certified for use with jet aircraft fuels, as opposed to aviation fuels. All heating in the aircraft is accomplished via the P3 engine bleed air.

You just need to: Create directory "Microsoft Flight Simulator" inside directory "C:\Users\%USERNAME%\AppData\Roaming" Copy file "UserCfg.opt" from "C:\Users\%USERNAME%\AppData\Local\Packages\Microsoft.Limitless_8wekyb3d8bbwe\LocalCache" into newly created directory above (1.) That's it - then you can run installer and after install you can remove directory from 1.

I neglected to check the failures tab. The left magneto had failed on and the right magneto failed off.

Yup found it. Thanks. I was actually looking at the A2A Comanche Tablet for it lol

Just resurrecting this old post. As far as I can see there's still no paintkit - is that correct? Any chance Black Square could release one please? I can make do with the plain white aircraft but a paintkit would be easier, to separate out dirt layers and other details (if one exists!)

That’s great, thanks very much.

I was recharging it from the tablet.

I like Elizabethton and Roanoak, cheers

@Black-Square Thank you!

Just experienced this myself. I was definitely not parked on a parking spot. I agree with @seipp that the restriction should only be chocks or brakes, to accommodate airports with crap parking design.

@Noob21 My father purchased the second Piper Navajo Chieftain off the production line (saved from the Lock Haven flood by being in the paint shop). In its first year had de ice boots, radar, and King KN74 RNAV installed. This was 1973. I remember watching the numbers roll up or down when he would change waypoints.

Thanks! @Black-Square

I suspected it was one of your personal touches, I appreciate it. So in this case I should ignore the ETM and keep the engines syncronised based on the engine instruments directly, correct?

@John-S Thanks for the kind words, I'm glad to hear that you are having fun. Logs are a bit difficult, since I cannot write to the file system with JS avionics. Best would be if you could find a reproducible case. Like a sequence of actions and a specific approach that always results in the problems you see. If I can then reproduce the issue on my machine, I can use the debugging tools to see what is going and then it is usually easy to find and fix the issue. The most difficult part is usually to reproduce the issue. A video also helps a lot to see what steps you are taking.

I recently turned on the headphones simulation in 2020 through the menus, but I actually didn't like it (certainly in comparison with the Comanche's custom implementation). So while I am excited for the next Duke update, I'm cautiously interested to see whether the variable noise cancellation (great idea!) works quite as well or if I'll prefer it switched off. I think I have become accustomed to the volume of the Duke in cruise now. It's when switching to the external view for screenshots that my ear drums are assaulted! I know it's realistic, but it would nice if the internal/external volume could be better balanced for my own sake, and that of anyone in earshot! Not sure if it could be handled via the tablet, or if it's baked into the simulation (perhaps a .cfg file edit). Maybe another idea for the list. I know the 2020 Duke update won't launch before the 2024 update is ready, as that might cause chaos and frustration, but at this point I'm cursing 2024 for dragging general progress down for 2020 products