I have the exact same mapping in 2020 and 2024, including zooming with: LB+RT to zoom in and LB+LT to zoom out in the “Cockpit Camera>Cockpit Zoom In/Out” mapping. The thing is, in 2020 there’s no conflict with the flight surfaces, but in 2024 the yaw moves when doing this action. I wonder if it’s a bug or by design; I’m leaning toward the latter. Is there any way to fix this?
I’ve also noticed that the zoom “jumps” when holding down that combination, whereas in 2020 it’s continuous and smooth depending on how far I press the trigger.
This topic has been moved from the Bug Reporting Hub to the User Support Hub > User Interface & Activities as it is the most appropriate category for your topic. Please ensure to complete the full Bug Reporting Template if you are wishing to report a potential bug within MSFS.
With this, in 2020, I have full control over the cockpit camera movement while making it immersive, eliminating unnecessary mappings like switching between cockpit panels or fixed views, and at the same time, it doesn’t interfere with the control surfaces.
But yesterday, on my first flight in 2024 with this mapping, it was a nightmare. Performing any action that requires the joystick or triggers simultaneously moves the flight surfaces. Even in cursor mode while controlling the EFB, I registered a movement that caused the plane to roll 90°, deactivating AP in the process.
I’ve also noticed that moving the cockpit with RB (hold) + LS and then controlling the view with RS causes it to become unusable even if you physically hold the RS down. You have to release it and move again to fix it.
For more information, I noticed that in the control options, the joystick detects two actions: one with an arrow where I move the joystick and then the same icon with the same arrow but with an additional arrow on the opposite side.
As notified in above post, when creating a bug report, please ensure to complete the full Bug Reporting Template. It contains key fields for the devs and users in order to replicate and contribute to your report.
What you are describing is tipically a binding conflict between the views contols and the autopilot (or other actions). So since you have provided detailed information, my recomendation is to wait for users support that could help on this.
Are you using the Live version (1.5.27.0) or the beta SU4 (1.6.13.0) ?