IFR Flights in Career Mode Often Don't Recognize Arrival

Bug Reporting Hub User Interface & Activities
, , , ,
1

Prefacing this by saying that based on observations on other social platforms this issue seems incredibly common, so I was surprised to not easily find an existing bug report for this. That said, I will not be surprised if one such report exists, but I was unable to find it - but for the mod that ends up merging mine with the one I couldn’t find, just know I did look! :slight_smile:

ISSUE DESCRIPTION

Description of the issue: Mission progress does not move to the arrival/approach phase, which results in no prompts to contact the arrival airport for landing. The final and most impactful result of this is that when you do just give up and land (suspending disbelief and role playing that you had a comms radio outage and just broadcast in the blind :sweat_smile:), the mission never recognizes that you did land. The final objective will remain on “Land at [ICAO code of destination airport]” regardless of what you do.

Some users have reported success in resolving this by taking off again, flying around the airport for a few minutes, and eventually the next step triggers properly. This is not always an option, especially for aircraft that may be very low on fuel on arrival, or (more frequently these days), airports in severe IMC at which it would be too risky to takeoff and make multiple landing attempts.

In the worst-case example, when my last IFR flight had this issue, I decided once I was on the ground to leverage the “Skip to Descent” function, which instead skipped to my aircraft crashing and immediately failing the mission, costing me hundreds of thousands of credits. (I’m aware the issues with “Skip to” are logged as separate bugs and I am not attempting to report/log that issue here.)

FREQUENCY OF ISSUE

How often does this occur for you: Frequently, but not 100% of the time. I’ve been unable to identify a pattern of specific airport types, routing, or aircraft which trigger/prevent this issue.

REPRODUCTION STEPS

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

  1. Fly an IFR flight in Career (I have most recently experienced this in a Charter - VIP flight flying the Pilatus PC-24 along the following route - EGNO DCT CWL DCT 5242N00142E DCT VOLLA DCT NIGUG DCT BASGU DCT MABAB DCT BUSCH DCT VOCIM DCT OKG OKG9K LKKV, with the RNAV approach to runway 11, available here)

  2. Observe that upon arrival to the terminal vicinity the mission objectives do not progress beyond (in my example) “Fly to LKKV”

  3. Observe that upon landing the mission objectives remain at “Fly to LKKV” and do not progress even upon leaving the runway/parking.

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: VelocityOne Flight, VelocityOne Flightstick, Axair MIAP, USB keyboard, USB mouse, 2 x iPads for instrument popouts

[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? AMD Radeon RX 7900 GRE

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

1 Like
2

I encoutered this issue two times last week:

On the videos, you can clearly see, that the mission didnt change the mission steps after the landings. I put there times with first landings, but there are also chapters in the video. So, devs can easily see the issue. Also, its full flight recording without skipping or simrateing.

1 Like
3

Can’t see any ATC communication? I also did not see that you called into the arrival airport to announce full stop landing on which runway. You might have but no ATC stuff was in VID.

When you are landing do you leave the blue boxes on so you can call on Final? I could hear the engine in the background but could not hear ATC answer you - might just be a sound thing.

4

Probably a totally separate bug worth reporting, but part of my issue is that at some point early in every IFR flight it becomes impossible to communicate with ATC. In this example I was climbing out and on the frequency to get IFR clearance from center (as my departure was uncontrolled). The Quick Reply ceases to do anything and the ATC window reverts back to prompting me to tune to the CTAF of my departure field, as if the flight had just begun.

image
image1115×1204 99.9 KB

So yes, for many of us, the option to communicate with ATC simply disappears. This was also the case in my initial example where landing never triggers any change in mission progress.

EDIT: This particular bug above (not the one for which this report was opened) was due to Volanta Premium Autosave being enabled. So, word to those with Volanta Premium: be sure to disable Autosave when flying in Career (or generally when desiring to use the default ATC).

5

ATC is a definite thorn in a pilots side. I often am left flying without being able to ask for flight following and subsequently IFR. I get that tune to the airport coms often too. Mostly for me, it eventually switches to a “request flitght following” tab after some many Nm. I have to leave the coms window open though.

Today, I had the situation where it was telling me I had to request a vector to the next waypoint, which I did not need! I was wanting to cancel IFR but this was the only option it would allow. So I had to request the vector and then it gave IFR cancel option.
ATC still needs tons of fine tuning.

Career mode needs tons of love too.

How much Cr did you lose because of it?

EDIT - for the quick reply issue, I have that too. Sometimes it works and sometimes not, I have to quickly open coms to click the tab, which is often the solution but it too can fail.

6

I dont know if you were watching both of videos and i understand, they are long and boring :smiley:
But i can assure you, i was trying to reply to ATC. But there was no option and even pressing Enter or arrow to the left on my gamepad didnt work.

1 Like