Task "Climb to 30,000 ft" cannot be checked-off (Medevac from MYGF)


ISSUE DESCRIPTION

Description of the issue:
Career mode: Flying an early Medevac mission from MYGF (Bahamas) to USA, in a Pilatus, for about $35,000 credits. After climbing to 30,000 ft, on my way to waypoint PLUMP, it again asked me to “Climb to 30,000” and I was there already. The “Climb to 30,000” task would not turn green. I gradually climbed above and below 30,000 but it would not go away. After a couple of minutes, the mission terminated with message “Mission Failed .. put patients life in danger” … apparently because I went above 30,000 ft in my attempt to get the task to register. So my Reputation score went down a huge amount.

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

FREQUENCY OF ISSUE

How often does this occur for you (Example: Just once, every time on sim load, intermittently)? I only tried this mission once, and it failed that one time. I did another Medevac mission successfully.

REPRODUCTION STEPS

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

  1. Career mode: Start the mission Flying an early Medevac mission from MYGF (Bahamas) to USA, in Pilatus plane, for about $35,000 credits.
  2. Climbing to 30,000 ft, on your way to waypoint PLUMP.
  3. Observe: it again asked me to “Climb to 30,000” and I was there already. The “Climb to 30,000” would not turn green. I gradually climbed above and below 30,000 but it would not go away.
  4. After a couple of minutes, the mission terminated with message “Mission Failed .. put patients life in danger” … apparently because I went above 30,000 ft in my attempt to get the task to register.

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: Hotas, but not relevant.

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

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

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

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

MEDIA

Please add a screenshot or video of the issue occurring.

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

Last I heard the oxygen system isn’t working on the Pilatus aircraft, so you can’t fly that high, which would explain why the patient died too. You can edit the cruise altitude in the EFB before you start the mission. Set it below 18,000 and then hit the File with ATC button

1 Like

Ah, I was not aware that I could edit EFB … I saw the “EFB” button on my screen before I clicked “Start Flying” but I did not know what it represented. Thanks for the info!!! I’ll give it a try.

I encountered a similar (but different) bug and reported it at Patient died & flight terminated after "Skip to Next Phase" In that bug, the plane successfully got to 31,000 cruising altitude, and that “get to 31” task was completed (checked-off) okay. I even completed the “keep plane stable during checkup on the patient” task, and that task was checked off okay. In that other bug, the “Mission Failed” event happened later when I attempted a “Skip to Next Phase” action.

Yes, there is still a problem with altitude on the Medevac Missions.

I thought it was fixed, since yesterday i did ~3 missions where ATC and Mission altitude where actually same, and misssion continued normally after reaching cruise altitude.

But Today i had one that was completely bugged.
Still said reach 40.000 after i leveled out.
Continued climbing, up to ceiling of PC24 of FL450.
Same 40k message, and visible mission path still above me.

Played around with ATC decrease alt, and on 39.000 i was in mission path (still at FL450 actual).
Reach 40k went away, but it did not trigger the continuation of the mission.
Got a heavy deduction/ low B rating at end.

Think my problem was maybe triggered because i tried to change some stuff in EFB i normaly don’t touch, like airline, reg. and flight no. (all still broken)

Pretty sure it is caused by the LIVE weather.

When i have it disabled, no problem with ATC/misson altitude.
When i have it enabled there is often problems with mission not recognizing cruise altitude.