If you look at the top of the forum page, click on website. Go to “Discover” and look at the drop-down menu. Look under support. Hope this helps!
I think that this line ‘thing’ is linked to the issue. I’ve done several flights now near large expanses of water (the precision helicopter landing activities near lighhouses and oil rigs for example) and they’ve worked just fine but I don’t see this line in those cases. As soon as I find somewhere where that line is visible I can re-create the error. Does anyone know what that line represents? It’s something to do with the way that the landscape is built out and rendered but is there anything that can be done to address it?
Here is a screenshot from my 1060 in the same spot. I just noticed that there are no waves in my original screenshot above. Maybe a shader issue??? MSFT are you there???
Does it crash with your 1060 as well?
Nope, naver crashed on my 1060. I switched back to it a while back to get thru some certs do i could continue career mode. I finally gave up and sold my Arc and got a 9060xt (arriving tomorrow). Hated yo do it but it definitely seems arc related. May not be their fault but oh well. All other games worked fine.
1 Like
Yeah, I think this water thing is an AMD/Intel problem because I’m flying just fine over large bodies of water with my RTX 3050 6GB.
I have a three-scren setup. Two are actual 21" 1080p computer monitors and I am using a 42" 1080p television for the main monitor. Everything played well with MSFS on all three monitors until I swapped out this tv for a different one, same size but definitely different. This is when the problems started. However, I can play MSFS on the other two monitors just fine so it has to be that MSFS does not like that different TV or at least my 3060ti does not like that tv when playing MSFS. I guess it is time for a dedicated gaming monitor for the main monitor or maybe it is a setting I can tweak in MSFS? Any suggestions?
Just tested this. No crash here. I haven’t had any more issues since I tweaked my undervolt on my cpu/gpu.
Hi - just an update as I had this issue with my Intel ARC and Flightsim crashing near large bodies of water. Intel released aa new driver yesterday - did a clean install of that and it’s completely fixed the issue - can do all of the certs that wouldn’t load previously and fly all of the locations that were always crashing out. The new driver fixed it so I’m happy now.
1 Like
That’s interesting, I didn’t see anything in the driver release notes that would suggest a fix but maybe they fixed something that affected another game in a similar fashion? Good news though. 
I am in the beta now again, and if I leave the FS20 original DLSS file, the free flight loads well in 2D, once I change it with DLSS-Swaper to the DLSS 310.3, before load totally the free flight in the bar, this error and CTD, totally reproducible already for me, only it loads with TAA or the old DLSS. I have to test now in VR with TAA-DLSS and installing the last Nvidia driver again. But sure I have to load the flight in 2D-TAA first, and then VR with the DLSS settings already or to have TAA also in VR MSFS settings, and set DLSS in FS20 settings after enter in VR.
This resolved it for me as well.
My error was also caused by using DLSS Swapper and using the latest DLLs. Reverting to the game’s original file fixed it.
However, this means DLSS is uglier and less performant. I found this registry edit tweak allowed me to once again use the latest available library in DLSS Swapper: https://www.youtube-nocookie.com/embed/J3fofOGVw5g
My solution for to be able to use the latest DLSS in FS20 is, start FS20 and then the flight with TAA e.g. (restart FS20 with TAA if you close it with DLSS selected in options), both in 2D or VR, and then after the flight loads, change in options to DLSS, and after the flight change it again to TAA before close FS20, if not this workaround don´t functions (I guess with the other antialiasings work also, FXAA tested). Tested with DX11, HAGS off, and with any of the more recent Nvidia drivers, if that is related and helps.
Could you write here the strings to add or modify in the Registry to solve this to test?
Hey. If i use DLSS V2 original files i no longer get the DXGI CDT.
Any work arounds?
Uninstalling Nvidia app has sense with my DLSS workaround solution related
“My solution for to be able to use the latest DLSS in FS20 is, start FS20 and then the flight with TAA e.g. (restart FS20 with TAA if you close it with DLSS selected in options), both in 2D or VR, and then after the flight loads, change in options to DLSS, and after the flight change it again to TAA before close FS20, if not this workaround don´t functions (I guess with the other antialiasings work also, FXAA tested). Tested with DX11, HAGS off, and with any of the more recent Nvidia drivers, if that is related and helps.”
, because that app can change the DLSSs and its profiles, or/and more, who knows. I have read also that installing the Nvidia driver with NVCleanstall cured this error, I would have to test also.
I’ll just stay with the original DLSS for now or maybe go back to my stable driver where i can use DLSS 4
Maybe the best for DLSS4 till this solved and other Nvidia driver patches don´t affect you, and you don´t have a Nvidia 50xx that needs new drivers more.
Well these new drivers have no benefit for the 5080 which i have just now for MSFS 2020
I may go back a driver if i don’t see good performance without DLSS 4
So i should uninstall the Nvidia app and reinstall the new driver manually?