>>712372775
I've never understood this. With vsync off, if you cap your framerate to your monitor refresh rate and it doesn't go above, shouldn't tearing never happen?
>>712370796
because I LOATHE input lag and I'm more than willing to deal with the tearing as long as the game has good response
this mostly applies to FPS I guess
>>712370589 (OP) >>712370796
paint huffer with a good rig here
tell me your general settings to have on what and whats bullshit, preferably with what priority as well
usually I try to keep a minimum of 80 FPS on modern games
>>712370589 (OP)
I don’t know what any of these PC settings from the last 15 years are or what they do except for motion blur and I hate that crap so I just turn off everything and set the FPS high.
>>712374078
To clarify: assuming you have an Nvidia graphics card, your FreeSync monitor is "G-Sync compatible" since G-Sync and FreeSync are just brand names for VRR (variable refresh rates) capability.
>>712371950 >rubber worn>>712371950
off down to the plastic on the left analog >>712375117
looks like the 360 version, retard. that shit ran at like 25 fps
>>712374936
vsync just introduces input lag and freesync/gsync/async makes it redundant, you need your monitor and gpu to support both (IE: GPU supporting Gsync and monitor supporting it as well)
I personally go with 180fps but any variable of 60 should be fine
