![]() |
|
Performance threads All discussions about CoD performnce |
![]() |
|
Thread Tools | Display Modes |
|
#1
|
||||
|
||||
![]()
In order for Vsync to keep everything synchronized, when it doesn't get 60 fps from the computer, it falls off to 30 fps because otherwise there would be tearing. Think about it, you can't have say 45 fps on a 60 fps monitor, there would be partial frames along the way...60/30=2 and 60/45=4/3=1.33
If the computer cannot get 30 fps, say it gets 29, then vsync will make it fall to 15 fps because 60/15=4, a whole number for whole frames. So use it knowingly. Louisv
__________________
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 |
#2
|
|||
|
|||
![]()
This is only true for vsync with double buffering. Triple Buffering solves that, and is a driver default for nvidia since many years.
There is a rather old but still good article about vsync, double and triple buffering on the german site 3dcenter |
#3
|
|||
|
|||
![]() Quote:
I have been using vsync + tripplebuffer in a few games for years and I've never seen my fps counter lock in at anything lower than 30 (i.e. I see 20, 22, 27 [etc...] fps in a few games that have vsync + tripplebuffer) Here is an extreme example (vsync on) ![]() As you can see my computer can't quite make 30fps, but it isn't dropping down to 15... |
![]() |
|
|