Has anybody tried these as opposed to the "game ready" drivers and does it help with any of the post SU5 problems?

Hi,

Yes, I've tried it.

Only two flights yet.

Smooth and no CTDs.

Edited August 5, 20214 yr by John Fields

Hi,

Not solved!

Third flight (the same as the two that I did before) and... CTD!

That's too bad!

Waiting for ASOBO new patch!

I have always used a Studio driver and never had a CTD with MSFS

Mike.

Hi,

The three flights I've done were the same LOWL (Linz) to LOLO (Ost Linz) with the same aircraft (C152) following the same path of the GPS. The third concluded with a CTD.

I've never used the Nvidia Studio driver before. But before the SU5 update and the hotfix (1.18.14.0) I haven't had CTDs for a very long time.

I tried this driver because I've seen a video saying that it might solve the CTD problem. But, in my case, it didn't solve it!

Since the last update, including the hotfix, I have had multiple CTDs. I've tried everything (no addons, no live weather, no air traffic... you name it!). So... I have to wait until next patch or update and... touch wood!

 

 

Using the Studio Driver is essentially the same as going back some revisions of the Game ready Driver.

22 minutes ago, swiesma said:

Using the Studio Driver is essentially the same as going back some revisions of the Game ready Driver.

Thats odd, I just tried it (as nobody said it was detrimental) and the word "beta" showed up, I wonder why they would need a beta of an older revision? I cannot say it has made much if any difference to the sim but need a good few hours using it to give it a proper trial run.

Well you can read it up - the Studio driver is basically a "stable" version of the drivers and not updated as often as the Game ready drivers.

 

Why it says Beta? Only God / Nvidia knows 🙂 

Edited August 5, 20214 yr by swiesma

I first tried the newest game ready driver with this patch, but I got visual artifacts and several CTD's, I then revert back to the trusted 457.30 and everything has been fine and stable since then, I have decided to stay with this excellent driver further on, why fix something that works.

Edited August 5, 20214 yr by Ixoye

Here's a bizarre one for you guys and gals: Briefly, test what happens if you use the Balanced or Performance power profile.

Here is a thread where user ememPilot and I talk about it: https://forums.flightsimulator.com/t/asobo-completely-quiet-about-these-ctd/428022/139?u=hst12

3 hours ago, swiesma said:

Using the Studio Driver is essentially the same as going back some revisions of the Game ready Driver.

As long as both drivers have the same version number they are essentially the same. Game ready drivers are just updated more frequently. 

From Nvidia forums: I just started using the Studio driver based on another thread and I'm very happy with it. I use my PC for other gaming though so I'm not sure how that's going to affect those gaming experiences. 

NVIDIA Studio Driver vs. Game Ready Driver: which should I install?

 

20

MAR 2019

 

APR 2021

Manuel@NVIDIA

2y

 

 

 

All NVIDIA drivers provide full features and application support for top games and creative applications. If you are a gamer who prioritizes day of launch support for the latest games, patches, and DLCs, choose Game Ready Drivers. If you are a content creator who prioritizes stability and quality for creative workflows including video editing, animation, photography, graphic design, and livestreaming, choose NVIDIA Studio Driver. If you are both a gamer and creator, choose Game Ready Drivers. Learn more about NVIDIA Studio Drivers here: https://www.nvidia.com/en-us/geforce/news/nvidia-studio-driver-now-supercharge-your-favorite-creative-apps/

Hmm, I personally think this particular 'fix' has a label on it, reading "Snake Oil".

I could be wrong - it happens a lot! 😄   But when CTDs are caused by GPU drivers, there are other pieces of evidence observable, such as spiking and odd graphical artifacts.   Although we have lost some visual fidelity with SY5, it seems to be about errors and ommisions at the Asobo side.    I just don't see this being a Nvidia driver problem.   People are desperate and some YouTubers will gain a lot of views, coming up with some new 'solution' for desperate people.  I saw a video yesterday where someone said deleting the MSFS desktop icon and regenerating it, had fixed their CTDs.........

I won't say this "fixed" my issues with SU5 but I've been tweaking with the usercfg.opt file with mixed results for the past week and a half and after following the recommendations in Overkill's post (see Telling it like it is) I've had 3 of the best flights I've experienced yet and with no CTD's. Graphics and performance both at the top of my level of experience so far and even prior to SU5. 

As I said in another post, it may simply have been a clean install of the drivers from Game Ready to Studio as I always use the Express Installation option when updating where this time I did a clean install for the Studio driver. 

I'm sure after the drop of HF2 there will be another set of issues to deal with. It's kinda' like watching my 18 month old grandson going through his teething process. He finally gets over a new one and the pain subsides, only to have another one pop through and "here we go again". 😁

Edited August 5, 20214 yr by Flypops

On 8/5/2021 at 4:00 AM, swiesma said:

Using the Studio Driver is essentially the same as going back some revisions of the Game ready Driver.

The last two 471.xx drivers were released the same time in GRD and NSD.

Furthermore, if you diff the two drivers files, you'll find out the binaries are the same...

The only differences I can notice are:

- NSD driver .inf/.cat is supporting less video card choices (mostly older ones though)

- GRD driver is probably enabling a few more and/or specific driver optimizations via the registry (binaries are the same).

On a personal note, I find NSD more stable in VR overall with HAGS OFF.