Piston & Turbine Dukes

I reinstalled aircraft, and now everything works fine, no problems.

I did a reinstall of the Turbine Duke and now zoom works fine.

That's what I'm here for! It wouldn't be any fun for me if I didn't get to see my users learning and becoming better virtual pilots :)

Incredible the amount of detail you put into these aircraft, Nick. They never cease to amaze.

They have been added and ready to go. I'm sorry that it's taken so much longer for a Duke update than I ever anticipated. I wanted to coordinate with the official MSFS 2024 release of my aircraft, since things have changed in both versions, but the speed of breaking changes in MSFS 2024 has taken six months to slow down to where I finally feel comfortable presenting my aircraft in MSFS 2024. Updates for all my existing standalone aircraft after Flight Sim Expo, I promise!

Integration with navigraph charts would be incredible in the EFB, or having the possibility to use the new MSFS2024 EFB in the 3D cockpit.

Using both seems redundant. As far as my case goes, I added _IsDown to my up and down events, and they work swimmingly. I've no idea why the difference; maybe the regular ones work better with the Rotorbreak command I see so often in flight sim peripheral channels. Supposed to imitate a mouse click I believe, but I've never used it.

Here is a fix, upgrading the GNS530 to the 2024 version: https://www.avsim.com/forums/topic/673298-how-to-import-a-flightplan-in-msfs2024/#findComment-5494400

Nick, I'm sure that you've been heads-down on the Starship for a good while now, but I was reminded of this issue yesterday when I pulled into the ramp at Nashville yesterday. I selected external power and went to play with the avionics after I shut everything down, and found myself eating through the battery instead of being connected to the power cart. Fortunately, it gave me an opportunity to play around with hot starts and vapor lock (and watch it all on the tablet as I went through the hot start checklist!), and I could always just click "recharge battery," but having the power cart would still be nice. Have you had a chance to look at this for the next round of aircraft updates?

No need to apologize, I’m sure you are very busy these days, with the upcoming release of the Starship (looking forward to it!). I suspected it was something like the situation you describe, that caused this. It was obviously not a problem, but I can also understand why someone with your attention to detail wanted to fix this. And somehow found the time to do so. Do you ever sleep? All the best!

Ok, thanks for clarifying

Here's a little sneak peek. I got the dynamic reg numbers hidden with the method you suggested - although MSFS 2024 still tries to put a tail reg on the aircraft unless I go into the in-game "Identification" menu and remove the reg number. Although this might look like a fictitious paint it's actually real - although there only seems to be one reference photo and apparently the aircraft has since been repainted! [image: b4tRohu.jpeg] [image: K1Dm109.jpeg]

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