Piston & Turbine Dukes

Well I went on Snapfish and made up two coffee mugs of my own as they were just 6 bucks each and I couldnt decide if I like the black or white mug better. Heres a video showing the mockup mugs. I'm left handed so I wanted the main logo to show out. https://youtu.be/6rJYd1e8xcc

Thanks, I ended up achieving this by coding the HCB via Mobiflight: -4096 (>K PROP_PITCH1_SET) and -4096 (>K PROP_PITCH2_SET) ... and make sure you delete any other feather bindings in MSFS you may have previously had. Once I pass either prop. lever through detent it selects full feather on that prop., but I assume there is not a graduation possibility in any case. I have checked the movement and each prop. RPM operates independently into feather as above. I have a question though, if I leave the prop levers at full fine, and shut the engines down, the blades appear to be in full feather when they stop (despite not moving the prop . levers at all) ... is this correct?

Hey thanks - yep, I'd certainly appreciate any further info. you're able to provide, thanks :).

Do you perhaps have any pics/vids of your panel when trying to intercept radials - would make it easier to detect anything wrong. Sounds like you are doing things correctly. I just know, that for me it has been working fine for me intercepting VOR radials. So there is likely not anything fundamentally wrong with the Duke.

Simhagers solution in 24 similar to 20. Bind feather 1 button to hold prop reverse thrust AND increase prop 1 pitch. Similar for prop 2. This means both feather buttons are mapped to hold prop reverse thrust. Just like windows 11 is a reskin of windows 10, fs24 looks better but none of the problems have been fixed. Microsoft.

@Black-Square I have a consistent way to replicate the issue. My TDS folder for the GTN750Xi is outside the community one so that I can show the instruments on a separate monitor. If I choose to use in the aircraft the GBS530/430 combo, the the APP will not show as active BUT eventually the localizer will be captured. Not the Glide/Slope. Using the KX instruments will bring back the APP showing as expected and the GS to be captured correctly. HTH

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