CTD after Update to Sim Update 10 Beta

Community Support CTD Help
, ,
#1

Are you using Developer Mode or made changes in it?

yes, and no changes

Brief description of the issue:

crash to desktop, never had this before, only after having updated to SU10 yesterdsay

Provide Screenshot(s)/video(s) of the issue encountered:

mmc_EGTKJBFtdu
mmc_EGTKJBFtdu1443×903 90.2 KB

Detailed steps to reproduce the issue encountered:

Select airport, press on fly now, and half way during the loading screen before spawning, I get a CTD. It doesn’t matter which airport.

PC specs and/or peripheral set up if relevant:

irrelevant

If on PC, Fault Bucket ID:

Fault bucket 2289884357001141437, type 5 - Event Name: MoAppCrash

Build Version # when you first started experiencing this issue:

1.27.9.0

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

If on PC, Fault Bucket ID - Instructions here - Please type in just the Fault Bucket ID # rather than a screenshot for privacy reasons:

#2

Did you empty your community folder? Also AIG is causing a crash with faib models.

#3

Topic moved to Sim Update10 Beta CTDs

#4

Yes, obviously the only way to make sure everything is vanilla state, is by removing (or simply renaming) the community folder :wink:

#5

Contact support

#6

You will also need to uninstall any and all Marketplace purchases as well to get a “Vanilla State”!

#7

when you’re launching fs2020, make sure XAMP isn’t running or an apache localhost server is NOT Running. because you get certificate errors/issues, and the simulator refuses to launch into the world. why would port 80/443 affect fs2020?

error fs2020
error fs20202560×1440 279 KB

#8

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: