Autopilot disconnect function on the NGX with Saitek yoke

[sidfadc 1,344]

Hi guys,

 

I use a Saitek yoke, any reason why the red button underneath the left handle disengages autopilot in the NGX when I don't have it assigned anywhere in my sim.  For some time now I have all joystick and button assignments removed in FSX main controls.  I use FSUIPC for axis setup and LINDA for button controls.  In both FSUIPC and LINDA there are no assignments for autopilot off.  Funnily enough I am having the exactly same issue with my Majestic Q400???  I'm totally confused.

 

The obvious answer is I must be mistaken but last night I put some time aside to look at this issue and I definitely do not have any button assignments on the red button in either FSUIPC or LINDA.

 

Can anyone help?

 

Thanks

Sid

Actually just thought!  You can assign buttons through the FMC I think?  Maybe I have it assigned in there as well, I never thought to check that last night!

[scandinavian13 5,192]

 

 

Funnily enough I am having the exactly same issue with my Majestic Q400???

 

This means it's being set in your sim's settings, in FSUIPC, or in some other program. I would double check your sim key command settings for duplicates/conflicts.

[sidfadc 1,344]

Thanks and yes that is the obvious answer but I went through FSX main controls, FSUIPC and LINDA last night and it isn't assigned.  I'm obviously missing "something" so I need to have another look.

[scandinavian13 5,192]

Thanks and yes that is the obvious answer but I went through FSX main controls, FSUIPC and LINDA last night and it isn't assigned.  I'm obviously missing "something" so I need to have another look.

 

Couple thoughts:

• An errant command was missed, or the wrong command was assumed (looked for AP disconnect instead of some other key command that would affect it, such as trim).
• A key command is set in the Saitek software that is causing something like trim up/down to be sent to the sim.
• A trim axis is set, but was not centered prior to AP engagement (this is an absolute must if you're using a trim axis instead of trim up/down commands), and it isn't so much the key being pressed that's causing the disco, as much as it's the key being pressed that reminds the computer to check for any other values from the hardware that should be fetched...such as the TO trim set a few hours ago that's still set on the axis.

 

Either way - if it's multiple aircraft, despite the ability to assign commands in the FMC, that's not going to be it. This isn't a PMDG issue if it's also affecting the Majestic.