Career mode Aviator Performance deduction because game swapped landing runway at last second

ISSUE DESCRIPTION

Description of the issue:

Several times now, I have been moments from landing a mission when the game suddenly changes the runway I’m “supposed to be” landing on. This is even after I have used the EFB prior to mission start to both “File Plan with ATC” and “Send Route to Avionics.” I even used the in-game ATC window to find nearest airport, select a runway for landing, announce position, announce every leg, including final, but I get nailed for “Undesignated landing area.” A couple of times, I’ve caught the final AI voice saying a different runway than what I selected and was configured for and I’ve had to do a go-around, do a teardrop off the end of the runway and land in the opposite direction to “make the game happy.” It’s nonsense.

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

no mods

FREQUENCY OF ISSUE

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

intermittently

REPRODUCTION STEPS

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

Most recent incident:

  1. Start a medium cargo mission from KHYS to KCKA
  2. Configure the flight plan altitude in the pre-mission EFB.
  3. Adjust the VFR approach because a teardrop isn’t needed considering the direction I’d be arriving at the destination.
  4. File Plan with ATC
  5. Send Route to Avionics
  6. Fly
  7. Pre-taxi configure the G1000 for what I want to do, add a couple waypoints here and there, including the user-defined “DWIND, BASE, and FINAL” waypoints because I like to have the EFB lines match the GPS lines as much as possible.
  8. Take off, request flight following, fly the mission to the descent
  9. Cancel flight following when I get about 15NM from destination
  10. Descend and at 10NM use the in-game ATC window “Nearest Airports” function to connect to KCKA
  11. Select a runway for landing, in this case RWY 35 because that’s what I filed on my flight plan
  12. Announce position at about 9NM out
  13. Announce when I’m on downwind
  14. Announce when I’m on base
  15. Announce when I’m on final
  16. Notice the Mission Objectives window didn’t give me credit for announcing final
  17. Tap ENTER key to let the Mission Objective function announce final on its own so I don’t get dinged
  18. Fail to notice the radio call “my” AI voice made was for the opposite runway
  19. Land
  20. As soon as wheels are down, I get nailed for “Undesignated landing area”
  21. Finish mission as normal, get marked down 25% for it.

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
FlightSimStuff throttle contoller
Logitech rudder pedals
TrackIR

[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?
Laptop 4080

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

MEDIA

Please add a screenshot or video of the issue occurring.

Communication window showing “my” radio calls. Note the two calls that I’m on final with differing runways. First was made using Comm window and second happened when I tapped ENTER:

Otherwise very good flight messed up by bug:

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

A

The solution is to manually announce ‘on final’ via the ATC window, not via the mission window.

2 Likes

I have this problem too and it always seems to be when I fly medium cargo in North Africa. Most of the time there is no Tower.
Does anyone know what distance you should announce when on Final with manual ATC?

I use the blue gates. The two final gates are for final. When entering the first of these two I announce final (manually via ATC window) and I always get 100%.

1 Like

I would rather fly without the gates tbh but trying today, it looks like between 0.3 and 0.4 miles is the sweet spot

Second this. It’s a “known” workaround - avoid using the “quick response” (via the mission goals script) to announce landing runway. If you forget and accidentally use it, you can manually use the comms menu, change to the desired runway, and make the call again. The last communication seems to be the one that sticks.

Why they set it up this way I’ll never know. I’d rather it judge you on choosing a runway that is appropriate for wind, slope, and terrain/obstacles than simply a callout that is defaulted rather arbitrarily.

2 Likes

Cheers. I’ll try this, and if it works, I’ll mark as solution. The bug itself should really get fixed, though, because the workaround to “play the game” is … don’t play the game. :man_shrugging:

2 Likes

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:
• this happened to me a couple times ans this last time was on a cargo flight, avionics said rwy28, the tablet said rwy28, i followed the game’s flight pattern and when i announced final it said rwy10 cause me to take a hit for landing in the wrong place.

If relevant, provide additional screenshots/video: