The Prop sync switch does work but only if there is a difference of more then 50 RPM.

I would assume that the engines sound slightly "out of sync" because they are at different distances from the pilot, even if they are perfectly "mechanically" synchronised.

The Prop sync switch does work but only if there is a difference of more then 50 RPM.

Slight correction, prop sync only works if there is less than 50 rpm difference between engines, and yes it works perfectly in the RealAir duke.

Ok thanks, i'll have to shape up on my engine management then :(

Slight correction, prop sync only works if there is less than 50 rpm difference between engines, and yes it works perfectly in the RealAir duke.

Jep, I missunderstood this.

The Turbine Duke is brilliant...beautifully modeled in all respects, but I have one frustrating gripe: The pitch control buttons on the AP sometimes stick, causing the vertical speed setting to "run away". Is anyone else having that problem? FWIW, I've already considered the possibility that I'm moving the mouse cursor off the click spot while the button is depressed, but that's not what's happening.

The Turbine Duke is brilliant...beautifully modeled in all respects, but I have one frustrating gripe: The pitch control buttons on the AP sometimes stick, causing the vertical speed setting to "run away". Is anyone else having that problem? FWIW, I've already considered the possibility that I'm moving the mouse cursor off the click spot while the button is depressed, but that's not what's happening.

Nope, I´ve never enountered this.

The Turbine Duke is brilliant...beautifully modeled in all respects, but I have one frustrating gripe: The pitch control buttons on the AP sometimes stick, causing the vertical speed setting to "run away". Is anyone else having that problem? FWIW, I've already considered the possibility that I'm moving the mouse cursor off the click spot while the button is depressed, but that's not what's happening.

I wonder if you have mouse "ClickLock" enabled in Windows, you can see if its enabled under mouse properties in the control panel.

I wonder if you have mouse "ClickLock" enabled in Windows, you can see if its enabled under mouse properties in the control panel.

We have had a couple of support queries about the "stuck" mouse locking the Vertical Speed selector. I've been wracking my brains trying to work out why a tiny minority have reported this, but never knew about the "clicklock" function in windows. Maybe this is the reason. If so, thanks Andy for mentioning it.KInd Regards,Rob - RealAir

Thanks for the suggestion, Andy.Rob, I'll give this a try as soon as I get home, in about 45 minutes, and will post my results here.

The Turbine Duke is brilliant...beautifully modeled in all respects, but I have one frustrating gripe: The pitch control buttons on the AP sometimes stick, causing the vertical speed setting to "run away". Is anyone else having that problem?

I have experienced this four times now in 48 hours on the Turbine Duke. It can be a real pain in the YOU KNOW WHAT when you have to disconnect your AP on a sketchy, low vis approach.

On my machine, at least, it is not "ClickLock". I verified that ClickLock was deselected, checked it, hit "apply", unchecked it and hit "apply" again. No change...the UP/DOWN buttons on the AP still cause intermittent VS runaway.

...How often does it happen to you?

On my machine, at least, it is not "ClickLock". I verified that ClickLock was deselected, checked it, hit "apply", unchecked it and hit "apply" again. No change...the UP/DOWN buttons on the AP still cause intermittent VS runaway.

Hi EMB and Tracon, in case you haven't written to me before, please do email me at RealAir support and we'll look at why this is happening for you in detail.Rob - RealAir

Well, in the emergency Procedures chehklist they say in any engine faillure "fuel selector- off". I think it means that you can switch to crossfeed to maintain stability. I personally haven´t had an engine faillure, so I can´t comment on this who I do it but my FS knowledge says crossfeed. So you can test who crossfeed works.

Hi,I don't have any real life experience with the Turbine Duke but I do have experience flying multis. Generally, when you have an engine failure and you decide to continue to your destination (almost never in real life), you want to secure the failed engine after feathering, that's why the checklist states that fuel valve must be off. The x-feed must be managed manually if you desire to use it, that means that you have to time the fuel consumption to maintain balance switching the valve between ON and X-Feed on the engine that is running not the failed one. Of course the time will depend on the rate that your plane is burning fuel. Like I said I don't have any real life experience with the Turbine Duke but I would try something around 30 minutes for each position.You should never ever leave a failed engine with its fuel valve OPEN, X-Feed or ON, never!hope that helps.regards,Igor