Piston & Turbine Dukes

Interesting. The Turbine Duke and Piston Duke's code should be identical. I can't tell you what that means for your specific issue yet, but it might be some clue in the future. Please let me know what you find. I'll be away from my desk for the next couple of days, but I will get back to you as soon as I can if you need anything else from me. The Just Flight support team is also always there if you need a hand.

Thank you, that is great! Personally, I would still like you to update the A36 as well, since I fly it a lot..
One more request for the A36 (present or future): Adjust the dimensions of the ADI and HSI to the correct ratios.
Sorry for being picky, but I notice it every time..

@Biggles3601 said in Ap and Nav not working in MSFS 24?:

I guess I was just cognitively biased towards expecting something to go wrong in 2024 and was looking out for it.

You're talking to an expert when it comes to this faux pas! It's embarrassing how many hours I have spent trying to track down bugs in my aircraft, only to discover that my MTBF failure system is behaving exactly the way it should, and the only bug is the triggered failure! It makes me very thankful that I don't have to think about debugging code while flying approaches in the real world!

@Black-Square Looks like the stutters have been fixed, or at least improved with the latest SU 1 beta. I've only done one flight but I didn't have any stutters at all. Hopefully it wasn't a one time thing.

Found the culprit. negative lod bias wes set to clamp in the nvidia controlpanel. Reverting it to the driver standard (allow) fixed the problem.

Thanks Nick. It's one of those issues that I consider 'interesting' rather than 'annoying'. Whether it gets fixed or not, I'm glad it's not just me that has seen it. I'll not worry about it as it doesn't impact my enjoyment at all. I think you have a million more important things to attend to at present!

@Romulus Very interesting!! Thank you for sharing. I can envision how that could happen in my code. That is also relevant to a note I have for another unannounced project that I'm currently working on. I will definitely be exploring that shortly, and I will implement a solution for the Duke, assuming it doesn't significantly disrupt current hardware and home cockpit builders' setups.

Yes, the indicator will move. It might be exceptionally slow, depending on how you are manipulating the control. I believe that it will be very slow using the switch in the cockpit, and much faster when using the default key/hardware binding in MSFS. Also, I'm sure you are already doing this, but make sure you are holding the switch down in the cockpit, and not just bumping it in either direction momentarily.

So gave the B60 a cruise stability test and the model exhibited both positive static and positive dynamic stability. Test parameters... ISA, no winds, 4500' msl, half tanks, centered CG, 30" @ 2600rpm. Set a stable cruise after speed settled for the power setting. PIO by pushing the nose down 5 degrees and let go with a fingertip on the yoke just to maintain wings level. The pitch oscillations reduced in magnitude until about 5 minutes later the aircraft was in level flight with no oscillations.

I am having the same problem with the Duke Turbine. With the GTN750 installed, FS2020 on Xbox crashes all the time. If I install any of the other options, I have trouble free flying. I was foolish enough to go and purchase the TBM850 leading to the same CTD’s with GTN750 installed.

@lilycrose
Thank you... I removed the GTNxi from the community-folder and it works :-)

Turn it off.

I have found the other post. It is titled Duke Problems and is mentioned by HarrisonD.
My Duke was flown as installed ie. PMS50(on Xbox I don’t seem to have a choice. It’s either PMS50 or TDS GTNxi). Interestingly, I have just selected TDS GTNxi then pressed Confirm.The Confirm button then said Done but both the Primary and Secondary displays are blank
Not sure about disabling content. Would have to look into that further.