Piston & Turbine Dukes

Hey @Randolf thank you, that's very kind of you. This is exactly what I was trying to do; however, I was trying to follow the manual's instructions for using the sliding arrows, etc from the main configuration window. I wasn't able to enter negative values there (via the RAW button), but via the Developer mode Behaviors I deduced that a negative value was what I needed, so I was very confused. But somehow I didn't notice the min/max boxes in the Assignment window -- I guess I was too focused on the other section. Thanks again! Derek

Yes, that's exactly what I need!

The speed at which you might be able to increment/decrement that variable would be up to the hardware binding software that you're using, but this very simple code will just increment/decrement the variable every time the code is run. (L:XMLVAR_Cabin_Heat_1_Position, number) ++ 100 min (>L:XMLVAR_Cabin_Heat_1_Position, number) (L:XMLVAR_Cabin_Heat_1_Position, number) -- 0 max (>L:XMLVAR_Cabin_Heat_1_Position, number)

I'm not sure about the earlier posts in this topic, but the Turbine Duke has different fuel capacities in each wing. Since the MSFS payload interface sliders load the aircraft to a given percentage of fuel, I would expect this difference to show up if you load the aircraft with the sliders. The left fuel system has a capacity of 138.4 gallons and the right has 132.5, which would account for your 6 gallon difference if the sliders were set to 100% for both tanks.

It's working fine! P.S Flight Sim Awards 2025 - You Are The Winners !!! Congratulations !

Thanks for your help. I did search the specific message and there is a lot of information there.

@Avionic Dear Avionic, I just finished testing again, and for some reason it worked now on both COM1 and COM2. I didn't change anything in FS'20, on the Duke's EFB and neither in the vPilot App. I remember clrearly that it didn't matter what COM was selected TX didn't light up in blue on neither COM1 & COM2. vPilot done this on my end a few times, usually afer a vPilot update, I start to think I might have to restart the computer after an update, because that is the only thing I have done differently between today's test and last weekend's. There were numerous shut down and turn on cycles. Anyways, I am glad it is working for now. Now I know it is not an issue with the Duke. Thank you for your ideas and time and effort trying to help. Same goes to @Black-Square . Wish you all the best and great health and happyness. Cheers.

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!

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!

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.