theyarecomingforyou wrote on Oct 8, 2011, 21:48:
Creston wrote on Oct 8, 2011, 21:11:
When VSync is turned ON you should not see screen tearing. However, any time your frame rate drops below 60 frames per second you will get a sudden more severe drop to 30 frames per second. This is how VSync inherently works.
Errr, wot? If this is how Vsync inherently works, then why do I never have that problem in every other game except Just Cause 2? For that matter, why do I not have this problem in RAGE itself when I force Vsync through the CCC?
It is actually how it works. That's why many gamers are opposed to it and are willing to put up with a bit of screen tearing. The advantage of V-Sync is that it stops graphics cards over working themselves. If I disable V-Sync in some games, especially games like Crysis 2, then my graphics card heats up quite dramatically.
But... that's not how it works? I mean, at least not in practice? Since V-sync is broken in the patch (literally. It just won't turn on), I forced it back on through the CCC, and I never have a drop down to 30fps? I had those in Just Cause 2, and it was super irritating, because the game would just constantly lurch back and forth, basically.
I don't have that problem AT ALL in Rage, and I'm sure that I dip below 60fps from time to time. It just seems weird. Other than JC2, I've NEVER had a game lurch me back to 30fps if I dipped below 60 (or 75, whatever my refresh rate was.)
Anyway, the game is playable again for me, but I still haven't found what setting I switched that caused it. I think it may have been the OpenGL Triple Buffer in the CCC.
One thing I will say, the Large Texture Cache option has a noticeable effect on texture pop-in (as in: improves it.)
Creston