V-Sync or FPS limiter ??
- Thread starter LazyBug
- Start date
Too many different hardware setups to blindly trust others 
If you only hear that it causes input lag, but you can't witness any
(or notice any difference no matter if you turn it on or not) then you
can just ignore what others say.
I use DxTory to limit my FPS to 120, but just to save some resources
If you only hear that it causes input lag, but you can't witness any
(or notice any difference no matter if you turn it on or not) then you
can just ignore what others say.
I use DxTory to limit my FPS to 120, but just to save some resources
Ok then V sync it is since i dont feel any different with it ON or OFF ..Too many different hardware setups to blindly trust others
If you only hear that it causes input lag, but you can't witness any
(or notice any difference no matter if you turn it on or not) then you
can just ignore what others say.
I use DxTory to limit my FPS to 120, but just to save some resources
By the way if i not mistaken DxTory is a third party recording software right ?? No tear screen ?? Before this I myself tried using Bandicam (another third party recording software) to limit the fps but tear screen is there.
i lock mine ingame at 65. If i do 60 i get tearing. Anything above 62 i dont get tearing.
In fact i not sure what is input lag .. is it mean the game take too long time to response to what you do ??I personally can not use v-sync. If i do i get substantial input lag from my T500RS..... to the point of being undriveable. I use rivatuner to lock my fps at 101. Seems to work really well.
i5 4690k 8gb r9 280x 3gb
Thanks
Monitor frequency 90hz ??
Thats very interesting to know; I like to have a try to do the same
i would get some random stutters depending on whats going on on the track. Like on the starting grid. but it smooths out when traffic clears up. I would lower your settings untill you can maintain over 65. It dips a lot for me during replays though. But thats because I have smoke generation on. Its very demanding in replays.
Yea, I understand that the controller input relates to fps, so the lower the fps the lower the fidelity. I chose 90 because having read a long article on the subject it was suggested that multiples of 30/60 are ideal for a 60hz monitor. Plus my card can deliver a solid 90 fps at high gfx settings.
Seems like there's lots of misinformation on what's causing screen tearing.
"The artifact occurs when the video feed to the device isn't in sync with the display's refresh"
(Wikipedia)
So if your game runs at exactly 60 FPS and your monitor has a refresh rate of 60, then there never should be any tearing of any sorts.
I'd basically go out and blame the monitor if you get screen tearing while running at a solid 60 FPS.
"The artifact occurs when the video feed to the device isn't in sync with the display's refresh"
(Wikipedia)
So if your game runs at exactly 60 FPS and your monitor has a refresh rate of 60, then there never should be any tearing of any sorts.
I'd basically go out and blame the monitor if you get screen tearing while running at a solid 60 FPS.
Yeah in theory never should be any tearing if game runs exactly 60FPS with monitor which has refresh rate of 60 but in my case it do happen if i use in game or third party fps limiter software.
But no tearing at all with V sync ON .. not sure how to explain this
Im assuming its because even though it says 60 hz its really more like 59.xxx. So no matter what unless its synced it will never be the same exact number. Thats just an uneducated guess though
One of the reasons that screen tearing can happen at a reported 60fps is that each frame is not delivered in the same time as all the others, as an extreme example if 59 frames are delivered in 3/4 of a second and the 60th frame is delivered in the last 1/4 you still have 60fps but it is not smooth. FPS is cited often as the be all and end all of performance metrics but it is not the whole story by a long stretch.
http://www.extremetech.com/gaming/1...benchmarking-is-moving-past-frames-per-second
http://www.extremetech.com/gaming/1...benchmarking-is-moving-past-frames-per-second
Screen tearing hapens when a frame is delivered by the card before the previous frame has been completely rendered, this can happen at any fps, the way to avoid it is by having a consistent frame time that is synced to the monitor refresh rate. The point being that tearing can happen at any fps depending on a lot of other factors. Fps is a fine metric, but it is far from the definitive one.
D
Deleted member 197115
-
Deleted member 197115
As weird as it might sound - Both.
You need both, frame cap and VSync in AC.
My best setting after 1.2.4 update is 61 fps cap (monitor refresh +1) and Adaptive VSync in NVidia control panel. Tried all other possible combinations, VSync off, frame cap equal refresh rate, frame cap not equal 1, 1.2x, etc, see sticky. None produced better result than cap + Vsync.
You need both, frame cap and VSync in AC.
My best setting after 1.2.4 update is 61 fps cap (monitor refresh +1) and Adaptive VSync in NVidia control panel. Tried all other possible combinations, VSync off, frame cap equal refresh rate, frame cap not equal 1, 1.2x, etc, see sticky. None produced better result than cap + Vsync.
