NVidia 310.54 beta -> good results

[msalama]

Hiya fellow DCS aviators & aviatrixen -

 

The newest NVidia beta drivers seem to render faster in DCSW, and if I'm not imagining things even help with the dreaded MRLS launches a tad. Nothing revolutionary of course, but IMO worth a try still - although YMMV of course.

 

Just a heads up, mind :)

[Azrayen]

Hi,

Good news, but worth to precise with which graphic card IMO ;)

[msalama]

Oh yeah, mine is a GTX580.

[Rusty_M]

Damn. I'm away this weekend. I could have dropped a CBU to have a look.

[Loki_]

I actually have a stutter once every 3 seconds that began with these beta drivers. Only in DCS. BF3 etc they seem fine. GTX 680.

[Markindel]

thanks for this news.

[Druid_]

Damn need to update my drivers ... Loki whats the latest drivers you are using stutter free?

[FZG_Immel]

Bump

[aceflier]

Just played on 104th server with these drivers. They seem good to me. No stuttering on my end.

 

I have 2 560ti's and a 2600k cpu at 5ghz.

[Mainstay]

GTX680 here and 3 or 4 seconds theres a freeze in DCS with these drivers

[Lange_666]

GTX480: no freeze, all smooth. But i don't see any improvement over the previous drivers so...

[nannicek]

For me...Improved graphics performance with these drives.......more smooth...:thumbup:

[msalama]

Well I'm not so sure anymore if these drivers actually are any better. Some off-axis view angles seem to have more stuttering if anything, but then they run really smooth when looking straight ahead. So I actually went back to the latest WHQL build today just to compare again... we'll see.

 

EDIT: And oh yeah, was experiencing some short freezes when taking off as well before the rollback.

[Lange_666]

GTX480: no freeze, all smooth. But i don't see any improvement over the previous drivers so...

 

Had a few short freezes yesterday while in FC3.

But this is not the only thing what's been wrong with these drivers (for me at least).

The last few days i suffered sometimes from crashes (no more video display, no recovery possible) with Opera, GameBooster (while running analyzer) and TrackIR while launching.

Used to have 310.33 beta installed prior to 310.54 and with those i had "videodriver not responding but recovered" errors with the same programs as mentioned above. With 310.54 there was no such error but the screen went black with no video signal anymore.

Took me a while to try and test various solutions provided on the net (of course none of these actually worked).

Rolled back to 306.97 WHQL which were stable for me.

[Sarge55]

Thanks for testing out these betas and reporting on them guys.

[BRooDJeRo]

Stuttering with old driver and not with new = driver related

 

Stuttering with old driver and also with new = not driver related

[BRooDJeRo]

or

 

Stuttering with old driver and also with new = still not fixed since 680 release

 

Depends if all 680 users are having stuttering or not.

[Lange_666]

Had a few short freezes yesterday while in FC3.

But this is not the only thing what's been wrong with these drivers (for me at least).

The last few days i suffered sometimes from crashes (no more video display, no recovery possible) with Opera, GameBooster (while running analyzer) and TrackIR while launching.

Used to have 310.33 beta installed prior to 310.54 and with those i had "videodriver not responding but recovered" errors with the same programs as mentioned above. With 310.54 there was no such error but the screen went black with no video signal anymore.

Took me a while to try and test various solutions provided on the net (of course none of these actually worked).

Rolled back to 306.97 WHQL which were stable for me.

 

After the roll back to 306.97 WHQL all was fine again but not for that long.

Today i sufferend again from the "videodriver not responding but recovered" error and a bit later, when launching TrackIR, the screen went black with no recovery besides hardreseting the PC.

This leaves me with a hardware problem i guess instead of a driver problem.

Haven't figured it out yet what causes this but reading through forums which make note of the same error points into the direction of the videocard. Those who had the same error changed their videocard in the end to solve the problem.

But i'm still a bit uncertain that this is the case because under load (playing a videogame) the videocrad never crashed on me. It only does this while some applications are started: TrackIR, GameBoosters Analyzer, Opera browers while loading a video from Youtube.

Also, when it crashes, as far as i can check, voltages and temps are all normal and well within range (under load, the temperature even doubles).

What bugs me a bit is that the videocard (sometimes) stops sending a signal to the screen when TrackIR is loaded and more... on the moment when the TrackIR device should be activated. If i unplug it and only run the TrackIR software, the videocard never looses it's signal.

This makes me think it's more of a power problem but... the videocard uses different outlets on the powersupply then the motherboard does. Or it must be that the PCI bus is shortly interrupted when the TrackIR comes on.

But then again... that does not explain the problem with GameBoosters Analyzer or Opera (which don't use extra power like TrackIR does).

 

So i'm still a bit in the dark on what causes the hang-ups: videocard or powersupply (or maybe the motherboard in general but that's only option 3 atm)...:cry:

[Mainstay]

Have you done a clean install of the whql drivers? Also what is your powersupply?

[Lange_666]

Yes (always) and it's a 1000W Coolermaster (more then enough power, doing it's job already for over 2 years without a problem but so did the videocard)

[Derk]

I had the same problem with my last pc build. I thought there was nothing i hadn't tried until i set my CPU back to stock values. It seems that the CPU OC i did played havoc on my GPU. Running smooth for 2 months now without OC's.

 

Oh, and the build before this one i had it too, but slightly underclocking my GPU solved the problem. It is also said that you can try to up the voltage on your GPU a bit, but i haven't tried that.

 

Good luck!

[msalama]

OK, da gig is getting weirder by the mahfahn minute. Sordid details following:

 

When I first installed the NVidia betas I thought they were great, i.e. running smoother than the latest WHQL and stable to boot. But then I started to notice all kinds of little stutters from the corner of my virtual eye, and looking straight aside they were actually pretty bad. OK, back to the WHQL then, I thought - reinstalled those and still the same feekin' thing (mind you that I always, always install display drivers clean, including weeding out unused registry entries and directories manually, so old driver crap left behind isn't the culprit here).

 

Now I've had certain NVidia & ingame configs for a long while already, and while DCS is indeed a hard beast to tame, they still have by and large worked pretty well for me - until now. I had to force a 35 FPS cap, and vertical sync at 1/2 the refresh rate - and while things are back to smooth again this all means I now have to run this old CRT at 70Hz instead of the previous 85! :mad:

 

To be continued...

 

PS. Yassuh, using an old beat-up 19" Viewsonic isn't the most clever thing a bugger can do, but money's too tight to mention ATM with Xmas coming and everything. I know I'll get the bugger running great again when I buy a new flatscreen comes spring, but what the heck happened to my old tried-and-true config which used to run so well until now - can the most recent sim version still be the culprit here???

Edited November 21, 2012 by msalama

[FZG_Immel]

can someone post their nvidia settings for DCS ?

[msalama]

Will do when the driver dance is done and I settle on something.

[Lange_666]

can someone post their nvidia settings for DCS ?

 

Currently i have:

- Max Pre-rendered frames: 1

- Multi Display: Single Display Performance mode

- Power Management: Max Power

- Tripple Buffer: On

- VSync: Adaptive (half refresh rate)

 

 

All the rest is standard.

 

 

I'm always getting a bit confused with these settings (AA, AF and all the other crap), certainly when developers set the stuff now (partly) ingame, give it other names then the ones in the nVidia settings to mess things up more and then prevent some stuff to work from within the driversettings.

To make matters even worse, i always forget the difference between AA, AF, FXAA, MSAA, TSAAA and all the other crap. Have to look it up every time (some peeps call it getting old...). Setting stuff to high and your performance takes a dive, setting it to low and it looks like shit (i hate the flickering around fences and single lines) and setting it to medium only solves your problem for 50% (hence the medium setting LOL).

And when you finaly cash out for that next big ass videocard, the devs come with another upgrade bringing that card directly back to where you were previously. It's a vicious never ending circle to pull money out of you wallet.