Piston & Turbine Dukes

I see that on my end too. Thanks for the detailed description. From interrogating variables, it's caused by "outer loop's" commands to the flight director, not the "inner loop", which is the autopilot's PID controller. From my work on the Starship, I've seen that the outer loop has some... interesting behavior when it comes to flight director commands during mode changes. I'll experiment with this a little and see if there is something I can do. That being said, the Duke owner who had a Century IV in his airplane told me that he actually warns passengers before changing autopilot modes because the "bump" can be significant when it commands pitch changes.

You always seem to come to me with the most interesting and minute issues! Thank you for taking the time to let me know about all of them. It was baked into the model file that way. No idea why. Thanks for pointing it out. Easy fix.

Nice! It is fantastic to see how dedicated you are to get everything working perfectly. Also in a case like this, where many users might never notice that anything is wrong. Makes it much more satisfying to dive deeper into the systems, when you know that the dev is not just aiming for having the basics "look kind of right", but actually wants to simulate the underlying systems properly.

@SomeoneCalledRay said in WT GNS Still unusable: So I got the GTN working, haven't retried the GNS because couldn't be bothered, but I had a weird issue today where no lateral modes apart from heading were engaging (pressing buttons, etc). I'll post about this shortly. I just had I think the same issue. Only heading would engage, and once it went into Alt, subsequently pressing Att would remain in Alt and level off at the current altitude. I think it was my first flight after updating to SU15, and restarting from the runway instead of cold and dark for a quick test worked OK. What ended up happening with you?

The event.txt file in FSUIPC uses this: AP_Century_IV_Pitch_DOWN#(L:var_AP_PitchKnob) 0.5 + 14.5 min (>L:var_AP_PitchKnob) AP_Century_IV_pitch_UP#(L:var_AP_PitchKnob) 0.5 - -14.5 max (>L:var_AP_PitchKnob)

I just finished playing with this myself. There's definitely something fishy going on. The sound is instantaneous on the exterior, but there is something on the interior delayed after the nose touchdown, but sometimes before the nose touchdown too. I'll pass this along to my sound designer and see what the problem is. Thanks for pointing it out. I always thought it was just the tires skipping down the runway after a bump.

@Black-Square I think it's something about the linearity of the rates. What I mean is this: In the Turbine Duke, the prop goes from invisible, to moving at perhaps 50-80 RPM (visually) in a fraction of a second, even though the NP indicates it's still spinning faster than that. But, after becoming visible, it does indeed take a while to stop. The animation doesn't depict a smooth deceleration from disc to visible blades at all (to whatever extent that it should be). Also, the audio seems to end long before either the NG or the prop stop spinning. It feels like the audio should last a bit longer, and the prop should have a somewhat more linear rate of deceleration. (To whatever extent that is realistic.) This is true of the TBM as well. For example, the spin downs of the Lancair Evolution and FlyJSim Dash 8 Q400 in Xplane 12 seem a bit more realistic, although even the Dash 8's props just suddenly stop at the end of their animation... So maybe just the Lancair? It's audio is also more consistent in its taper off. Of course, I'm open to hearing that the Lancair is the one that's wrong. Finally, while the TBM 700 seems to take a while to feather its prop after shutdown, as per your linked video, the 850 and later models seem to feather much faster: https://www.youtube.com/watch?v=QfSDPwsIAlo

Aircraft that are inherently stable should converge back to their trimmed state, assuming their CG is properly balanced. However, not all planes are inherently stable, as stability is the opposite of maneuverability. Generally, the more high performance an airplane is, the less inherently stable it is. All of that being said, I find the Duke to be quite stable when trimmed, and hand flying it is a joy.

@Randolf Loading Position is working now - thx And by the way: AAO was updated today in the JustFlight marketplace.

I created another thread to be able to have a blender model ready for painting, and a photoshop one too. Hope someone steps up to do it.

@Randolf thanks for the hint - I will take a look to your AP-Template. and thanks again for your savestate solution

@Black-Square Great! That will do for sure! It will be Punta Cana to Dubai. I want to challenge myself to always keep the engines at 100% health. Hopefully this patch will drop soon?

I see that you found a way to send the message. Thanks for sharing his contact information. I just sent him an email, so hopefully we will hear back soon.

Thanks for all the notes! It's always my power users who discover the most obscure bugs. The RNAV localizer 360° wrap-around was already reported on this forum, and the fix is ready for the next update. As for the needle positions, it may be due to the fact that the wraparound allowed for inadvertent selection of OBS courses beyond 360°. The update should fix all that shortly. Indeed you found something from the Piston Duke that accidentally made its way into the Turbine Duke! The fuel flow failure triggered the loss of a circuit that does not exist in the Turbine Duke. I've fixed that as well. Thank you for letting me know!

@Piper201 said in If you have engine problem - check your bindings (Honeycomb Bravo): SimHanger Flight Simulation Yes they do. I set up my Honeycomb Bravo using their tutorial back in 2020, but a lot of thing changed since than LOL

@Randolf I just think, since it's already been made, it would be a nice customisation addon. I'd like to be able to remove the ADF and KNS-81 personally anyway (like I said, dual GTN750s would be awesome).

I was just doing a test with night flying and saw it come on very briefly (perhaps the 2 seconds that the audio should play?). Tested a bit more and it stays illuminated longer the less VS you pass it with, so it is just connected to distance below DH selected. The lamp is however supposed to stay illuminated untill you reach 20 feet AGL so it should have stayed on for my screenshot. [image: abGEm0f.png]

@Mustang For what it is worth I decided to to change the "Yoke" set up for the DC-6's. 4 mags and one switch, I removed the L,R,Both and Start...Then...I got really feisty and cleared out "All" electrical bindings...on both Wheel and Throttle. There are times I can't get my fingers behind the engine controls...like right after Take Off. So it may be a little "Old School", I just use the Mouse". And also the Lear 35 (PWS) just got an update and I noticed the landing lights would not go out at all, and that is with the above "No switches" set-up, SU-15 issue adding fuel to problem?

@Nicotine70 This is a Life Saver Thank You so much been pulling out my hair to try to figure out why all of a suddon it didn't work but with advice it works for me again Thank You