14 hours ago, Fielder said:

Western USA.

 

4 hours ago, Roy Warren said:

Since I have been unable to get MSFS2024 to load maybe changing servers might help.

How do I change servers?

Roy

You cannot chose which server you connect to for streaming content. The “server” option is only for multiplayer - it has no other purpose, and if you do not use multiplayer, then changing the “server” option does absolutely nothing whatsoever.

MSFS itself chooses which servers you connect to using its own internal networking map, and that is based on the geographic location of your ISP’s Internet gateway. The internal networking map is probably updated every time you launch MSFS. The only way to “change servers” is to use a VPN to make it appear that your Internet gateway is in a different geographic location than it actually is.

I have studied the TCP/IP connections that MSFS makes when running extensively. There is not “a” server (singular). Typically there are 5 or 6 discrete TCP/IP connections to different IP addresses which are not necessarily in the same locations. I am located in the US Northeast - typically when MSFS is fully established, I am connected to servers in Seattle, Portland Oregon, New York City, and (occasionally) Chicago or Virginia. Some IP addresses resolve to Microsoft Azure - others to Playfab (which is owned by Microsoft).

The only services I use besides regular scenery streaming is Live Weather. If a MSFS user enables live traffic and multiplayer, there will be even more discrete TCP/IP connections.

Updated drivers to 572.16 a few days ago and FS2020 is running flawlessly so far.

Now for something new...

After flying a couple of weeks w/572.16 I had a CTD yesterday after about an hour in the air.  An announcement immediately appeared from nVidia stating that their driver had an issue and crashed the simulation (paraphrased).  Now that there was direct evidence of a driver issue, I downloaded and installed the latest: 572.42.

Now I am experiencing something new.  I have made two flights with the Longitude with no issues prior to the approach.  However, I've had the same thing happen with both flights while on final (ILS on one and RNAV on the other):

Approaching the DH there is suddenly a "sizzling" sound and all of the cockpit lights blink - then, they all go out (the Nav displays and guidance stay active and lit but all other lights (cockpit interior, instrument backlighting, etc.) go dark!  I was able to recover the lighting by moving the lighting control knobs and land normally - very strange!

Almost reminds me of a kind of electrical malfunction simulation...

Edited February 18, 20251 yr by RandallR

Found a bunch of my settings including multiplayer options had changed on my last session, very odd as I wasnt aware that any update happened.

Checking for update was really bad last night for me, it took 8 minutes to get through, otherwise it was running flawlessly.

I'm on 2020 and have done a few medium haul flights, and have been using 572.42 for a few days without problems. I'm not using the Nvidia app, any frame generation or DLSS though, and after the driver update I cleared out the Nvidia cache. The only thing I've noticed on the MSFS site was they have been having issues with 'Online Services' for the last 5 days for 2024.

On 2/10/2025 at 4:08 PM, rayharris108 said:

Me neither. Using the same graphics driver as you, flying in a variety of short-medium range airliners (PMDG, iFly, Feneix, FBW, Heawinds etc) pretty stable with DLSS 4 and a 4 series graphics card. Only thing I notiiced is perfomrance in heavy traffic and large airports with Photogrmmetry cities can be a bit choppier than the previous driver, but not enough that I can be bothered to revert in my case.

I thought it was just me. I flew Taog's Hangar's Lama and clearly noticed an fps drop using the new driver.

On 2/9/2025 at 4:32 PM, JustanotherPilot said:

Past 3 years of flawless enjoyable flights in MSFS 2020 from GA to Airliners, now every flight ends in CTD, thinking it might be the latest Nvidia 572.16 driver, I rolled it back but still, the same problem exists. I don't have the this issue in MSFS 2024. Eventviewer tells me  that Flight simulator.exe is the culprit ("Faulting module path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.38.2.0_x64__8wekyb3d8bbwe\FlightSimulator.exe")

Is anyone having this problem in 2020 and can anyone offer a fix.

Same here. My BATC was stuttering, screen would dim a little bit every once in a while, and constant CTD usually on descent or final and it got worse as newer drivers came out. It got to the point that I'd get a GPU out of memory and CTD when I changed a MSFS setting and then applied it. So, I underclocked and undervolted my GPU with MSI Afterburner just a tad (1.075 to .975mv, and -100mhz), went back to driver 566.36 and problem solved. 

I can now run 2.25xDL resolution (5160x2160), TAA, frame gen and locked at 50fps, BATC with traffic, no CTD. Butter. Still occasional CTDs after exiting a flight and clicking fly on a new one but at least I'm not in the middle of a flight. Its something you may want look into even if you've figure your issue out. You will see no performance degradation and in the very least your card will run cooler. I'm running a 3090ti btw.

On 2/9/2025 at 5:36 PM, edpatino said:

I have no issues at all with FS2020

I'm sure you mean no ill intent with your reply and are a well-meaning person. But, in general, a response like this to someone who is trying to solve a problem is not super helpful. Especially since no insight is provided on what exactly your setup and settings are. This type of response is very prevalent on discussion forums and I'm genuinely curious as to what exactly the point is. I'm seriously not trying to be a jerk. 

 

 

On 2/10/2025 at 4:12 AM, kiek said:

Same here, works like a charm

See, another one. In what way does this point the OP towards a possible solution? 

3 hours ago, sivart2000 said:

I'm sure you mean no ill intent with your reply and are a well-meaning person. But, in general, a response like this to someone who is trying to solve a problem is not super helpful. Especially since no insight is provided on what exactly your setup and settings are. This type of response is very prevalent on discussion forums and I'm genuinely curious as to what exactly the point is. I'm seriously not trying to be a jerk. 

 

 

It is actually very valuable information to know that others are running the same version of software without issues. There have been times after updates where everyone experiences some sort of issue. If that is the case, you shouldn't do anything. If you are the only one crashing, you need to start troubleshooting. Did you update a driver? Did you install some other software? Did you just install some addon scenery or plane? Have you plugged some new device into your computer? Have you recently changed your diet in any way?

56 minutes ago, rjquick said:

It is actually very valuable information to know that others are running the same version of software without issues. There have been times after updates where everyone experiences some sort of issue. If that is the case, you shouldn't do anything. If you are the only one crashing, you need to start troubleshooting. Did you update a driver? Did you install some other software? Did you just install some addon scenery or plane? Have you plugged some new device into your computer? Have you recently changed your diet in any way?

I get your reasoning. I think a more constructive response might be "I'm running ***.** driver and its working for myself and others" and then give some specifics on your system and settings. I think without context, the "mine runs fine" blanket statement seems a bit unhelpful when you are in the frustrating situation of troubleshooting an issue.

13 hours ago, sivart2000 said:

See, another one. In what way does this point the OP towards a possible solution? 

Well, if the OP gets more of these comments, it is more likely that it is not a problem in MSFS2020 but a problem at his end. 
Looks helpful to me. 

Edited February 23, 20251 yr by kiek

2 hours ago, kiek said:

Well, if the OP gets more of these comments, it is more likely that it is not a problem in MSFS2020 but a problem at his end. 
Looks helpful to me. 

Ok. You guys have a point, which is why I asked the question.

It looks like to me, because I did have the same issue, that it is a combination of MSFS, Nvidia drivers and the user end. I had all the latest drivers installed and ran DCS flawlessly. I kept running into more and more CTDs however in MSFS. Like I said, rolling back to an older driver eliminated about 80 percent of my crashes and they completely disappeared when I added an under volt. I did try the newest drivers with an under volt but I was getting a CTDs still.

I know for sure that my VRAM usage went up with the newer drivers. My usage is pretty high anyway because I run 2.25xDL on my 3090ti with 24GB VRAM. But, with the 566.36 I'm at about 70% VRAM usage and the new drivers have me at 98-100% VRAM usage. I think this combined with the way MSFS handles memory plus my PSU being the minimum wattage (went from RTX2080 to RTX3090ti, 850w PSU) necessary to run my rig set me up for CTDs. All things you may want to look at.