After countless testing and reboots I think I found the culprit causing the error which only started happening after the update to SU 1.31.22. It's reproducible in my setup. Depending in your point of view, the error is caused by the new upgrade in MSFS, the old 1070ti GPU, or a setting in the nVidia GPU driver. In my case, that setting is the "4x Sparse Grid Supersampling" set in the nVidia Inspector app used to get rid of shimmering in Prepar3d.

 

So ... what did you set it to?

When I fly MSFS (for the Longitude), I turn the setting off; and when I fly P3D (for the Learjet 35) I turn it back on. Hopefully, there's an alternative solution somewhere.

I guess there's still a little bit old-fashioned left in me and those bright easy-to-read round dials and walk-through cabin in fast bizjets that make it difficult to totally abandon P3D...

P.S. I also downgraded to nVidia driver 526.98. But, I get the same graphic error when I have "4x Sparse Grid Supersampling" set. It could be that SU 1.31.22 has an adverse effect on multiple versions of the driver when ""4x Sparse Grid Supersampling" is active. After testing 4-5 nVidia driver versions I gave up. 

 

Edited April 5, 20233 yr by bofhlusr
Typo

OK - thanks - I'll go check my settings!! I'm not getting any CTDs or anyrhing but have totally forgotten what my supersampling settings are. I tweaked my nVidia settings to death many moons ago and haven't had to change them for ages. I'll report back!

EDIT: Arrgh ... brain fog! I forgot those settings only apply if you use NVI - which I haven't used since I removed P3D from my system (not enough room for both!). So ... I shouldn't really have chimed in on this thread! LOL!

Edited April 5, 20233 yr by Adamski_NZ
Daft old fart

11 hours ago, bofhlusr said:

After countless testing and reboots I think I found the culprit causing the error which only started happening after the update to SU 1.31.22. It's reproducible in my setup. Depending in your point of view, the error is caused by the new upgrade in MSFS, the old 1070ti GPU, or a setting in the nVidia GPU driver. In my case, that setting is the "4x Sparse Grid Supersampling" set in the nVidia Inspector app used to get rid of shimmering in Prepar3d.

 

ICan I ask what the error in the graphics was please?  What were you seeing?

6 hours ago, bobcat999 said:

ICan I ask what the error in the graphics was please?  What were you seeing?

3 hours ago, bofhlusr said:

I have 4090 card with latest nVidia drivers and I get this error mostly when I switch from windowed to full screen or back, or from 2D to VR or back, by the way I don't have NVI.

15 hours ago, penta_a said:

I have 4090 card with latest nVidia drivers and I get this error mostly when I switch from windowed to full screen or back, or from 2D to VR or back, by the way I don't have NVI.

When you get the error, are you able to continue with MSFS or do you get a CTD (crash-to-desktop)? In my case, it was a CTD before MSFS completely loaded. As a result, I did not have access to MSFS and it became inaccessible. I went back to P3D, found that I had new problems there as well, and I was forced to do a lot of tests and experimentation until I arrived at a solution which gave me access to both MSFS and P3D. The first thing I did as soon as I had access to MSFS' Option page was to delete my cache.

1 hour ago, bofhlusr said:

When you get the error, are you able to continue with MSFS or do you get a CTD (crash-to-desktop)? In my case, it was a CTD before MSFS completely loaded. As a result, I did not have access to MSFS and it became inaccessible. I went back to P3D, found that I had new problems there as well, and I was forced to do a lot of tests and experimentation until I arrived at a solution which gave me access to both MSFS and P3D. The first thing I did as soon as I had access to MSFS' Option page was to delete my cache.

MSFS works just fine, except when I try to switch display mode from full screen to windowed, I get that error then CTD.