Why must that be so?CrapSandwich said:Well it's a safe assumption they're shooting for 30 fps and would cap it there. So if there's tearing, it must be because the fps is dropping below 30.
I just tested Half-Life 2 on my PC with vertical sync disabled and used "FPS_MAX 30" to prevent the framerate from going beyond 30 fps. The framerate was clocking in at 30 fps on the dot, yet there was tearing all over the place. If what you are saying were true, this would not be the case, would it? We've seen this plenty of times in the past on consoles. It is obviously possible to prevent a framerate from exceeding a certain point while tearing continues to occur.
/slaps headthats simply not true, ive been playing quake 3 @ 125fps for more years than i can remember and the game has zero tearing, absolutely none
When dealing with the PC, you actually have OPTIONS! That's right, you can enable or disable vertical sync! If you don't see tearing, chances are good that v-sync is enabled (though that would require your monitor to display at 125hz).
With Vista SP1, a bug was introduced that prevented nVidia control panel from enabling system wide v-sync. Many games lack the ability to enable this from within the software, however, so tearing occured. Halo 2 on the PC, for instance, was running at an insanely high framerate but also suffered from hardcore tearing.
Anyways, if you people want to think I'm just making shit up to support the PS3, do as you please.