CTD 3 times…from April 25 update…unbelievable…have rolled back Nvidia driver to 531.29
Crash stated over clocking etc… overheating… note: system normal; Not over heating etc… system not overclocked! System run great…before this update…but l did update drivers and are systems up-to-date…Thinking Nvidia is causing all problems at this… RTX 2070 SUPER i7-9700K 3.6 Ghz 128 ram…
Also, one basic problem with Asobo statements as to Update ALL drivers… There should be a major CAVEAT to graphic drivers! Also,with then working with and giving input to Nvidia! Someone is not listening to the community to this related issues. The products are very good… But a little more detail and polishes releases…needed from Asobo. Made it the best… so the next release should maybe smaller more detail to problems solving and pride to your amazing work. And you should be very proud!
Also, let the graphic company’s now this is unacceptable and the community has strong voice… To revenue and bottomlines of each of these companies! Old saying " garbage in garbage out". The power of community will be heard slowly.
On a positive note Flight Simulator 2020 is beyond good a exceptional game. I have enjoyed many hours from the first time it came out till now. All best…Kevin Hudson
Hey @Kevin_Hudson,
I’m sorry to learn that you’re dealing with CTDs following the WUXIII update. It can be quite annoying when things go haywire after updates. Just wondering if you have any addons in your community folder? If not, have you considered doing a full reinstallation of the game as a last resort? Sometimes, files can get corrupted, and reinstalling can help fix the issue.
All good here. In fact, the performance is amazing for me on this one. I’ve been sitting at 60-62 frames for a long time in the air now in a F-22 at Mach 2+. Butter smooth. Check add-ons. I have hundreds. There were a few I had to get rid of before the update. I tend to remove any add-ons from the sim on a WU that are in the area then add them back if needed.
Good luck!
Did find the problem it was Nvidia driver 531.61…Rolled back to 531.29 all back to normal.
Kevin Hudson