52 minutes ago, Gazzareth said:

That depends very much on the GPS you are using. If it's PMS you leave that switch alone and change it on the GTN itself. Not sure for the TDS / GNS though .. .. but I would assume that the GNS goes by the switch, else it's kind of pointless..

Hm, good point.

I've only used the TDS GTNXi, but there that button definitely switches between VOR/LOC and GPS. You can also switch from the GTN unit (or even let it auto-switch on an ILS approach), and the button on the panel will display the current mode.

Not sure how this works with other GPSs though. 

2 hours ago, Cpt_Piett said:

You were indeed right all along... and as I had doubts, I shall retreat to Dagobah and re-think my life... maybe I'll buy some death sticks as I'm probably going to check out that cave Luke was talking about 🙂

“Pass on what you have learned. Strength, mastery, hmm… but weakness, folly, failure, also. Yes, failure, most of all. The greatest teacher, failure is.”

😇

Since you seemed to be having more problems with the engines than some of us, did you see this post on the Just Flight support forum?

https://community.justflight.com/topic/6599/if-you-have-engine-problem-check-your-bindings-honeycomb-bravo

I'm glad the mixture control will be more tame now, but the way you make it sound is much worse than what I think a lot of us were experiencing since it didn't take away from my enjoyment of the aircraft at all. It certainly would not be the first time a control binding issue caught me off guard.

15 hours ago, martinboehme said:

Then I don't really have any good ideas...

Which GPS are you using? Can you share a screenshot that shows the problem happening? 

Thank you, Martin.
It turns out that the problem was due to an incompatibility between the Stream Deck programming for the Duke and that of the MiniCockpit which I also use for the GA planes. Using hardware instruments is much more immersive than mouse clicks, but it can cause some serious headaches when the programming of the actions is not perfect. It's settled now. 😊

 There is definitely something wrong with the trimming in the piston Duke. Ryan, I hold the utmost respect for you, but using a trim button in an aircraft with a trim wheel is not the answer. I was told this same thing regarding this wild pitch issue in the 414. 

 With the 414 it was a simple fix by downgrading to a previous version.   FlySimWare still denies there being an issue, even though my Saitek trim wheel works perfectly with their earlier release.

7 hours ago, David Roch said:

Thank you, Martin.
It turns out that the problem was due to an incompatibility between the Stream Deck programming for the Duke and that of the MiniCockpit which I also use for the GA planes. Using hardware instruments is much more immersive than mouse clicks, but it can cause some serious headaches when the programming of the actions is not perfect. It's settled now. 😊

Excellent, glad to hear it! 

I've been searching and searching but I can't find any remedy telling me how to get my mouse to work on the tablet. I click and click and cannot get any slider or input to work. Does anyone know what I need to do to get this operational?

Any help is much appreciated.

4 hours ago, Piper5299X said:

 I hold the utmost respect for you, but using a trim button in an aircraft with a trim wheel is not the answer.

Both the (real) Duke and 414 do have trim wheels, but they also have electric trim motors with yoke-mounted switches. The electric trim is the standard way to trim these aircraft. I doubt that a Duke or 414 pilot would ever use the trim wheel operationally unless the electric trim failed.

Aw the Duke 😺 the supreme highruler of the flight sim world....

Yesterday I have finally installed SU 15 and the new Duke update and now the GNS530 functions flawless.

And yes planes are all trimmed electrically, even the 737, with a little rocker switch on the yoke. But the trim wheel (even in an Airbus 320) can be moved by hand too, and some more simple GA planes have manual trim wheel.

 

20 minutes ago, JetCat said:

Aw the Duke 😺 the supreme highruler of the flight sim world....

Yesterday I have finally installed SU 15 and the new Duke update and now the GNS530 functions flawless.

And yes planes are all trimmed electrically, even the 737, with a little rocker switch on the yoke. But the trim wheel (even in an Airbus 320) can be moved by hand too, and some more simple GA planes have manual trim wheel.

 

What Duke update?? My account only shows 0.1.0. Did I miss something??

There was a Duke update I think a week ago or two weeks ago to make the GNS 530 GPS functional for the new SU15 update 😺 I was a bit preoccupied with my new Apache for a few weeks that´s why I have installed the SU15 and the Duke Garmin update yesterday.

I find the temperature in the cabin going extremly fast way too high when on the ground. On a decent day with 25°C outside air temperature, 6 pax inside, by the time I am ready to take off the temperature inside the cockpit is around 42°C.

I know by experience that it can be pretty hot on a suny day at the ramp but I find the rise in temperature a bit too extreme.

1 minute ago, Bushido5 said:

I find the temperature in the cabin going extremly fast way too high when on the ground. On a decent day with 25°C outside air temperature, 6 pax inside, by the time I am ready to take off the temperature inside the cockpit is around 42°C.

I know by experience that it can be pretty hot on a suny day at the ramp but I find the rise in temperature a bit too extreme.

The best place to report things like that would be here https://community.justflight.com/category/87/piston-turbine-dukes

4 hours ago, JetCat said:

There was a Duke update I think a week ago or two weeks ago to make the GNS 530 GPS functional for the new SU15 update

It might be 'functional' but its display of waypoint distances in mine is useless. Back to the 750 I'm afraid.

4 minutes ago, sloppysmusic said:

It might be 'functional' but its display of waypoint distances in mine is useless. Back to the 750 I'm afraid.

Sometimes if you're using Direct To vs having a full flight plan loaded the variables won't show.  I don't know why this is.. I keep seeing it randomly.