CTD At KSEA With 572.16

[TexasGary]

I am running MSFS 2020 with an RTX 4090.  I updated to 572.16 via the Nvidia App and set DLSS Override-Model Presets for Frame Generation and Super Resolution to "Latest" and since I use DLAA I set DLSS Override-Super Resolution to "DLAA 100%".  I made a few flights, and I was really impressed with the latest driver with DLSS 4.  Clean, crisp graphics and little to no ghosting on the PFD speed and altitude tapes.  But now whenever I select KSEA as a departure airport and the map zooms into the airport to start the flight it always crashes back to the desktop.  I tried randomly starting at several other airports, and it doesn't CTD.  Is anyone else running 572.16 having this CTD at KSEA? 

[B777ER]

32 minutes ago, TexasGary said:

I am running MSFS 2020 with an RTX 4090.  I updated to 572.16 via the Nvidia App and set DLSS Override-Model Presets for Frame Generation and Super Resolution to "Latest" and since I use DLAA I set DLSS Override-Super Resolution to "DLAA 100%".  I made a few flights, and I was really impressed with the latest driver with DLSS 4.  Clean, crisp graphics and little to no ghosting on the PFD speed and altitude tapes.  But now whenever I select KSEA as a departure airport and the map zooms into the airport to start the flight it always crashes back to the desktop.  I tried randomly starting at several other airports, and it doesn't CTD.  Is anyone else running 572.16 having this CTD at KSEA? 

What scenery you using for SEA, stock, BMAmsim, FT?

[TomCYYZ]

Yep, same here.

 

[TexasGary]

This happens with stock scenery.

 

[Gilandred]

Try deleting the Nvidia app and see if it works.  The app was causing me to CTD when trying to load the game,

[Noel]

1 hour ago, TexasGary said:

Clean, crisp graphics and little to no ghosting on the PFD speed and altitude tapes. 

Hi Gary,

If you were using v3.8 previously can you give me your impression of how much improved graphics and ghosting were.  I spent hours trying to make the new driver work with DLSS 4 and ended up reverting back to a former driver, deleted NV app, and inserting DLSS3.8 into the Contents folder which was very new for me as it was still v2!! and I'm now having best ever graphics and very little smearing/ghosting, almost none.  I ask to help me decide if it's worth going thru this attempt at getting DLSS4 working.

[TomCYYZ]

30 minutes ago, Noel said:

Hi Gary,

If you were using v3.8 previously can you give me your impression of how much improved graphics and ghosting were.  I spent hours trying to make the new driver work with DLSS 4 and ended up reverting back to a former driver, deleted NV app, and inserting DLSS3.8 into the Contents folder which was very new for me as it was still v2!! and I'm now having best ever graphics and very little smearing/ghosting, almost none.  I ask to help me decide if it's worth going thru this attempt at getting DLSS4 working.

I am a little confused this whole NV App thing. I did similar but, when you say "inserting DLSS3.8 into the Contents folder", is that using DLSS Swapper or physically inserting into Contents folder. I cannot load a flight now after reverting back to Nvidia driver v 566.14 and changing DLSS version back to 3.8.10.0 using the Swapper app. Should I be physically replacing the  DLSS3.8 into the folder?... BTW not sure where this folder is...Thanks.

Edited January 31 by TomCYYZ

[TexasGary]

Hey Noel, here's my take on the new driver with DLSS 4.  I've only made a handful of flights, but to me the biggest improvements are:

1) Higher FPS.  Since I didn't note my fps before updating I cant say exactly how many frames I gained.  But in some areas where system previously struggled a little (PMDG 738, addon scenery, GSX, FS Traffic, lot of cloud cover) it is now noticeably smoother.

2) Almost no ghosting on altitude or speed tapes.  Prior to updating I had noticeable ghosting, but now I don't notice any ghosting at all

3) No more noticeable artifacts.   Prior to updating I always noticed some small artifacts on the left and right cockpit windows in the CJ4.  But now they are not there.

The only downside I have seen so far is the CTD at KSEA that I didn't have prior to updating to the current driver.

[Noel]

13 minutes ago, TomCYYZ said:

is that using DLSS Swapper or physically inserting into Contents folder

Physically copying in to C:\XboxGames\Microsoft Flight Simulator\Content

I read on TechRadar you can just drop it in.  So I moved the current file out and dropped in dlss 3.8 which has been a very nice upgrade so far.

Edited January 31 by Noel

[TexasGary]

If anyone else can confirm this CTD at KSEA I'll submit a ticket on it.

 

 

[Noel]

1 minute ago, TexasGary said:

The only downside I have seen so far is the CTD at KSEA that I didn't have prior to updating to the current driver.

Awesome thanks for that!  I may try again but honestly I have no idea why 2020 would not fully launch to the Welcome screen it would hang about 80% whenever I selected the recommended dlss overrides displayed for 2020 in the NV app.  It took me hours to set everything straight after that because for some reason the MSFS install got slightly borked and other stuff.  And plus I had some odd behavior w/ the new driver where I had to reinstall it thru the NV app, but it would hang on exit as well.  So now back to the prior driver.  And now with dlss 3.8 it's also a pretty good jump in IQ and artifact reduction.

[TomCYYZ]

20 minutes ago, Noel said:

Physically copying in to C:\XboxGames\Microsoft Flight Simulator\Content

I read on TechRadar you can just drop it in.  So I moved the current file out and dropped in dlss 3.8 which has been a very nice upgrade so far.

Strange, I have an XboxGames directory, but not like yours, mine is:

C:\XboxGames\GameSave\pgs;wgs...two empty folders :pgs & wgs

Could it be because I have a Steam installation of MSFS2020?

So, not sure where to find this folder.

 

Edited January 31 by TomCYYZ

[TomCYYZ]

13 minutes ago, TexasGary said:

If anyone else can confirm this CTD at KSEA I'll submit a ticket on it.

 

 

I have "bmworld" version and both it and default version now give me a CTD since I INSTALLED the nv aPP (I have since deleted the app). I too have no problems starting a flight from any other airport.

[SN737]

2 hours ago, TexasGary said:

I am running MSFS 2020 with an RTX 4090.  I updated to 572.16 via the Nvidia App and set DLSS Override-Model Presets for Frame Generation and Super Resolution to "Latest" and since I use DLAA I set DLSS Override-Super Resolution to "DLAA 100%".  I made a few flights, and I was really impressed with the latest driver with DLSS 4.  Clean, crisp graphics and little to no ghosting on the PFD speed and altitude tapes.  But now whenever I select KSEA as a departure airport and the map zooms into the airport to start the flight it always crashes back to the desktop.  I tried randomly starting at several other airports, and it doesn't CTD.  Is anyone else running 572.16 having this CTD at KSEA? 

Do you have navigraph subs?. If you do, double check if you updated to AIRAC Cycle 2501 rev.2, from Navigraph Hub. there was an issue with with rev.1 that caused CTD all over with specific airports.

P.S. KSEA was one of the CTD affected airports, payware and stock.

Edited January 31 by SN737

[Noel]

17 minutes ago, TomCYYZ said:

Could it be because I have a Steam installation of MSFS2020?

That would be my first guess too!  I'm on Win 11 23H2 FWIW