Can't skip to shutdown, a critical composent (sic) has failed - no way to complete the mission

Sim Update 3 Beta | MSFS 2024 User Interface & Activities
, , ,
1

ISSUE DESCRIPTION

Description of the issue:

  1. Never saw this message before so assuming this is a new feature?
  2. The message is misspelled
  3. In this case due to other known bugs there was no path to taxi to the stand as the stand was blocked by the fire truck
  4. It said it was a hard landing and there was a landing gear malfunction - but it was not a hard landing - looks like and old (but fixed) bug with the air tractor came back - on rollout it started bouncing and then gear malfunction and tire malfunction.

Did you experience this issue before you joined the Beta?
3 and 4, yes; the inability to skip and misspelled message seem new.

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

FREQUENCY OF ISSUE

How often does this occur for you (Example: Just once, every time on sim load, intermittently)?
This was the first time - did a similar mission yesterday w/o this problem. Should have known it would not end well when I had to skip to takeoff due to the fire truck blocking the taxiway.

REPRODUCTION STEPS

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

  1. chose an initial attack freelancer mission
  2. landed (allegedly hard)
  3. hit alt-N after reaching the hold short point

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:

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

[PC Only] Many issues may be due to an outdated graphics card. Please state your Graphics Card Driver Manufacturer (NVIDIA, Intel, AMD) and Version:

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

2

The issue with the “hard landing” seems to have been resolved in the latest beta build; can’t speak to the verbiage of the error as I no longer get this error. Generally speaking, maybe running spell check on commit for messages might be a good idea?