Page MenuHomeFeedback Tracker

vsync fails to cap fps at monitor refresh rate.
Closed, ResolvedPublic


While playing around with the settings I found that the vsync doesn't cap at my monitor's refresh rate (120 fps), but at a lower frame rate (almost always 110 fps, but I had it cap at 70 once).


Legacy ID
Unable To Duplicate
Steps To Reproduce

enable vsync

Additional Information

enabling and disabling vsync gets me 110 and ~160 respectively (draw distance low).

i7 3770k

GTX 680 (EVGA)

16 GB (4x4 quad) DDR3

Mother Board
P9x79 LE

Acer GD235HZ @ 120hz

Event Timeline

Dman010 edited Steps To Reproduce. (Show Details)Mar 11 2013, 11:16 PM
Dman010 edited Additional Information. (Show Details)
Dman010 set Category to Performance.
Dman010 set Reproducibility to Always.
Dman010 set Severity to Minor.
Dman010 set Resolution to Unable To Duplicate.
Dman010 set Legacy ID to 146750284.May 7 2016, 12:21 PM

VSync in ArmA was never a good idea to use. Unless you use TrackIR or freelook very often (like literally ALL THE TIME), it's not a big deal. Just my two cents. :)

pystub added a subscriber: pystub.May 7 2016, 12:21 PM

Make sure your drivers are not forcing triple buffering on. Triple buffering allows frame-rate to be not at refresh rate divided by integers.

The 0000113:0000160 is suppose to be "~" + "160" in case anyone is confused by the random link.

Also pystub I checked my nvidia settings and triple buffering is set to off so its not that, but its not really a big deal I normally don't play with vsync on anyways I just put it up because I noticed the bug, and any bug is a bug that need fixing (priority dictates the order, of course).

Unable to reproduce in the latest dev build. Closing, since this ticket is very old and has not recieved any attention in a long time.

If the issue is still reproducable for you, please create a new ticket.