Piston & Turbine Dukes

Thanks. Basically, yes, that's the same or very similar. In its simplest form, I save the control binding profile and livery for the Grand Duke, but upon next MSFS2024 startup, it's reverted and I have to select each of the profiles again (although from memory I think one of them is OK, but I can't be sure) - the livery certainly isn't and at least 2 of the 3 profile settings have to be re-selected. However, for the Stock Duke and Turbine Duke, the 3 x control binding profiles and the chosen livery remain in place from my previous 'save', even after shutdown and fresh re-start. It's only the Grand Duke that continues to fail in this regard.

@CdnCptMoustache I just looked into this, and that variable is only set to zero in the Turbine Duke, and Starship. There's a high probability it was a mistake, and I copied it over to Starship, but I will test things out and see if that's the proper solution before the next update. Thanks for pointing it out. This problem was on my list, but I haven't thought about it in a while.

An excerpt from the next changelog for you When the remote compass is slewed to an incorrect magnetic heading, the autopilot will now follow the HSI’s heading bug to this new incorrect heading.

Hi again, could I please get some support on my config. control bindings in MSFS2024 not saving on the Grand Duke (but all OK on the Stock Duke and Turbine Duke) - I'm at a loss to explain or fix it? I have to go ina and select the binding profiles (and aircraft livery) every time whenever I select the Grand Duke. Many thanks.

@fidlar Glad to hear it! You know where to find me if you have any more questions!

Very glad to see and let anyone else know the bundle is up!

Is that’s what’s going on with the flickering, that can be seen with the pilot door open, on the Caravan?

There is also Reverse Hold button binding which effectively flips your axis to 0 -> -100, meaning you pull to idle, hold the button, push physical axis forward, but it increases reverse.

@tyleraviator1999 I'm sorry for the delay! I could swear I answered this already. It must have been a similar question. There is definitely a bundle for the Dukes on the MSFS 2020 marketplace right now, but we still haven't had the bundle for the MSFS 2024 marketplace approved yet, despite already having bundles for other aircraft there already. Unfortunately, this means I don't know for certain how the 2020 bundle purchase will carry over to MSFS 2024. I suspect it works as-is right now, or else I would have heard otherwise after more than a year. Hopefully someone will stop in to confirm this for us. Sorry that's a lot of uncertainty without someone able to confirm directly. We are often just as in the dark regarding how the MSFS marketplace works as you guys, I'm afraid.

@Black-Square Thanks

Thanks a lot! I must've missed that page when reading the manual! Thanks for the help!

@Pondimus Came here looking exactly for this - unfortunately the avatar from 2024 is a bit buggy, it keeps twitching and breaking immersion. I wish there was a way to totally disable 2024's avatar and use the Just Flight Co-Pilot model from 2020 in 2024 instead.

I hope it works for you. I did all those things and still had the issue. Let us know if the issue returns. Thanks

I suppose the quality might be objectively better, but I actually prefer the Duke soundset overall - much 'growlier'. Just goes to show this kind of stuff is in the ears of the beholder..

Thanks for looking into it. Has to be incredibly frustrating for you! At least in this case there's an easy workaround for now - turn em off lol.

Thanks for sending them another reminder to fix this issue, asobo should be ashamed of themselves for doing nothing to fix it on their end its unacceptable I'm very disappointed in them.

Sorry for the delay. Just getting back from an audio recording trip for the Twin Commanders and the King Air. 1-3 are generally in the realm of "my aircraft don't support Ctrl-E", and "MSFS 2024's flight starting/restarting system are very confused." I will look into the loss of synchronization with reloads to see if there is an easy solution, but when I have looked into similar things in the past, they were beyond my control to fix. This has been reported, and I've already fixed it for the next update. Thanks. I will test this next time I have the simulator open, but the code is identical to my other aircraft where this feature has been working for years. You're referring to the copilot's side localizer for use with the KNS-81? You can control the OBS simply by modifying L:var_RNAV_OBS, number. Let me know if you have any trouble with that. I use the simulation variable A:SURFACE TYPE, ENUM, which is the only way to read surface type to the best of my knowledge. I know next to nothing about scenery design, but I believe that the designer should have the opportunity to select an appropriate surface type tag while creating any custom materials. The audio panel switches are not state saved in any of my aircraft. Sorry for the disappointment. Let me know if you have any more questions, or if there is anything else I can do for you!