CTD upon touchdown at KIMT Iron Mountain/Kingsford

Using the template below will greatly help the team reproduce the issue and ease the process of fixing it. Before posting, search for an existing report. If you are not sure it’s a bug, please first report in User Support Hub.

2 tags are required - add them in the tag section next to the title above:

Feel free to delete this quote section after adding your appropriate tags.


ISSUE DESCRIPTION

Description of the issue:
CTD at the moment of touchdown at KIMT Iron Mountain/Kingsford in the Vision Jet G2

[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 so far (twice)

REPRODUCTION STEPS

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

  1. Freelance charter mission from KMCD Mackinac Island to KMIT
  2. Using flight plan that was set in EFB (IFR; FL200; VFR Straight departure; CABAR - WODEV - VUYUK; Approach: ILS 1 via OMOLE)
  3. Follow flight plan, intercept glide slope at OMOLE after doing procedural turn at CFVPH. AP disconnect at 1.3NM from runway, manually land with full flaps, gear down, and approach speed of 90kts

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:
Logitech Extreme3d Pro, keyboard and mouse

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

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

[PC Only] Many issues may be due to an outdated graphics card. Please state your Graphics Card Driver Manufacturer (NVIDIA, Intel, AMD) and Version:
NVIDIA 560.94 (NVIDIA RTX 2070 Super)
[PC Only] What other relevant PC specs can you share?
Intel I7 10700k, 64GB DDR4, 4TB NVME SSD (2 2TB drives)

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:

Just did an approach to KIMT in Vision Jet with MSFS 2024 and had no issues. it doesn’t seem like it would be related to the autopilot since you’ve had it off at touchdown. To me, an approach to KIMT Rwy 1 is the only important factor here. I’m wondering more if it could be related to your setup of the Logitech Extreme 3D and some button you have configured. If you would provide details of your configuration I can try to duplicate it as I have the same joystick available (I normally fly with a CH Yoke and Pedals) but use the joystick for helicopters).

I was thinking it was just the mission itself that was bugged. I had another issue occur during the flight both times: ATC saying I was 300ft above FL200, when I was at FL200 with the altimeter set to what ATC told me. Just a minor bug and more of a non issue. But I’ll need to try another mission that lands at KMIT to see if it is something on my end.

If I don’t have a chance to try today, I’ll try tomorrow.

As for the 3D pro set up, this is what I have:
Joystick slider: Throttle Axis
Button 1: nothing
Button 2: brakes
Button 3: toggle propeller reverse thrust
Button 4: increase flaps
Button 5: toggle landing gear
Button 6: decrease flaps
Button 7: nothing
Button 8: toggle parking brake
Button 9: next throttle detent (I never use this)
Button 10: nothing
Button 11: AP off
Button 12: AP on
Button 11 + joystick POV: trim (I don’t really use this much)

1 Like

Thank you for this report. We’ve moved your topic into the User Support Hub.

The Bug Reporting Hub is for posting suspected or confirmed bugs that other users are able to reproduce without duplicating an existing bug report. Using the template or providing all the relevant information about your bug and sim setup is required in order to provide valuable information, feedback, and replication steps to our test team.

If you are not sure if your issue is a bug or need further input from the community, please use the User Support Hub category. If the community can replicate your issue, first search the Bug category to see if there’s an existing topic. If it already exists, contribute to that report. Duplicate bug reports will be closed.

If you believe it is a new report and no duplicate exists, then create a new bug topic using the provided topic template.

All issues caused by or involving third-party addons/mods should be reported to the third-party developer. Assure that no addons/mods are used when reporting issues in Bug Reports.

Added my Extreme 3D Pro to MSFS 2024. Noticed that the default settings, which may have been added by Patch 3 today (not sure), are completely different than your settings. Are you using your preferred settings or were they manually added due to some of the problems with the Extreme 3d Pro I’ve seen described on this Forum?

If you get the same crash behavior on your next attempt, you might try the defaults and see what happens. Due to the extensive fix list in Patch 3, you probably should try things again anyway and see if you can repeat the incident. It could be an included fix will resolve your issue. I noticed there was a fix for a flight path issue that caused a crash, so maybe they’re related?

Update: Tried a flight with the Extreme 3d Pro (default settings), runway 1 approach. It did not result in a CTD and the joystick worked well. If you try it and get a CTD again, I will duplicate your exact flight path and again try to duplicate your results.

Hello, I just installed MSFS2024 the other day, BUT the sim CTDs often, mostly upon touchdown at any airport, anywhere. Here is my FaultBucket for the mosst recent event. As far as I know I haven’t added anything so I think my community folder is empty, but I’m not sure where to find it. I’m hoping somebody can make some sense out of this and lend a helping hand. TIA!

Fault bucket 1330800558772643319, type 5
Event Name: MoAppCrash
Response: Not available
Cab Id: 0

Problem signature:
P1: Microsoft.Limitless_1.4.20.0_x64__8wekyb3d8bbwe
P2: praid:App
P3: 1.4.20.0
P4: 00000000
P5: FlightSimulator2024.exe
P6: 1.4.20.0
P7: 00000000
P8: c0000005
P9: 0000000003840bc8
P10:

Attached files:
\?\C:\Users\mjoli\AppData\Local\Packages\Microsoft.Limitless_8wekyb3d8bbwe\LocalState\AsoboReport-Crash.txt
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.ac503854-115d-45bb-b71e-9700d212cc68.tmp.mdmp
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.c236545a-5943-4b41-bae6-490127007afa.tmp.WERInternalMetadata.xml
WPR_initiated_DiagTrackMiniLogger_OneTrace_User_Logger_20250624_1_EC_0_inject.etl
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.845f6d2b-afed-4df9-ba21-2d88399556d2.tmp.etl
WPR_initiated_DiagTrackMiniLogger_WPR System Collector_inject.etl
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.b6763556-2b48-4da5-84e5-d7f3dfd0b454.tmp.etl
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.94cc5690-04ac-4711-a883-0078abde8fbf.tmp.csv
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.d467d005-4c6e-47c6-ae76-7d91a17a1078.tmp.txt
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.6d7c1d3f-d39b-4d65-a749-972fc50c3c83.tmp.xml

These files may be available here:
\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_Microsoft.Limitl_10e4ae547023f81ad051caff8fb55b67d2e42df_fea788ec_7af361d2-def5-483e-9f1d-8b6697a2132a

Analysis symbol:
Rechecking for solution: 0
Report Id: 3591213e-7f9a-4005-a67b-873283975090
Report Status: 268435456
Hashed bucket: a2c3a8e7bcb0d9a55277f40eac88e5f7
Cab Guid: 0