Piston & Turbine Dukes

@rondon9897 You set up the standby frequency and then swap it to active. You can only alter the frequency that is in the standby box (right side), once swapped to active it cannot be altered. This way you always have your "next" frequency tuned and ready for use.

@Ipf5ZDco16 I would guess the priming rate is part of the special engine simulation code and is probably not something that we can modify as end users.

I wasn't able to hold the starters to on until the engines started, in the piston duke today. I use the left mouse button. A couple of other guys in the group had the same problem.

@sandeepkr70 yes there is.

I imagine one of Nick's worst enemies is potential 'feature creep' - deciding what to implement and what to leave on the wishlist. Especially when us users start making demands for every aircraft... Whether they come or not, I also love all these little features I still wonder about the typical operation for heating the Duke. Perhaps different pilots have different preferences. Once airborne, I had thought it preferable to use heat from the engines instead of the combustion heater, but seems this may not be the case. In the sim (especially) it's hard to regulate the heat with the pressurisation hot air controls. I've pulled the air handles out partway before to alleviate load on the combustion heater, then realised my cabin was 30°C a short time later... toasty! Seems that relying on the combustion heater alone with a boost from the pressurisation hot air (where needed) is the way to go. This is more or less indicated in the manual's guidance, typically at -12°C OAT and below, yet it also says the combustion heater is a notoriously dangerous piece of equipment! So roll the dice and take your chances...

@Black-Square The odd thing is, this just recently started. I have about 12 Hobbs hours and half of that is night flight, and this just started. Nothing has changed. I'll try the empty Community folder this week and report back. Thank you for the response.

@Avionic I agree with you 100%, the wider spotlight is better (if a bit too intense) than the 'cabin bounce' effect. To implement our own fix, as far as I have read, we'd need to copy one of the Asobo light .fx files to create a new light with the wider cone and reduced intensity (easy enough), and then reference it in the systems.cfg file. It might also be necessary to put the path to the effects folder (with the new effect) in the aircraft.cfg file. I've skimmed the SDK and it gives all the information for each part, but doesn't 'join the dots', so I'm not sure if would work or whether more steps are needed. I'll wait for an expert on this one. If I try it and fail, I'll likely waste hours trying to solve it out of dogged determination. I'm not sure it's worth that much time investment so it's safer not to start! I can get by with the cabin bounce effect for now until something better comes along.

@hughesj2 Interesting tip, I will surely try it, THX!

I just have the same issue in the Baron 58, did you find a solution?

@Black-Square Ah, ok. No problem! Honestly, that's more exciting to know it's actually coming rather than a genuine mistake. Looking forward to it!

OK now it's working, 21 folders I have removed, now need to see which one it is...

Ahh, OK. I do throw the ignition switches into auto on final. I will try that. And thankyou for the pointer over the the bindings. CG.

There's a version 1.2? Has it been released yet? Oh, version 1.2 of the TBM... still (im)patiently waiting for the Duke update.

Sounds good. Makes sense.

Pretty sure I do, v1.1 (or 0.1.1 in the Manifest.json) as we've only had the one update so far if I recall. I landed today in light rain and saw no issues, so replicating the conditions for it might be tricky. At the time I made the video, I didn't actually start up or go flying to see if the effect disappeared - the conditions were worse than the forecast so after loading up the sim I closed it again and went to do something else with my day! (I was at a short strip near the limit of performance already and there was a 20kt crosswind too.) It's way down the fix-list for me, but in case it was an easy/obvious fix I thought it worth a post. I did a quick search but didn't find any other posts (probably didn't use the right words). I also have the Comanche installed, knowing it affects the Duke's landing lights for a few people (but so far not for me). Anything is possible, however improbable!

Expensive!

After much troubleshooting using Addon Linker and removing things from the community folder, the problem at least for me, was the Navigraph AIRAC Cycle rev.2 - once I removed that the ILS returned to full functionality. Interestingly, after reinstalling it again it still worked. Weird.