Seriously, Who ever decided that it was a good idea to force Vsync should be flayed alive.
I suffer more performance problems from having it enabled. I cannot stop it with my user config, nor my attributes.xml. I'd love to see a reason for having this be the case.
Has anyone found a way to prevent it from limiting our frames?


Vsync... Why won't it go away
Started by Tholis Verrin, Nov 01 2012 05:07 PM
5 replies to this topic
#1
Posted 01 November 2012 - 05:07 PM
#2
Posted 01 November 2012 - 07:00 PM
Didn't now it was always forced on. I deselected it in my options. So your saying the option for enable/disable vsync doesn't work?
#3
Posted 01 November 2012 - 07:38 PM
Showing my graphics noobness a bit here, but what exactly does vsync do/why is it unfavorable?
#4
Posted 01 November 2012 - 08:59 PM
Vsync locks your frames to a certain number, 30 40 60 etc. It's to prevent image tearing, but I don't enjoy having my frames locked to a low number, when my pc can perform better.
#5
Posted 19 December 2012 - 12:01 PM
ISP, You are correct. During Closed I was running around 100, with dips at worst into the 80s. Now I stuck at 60, with dips into the teens. I've got an AMD 7970, and I hate looking my card usage and and seeing nearly half of it idle when my frames drop.. It pains me. I can click vsync off in the options but it doesn't seem to matter.
#6
Posted 19 December 2012 - 12:15 PM
Tholis Verrin, on 19 December 2012 - 12:01 PM, said:
ISP, You are correct. During Closed I was running around 100, with dips at worst into the 80s. Now I stuck at 60, with dips into the teens. I've got an AMD 7970, and I hate looking my card usage and and seeing nearly half of it idle when my frames drop.. It pains me. I can click vsync off in the options but it doesn't seem to matter.
There is no way vsync can cause you to dip into the teens if your previous low was 80fps. That's not how it works.
There's no way I would run with vsync off if I had the performance you claim to have. Tearing = ***.
All that said I don't see why its locked on. You have it turned off in your driver configuration? What commands are you trying in cfg? And at what point did this happen? Just this last patch? Because I'm almost positive I had it off a few weeks ago for testing.
Good luck.
1 user(s) are reading this topic
0 members, 1 guests, 0 anonymous users