I don't think/hope that the Lod problem was intentional I only started seeing the Los circle after I was flying in England in France it was normal... :( hopefully they release a quickfix for the Lod and hurri this week.

I just did a complete re-install and copied back in my key bindings only and I clawed back some of the lost fps. Now a steady 45 FPS with all graphics full.

But nothing like the 80-140 I uesd to get.

This is quite an interesting observation. Maybe there is something in that?

I feel the performance has improved since I bought CloD not so long ago.
I'm running with ATI also.
It plays smoother now than ever. The frames could be better still I'm sure, but it's much more enjoyable than when I first fired it up.

Vsynk may be a problem. It cuts FPS from 60 to 30 to 15. Need to use a 3rd party utility to enable triple buffering if vsync is badly needed (drivers CP handles triple buffering in OGL only). In release version there was no true fullscreen and vsync could cause less problems.

Patches cause slow downs because:
- files get more and more fragmented when patching as HDD gets filled in month by month and internal Steam defrag is not good enough.
- new versions may not woork well with old conf.ini and other ini files. Need to delete Documents/1C-Softclub folder (backup control and info-window settings first)
- new patch files need to be cached by windows again and this takes time
- if you did not add both Steam and Documents/1C folders to 2-3 exclusion lists of your antivirus (real-time file monitor, network monitor, etc.) , it will scan new patch files when loading them
- new graphics drivers introduce new image enhancements (like new AA methods) which may be switched on by default in drivers.
- AA was improved in game a bit and may conflict with drivers AA settings if used (need to be set to application controlled).
- etc., etc. Please see a link #2 in my sig for more ideas of what can go wrong in a system.

Try running in pseudo mode, disable all background applications like TS overlay or Skype, upgrade motherboard drivers, check if PSU is clean and not getting overheated, check out if GPU fan is clean of dust, check if clocks and temps are the same as some months ago, etc.

fairly good system...are you serious:confused:
your system rocks buddy

Concur about HT. Switch it off in BIOS, it's just a great big overhead in general (for me anyway).

I'm getting similar results. Performance on this build is smoother. Maybe I'm noticing the framerate drop more over cities, due to the game running smoother. Before, everything was j-j-jerk-o-vision at low alts and difficult to pin down what was actually going on.

Up close to planes is much smoother. Particle effects cause less slowdown (but still noticeable). Trees seem toxic on this version though.

i7 @3.8Ghz
GTX 680 4GB

I have never come across this in all my years of gaming and multiple Ati gfx cards – is this something peculiar to nVidia? Using VSYNC in every game I have limits the upper frame rate to the screen’s refresh rate, but does absolutely nothing to lower frame rates. I have always used it to limit frame rates this way and avoid ‘tearing’, and still do. It works this way for me in CloD currently.

The way vsync functions causes the loss in framerate (triple buffering is a nice technique to help solve some of the issues). However this loss in framerate only occurs when your framerate drops below your refresh rate. nVidia recently has released their own iteration called 'adaptive v-sync' that aims to correct the issue with vsync cutting framerates down when under your refresh rate, and to not have input delay when at/over your refresh rate.

For a nice explanation of how v-sync actually works and why there is a performance decrease I would recommend to take a look at this nice little blurb from the Hardocp forums,

http://hardforum.com/showthread.php?t=928593

I hope this sheds some light on the mysteries of v-sync :grin:

From this thread, it is obvious that the NVidia series 5 (590, 580 and one 570) is currently a problem with CoD.

Thanks for that, but I do not have a problem understanding the theory, merely the affect. As I said, I have never seen frame rates being limited to dividers of the refresh rate with VSYNC enabled, but this may be due to the games in which I use it (some have apparently included a form of adaptive VSYNC for some time). In CloD it appears to function as a frame limiter, loosely enforcing an upper limit but allowing normal fluctuation at lower rates.

A new race simulator (rFactor 2) has a choice of 4 different methods of implementing the option, which should suit most tastes, but from what I’ve seen this is somewhat unusual. I have no idea which method CloD may use, but it does eliminate the tearing that becomes apparent when turning my head around rapidly in the cockpit without influencing frame rates that are less than my monitor’s refresh rate. A log of frame rates using MSI AfterBurner, both with and without VSYNC enabled, only shows a difference in rates above the imposed maximum value.