PC-24 Career related issues (Start Up / NAV-Mode / Heading Bug) // After update 1.2.7.0 / remains after 1.2.8.0

Bug Reporting Hub User Interface & Activities
, ,
1

ISSUE DESCRIPTION

I add the remaining career bugs after update 1.2.8.0 in a new post in this topic below.
So far just the engine start.

The following issues were noted after 1.2.7.0 update

Description of the issue:
As in the topic PC-24 completely broken already reported, only few general items have been fixed. But there are some career specific issues, which work in free flight.

Engine Start
The engines will not ignite in career mode, even though the aircraft has sufficient fuel at the beginning of the mission. The engines spool up, ignition is initiated, and the booster pumps are activated, but the engines fail to ignite. (This issue does not occur in free flight mode. In free flight, the engines can be started, but only once. If the start is aborted, the same issue occurs, preventing a second attempt.)
(Screenshots 1 & 2)

To proceed with the mission, the start-up phase can be skipped directly to the taxi phase using CTRL-N, which results in the plane being ready with running engines.
(Screenshot 3)

NAV - Mode
NAV mode initially seems to work correctly. The bearing pointer appears in blue on the central navigation screen after the flight plan is activated.
(Screenshots 1 & 2)

However, this changes after skipping to the taxi phase. The bearing pointer suddenly turns white, and NAV mode will not engage, even if the flight plan is re-sent to the avionics and set as active again.

Heading Bug and Track Mode
Initially, the heading bug adjusts in one-degree increments when using an external dial (Bravo Throttle Quadrant).

However, after using CTRL-N, the heading bug adjusts in ten-degree increments when controlled by the external dial. To make fine adjustments in one-degree steps, the heading dial in the cockpit must be used with the mouse.

Additionally, the Track mode does not appear to function properly. Engaging it has no noticeable effect, even in the presence of strong crosswinds. (Same issue with PC-12)

Personal comment:
Many features of the game are fantastic. I truly enjoy the career mode; it’s an excellent addition that adds an extra layer of depth to the gameplay. However, I am disappointed with how reported and even acknowledged issues/bugs are being addressed and resolved.

[PC Only] Did you remove all your community mods/add-ons? If yes, are you still experiencing the issue?

  • Yes

FREQUENCY OF ISSUE

How often does this occur for you (Example: Just once, every time on sim load, intermittently)?

  • Every time I want to fly a mission.

REPRODUCTION STEPS

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

1.Start a freelance mission with the PC-24 in career mode.
2. Do not use CTRL-N; attempt to start the engines manually (no ignition). Additionally, load the current flight plan and check the bearing pointer color (blue) on the upper center screen after activation. Dial in the initial heading for the autopilot using an external dial; the heading bug will adjust in one-degree increments.
3. Use CTRL-N after the engines fail to start manually. The plane will then be ready for taxi with running engines. (Heading pointer is now white)
4. After takeoff and aligning with the current flight route, engage the autopilot in NAV mode. However, NAV mode will not engage. Additionally, the heading bug now adjusts in ten-degree increments when using an external dial.

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:

  • Bravo Throttle quadrant

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

  • No

[PC Only] What GPU (Graphics Card) do you use?

  • Not relevant

[PC Only] What other relevant PC specs can you share?

  • Bravo throttle quadrant
  • Virpil Joystick

MEDIA

Please add a screenshot or video of the issue occurring.
Screenshot 1
(Engine Start and Ignition sequence)

Screenshot 2024-12-11 143711
Screenshot 2024-12-11 143711948×555 50.1 KB

Screenshot 2
(Ignition failed, bearing pointer blue)

Screenshot 2024-12-11 143821
Screenshot 2024-12-11 1438211025×690 62.2 KB

Screenshot 3
(After CTRL-N, eninges are running, bearing pointer now appears white)

Screenshot 2024-12-11 143929
Screenshot 2024-12-11 143929976×668 54.8 KB

Screenshot 4
(Heading bug moving in ten-degree increments)

Screenshot 2024-12-11 163703
Screenshot 2024-12-11 1637031245×449 32.6 KB

[END OF FIRST USER REPORT]

: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:
•

2

Do you have the same issue if you follow the OP’s steps to reproduce it?
• I am unable to get the PC-12 to even activate autopilot in career mode. Free flight seems to work fine. But in career mode, nothing. The AP blinks red but will never engage. I have yet to have it work.

Provide extra information to complete the original description of the issue:
• I have tested the PC-12 (along with other aircraft) in free flight and the AP seems to work most of the time. But in career mode, nothing. AP won’t engage.

If relevant, provide additional screenshots/video:
•

3

Make sure you don’t use ALT-N to skip any step. You have to do every step by your self. Because as soon as you use ALT-N just once, autopilot only works in heading and altitude mode. All other functions (NAV / ARP) won’t work anymore.

4

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:
•
Boy, this sim is really pushing my buttons! I saved up to by the PC-24 for cargo missions because I had an issue with the 208B! Now, it appears that this aircraft is also a buggy mess. As stated, Ctrl-E does nothing.

If relevant, provide additional screenshots/video:
• Restarted the mission a couple of times, and actually managed to start the engines using Ctrl-E. However, the right engine is showing a fire warning!!! This is from cold start. It shuts down almost immediately, making any flight impossible on one engine. I give up with this game.

Screenshot 2024-12-16 201935
Screenshot 2024-12-16 2019351920×440 53.8 KB

5

First impression after update 1.2.8.0

Switches move, cockpit so far seems ok.
BUT:

  1. After 3 restarts of a career mission, I managed, that the right engine starts up properly, sticking exactly to the checklist. But the left engine motors at 25%, but will not ignite. 3. I still have to use CTRL-N to get both engines running.
    (Seems to be resolved) :white_check_mark:

  2. NAV mode still not functioning after using CTRL-N.

  3. Heading-Nob is still erratic, most of the time making 10° increments, occasionally 1°.

Workaround for issue 2.
Don’t use CTRL-N for start up. If the start up of any engine does not work, start NAV-Mode before you skip to taxi.

I will update this post as I fly missions with the PC-24.
I love this plane, despite it’s issues.

3 Likes
6

Just a thought - I don’t have the PC-24 in career mode yet, but on the PC-12, I’ve and others have had the issue with NAV mode not working. Checking the copilot’s PFD. It may be set to a different NAV source. Cycle through the NAV sources with the NAV SEL button on the copilot’s panel to select FMS.

Note that pressing the NAV SEL button will turn off NAV mode, so you’ll need to turn it back on. Also, you will need the heading of the plane to point towards the desired track.

7

I am also now unable to start engine number 1, it will not ignite as the information provided above states, its the same for me in career mode

8

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:
• Auto Throttle hunts to find speed making it unusable at cruise. Works well on climb but cruise varies from full throttle to no throttle

If relevant, provide additional screenshots/video:
•

9

today the engines refused to start. I don’t know if something has changed server side, but this is very annoying.