Piston & Turbine Dukes

Uninstalled (included a couple of liveries) then reinstalled 1.0 and tested and it worked. Then upgraded tested and it worked?? don't know....but thanks for the help. Love this plane!!

i was wrong, when said in mv corsair auto rich in model. there actually working autorich and autolean. about dukes. i really hope turbine and piston will not react on mixture and condition axes respectively... because some people include me set mixture and condition in the same axis, in turbine duke mixture axis moves lever from 0 to 100 and back(not problem when you don't know it), in piston one, playing with mixture+condition axis on big alt can kill engine and will try to kill it in any way. for example azurpoly bronco have 0 react on mixture. and afaik some turbo models use or used before mixture axis for condition operation. so. would be cool, if turbine model will ignore mixture axis and piston - condition. because changing profiles where we can not to do this.... why?

REALLY appreciate both of you taking the time to articulate these details. The Black Square aircraft have inspired me to take my understanding to the next level, before I start to activate failures. Thank You!

My guess is that he will wait until the new duke update its out, and then push that version to the marketplace

@Black-Square Ah nice to read, just wanted to know when next update is planned! Thank you!

Works perfectly! Thank You!

Thank you so, so much @theegg52!

@Randolf said in RNAV LVARs: when the plane is stationary on the ground, the DME display when switched to RNAV mode, starts counting wildly upwards till it reaches 999.9 and stays there I saw this for the first time today and immediately found the problem. It was due to the interpolation I added to enable autopilot tracking from the RNAV system. Believe it or not, the DME information update interval from the simulator is so slow that it cannot be used to accurately drive an autopilot! I suspect that code has been unchanged since the 1980's.

Hi All, I added a quick solution to this in all four of my aircraft that have the tablet installed now. There will be an persistent option on the tablet titled "VR Tablet Static Position", which will lock the tablet in a position much further away from the camera, and obscuring as little of the panel as possible. I my VR users will find this to be a comfortable solution!

@Black-Square said in START/IGN Fuse always blowing: hardware bindings are causing the starters to continue running behind the scenes Good call. Using SPAD once I unbound the key switches works like a top. Thanks for the hint!!

I think that too and was sad is I spent some time seeing if it was a problem but as I found it was a storm in the teacup I did learn a lot about the dukes and also the sim so it was not a total waste. smiles

Thanks, I understand better. I no longer have any problems starting the engines.

The only other solution I can suggest is to use the flashlight (Alt-L) temporarily as needed. Perhaps change the keybinding to something that's quicker/easier to use, or a spare button on a controller. May cause night-vision blindness; use with caution! (There are always those incredible flashlight-colour-changing add-ons which you can buy in the Marketplace. Surely great value!)

From memory (standard disclaimers: only for simulator use, I won't be liable, I'm not a flight instructor, etc.), the Cessna 172S POH says to lean for ground operations by setting 1200 RPM, then leaning for max RPM. In practice, you can lean somewhat further, and at some point you know from experience about how far you need to pull the mixture knob out.

@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.