Fulqrum Publishing Home   |   Register   |   Today Posts   |   Members   |   UserCP   |   Calendar   |   Search   |   FAQ

Go Back   Official Fulqrum Publishing forum > Fulqrum Publishing > IL-2 Sturmovik: Cliffs of Dover

IL-2 Sturmovik: Cliffs of Dover Latest instalment in the acclaimed IL-2 Sturmovik series from award-winning developer Maddox Games.

Reply
 
Thread Tools Display Modes
  #1  
Old 07-02-2012, 01:28 PM
Ataros Ataros is offline
Approved Member
 
Join Date: Jun 2010
Location: USSR
Posts: 2,439
Default

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.

Last edited by Ataros; 07-02-2012 at 01:34 PM.
Reply With Quote
  #2  
Old 07-02-2012, 09:18 PM
TonyD TonyD is offline
Approved Member
 
Join Date: Apr 2011
Location: Jozi, SA
Posts: 263
Default

Quote:
Originally Posted by Ataros View Post
Vsynk may be a problem. It cuts FPS from 60 to 30 to 15. ...
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.
__________________
I'd rather be flying ...

Gigabyte 990FXA-UD5 | AMD FX-8350 | MSI HD7970 TFOC-BE | 8GB Corsair DDR-III 1866 | Win8.1 Pro 64-bit
Reply With Quote
  #3  
Old 07-02-2012, 09:30 PM
Al Capwn Al Capwn is offline
Approved Member
 
Join Date: Sep 2011
Location: MA, USA
Posts: 67
Default

Quote:
Originally Posted by TonyD View Post
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
Reply With Quote
  #4  
Old 07-02-2012, 10:19 PM
louisv's Avatar
louisv louisv is offline
Approved Member
 
Join Date: Jan 2010
Location: Montreal
Posts: 287
Default

From this thread, it is obvious that the NVidia series 5 (590, 580 and one 570) is currently a problem with CoD.
__________________
EVGA X58 FTW3 motherboard
Intel 980X CPU, not OC'd yet, 3.46 Mhz
Crucial Tracer memory 8-8-8-24 12GB
Crucial M4 256GB SSD, WD Raptor 600 GB hard disk
EVGA GTX580 graphics card
HP ZR24W Monitor 1900 X 1200 24"
Thrustmaster Warthog joystick
Saitek Combat rudder pedals
TrackIr 5
Reply With Quote
  #5  
Old 07-03-2012, 01:52 PM
badfinger badfinger is offline
Approved Member
 
Join Date: Jun 2010
Location: League City, TX
Posts: 322
Default

Quote:
Originally Posted by louisv View Post
From this thread, it is obvious that the NVidia series 5 (590, 580 and one 570) is currently a problem with CoD.
Not so obvious to some. I'm not a computer expert, nor an expert on WWII aircraft performance. But, my system is running fine, my FPS is up, I see improvements with each patch, and am happily flying around "shooting down what's up and blowing up what's down."

I am also not bothered about things like fuzzy horizons, a wrong font, or the sunset being the wrong shade of red.

See specs below.

binky9
__________________
Win10 64 bit
1T Hard Drive
ASUS P67 motherboard
Intel i7 3.4ghz Processor
GTX 780 Graphics Card OC
24GB Ram
Track IR5
50" LG HDMI LED 1920x1080 60hrz
MS FFB2 Stick
CH Pedals
Saitek Throttle/Prop/Mixture and Trim wheel
Thrustmaster MFDs

League City, TX
Reply With Quote
  #6  
Old 07-04-2012, 04:22 AM
mikec5airguard mikec5airguard is offline
Registered Member
 
Join Date: Aug 2010
Posts: 6
Default

I dunno if its limited to nvidia, I think I have an OK sytem, and the framerate is all over the place, from 110 to 20's in black death track.
Reply With Quote
  #7  
Old 07-03-2012, 01:23 PM
TonyD TonyD is offline
Approved Member
 
Join Date: Apr 2011
Location: Jozi, SA
Posts: 263
Default

Quote:
Originally Posted by Al Capwn View Post
...

I hope this sheds some light on the mysteries of v-sync
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.
__________________
I'd rather be flying ...

Gigabyte 990FXA-UD5 | AMD FX-8350 | MSI HD7970 TFOC-BE | 8GB Corsair DDR-III 1866 | Win8.1 Pro 64-bit
Reply With Quote
Reply


Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT. The time now is 03:18 PM.


Powered by vBulletin® Version 3.8.4
Copyright ©2000 - 2025, Jelsoft Enterprises Ltd.
Copyright © 2007 Fulqrum Publishing. All rights reserved.