Please remember that any mention of competitors, hinting at competitors or offering to provide details of competitors will result in an account suspension. The full rules can be found under the 'Terms and Rules' link in the bottom right corner of your screen. Just don't mention competitors in any way, shape or form and you'll be OK.
Ok answer this then
Why dont you notice input lag on desktop "web browsing etc"
Windows force vsync hence you never see screen tear on the browser or desktop etc.
In games, input lag can be the difference between dying and not dying.
Noob.![]()
630 SPM in BF3... who's the noob? Come and get me big boy.
Need to get you off those softcore servers with your doritos, crosshairs and auto heal.![]()
All yours are time based
And hardcore is just full of people who either generally:
a) can't aim
b) can't move
c) have some form of disease which makes them play like err.. can't really say on this forum.
What tool is that MAtt? Got me curious now![]()
Any links to prove this? not saying you wrong, just proof is whats needed.
On BF3 if you disable the ingame TB the game does feel choppy vs it being switched on.
http://www.anandtech.com/show/2794
'Render Ahead' is used in Direct X. By default its two buffers. Creating a third buffer = 'triple buffering'. As I said earlier Direct X displays all the rendered frames in the queue hence the increased in input lag.
OpenGL triple buffering has the same lag as double buffering since the third buffer can be dropped. This is not possible with Direct X.
Nvidia control panel has option for triple buffering which only affects OpenGL due to the reason above. The maximum pre rendered frame option is basically 'Render Ahead' which affects direct X. Again for the reason above.