NVidia 310.54 beta -> good results

[Lange_666]

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!

 

Nothing over- or underclocked atm (i always keep things running at stock speed). But i will find out in the end, no worries...:pilotfly:

[msalama]

can someone post their nvidia settings for DCS ?

 

OK, current DCS and NVidia settings attached, HTH :)

[Wolf Rider]

Your AA setting needs to be Application Controlled (not Overide Program setting)

and setting Threaded Optimisation to Off (instead of Auto) helps immensley, as well set the FPS limiter to the same as your monitor Hz.

Edited November 23, 2012 by Wolf Rider

[msalama]

OK, I see my settings need some explaining :) But first, let's remember that there really aren't any hard and fast rules for setting up one's computer, because due to the PC platform being so wildly heterogeneous every machine indeed is a different beast altogether.

 

Your AA setting needs to be Application Controlled (not Overide Program setting)

I tried this a while back and saw no performance difference whatsoever. The current settings, however, look much better, and at the same time also work well with some other games I occasionally play (SH3, RoF).

 

and setting Threaded Optimisation to Off (instead of Auto) helps immensley

Tried this too, but everything maxed out (i.e. in a worst-case scenario of sorts) threaded optimization set to on gave me a couple more f/s. So on it went - and stays.

 

as well set the FPS limiter to the same as your monitor Hz.

Not necessarily, if one aims for constant and non-fluctuating FPS. Set like this I've got everything locked at 35 f/s because I found my FPS never goes below that, even when there're lots of units puttering about and explosions going off, etc. And no stutters either, mind you!

 

The 35 FPS criteria, BTW, comes from an old 19" CRT I'm still using until the spring at least. The bugger only accepts refresh rates of 60, 70, 75 and 85Hz respectively, and the minimum acceptable refresh rate for comfortable all-around use is 70Hz, AND said rate also goes well with NV Inspector's 1/2 rate vertical sync - which, incidentally, happens to be exactly 35 FPS ;) So my aim here isn't so much to squeeze every last inch of performance out of the system, but rather get the sim run SMOOTHLY all around - and with these settings it does exactly that I've found.

 

I hope this clears it up a bit?

Edited November 23, 2012 by msalama

[msalama]

PS. Oh yeah, should've prolly added a disclaimer to the settings as well in the 1st place, but better late than never. Therefore:

 

 

 

YMMV YMMV YMMV

 

;)

[Lange_666]

Your AA setting needs to be Application Controlled (not Overide Program setting)

Yes but then his ingame setting should be set to certain value instead of off.

That's why i said above that it's a mess. Sometimes you have to set it ingame, sometimes you have to set it in the control panel, sometimes you can set it to override and sometimes override doesn't work. And in most cases you only find out by testing after each update.

 

and setting Threaded Optimisation to Off (instead of Auto) helps immensley

I always thought that this setting had to do with the GPU (didn't really dig into it in the past) but it seems that it's about the CPU.

From TweakGuides: Threaded Optimization: Controls the use of multithreaded optimization for all 3D games on systems with multi-core/HyperThreaded CPUs. The available settings are Auto, On and Off. I strongly recommend the default option of Auto, allowing the drivers to set this appropriately for various games based on your hardware. Only turn Off for troubleshooting purposes if you believe a particular (older) game is not compatible with multi-core CPUs, and only set to On if troubleshooting to see if it improves performance in a recent game.

 

But your comment made me test it again and honstely, i don't see any difference between Auto, On or Off (but i can only comment on my own system of course).

 

set the FPS limiter to the same as your monitor Hz.

Since his VSync setting is set to 1/2 the refreshrate, there is no use in setting it to 60 (assuming that the refreshrate is 60Hz). Lowering to 30, either through nVidia's inspector or MaxFPS = 30 in the graphics.cfg files does the same thing.

Edit: see above: msalama's refreshrate seems to be 70 so 35 is a perfect value!

 

For those who experience LCD motionstutter by framerate drops below the monitors refreshrate (everybody does have it but not everybody sees it or cares about it), setting the VSync rate to Adaptive at 1/2 refreshrate does wonders. The only drawback is that you now have some motion stutter in the TGP or MAV MFD screens, like the refreshrate for the MFD's dropped to 1/4 instead of 1/2. But it's a minor drawback, at least for me.

 

Also, mslama's Max Pre-render setting is 8 where everybody says it should be set to 0 (you can't do that anymore since the 300 drivers saw the light of day, minimum is now 1).

I played around a lot with this setting in the past and really didn't see much of a difference between default (3) or min (now 1). But when i set it to anything higher then 4 i saw a difference but worse so i'm a bit amazed that msalama setting is 8!!

 

Same goes for Texture Filtering: Negative LOD Bias. His setting is still on "Clamp". Now on every driver below 300 i had to set this to "Clamp" too because when i had it set to default "Allow" (below 300 drivers the default was "Allow", now it's the other way around), the images looked not that good. But since the 300 release i have to set this to "Allow" in order to get the best image quality.

Edited November 23, 2012 by Lange_666

[msalama]

so i'm a bit amazed that msalama setting is 8!!

 

I see no input lag with this set to 8, so THEORETICALLY the card then renders as many as 8 frames ahead whenever it can. TBH I'm _not_ sure if it actually works, but at least it doesn't seem to harm anything so I've just decided to max it out.

 

His setting is still on "Clamp".

WHOOPS!!!

 

Thanks for pointing this out, just an oversight from my part and should of course be on "allow". Thanks again :D

Edited November 23, 2012 by msalama

[msalama]

Hmmm... negative bias set to "allow" doesn't seem to do anything qualitywise. Could've something to do with my in-game performance tweaks or something, I don't know? But I'll just let it stay on allow for now regardless...

[Lange_666]

I just went ingame after playing around a bit with either "Clamp" or "Allow" and i don't see difference anymore between the two. Maybe something has changed between early 300 versions and 306.97 which i have installed right now.

 

BTW: there are new beta's out 310.61

[msalama]

BTW: there are new beta's out 310.61

 

Not much difference between this and the previous release it seems, just some game-specific tweaks if I understood correctly. I, OTOH, reinstalled the 310.54 betas yesterday and they now seem to behave pretty well with the settings mentioned above (f/s capped at 35, etc). TBC...

[Lange_666]

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:

 

Solved: Driver issue, so not a hardware problem. Currently at a new install of 306.97 WHQL since thursday evening, not a single error anymore, no more freezes either.

[msalama]

Driver issue, so not a hardware problem.

 

So what was the driver causing it specifically?

[Lange_666]

At your service... just scroll up a bit or click below which warps you right at it...

 

http://forums.eagle.ru/showpost.php?p=1611266&postcount=21

 

 

 

Edit: thread jumped to another page so instead of scrolling up... it's better to use the provided links...

Edited November 26, 2012 by Lange_666

[D4n]

Anybody knows a solution for my problem here?

http://forums.eagle.ru/showthread.php?t=98373