Do you have the same issue if you follow the OP’s steps to reproduce it?
• Yes
Provide extra information to complete the original description of the issue:
• Also occurs in the A320N, A321LR, A400M and Beluga XL. Also occurs with the autopilot engaged in these aircraft.
If relevant, provide additional screenshots/video:
Takeoff from Runway 24L at LIRN. This video shows how when using the cursor mode in any capacity during this phase it’s like the AI Copilot is trying to retract or change the flaps and mess with the throttle as seen my the flickering on the PFD.
This is shortly after the first video I linked to you. Showing that basically without fail activating the cursor mode causes something or someone to mess with the throttle.
This is when I had just got cruise on the short test flight to capture this footage, again activating cursor mode to do anything causes the throttles to TOGA themselves without fail. So any cursor mode usage has to be quick if you don’t want to begin overspending or stalling depending on what it decides to do.
This video shows the prior setup and capture of GS and LOC and activating autopilot 2 for the DUAL ILS approach, checked to make sure the throttle was correct as you mentioned, just to make sure it hasn’t been pilot error this entire time I’m hoping it’s not lol
This video shows the final approach into LIRF 16L just after capturing the LOC and GS and descending smoothly with the CAT 3 DUAL landing, also again checked the throttle detent to make sure it was correctly positioned, as stated previously at the last moment after the PFD transitions to LAND mode it suddenly pitches up and deactivates autopilot and goes TOGA. Again not entirely sure if I’m doing something wrong, it’s a bug simulator side, or aircraft side.
