I did some research on the topic of Direct3D v-sync. It's entirely conceivable that forcing v-sync through nvidia's control panel for OpenGL games causes the issue the poster was seeing. Remember that this game, the game I was helping him troubleshoot, uses an OpenGL renderer.

It's worth mentioning again that the v-sync option selectable in the game itself is Adaptive. The result is often an inconsistent, jarring experience as it caps you to 30, then 60, then 30 again and again. Standard v-sync is what you were forcing when you set v-sync on in the nvidia control panel and you were probably just dropping a frame or two here and there. If you can't maintain 30, it will drop you to 20, then 10 and so on. Standard v-sync will cap you to 30fps in an instant if you cannot maintain 60fps. It will therefore cap you to 30fps.Īdaptive differs from standard v-sync.

The same as Adaptive, only the frame rate needed to maintain v-sync is 30 instead of 60. This should make a pretty consistent and responsive experience for most players.Īdaptive (halve refresh rate) is exactly what is sounds like. If/when you return to 60fps rate, sync is re-enabled. However the frame rate is free to change to any value (it may only drop to 59, for example) without consequence. As soon as your system cannot sustain precisely 60fps, sync is disabled and you will probably experience tearing of the image. Using this option, v-sync will only be enabled when you are maintaining 60fps. The behaviour you describe is what would be expected.

Max ppf 64