Blur Busters Forums

I didn't find an "Impact of Refresh Rate" entry in that article It's here: http://www.tftcentral.co.uk/reviews/content/lg_34uc79g.htm#refresh_freesync But I don't know if it's actually relevant. Thanks, ctrlf didn't yield anything. Well, it is pretty shitty and I wouldn't want to keep that monitor,...

I have that monitor as well. I can't use it at anything above 100hz right now and I have a feeling I know what you are talking about and why. http://www.tftcentral.co.uk/reviews/lg_34uc79g.htm Read the part @ "Impact of Refresh Rate" and it talks about an issue that apparently LG knows about and is...

I've always used fraps frametimes and the net graph's framerate variance indicator to check for inconsistencies, and again, it's pretty good now. Also do not get wander-tearing with fps_max 128 @ 128Hz. With an external limiter, net graph variance is always 0.1 for some reason. And maps take signifi...

what would be the benefits of using 128Hz instead of 120 or 144Hz? Well, 8Hz more compared to 120Hz, for one thing. :p I just used to play 1.6 at 100Hz/100fps and wanted to replicate that feeling in GO. 128fps is the absolute minimum competitively viable framerate in GO because that's the maximum a...

External caps add a little input latency. And I don't know when RealNC has last tested the in-game cap, but last I checked, Valve had severely improved the frametimes on it to now be not too far behind external means. I'd recommend using the in-game cap, and to cap at the highest rate above 128 that...

Without drivers installed (NVIDIA), my cursor gets noticably less laggy and noticably tears.

With something like f.lux enabled it's actually really easy to distinguish hardware cursor from "rendered" cursor - it's clear white usually and then gets tinted a warmer color temperature when clicking to drag a window. Btw.: There's no cursor tearing because the Windows DWM uses frame "pacing" or ...

I'd take it, but sending overseas sucks (they'd probably confiscate it thinking it's a bomb), I'm kind of jumpy as far as conclusions go (although I did obviously understand that both those results are within random variation range), and I'm also still kind of looking to eventually finish my own som...

200us slower than the measurements in the previous post, but that's more likely related to random inconsistencies every time i alt-tab/restart csgo. -no-browser: inconclusive. i have to restart steam and csgo each time. not sure if the variability is related to that or if -no-browser really makes i...

Simply saying that you shouldn't cap below 300fps would be a assumption based on the test results. That's you jumping to conclusions - I've never said that! I'll keep capping at 128. I'm just saying that, apparently, the lower caps introduce a latency behaviour that is worse than as is expected fro...