Piston & Turbine Dukes

@Raller said in COWL flaps when loading the plane on the runway: Mississippi, 2 Missisippi, 3 Missisippi That is indeed exactly how Duke operators learn how to manage their cowl flaps. The real reciprocating engine Duke owner who contributed to this project recently said to me that he plans on creating an aftermarket solution for Dukes with a small digital indicator for the cowl flaps position.

@Nicotine70 I've sorted the issue now. The fix? Absolutely nothing, it randomly decided to work for no apparent reason at all. It's definitely not a binding issue as I have nothing bound to any AP controls (control surfaces, trim and power management only).

Strange enough, moving the A2A Comanche out of community resolved the problem.

@lilycrose - I’ve been noticing the same thing. While I think I’m usually pretty kind to the engines, there was one flight where my CHT hit the redline a few times, and I’m surprised that both of my Duke’s engines have remained at 100% after all of my flights so far with no repairs done. When I was primarily flying the Bonanza it definitely showed a little wear over time with similar treatment. It has had me starting to wonder if there’s something not quite working here.

@Black-Square - Thanks. Sure enough, it was a failure and I misread the manual.

Just finished that flight, SCCI-SAWH. I changed from PMS750 to GNS530 and 430. I didn't use the GPS for navigation, but only VLOC mode. No problems at all. Everything worked as expected. Maybe i will try it again with 530 but using the GPS for navigation.

Thank you very much, that's what I understood.

Ok. then I made a mistake in my thinking. I was of the opinion that the friction lock acts on the trim. Thanks for the quick answer. Michael

@LondonSimmer looking at the files, I don't think the final prop heat amp value is actually saved into a convenient variable, but this is a simplified expression that is used to calculate value on the prop amp meter on the panel: (A:PROP DEICE SWITCH:1, bool) 17.5 * (A:CIRCUIT ON:10, bool) * (A:PROP DEICE SWITCH:1, bool) 18.0 * (A:CIRCUIT ON:11, bool) * + (A:ELECTRICAL MAIN BUS VOLTAGE:1, Volts) 12 > * The actual expression is much longer, and introduces effects like the needle wobble, but this should be just the plain numbers, if I got it right. Seems to work for me.

I think you might be right about the rnav/nav1 selector its probably with the kns, even tho i dont have the KNS installed on my plane only 2 GTNs... so i'm not sure.. I still dont get why i dont get the GS working as its a different issue, ill try again to fly an ILS and see if i can get it to work Edit : okay i just tested again and now it seems to work ill try with a 3D rnp now Edit : okay seems to work now idk why i'll let you guys know if it does it again

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)