Just now, St Mawgan said:

Show me how it is a failure on yours! 

I'm already satisfied from your elusive answer.

1 minute ago, Claudius_ said:

I'm already satisfied from your elusive answer.

Er ok then. Ciao. 

2 hours ago, mobiel said:

Does somebody having this issues aswell? Only during movement

 

I started noticing this after this new driver installation. And it seems to be a little worse when using DLSS.

I've just rolled back to the previous driver. I was getting major stutters and very increased GPU temps. DLSS was a disaster on my system with unreadable cockpit displays and strange visual artifacts everywhere. 

1 hour ago, Alvega said:

I started noticing this after this new driver installation. And it seems to be a little worse when using DLSS.

I've found a few issues like this, and as you say, whilst they exist with TAA, they look far worse in DLSS.  I'm guessing that the addon probably needs to be recompiled in the latest SDK or it is using textures that are not DX12 compatible.

There is probably nothing you can do other than accept these anomalies or go back to DX12.

For what it's worth as an exclusively VR user (HP Reverb G2, RTX 3080, Ryzen 5800x3d):

Using the new Nvidia Driver I lost about 7-10 frames keeping the exact same settings I had been using.  That's testing on both DX11 and DX12.  I've reverted back to what I consider the gold standard driver currently 516.59, and I've once again got super smooth framerates.

To me anyway, DX12 and this new driver do not provide anything worthwhile...in fact, they make things worse.

 

4 hours ago, mobiel said:

Does somebody having this issues aswell? Only during movement

 

I've had that since launch with TAA

19 hours ago, Steve Dra said:

OK....officially getting worried here.....all tips and hints delivered here have not helped my situation.

MSFS simply CTDs after the loading screen (the one where you see the TBM with KSFO in the background.  Its gets to the screen where MSFS "should" start loading, and CTD immediately.

I reverted back to the studio driver (and used the clean install option)...and now with the studio driver, getting the exact same issue. 

Never have I ever had this happen with a driver update...MSFS has been just about flawless since I bought it day 1.

Hope more suggestions come in...I'm HARD DOWN! 😞

 

If you see the TBM with KSFO in the background it is because you do not run MSFS in administrator mode. 

18 hours ago, Steve Dra said:

I did

twice in fact....a full shutdown...then a "reboot" after

Did you try a repair install of MSFS? I'd also do an SFC /SCANNOW for system files.

1 hour ago, vgbaron said:

Did you try a repair install of MSFS?

I did the 1st one where it does not delete anything....will try the next step where it clears data. 

"I'd also do an SFC /SCANNOW for system files"

Will have to remember how to do that...old age you know 🙂 

1 hour ago, guibru said:

If you see the TBM with KSFO in the background it is because you do not run MSFS in administrator mode. 

I think I've set it up to run in administrator mode, but will check that, thanks.

Wow! Strange happening this morning that forced me to roll back to the old 516.94 driver.

First, specs: 10700K @ 4.9 ghz, RTX 3080 12 gb, 2K monitor. 

I had installed the new 517.48 driver yesterday with no problems. With either DX 11 or DX12, TAA or DLSS, everything was fine (I marginally preferred TAA, it seemed a bit sharper). My GPU was loafing at around 45%, my CPU main thread around 85%. Temps were all normal (I monitor with MSI Afterburner). I'm locked down at 36 fps in NCP, and was easily able to maintain that.

This morning I started up MSFS, same plane, airport and conditions, and it was a stuttery mess, with the fps now down to 10 (!) where the previous day they had been a rock solid 36. And using MSI Afterburner, I saw why: my GPU was now running at 100%, but my CPU main thread was only at 35%, almost a complete reversal from the day before. But temps on both GPU and CPU were still the same and normal.

<offensive initials not allowed>?!!!?

I tried restarting the sim, and rebooting the pc, but still the same result. Anyway, I didn't feel like messing around, I wanted to fly, so I rolled back to the 516.94 driver, and everything is now back to usual, with rock solid 36 fps and very smooth performance.  

I wonder if it might be in my NCP settings, I had kept the same settings I had in SU9: in MSFS, I have v-sync turned off, all settings otherwise on standard Ultra, while in NCP, I have  Low Latency Mode set to Ultra, V-sync set to Fast, and fps locked at 36. But if something in the settings, why did everything work fine yesterday? I don't know. 

Any thoughts?

I may try messing around with the new driver and settings later, but as said, at the moment I just want to fly, and everything is working fine. 

Thanks - Bob

 

 

Edited September 28, 20223 yr by BBCM

6 hours ago, mobiel said:

Does somebody having this issues aswell? Only during movement

 

Matrix has you!

4 minutes ago, Drumcode said:

Matrix has you!

Hehe....its when you see that "code" as a "blonde, redhead, brunette" that you really start to wonder....😆  (BTW I have seen that back when my MSFS was working) 😞 

8 minutes ago, Drumcode said:

Matrix has you!

“Were you paying attention, Neo? Or were you looking at the woman in the red dress?” 😎

6 hours ago, mobiel said:

Does somebody having this issues aswell? Only during movement

 

Mainly in VR yes indeed.