A310 Increase/Decrease Altimeter Key Bindings not Syncing when Link Instruments is ON

:wave: Thank you for using the Bug section, using templates provided will greatly help the team reproducing the issue and ease the process of fixing it.

2 tags are required: One for platform, and one for aircraft.

Are you using Developer Mode or made changes in it?

No

Have you disabled/removed all your mods and addons? If the issue still occurs with no mods and add-ons, please continue to report your issue. If not, please move this post to the Community Support section.

Yes

Which aircraft are you reporting an issue about? (Please also add the proper tag for it)

A310

Which aircraft version are you experiencing this issue on? (You can find this listed in the Content Manager under the Aircraft Name)

1.1.12 & Enhanced 1.1.7

Brief description of the issue:

When “Link Instruments” is set to ON, the Increase & Decrease Altimeter key-bindings are only adjusting the Captain’s altimeter. The standby and FO’s altimeters remain unaltered.

Adjusting the Captain’s altimeter with the physical knob on the instrument via mouse will result in all three altimeters being adjusted, as expected.

Provide Screenshot(s)/video(s) of the issue encountered:

Detailed steps to reproduce the issue encountered:

Set key-bindings for Increase & Decrease Altimeter, set Link Instruments to ON in the EFB. Attempt to adjust the altimeter via the key-bindings and observe only the Captain’s altimeter will change values.

PC specs and/or peripheral set up if relevant:

n/a

Build Version # when you first started experiencing this issue:

1.35.21


:loudspeaker: For anyone who wants to contribute on this issue, Click on the button below to use this template:

Do you have the same issue if you follow the OP’s steps to reproduce it?

Provide extra information to complete the original description of the issue:

If relevant, provide additional screenshots/video:

Do you have the same issue if you follow the OP’s steps to reproduce it?

Provide extra information to complete the original description of the issue:

I’m testing the A310 in SU15 beta 1.37.15.0 and this issue is still plaguing the aircraft’s autopilot controls.

It would be nice if this would shift from feedback logged to bug logged and get slated for fixing…

If relevant, provide additional screenshots/video: