3 hours ago, bahnzo said:

I'm getting CTD's when trying to load large airports. I've seen other's report SFO and KORD, I tried CYVR (vancouver) today and same thing happening to me. It causes a CTD when in the loading screen. 

I'm curious is this happens when you approach a large airport as well? Anything else?

Sigh......

 

Edit: turns out not just large airports, but anything reasonably sized. KBLI (Bellingham, WA) a field with just a single runway, yet still reasonably sized, crashes as well. 

Loaded up in every one of those airports in one go without restarting game in between. No issues.

7 minutes ago, Sigwolf said:

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.

I specified it on the initial installation. But I probably just selected H: drive with the rest being the original path, so that Windows magically made their own file structure on my H drive as well. 

Update: It's not in that path. It's here:

H:\WpSystem\long_string_of_numbers\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe

I deleted the long string of numbers in case there was a serial there or something.

Edited October 31, 20205 yr by Republic3D
update

Locher removed from community, now works.

4 minutes ago, EmaRacing said:

Locher removed from community, now works.

Excellent find I had Locher installed also.

What is Locher? Is that some 3rd party add-on or something from Asobo?

1 hour ago, Republic3D said:

I specified it on the initial installation. But I probably just selected H: drive with the rest being the original path, so that Windows magically made their own file structure on my H drive as well. 

Update: It's not in that path. It's here:

H:\WpSystem\long_string_of_numbers\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe

I deleted the long string of numbers in case there was a serial there or something.

That's bizarre, and the first I've time I've seen someone report that problem.  I wonder if they have somehow made the installer even worse since release.  I installed it on release day, and realized I was too anxious and paged too quickly through the first install and let it go to the default location.  When it finished and I saw the idiotic directory structure it defaulted to, I bit the bullet, deleted it, and reinstalled the whole thing where I wanted it.  Luckily, I haven't had any issue since, and have had no issues moving things in or out of the community folder, or editing files in the official folder.  Wish I had more to help, but I have no idea how to fix it if the installer didn't put the community folder in the path you specified.

Maybe leaving the same '8wekyb3d8bbwe' that was in the default path at the end of your specified path confused the installer somehow.  That's only a guess on my part, though, and the only solution I could think of for that would be a potentially long and painful complete re-install.  It would be worse to have to do that and have it do the same thing, but it's all I've got.

 

...edit... it could well be the \WpSytem directory at the start of the path that confused the installer, as well, if that possibly triggers Windows to treat it as a protected file structure.  Unfortunately the conclusion is the same, a re-install may be the only fix.

Edited October 31, 20205 yr by Sigwolf
clarification

2 minutes ago, captain420 said:

What is Locher? Is that some 3rd party add-on or something from Asobo?

3rd party addon from flightsim.to I believe.  Be interesting to find out how one airport can cause difficulties elsewhere.

I have the same exact problem with moving files out of the Community folder, it won't allow me too either. And I have my sim installed on D:/ drive.... with the main flightsimulator.exe on C:/Program files....

The way that it installed my MS store version of MSFS was still in C:/username/appdata/bla bla bla, but there are or shortcut or links to the actual files on D:/ drive. It's a pain in the word not allowed since I can't move stuff out of community folder or else it will pop up saynig my organization doesn't allow that. The only thing I'm allowed to do is delete stuff and add stuff to the community folder.

2 hours ago, bahnzo said:

Ok, I removed my /Community folder (again). And they are loading. So there's a mod in there causing it. 

Can't wait to add them back in one by one, load the sim, load an airport, rinse and repeat. 🙂

This is why I've given up on mods/sceneries and liveries.  Way too much hassle everytime they update and break the game. By all means, I'm missing my favorite airports but I cbf trawling the internet every two weeks to find them all again and re-download the new versions and installing.  

Steam shows I have 170 hours of game time.  Logbook shows 74 hours of flight time.  Don't even want to think about how many hours of modding time spent.  

40 minutes ago, captain420 said:

What is Locher? Is that some 3rd party add-on or something from Asobo?

Locher is an airport in Italy.  The addon has cables attached to the powerlines these addon cables may be what is causing the conflict.

27 minutes ago, captain420 said:

I have the same exact problem with moving files out of the Community folder, it won't allow me too either. And I have my sim installed on D:/ drive.... with the main flightsimulator.exe on C:/Program files....

The way that it installed my MS store version of MSFS was still in C:/username/appdata/bla bla bla, but there are or shortcut or links to the actual files on D:/ drive. It's a pain in the word not allowed since I can't move stuff out of community folder or else it will pop up saynig my organization doesn't allow that. The only thing I'm allowed to do is delete stuff and add stuff to the community folder.

It's just odd that the MS store installer is doing different things for different people... (or maybe not, considering it *is* Microsoft, after all)

Did you install on release day, or a later date? (Just wondering if they changed something at some point)  When I installed, it only put one zero-byte file under c:\users\username\appdata\... named 'FlightSimulator.exe' with no other shortcuts, links or files even with protected OS files shown.  The actual FlightSimulator.exe was installed into 'C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.10.8.0_x64__8wekyb3d8bbwe' along with FS files and directories, but no visible reference or link to the Community or Official directories. That directory's name is updated automatically to reflect each patch.  The Community and Official directories (which has the bulk of the install) went to the path I specified, \Games\MSFS.  It's given me no issues with adding, deleting, or moving files in or out of Community, nor editing cfg files in Official with this setup.

Will it let you Ctl-X to cut a file (or files) out of Community and Ctl-V to paste them elsewhere, or does this give the same pop up that a move attempt triggers?

I installed on release day. I get this pop up whenever I try to copy anything out of the Community folder, same with cut.

Edited November 1, 20205 yr by captain420

13 minutes ago, captain420 said:

I installed on release day. I get this pop up whenever I try to copy anything out of the Community folder, same with cut.

 

Just bizarre.  Just realized the difference could come from my install originating from Game Pass.  It should be the exact same installer, and it still came from the MS Store, but maybe MS screwed something up there.  That's the only thing I can come up with that could possibly explain with differing install behavior.

 

...edit... One last possibility. Are you trying to move files from a user or administrator Windows account.  I suspect you're probably already using an admin account, but if not, it is something else to try,

Edited November 1, 20205 yr by Sigwolf

KSEZ final had a complete sim stop for about 4 seconds (not CTD) almost over the fence! So annoying.

Edited November 1, 20205 yr by Flyfaster_MTN002

1 minute ago, Flyfaster_MTN002 said:

KSEX final had a complete sim stop for about 4 seconds (not CTD) almost over the fence! So annoying.

Not sure what airports you're flying into, but it must be an interesting mod... 🤣