I found that removing "bmw-airport-locher" stops CTDs at certain larger airports.

https://flightsim.to/file/1811/locher-sarentino-airfield-loch

I think that others have brought this up. It's a shame because it a gem of an airport.

I just read this:

"ASOBO has made changes to the latest version of the MFS. Locher Airport has stopped working correctly for some users. Please wait while I figure it out and make corrections."

 

Edited October 31, 20205 yr by DJJose

13 minutes ago, Republic3D said:

I have no add-on liveries installed. 

Same issue. 

I have water elevation fixes for Alaska, plus 3x water elevation fixes for Norway. Maybe that's an issue.

If you are CTDing in game, remove all mods from the Community folder. 

6 minutes ago, DJJose said:

I found that removing "bmw-airport-locher" stops CTDs at certain larger airports.

https://flightsim.to/file/1811/locher-sarentino-airfield-loch

I think that others have brought this up. It's a shame because it a gem of an airport.

I just read this:

"ASOBO has made changes to the latest version of the MFS. Locher Airport has stopped working correctly for some users. Please wait while I figure it out and make corrections."

 

That's good to know. I don't have that one installed though.

6 minutes ago, abrams_tank said:

If you are CTDing in game, remove all mods from the Community folder. 

Yep, we're just trying to find out which mods cause the issue. 

28 minutes ago, DJJose said:

I found that removing "bmw-airport-locher" stops CTDs at certain larger airports.

https://flightsim.to/file/1811/locher-sarentino-airfield-loch

I think that others have brought this up. It's a shame because it a gem of an airport.

I just read this:

"ASOBO has made changes to the latest version of the MFS. Locher Airport has stopped working correctly for some users. Please wait while I figure it out and make corrections."

 

Mine seems to be related to an airport as well. One that I myself created. It's not released, so it's not causing issues for anyone else. But I'm guessing there's a typo in an .xml maybe.

 

Edit: Mine was a LivingWorld .xml file. Not sure what was bad about it, but removing it solved all issues. Doesn't seem to be any typos in it, so again, not sure what's up with it. 

Edited October 31, 20205 yr by bahnzo

13 minutes ago, DJJose said:

I found that removing "bmw-airport-locher" stops CTDs at certain larger airports.

https://flightsim.to/file/1811/locher-sarentino-airfield-loch

I think that others have brought this up. It's a shame because it a gem of an airport.

I just read this:

"ASOBO has made changes to the latest version of the MFS. Locher Airport has stopped working correctly for some users. Please wait while I figure it out and make corrections."

 

LOL! the link in your message got my Macbook to CTD 😄

I had a CTD just now... haven't had one for months...if its a mod it wasn't happening before.

Was flying near TNCM (departed TQPF in the Bonanza)

Bummer

Edited October 31, 20205 yr by ryanbatcund

I can't even do the testing, because I get the "Your organization does not allow you to place this file here" error message every time I try to copy a mod or move it. It's an DRM issue for people who have the Microsoft Store version of Flight Simulator 2020.

4 minutes ago, Republic3D said:

I can't even do the testing, because I get the "Your organization does not allow you to place this file here" error message every time I try to copy a mod or move it. It's an DRM issue for people who have the Microsoft Store version of Flight Simulator 2020.

Not for everyone who has the MS store version, just those that accepted the default install location rather than specifying a custom one outside the windows protected directory structure.  It would solve so many problems if the MS store let users select a default install location of their choosing like just about every other store installer, but that isn't the MS way apparently...

Ya I'm crashing to desktop at large urban areas.  I just deleted most of the stuff out of the community folder to see what happens.

2 minutes ago, Sigwolf said:

Not for everyone who has the MS store version, just those that accepted the default install location rather than specifying a custom one outside the windows protected directory structure.  It would solve so many problems if the MS store let users select a default install location of their choosing like just about every other store installer, but that isn't the MS way apparently...

But they did let users choose in the installer!!!! I chose c:\msfs for the store version and have not had this problem.

27 minutes ago, bahnzo said:

Mine seems to be related to an airport as well. One that I myself created. It's not released, so it's not causing issues for anyone else. But I'm guessing there's a typo in an .xml maybe.

 

Edit: Mine was a LivingWorld .xml file. Not sure what was bad about it, but removing it solved all issues. Doesn't seem to be any typos in it, so again, not sure what's up with it. 

How ironic given your comments about Asobo not testing properly. Don't think you can blame them for your private mod issue.

15 minutes ago, Sigwolf said:

Not for everyone who has the MS store version, just those that accepted the default install location rather than specifying a custom one outside the windows protected directory structure.  It would solve so many problems if the MS store let users select a default install location of their choosing like just about every other store installer, but that isn't the MS way apparently...

 

11 minutes ago, CJ1045 said:

But they did let users choose in the installer!!!! I chose c:\msfs for the store version and have not had this problem.

 

That's weird, because I chose a different installation path as well. I installed my sim on my H: drive, and I have Windows on my C : drive. 

Here's my installation path:

H:\WindowsApps\Microsoft.FlightSimulator_1.10.8.0_x64__8wekyb3d8bbwe

However the community folder is still on C : drive here:

C:\Users\myusername\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\Packages\Community

And it just won't let me copy or move folders or files out of there. Ridiculus.

 

Edited October 31, 20205 yr by Republic3D
update

4 minutes ago, CJ1045 said:

But they did let users choose in the installer!!!! I chose c:\msfs for the store version and have not had this problem.

Read my post again... "just those that accepted the default install location rather than specifying a custom one outside the windows protected directory structure".  I know you could pick a location, as I did.  I was referring to the store installer itself allowing a default structure, like install all games under 'D:/Games/MS' rather than defaulting to some obscure directory buried 18 levels deep with nonsense naming conventions in the Windows protected file structure.  Just as Steam, Epic, Uplay, Origin, or many other stores allow.  It would cause a lot less user headaches.

8 minutes ago, Republic3D said:

 

 

That's weird, because I chose a different installation path as well. I installed my sim on my H: drive, and I have Windows on my C : drive. 

Here's my installation path:

H:\WindowsApps\Microsoft.FlightSimulator_1.10.8.0_x64__8wekyb3d8bbwe

However the community folder is still on C : drive here:

C:\Users\myusername\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\Packages\Community

And it just won't let me copy or move folders or files out of there. Ridiculus.

 

Did you specify that H: location on the initial install, or did you just specify that for the update path after a patch was applied?  I'm just curious because it seems odd that the version number is in your user specified path.  I just installed mine to D:\Games\MSFS, and that's were the 100 or so Gb's went, including the Community folder.

Me too, trying to load KLGA, CTD at 80% loading, small airports working. Another great gift from BUGSOBO came with patch 5...