Pilatus PC-24 Autothrottle Engagement Failure - Invalid Node Code Bug

Bug Reporting Hub Aircraft & Systems
, , ,
1

Using the template below will greatly help the team reproduce the issue and ease the process of fixing it. Before posting, search for an existing report. If you are not sure it’s a bug, please first report in User Support Hub.

3 tags are required - add them in the tag section next to the title above:

Feel free to delete this quote section after adding your appropriate tags.

ISSUE DESCRIPTION

Description of the issue:

The Autothrottle (AT) button fails to arm or engage the autothrust system on the default Pilatus PC-24 under any flight configuration. Physical cockpit clicks, hardware bindings, and DevMode execution all fail to toggle the system. DevMode tracking reveals an internal scripting reference error.

FREQUENCY OF ISSUE

All missions, flights, and conditions.

REPRODUCTION STEPS

Please list clear steps you took in order to help our test team reproduce the same issue:

  1. Load into a flight with the Pilatus PC-24.

  2. Power on the aircraft, set up autopilot for at, and attempt to engage the AT button via mouse click or mapped hardware keybind.

  3. Observe that the button fails to illuminate and does not engage autothrust.

YOUR SETTINGS

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 User Support Hub.

What peripherals are you using, if relevant:

Honeycomb Alpha, Bravo, Charlie. Mapped hardware to TOGA button on throttle 1. Tested on 2 axes.

[PC Only] Are you using Developer Mode or have you made any changes to it?

Dev Mode used for observation.

[PC, MSFS 2020 Only] Are you using DX11 or DX12? N/A

[PC Only] What GPU (Graphics Card) do you use? AMD Radeon RX 9070TX

[PC Only] What other relevant PC specs can you share? Quest Meta 3 using Virtual Desktop; behavior independent of monitor or VR modes.

DevMode Behaviors / Console Logs:

  • Using Ctrl + G to monitor the Behaviors Window under InputEvents/Components:
  • When pressing the AT button, the tracked parameter spikes briefly to ~60 (on a 0-100 scale) and instantly forces itself back to 0.
  • The DevMode console simultaneously throws a red error script: “Autothrottle_Arm node invalid”.

MEDIA

Video of PC-24 Autothrottle Engagement Failure

Please add a screenshot or video of the issue occurring.

2

On PS5 i have the PC-24 and AT during flight works fine (95% of the times) The only point where it doesn’t engage is during take off while in the real thing it should.

3

WORK AROUND:

Map any button to ARM AUTO THROTTLE. Press it before taxi/take-off. This will force the Node error to reset and remap the node to the display event. The button will work correctly.

4

I have mapped the AT to a button. You mean I should press it before takeoff when you are ready to take off? I did it but there a sound error and it doesn’t engage. Even before rotate it doesn’t engage, only when you are flying and took off just few feets above ground

5

I use a keyboard mapping to arm the auto throttle, set TO GA once lined up then full throttle. Not had any issues so far - I don’t have the same control hardware as you though.