2 hours ago, Sigwolf said:

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,

I installed on release day too. The Premium Deluxe version. I'm administrator. 
Copy, Cut & Paste or Move is strictly verboten. 

I think you're right that it's better to re-install the game now, I only have 4-5 payware airports and one addon aircraft in addition to a large amount of freeware mods. 

But I'm not exactly sure what I should do when re-installing. Should I just make a directory like H:\FlightSimulator and let it install there? 

 

And if anyone has a suggestion with regards to what addon is causing this, except the "Locher" airport.. please let me know.

12 minutes ago, Republic3D said:

I think you're right that it's better to re-install the game now, I only have 4-5 payware airports and one addon aircraft in addition to a large amount of freeware mods. 

But I'm not exactly sure what I should do when re-installing. Should I just make a directory like H:\FlightSimulator and let it install there? 

 

It probably won't hurt anything more than a potential tremendous waste of your time, but with Captain420 reporting the same behavior I'm less convinced it will help.  Initially I thought maybe it just glitched during your install.  If you do go through with it, it probably is a good idea to keep the install path simple like the one you suggested.  I wonder now if for some reason Microsoft decided to do something different with the install path logic between the Game Pass version versus straight MS store purchased version, even though they are both installed through the MS store.  It makes no sense that they would do this, but very little of this process has made sense, so far.

It's no wonder people are getting wildly different results inside the simulator itself when MS can't even make the install process consistent...

1 minute ago, Sigwolf said:

It probably won't hurt anything more than a potential tremendous waste of your time, but with Captain420 reporting the same behavior I'm less convinced it will help.  Initially I thought maybe it just glitched during your install.  If you do go through with it, it probably is a good idea to keep the install path simple like the one you suggested.  I wonder now if for some reason Microsoft decided to do something different with the install path logic between the Game Pass version versus straight MS store purchased version, even though they are both installed through the MS store.  It makes no sense that they would do this, but very little of this process has made sense, so far.

It's no wonder people are getting wildly different results inside the simulator itself when MS can't even make the install process consistent...

Yes, it doesn't really make much sense. There are so many weird issues people experience, both with regards to the install process and the simulator itself. But I appreciate the help!

1 hour ago, Sigwolf said:

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

K S E Z !

Ahhh!  That's *entirely* different.  😜

4 hours 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.

Yeah I got the same problem. Workaround is to just delete it and redownload the mod.

Just curious, is anyone who is having the CTD at large airports, have more than 16gb of RAM?  I think that many CTDs are purely running out of RAM. MSFS doesn't handle that gracefully.

I just had my first ever loading screen CTD while loading LAX. That's with the "CTD Hotfix" patch just released, kind of ironic. Just had installed the latest LA mod from flightsim.to - now trying without.

12 minutes ago, bszuch said:

Just curious, is anyone who is having the CTD at large airports, have more than 16gb of RAM?  I think that many CTDs are purely running out of RAM. MSFS doesn't handle that gracefully.

32 here.

7 minutes ago, Colonel X said:

I just had my first ever loading screen CTD while loading LAX. That's with the "CTD Hotfix" patch just released, kind of ironic. Just had installed the latest LA mod from flightsim.to - now trying without.

Do you have Locher airport installed I think it's causing the CTD's

Ok it also crashed with no scenery. This will initiate a hiatus of the Colonel for a couple of patches. Best for everybody, I already feel the rage after 2 CTD's. Good luck to everybody!

32 minutes ago, bszuch said:

Just curious, is anyone who is having the CTD at large airports, have more than 16gb of RAM?  I think that many CTDs are purely running out of RAM. MSFS doesn't handle that gracefully.

64 GB RAM and 24 GB VRAM.

 

I deleted nearly all my mods and now it's working for me. But it's impossible to say exactly which one, or which ones that cause it.

KSFO = CTD every time it loads

KJFK & KLGA = OK

32 GB memory

Hot Fix installed.

1 hour ago, Colonel X said:

Ok it also crashed with no scenery. This will initiate a hiatus of the Colonel for a couple of patches. Best for everybody, I already feel the rage after 2 CTD's. Good luck to everybody!

I did a takeoff (GA) from LAX and landing at SMO without issue.  No mods or tweeks here though.  Do you still have LOD boosted up in your config file that might be the cause.. Hope you get it worked out!

Just took off from SFO in A320 mod. No issues.  Flew around and landed at LAX last night with no issues.