Most of us are familiar with the issue of framerate being cut in half to 30 when your framerate goes under 60 with vsync enabled. The solution to that would be triple buffering, which basically makes it so the framerate only goes as low as it would go when it drops without vsync. (How it works is a lot more complicated than that but I'd like to keep this post short and succinct.)
However, I've noticed that on my PC, even when the framerate goes under 60 without triple buffering and with vsync this never happens. I've ensured that none of the programs I run are forcing triple buffering, and that the control panel isn't doing it either (the CP's option is only for OpenGL anyway.) Now, some games, like the Battlefield games, enable triple buffering by default, but not all games do and none of the many, many games I own display the behavior of dropping the framerate to 30 when the framerate goes under 60 with vsync on.
I'd just really like to know what is going on here.
However, I've noticed that on my PC, even when the framerate goes under 60 without triple buffering and with vsync this never happens. I've ensured that none of the programs I run are forcing triple buffering, and that the control panel isn't doing it either (the CP's option is only for OpenGL anyway.) Now, some games, like the Battlefield games, enable triple buffering by default, but not all games do and none of the many, many games I own display the behavior of dropping the framerate to 30 when the framerate goes under 60 with vsync on.
I'd just really like to know what is going on here.
Facebook
Twitter
Instagram