Piston & Turbine Dukes

@Black-Square
Thanks for the input! Unfortunately as I'm on the Xbox platform, this makes matters a little more complicated as I rely on the in-sim Marketplace. The version of the 750 I can use is whatever comes loaded with any given aircraft. Since it's not a separate module on Xbox, I have no way of updating it. You do bring up and interesting point though, and one that I haven't thought of before... Given the rate at which the 750 receives updates, how will these updates ever make it to Marketplace products which come with the free GTN pre-installed? I suppose it's up to individual devs?

Thank you for your help Zwoop68

Wow, you're absolutely right about that. It appears to be a bug/"feature" of the flight simulator, as the input event "K:PITOT_HEAT_TOGGLE" is completely disabled when there is a pitot blockage. Given what I have seen under the hood of MSFS, I suspect that behavior has been there since at least the early 2000's. I've been contemplating creating my own elaborate simulation of pitot-static effects, which would solve that problem as a side-effect. Thanks for pointing it out.

What a tiny detail on the ADF instrument! I've fixed that now. It was very easy, as you said. Thank you!

I think this is clear / resolved now. After I arm APPR, altitude adjustments need to be performed using the pitch knob. If the pilot prefers to use the CWS button, they need to re-arm APPR as AP is temporarily deactivated when CWS is used.

I have my Streamdeck + knob set up to zero the pitch knob when pressed, and to apply +1 or -1 to the pitch each time it is turned clockwise/counterclockiwise. Any other inputs or perspectives on this topic would be appreciated.

Thoroughly enjoying flying the Turbine Duke ... with each flight I get better and better.

@hangar_101 Bit off topic, but this seems to work also on a TBM.
File is ...bksq-aircraft-tbm850/SimObjects/Airplanes/bksq-aircraft-tbm850/model/AnalogTBM.xml and line number 613:

TBM_FuelLever.png

You can watch both videos where readings are different then what I have posted but both these videos are before the update. It may be that you have corrected the behaviour of manifold pressure at these altitudes or goes wrong. Please guide me on that.
https://www.youtube.com/watch?v=YXenEWyGIoM&t=173s
https://www.youtube.com/watch?v=ooXdnkZChJ0&t=121s

@Black-Square said in Unable to match the Climb & Cruise numbers in the manual:

What a beautiful screenshot. I don't get to see enough of those online! It seems most social media users fly the big tube-liners, so I rarely get to see the Dukes in use.

You are right, but there are a fair amount of screenshots of the Duke and others in various Discord servers. V1's Discord has a lot of fans of GA. ;-)

The thread below has some of the answers you are looking for

https://community.justflight.com/topic/6794/cowl-flaps-and-potenciometers/11

Put on the engine covers.

No problem, I'll test more during these weekends. from cold n dark to cutting the engines, implementing these suggestions. What you do is incredible work, I'm sure it could be something here on my side. Congratulations on the work with Duke, it really is a new level for MSFS. Greetings from Brazil!

@Allard You can mute it by pulling the circuit breaker for the stall horn on the copilot side.

Thank you so much for your prompt response.

In the event it has not already been brought to your attention: A correction needs to be made to both Piston & Turbine Duke manuals which do not list the Flight Director variable as "L:var_FlightDirectorVisible," but rather, "K:TOGGLE_FLIGHT_DIRECTOR."

In pursuing this matter with RSG, this is the response I received:

Since a large number of the variables for the Duke's use L:vars you would need to program the GFC500 autopilot using software like Spad.next. Our current device interface is not able to send L:Vars.

Additionally the Duke's internal coding (at least on the Turbine version) has a flag in it to maintain the activation of the MSFS Flight Director and HDG modes on the Century 4 autopilot. The L:var flag that is listed in the manual for the flight director will only turn on/off the FD needles on the attitude indicator in the 3D cockpit, while the lights on the GFC500 will always stay on for the flight director.

I do not have Spad.next, so I am unable to test it with the GFC500. But I do have FSUIPC, and unfortunately, the GFC500 does not show up as an addressable device.

I will pursue this matter further with RSG to see if they might consider updating their interface to include L:Vars. I would be open to other solutions you might have.

Thank you for your time, and for providing such awesome products.

Ahhh that explains it, awesome, thanks! This is the attention to detail that I admire in your add-ons.

@michel J'espère que ce message se lit correctement. J'utilise Google Traduction. Je pense qu'il s'agit d'un problème connu avec les installateurs Windows. Veuillez créer un ticket avec l'assistance Just Flight, et ils vous aideront. Étant basés au Royaume-Uni, ils pourraient même avoir quelqu'un qui parle français !

@DrZGard I've reinstalled the previous update (the initial version, before the update) and this issue has disappeared. Odd haha.

I'll take to a place I landed last night in Ireland that's grass and kinda bumpy.