CTD when starting an aircraft

Bug Reports SDK: Tools/Samples/Documentation
, , ,
1

Version: Sim v1.37.19.0 | SDK v0.24.3

Frequency: Consistently

Severity: High

Context: This happens when working on my own custom scenery.

Bug description: I’ve noticed that whenever I close developer mode and I attempt to start an airplane the sim crashes to the desktop.

Repro steps: I close the project, then close DEV MODE in order to start the aircraft and taxi around. I’ve tried closing dev toolbar using Devmode > Exit DevMode. I’ve also tried using General Options > Developers and turning the feature off. After dev toolbar is gone. I attempt to start the aircraft and the sim freezes and then CTD’s.

I’ve tried this with the stock Cessna 152 and other planes with the same result.

Attachments:

Private attachments: Send a PM to @PrivateContent with the link to this topic and the link to download your content

2

Hello,

do you have any logs in event viewer to specify what the crash error might be?

3

Hello @tabletopANDROID

Please follow these guidelines and provide us with a dump file and possibly your scenery project so we can replicate the crash.
How to report a bug or crash - Bug Reports - MSFS DevSupport (flightsimulator.com)

Regards,
Sylvain

4

I believe the application error and the two windows error reporting are related to the CTD.

image
image890×213 13.4 KB

I did setup crash dump. I’m sending a private message per the instructions.

Here’s the application error details:

Faulting application name: FlightSimulator.exe, version: 1.37.19.0, time stamp: 0x00000000
Faulting module name: FlightSimulator.exe, version: 1.37.19.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x0000000000bf0cd7
Faulting process id: 0x0xAB88
Faulting application start time: 0x0x1DAD97DBF884636
Faulting application path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.37.19.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Faulting module path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.37.19.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Report Id: 14eb6fe2-3368-4f06-aa05-0c649da53089
Faulting package full name: Microsoft.FlightSimulator_1.37.19.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App

Here’s the first error reporting:

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

Problem signature:
P1: Microsoft.FlightSimulator_1.37.19.0_x64__8wekyb3d8bbwe
P2: praid:App
P3: 1.37.19.0
P4: 00000000
P5: FlightSimulator.exe
P6: 1.37.19.0
P7: 00000000
P8: c0000005
P9: 0000000000bf0cd7
P10: 

Attached files:

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_Microsoft.Flight_77faf2a85a1c3c217b2c85cc8a5e632caae966_34544930_f5b3e6a3-fbbe-437b-b92c-3644731923b7

Analysis symbol: 
Rechecking for solution: 0
Report Id: 14eb6fe2-3368-4f06-aa05-0c649da53089
Report Status: 4100
Hashed bucket: 
Cab Guid: 0

Here’s the second error reporting:

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

Problem signature:
P1: Microsoft.FlightSimulator_1.37.19.0_x64__8wekyb3d8bbwe
P2: praid:App
P3: 1.37.19.0
P4: 00000000
P5: FlightSimulator.exe
P6: 1.37.19.0
P7: 00000000
P8: c0000005
P9: 0000000000bf0cd7
P10: 

Attached files:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.34d9d659-c7ba-4db2-a454-4981f3971858.tmp.WERInternalMetadata.xml

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_Microsoft.Flight_77faf2a85a1c3c217b2c85cc8a5e632caae966_34544930_f5b3e6a3-fbbe-437b-b92c-3644731923b7

Analysis symbol: 
Rechecking for solution: 0
Report Id: 14eb6fe2-3368-4f06-aa05-0c649da53089
Report Status: 2147487744
Hashed bucket: 28eb5d4ceb146718b748cb4938bde163
Cab Guid: 0
1 Like
5

Hello @tabletopANDROID

The crash seems related to taxi ribbon display. Sim fails to retrieve correct taxiway data, possibly when the airport is being refreshed on package mount/unmount.

However, I’m not sure to understand how you managed to have the ribbon enabled. This airport has no tower or ground frequency so I’m unable to request for push back and takeoff in order to receive instructions that will enable the ribbon.
The only way I found to replicate the crash so far is to enable “AI Piloting” and open/close your project in the Scenery Editor. AI will do a push back and ribbon will show up. Opening and closing the project when the ribbon is displayed will trigger the crash after a few seconds.
Let me know if you can provide further details on your repro steps.

I’ll add this to our backlog.

In the meantime, you can check if disabling the ribbon assistance (at least when the airport is being refreshed) is a good workaround for you.
Edit: Not sure it will, I suspect it will crash for the same reason in a different system.

Regards,
Sylvain