Thank you using the Bug section, using templates provided will greatly help the team reproducing the issue and ease the process of fixing it.
Are you using Developer Mode or made changes in it?
yes
Brief description of the issue:
Whenever resyncing, reloading, or changing aircraft in the aircraft selector, instant CTD
Provide Screenshot(s)/video(s) of the issue encountered:
Faulting application name: FlightSimulator.exe, version: 1.27.11.0, time stamp: 0x00000000
Faulting module name: FlightSimulator.exe, version: 1.27.11.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x00000000015eca39
Faulting process id: 0x2148
Faulting application start time: 0x01d89c8fc7f893e8
Faulting application path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.27.11.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Faulting module path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.27.11.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Report Id: d16acbe2-b399-4c75-bb40-05097f77db48
Faulting package full name: Microsoft.FlightSimulator_1.27.11.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App
Detailed steps to reproduce the issue encountered:
PC specs and/or peripheral set up if relevant:
If on PC, Fault Bucket ID - Instructions here - Please type in just the Fault Bucket ID # rather than a screenshot for privacy reasons:
Fault bucket 2277909731421704862, type 5
Event Name: MoAppCrash
Response: Not available
Cab Id: 0
Problem signature:
P1: Microsoft.FlightSimulator_1.27.11.0_x64__8wekyb3d8bbwe
P2: praid:App
P3: 1.27.11.0
P4: 00000000
P5: FlightSimulator.exe
P6: 1.27.11.0
P7: 00000000
P8: c0000005
P9: 00000000015eca39
P10:
Are you using DX12?
yes
Are you using DLSS?
yes
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:
If on PC, Fault Bucket ID - Instructions here - Please type in just the Fault Bucket ID # rather than a screenshot for privacy reasons: