14 minutes ago, omarsmak30 said:

@Bobsk8 I want to thank you for this video. That Nvidia fix has almost eliminated my issues with SU5! My V-Sync wasn't working, my windowed mode was buggy with camera jumping around,  I had some weird shimmering surrounding any light source plus my annoying CTDs. All these issues (not sure about the CTD, so far I have got no CTD since I switched Nvidia driver but I will need to test further) have been resolved by completely reinstall the Studio driver. Thanks again!

Glad it helped. 

3 minutes ago, Bobsk8 said:

It has always been that way, read only most of the time doesn't work. 

Yes Bob, but some were saying " its people changing there config and using Read only." Like Read only was the source of peoples problems.

 

Why dont Nvidia just say what "normal" driver version they now call "Studio driver." if there just older normal drivers.

Edited August 5, 20214 yr by Nyxx

21 minutes ago, omarsmak30 said:

That Nvidia fix

which one, did I miss anything?

5 minutes ago, DAD said:

which one, did I miss anything?

Peopel are using/trying the "studio" drivers not the normal ones.

1 minute ago, Nyxx said:

Peopel are using/trying the "studio" drivers not the normal ones.

ok, thx. just realized that I can update my normal driver to 471.41 anyway, will do that at least

4 minutes ago, Nyxx said:

Peopel are using/trying the "studio" drivers not the normal ones.

Or just complete clean reinstall driver could also have helped depite being studio or game driver. Nevertheless I am happy now and I won't touch it for sometimes 😅

Edited August 5, 20214 yr by omarsmak30

2 hours ago, Swe_Richard said:

The sim is unusable for me in this state and I doubt it will ever be fixed.

So why is it working fine with no CTDs for some of us? I’ve not had a single CTD despite hours of use with “ultra” settings. I get the frustration, but the melodrama is silly.

There’s obviously something that affects a number of people with a specific game configuration and/or hardware configuration, and not others. And they’ve isolated the “x factor” through crash dumps or other troubleshooting.

 

3 minutes ago, omarsmak30 said:

Or just complete clean reinstall driver could also have helped depite being studio or game driver. Nevertheless I am happy now and I won't touch it for sometimes 😅

It is possibly worth pointing out (to those who do not realise it) that a clean install will also clear out any changes you might have previously made in the Nvidia Control panel programme specific to MSFS, like I had my FPS max instruction & a few other things changed there. I presume this wiping out affects everybody?

Driver change is a good first troubleshooting step for a CTD issue, and a good last attempt for most other issues.

It seems like so many questions these days are purely rhetorical, and are framed in a way to make a statement rather than to promote analysis for improvements. Sample size is a big problem, a 2 hour flight on one PC is about the equivalent test of running notepad to test if a beta build of Windows is actually stable. An embellishment perhaps, but it gets the point across.

 

Edited August 5, 20214 yr by Alpine Scenery

1 minute ago, Espana Pete said:

It is possibly worth pointing out (to those who do not realise it) that a clean install will also clear out any changes you might have previously made in the Nvidia Control panel programme specific to MSFS, like I had my FPS max instruction & a few other things changed there. I presume this wiping out affects everybody?

Yes. I always do a clean install, then have to put settings back (general and program specific). A bit of a pain, but I'd rather do a clean install.

Just now, March Hare said:

Yes. I always do a clean install, then have to put settings back (general and program specific). A bit of a pain, but I'd rather do a clean install.

I had never seen the option before but understand a lot of folk have advised a clean install in the past. Another lesson learnt and noted in my little red book.

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 (clean Install with DDU), and everything has been working flawless and stable since then, I have decided to keep this excellent driver further on, why fix something that works.

1 minute ago, Espana Pete said:

I had never seen the option before but understand a lot of folk have advised a clean install in the past. Another lesson learnt and noted in my little red book.

Its helpful to screenshot your Nvidia settings when you first get that blissful feeling that everything finally feels right. I know I have altered a few things experimentally, and then lost track later. So that can be good or bad to do that, just have to keep note of your stuff.

1 minute ago, Ixoye said:

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 (clean Install with DDU), and everything has been working flawless and stable since then, I have decided to keep this excellent driver further on, why fix something that works.

I keep meaning to revert, too. It's happened some months back where complaints came in about the sim but it was the driver (obviously not the case at the moment, with the issues acknowledged, but I think the current driver might be causing some problems).

10 minutes ago, neil0311 said:

So why is it working fine with no CTDs for some of us? I’ve not had a single CTD despite hours of use with “ultra” settings. I get the frustration, but the melodrama is silly.

There’s obviously something that affects a number of people with a specific game configuration and/or hardware configuration, and not others. And they’ve isolated the “x factor” through crash dumps or other troubleshooting.

 

Well of course it works for many, I didn't say anything else now did I? I said the sim is unusable FOR ME which is absolutely true as it crashes constantly since SU5 and the HF (very stable before the update). Besides, I seriously doubt they've isolated any "X-factor" yet and from the correspondence I've had with the support they simply do not know what's causing the crashes.