cs 1.6 has its limits. you can go beyond 100fps using developer "1", but it has severe effects on movement etc iirc

I sent you an iMsg zadrot

goldsource has a dev mode as you said. gives you "unlimited" (1000 to be exact) fps, but decreases your speed, so wont get any advantage from moving faster with more fps...basicly you are a lot slower during dev moe BUT you can shoot faster, and the recoil is smaller, so some people are toggling the command during rush and stealth. this is why its banned on cups.

tf2 and other source engine games used to have unlimited, then 500, but the orange engine only support 300 now.

cpma = no limit
df = 150fps limit
wsw = no limit

In Defrag, com_maxfps is clamped between 60 to 140.

I stand corrected

cpma is caped at 125 when playing online and uncapped offline. theres a tweeked cnq3 client that alows for uncaped fps online tho.

I stand corrected, again :D

this is why I should have an fps counter in my hud

They don't have a programmer who's skilled enough to change it after TTimo's departure. Sad that the one of the most popular and skill demanding fast FPS game is the most jerky(after cs1.6 which is more dead than QL. )
It was a common 'fix' among developers in different Q3-engine games(OSP, COD, ET, etc) to cap fps to stop the physics abuse at higher values like 333fps, etc. But even at QL release there wasn't a single reason to cap it since physics was made fps-independent for ages in most of those games.

what do you mean by jerky

125fps is just too low, It's not like it's only about the amount of frames, higher fps feels better and smoother on ANY refresh rate be that 60hz, 120hz or 144hz due to more accurate frame timing.

125fps means ~8ms between frames.
every generated frame waits a bit less ~8ms.

250fps benefits:
- reduced (or even removed completely) stuttering
- smaller display latency - usually there is a frame or two in the buffer.
- maybe more consistent flick shots etc.
- higher refresh rate on displays that can go beyond 125 fps.

mi from QL forum.

iirc fps-independent physics have been part of idtech3 since literally forever, ttimo had plenty of time :p

pmove_fixed was introduced in q3 point release 1.25 (afaik) which was released in october 2000. that's a good 12 years time at id and a whole lot of games and updates released, same for COD and ET etc. i have no idea why no one ever bothered to change the maxfps cap, though :d

That changes were made in modes that had teams of developers. Now we have no modes and developer team of 1,5 men (sponge & SyncError).

It's just changing maximum value of cvar. I guess question is not in programming skills.

QL has fps-independent physics, the upper cap has nothing to do with this.

i said about common practice in older games where it was not, didn't mention QL as it was known to have independent physics since start but somewhy featured an fps limit all the time

Could you expand to say what it is to so with?

Server will still only reg 40 snaps a second. So the gains will be minimal in my opinion. Besides, you can only see the amount of frames your display refreshes. So lets say FPS_MAX will be set to 250 and your monitor still refreshes @ 60,75, 120 or 144 fps, you would still be only able to see that amount. Those 240hz monitors are just copying each frame i.e: 2x120hz (instead of 1x240hz).

Whereas improving the snaps value would enhance the game in big quantities (less through rails, more accurate hitscan, less jerky/warpy playermodels, game feels smoother online, etc.

Snaps 40> 60/80/100/125 (the latter would be epic).

Yeah server still generates 40 snaps per second but changing it is much more harder for QL team than changing maximum value of com_maxfps. And it may increase cost for renting servers cause CPU calculation increased by increasing snaps.

So lets say FPS_MAX will be set to 250 and your monitor still refreshes @ 60,75, 120 or 144 fps, you would still be only able to see that amount.

250fps benefits:
- reduced (or even removed completely) stuttering
- smaller display latency - usually there is a frame or two in the buffer.
- maybe more consistent flick shots etc.
- higher refresh rate on displays that can go beyond 125 fps.
mi from QL forum.

Those 240hz monitors are just copying each frame i.e: 2x120hz (instead of 1x240hz).

Yes, they inputs and show only 120 unique frames but they arent just copying each frame. Take a look at
http://gaming.eizo.com/wp-content/uploads/fil...epaper.pdf
There is already LCD and CRT that showing more than 120fps and will be much more in near future.

Doubt if increasing the FPS would decrease the stuttering. Would probably make it a bit less noticeable.

But I guess we can all agree that snaps are more important than FPS at the moment. By the way, that monitor looks interesting. But basically it's a 120hz monitor with implemented lightboost. Would be a great product if it doesn't produce inputlag like the current 120hz + softwarebased lightboost mode, got a review?

If you doubt, you can test it.
devmap a map
timedemo 1
use AfterBurner or other software with OSD to show real framerate.

atm increasing com_maxfps is more quickly and easy to do. Changing snaps need more tests and restart all the game servers which will cause stop of service.... And if rumors ( http://esreality.com/post/2471069/re-syncerror-talks ) about new FPS product from ID is true then we will never get snaps update in QL.

At some review ( http://www.pcgameshardware.de/LCD-Hardware-15...t-1094860/ ) names 15ms of input lag. They compared this 1920x1080 LCD at 120hz with CRT....Where they found CRT that can handle 120hz at 1920x1080? Better to wait more adequate tests of input lag and other benchmarks of two new displays(from benq and eizo) at http://www.blurbusters.com/ Each of this monitor has unique motion blur method (Lightboost like).

Ping has some jitter, let's say +-10ms changing all the time. The problem with very high snaps could be that many packets would be received out of order. Increasing snaps is definitely something to test if id decides to rework the network code (together with fixing warpers and other changes). Increasing the fps cap on the other hand is simple and instant improvement for most players.

But that problem would be non-existant if the server itself has proper hardware + bandwidth, right?

No. Main problem is player connection. When ppl whine about big ping and packetloss to server it's mainly their connections problems (bad routing to game server) coz servers placed at good hosters i guess. For example imho most populated QL game servers in germany are hosted at decent place ( https://www.facebook.com/i3d.net/info ).

that's in .nl and the i3d servers have been 'less than decent' in the last 2 years :C

Interactive 3D (i3D.net) is a premier world wide game server provider (GSP/Game hosting). We are an independent provider of dedicated servers and professional colocation services. Our 3500 m2 datacenter and office is in Rotterdam and over 8,000 servers are placed in Amsterdam, Rotterdam, Frankfurt, Paris, London, Tokyo (Japan) and Sydney (Australia). We operate a 225 gigabit network spanning the globe from Washington DC to London, Amsterdam, Rotterdam, Paris, Frankfurt, Stockholm, Warsaw, Milan, Sydney and Tokyo.

ql .de servers are located at Frankfurt i3d.net

i know, i ping 45+ to those eventhough i live in frankfurt. the cause is faulty router at i3d they manage to ignore for 2+ years. yay, quality hosting.

Or you failed to contact or i'm too lucky
http://www.esreality.com/?a=post&id=2369819#pid2370189

that indeed looks good, i didn't get a response from i3d. interestingly though my ping just dropped to 16ms...ahem :D

if i run into problems again, i'll mail noc@i3d.net and see what happens.

that's wrong, with proper couter mesures higher snap = better experience.

On all Source Engine games and others we have some 100-128 tickrate servers since decade. It is definitly much precise.

Not to mention that we all have at the very least adsl here. A lot of us already even have optic fiber symetric 100/100MB or even much more 500/200 200/200 etc.

higher snaps was tested in vq3/cpm and it's benefits aren't as noticeable as manipulating with xerp and netcode overall whereas it made warpers warp even more due to packet jitter so there's more connection whine in future if that's changed ;(
Not even mentioning that raising snaps would double their hosting hosts which was the main reason it was only slightly raised to 40 from 30 a couple years ago. Since then they hardcoded everything like trash around 40 value so that for example the 'new' staircase code works like shit if you raise sv_fps to 125 in local game, etc. They might fix that and make sv_fps an option when creating a server but personally I'm not a fan of such diversity not to only get used to different location pings but also to sv_fps, fuck that.

as for com_maxfps as I said before it's not only an advantage for those with 144hz/CRT monitors lol. You should try any game(CPM/warsow/etc) at 125/250fps and you'll notice a huge difference, it's much smoother, got less tearing and the latency is noticeably reduced

this, so much. we already tested higher sv_fps (snaps) values and it produced nothing close to what everyone wished for.

Just imagine playing @ 120hz, 125fps, 125 snaps, 125 cmdrate.

Fps is like the "reality-meter" if the reality is too fast it will be like on drugs, you burn out too soon. Too slow and you will be chilled out, like cpl 2000 . Hey look lost world!

Makaveli is such a noob here lol.
;-)

Fatality's movements/ timing / aim are ok ...
Not so smart but that was enough to win such opponents.

Shit there's loads I forgot about that map, the only thing I remember is the tele exit.

Has been requested many times since QL Beta. That and increased server snaps. iirc past 300fps QL has some bugs.

i dont want an even more lg-heavy game.

keep it as it is, 125 <3

if the lg becomes a problem just nerf it...?

its a problem since vq3cpm and noone touched it

No one touched it?

First there was damage reduction (from 8 per cell), then there was distance falloff for damage, then hit boxes were replaced with hit cylinders that are smaller on average.

It got to the point where it was necessary to enlarge the cylinders a bit because it simply stopped being fun to play the game when nothing hit.


Anyways, this is all off-topic in this thread. If you think gaining 2 ms is going to make LG stronger, you have really wrong idea about why other players are stronger than you. Watch out, errors in judgment like that can stop your own development.


So to summarize: 250 FPS won't give anyone competitive advantage. But it does make the game feel a bit smoother. It's only about the comfort of players and ability to use your hardware. Why not provide that?

If only everyone would think that way, Jesus <3.

don't debate quake stuff with hitsu. he just writes random shit.

"vq3cpm" might very well be his finest work.

i'm unaware of this but it definitely sounds like shitsu.

You forgot on your list all Source Engine games has 300 FPS cap. CS, L4D etc.

it's just a default cap which you may remove completely with /fps_max 0 or set a higher value

not in L4D2

all of these requests and none of you could even get 2+ frags on me in duel....


***NEXT THREAD PLZ K THX BYE***

iirc ql physics is not truly fps independent but rather some workaround.

please vote at QL Forum suggestion thread: http://www.quakelive.com/forum/showthread.php?34236

rotfl, u guys have 120hz monitors and still complaining? try 75hz and not stable 125fps :D

%random_facepalm_image%

why is warsow with 125fps and 75hz smooth as fuck and ql isnt?

coz made by community

that sorta kinda makes sense.

This would be nice addition to quakelive. However there is not that much of a difference because of the blurring you get from LCD`s .
And lightboost only works up to 120hz , and that is said to be causing some delay.

When i try out the different fps settings i qw , 70/120/125/144/250/288/400 etc , from 120~ fps and on i basically only see smooth w.blurring to smooth w.blurring

Needs wall of text from DCR explaning why this is good

yeah hurry up on this

125fps does not feel that smooth compared to 144fps on my vg248qe


there is a difference, it's not hard to tell.

-__-

Please tell me that's some kind of weird sarcasm.

Thank you all for voting and discussing.

I'll raise the cap in a future update to better support high hz monitors. The increase really isn't that necessary, but I'm not against increasing the max fps cap.

SyncError

http://www.quakelive.com/forum/showthread.php...post276873

And now that I've spent a week debating the tumultuous fps cap, I can return to dedicating all of my time towards deciding what twisted hoops those poor accursed cheaters have to jump through to redeem themselves within our beloved community. When will I find time to work on something as meaningful as this...

...maybe never.

Make them pay a $1000 redemption fee!

Gee, way to give them a roadmap. Now everyone's going to be cheating. :(

How about a fucking simple official list of cheaters/abusers on QL forums? There's still no reply from you on several IMPORTANT ban cases like reyka for example(who's a Team Russia member), maza only got a reply after raging for several days aswell, whereas you drop comments like this...

250fps so there isn't tearing, pretty please?

Sure thing.

Thanks a lot! :D

Taking requests are we? OK. I want the ability to change my playermodel to Johnny Bravo, also.

Pretty please? -=8]

^^ TPD

Tourism Product Development?

CoD4 Promod had 250 fps limit
Pure CoD probably no limit but maybe some servers had some cvars for it. Probably best for "exploiting" cod was 333 fps, not sure.

CoD partially is using quake engine.


found this:
"63 FPS or lesser- jump only to 39.5 units max (exception are 52 and 55 FPS. Those values can used like analog of 71 FPS)
71 FPS. Character jump to 40 units stably. 40.5 units is impossible for this value. Same results for 76 FPS
83 FPS, 90 FPS and 100 FPS are bad again - 39.5 units max
111 FPS - 40 and 40.5 units are overcame
125 FPS - 41 height unit overcame
142, 166 and 200 FPS - strange fall again. Character overcame 39.5 units max
250 FPS - 42 units line overcame
333 FPS - same is for cod 2, with 333 fps you can jump at 46 units."

333fps also heard about - more silent movement, faster shooting, less fall damage

fast google http://www.codjumper.com/forums/viewtopic.php?f=39&t=9243

"Enemy Territory Tuning Tips & Tricks
/com_maxfps X
Because of a bug in the QuakeIII engine its possible to lock your FPS at a certain number.
Example: /com_maxfps 43 - /com_maxfps 76 - /com_maxfps 125 - /com_maxfps 333"

Yep but doesn't matter anymore in QL. Last I checked maxpackets is still tied to fps though, but 250 is a multiple of 125 so it's all good!

And yes it does feel a lot better than 125, even on a crappy 60hz LCD and a server with lowish snaps, (just try it yourself on CPMA, Quakeworld or even vanilla Q3)

I agree that vQ3, cpma and quakeworld feels much better and smooth. But even with 125 fps it feels better :P

haha true, not really sure what's up with QL sometimes.

Can you both (kalston and H1ghlander) re-explain your last 3 posts please?

If you can't be arsed it's fine :D.

wat? :D

I think I won't even be able to explain what I don't understand xD, nevermind, but thanks.

I can explain, but I don't know what :D

First what does maxpacket do exactly? I see it sometimes but I still don't know how it works? :/

http://www.regurge.at/ql/Lorfa/
ctrl+f "maxpackets"

"Description:
Controls how many updates you send to the server.
Recommendation:
I recommend setting this to 125. Using the default of 63 feels laggy.
With 125 fps at maxpackets 63 one packets will be sent every other frame. With 125 fps and maxpackets 125, one packet will be sent every frame.
Supposedly like com_maxfps, it is limited to integer values of 1000/x. So for example: 125, 111 (close enough), 100, 50, 40. "

:P

It should be noted that the default isn't 63 anymore but 125.

Yes I need to update that, my apologies.

Updated.

Because of a bug in the QuakeIII engine its possible to lock your FPS at a certain number.
Example: /com_maxfps 43 - /com_maxfps 76 - /com_maxfps 125 - /com_maxfps 333"

... a bug?

not my words, only copy&paste :P

But guys. What if you can't get 250 fps due to shitty hardware (or not shity even) and your framerate varies between 100- 250 all the time. Doesn't this make you harder to hit for the opponent?

A lot of people complain about not reaching 125 fps on alot of maps.

I got fix for it.

to buy something better than wooden pc.

there is no need to have high end pc for Quake, really, it has low requirements.

c'mon bro... a lot of people don't have the ability to buy a better PC. And besides, alot of people with a decent (not wooden) PC complain about drops all the time. For instance on 'Asylum' or 'Toxicity'.

Trying to get a serious reply here.

Hey Alborz, I don't know for everyone, but this is my case, I have a high end PC, and I don't know why Asylum for instance WILL NEVER run perfectly @125fps :/.

I tried on 3 different PC.

On my best pc with my gaming cfg (meaning all details removed) I get 125 fps all the time, BUT something weird happens sometimes, when I look at these spots:

http://i.imgur.com/VmcHQrx.jpg
http://i.imgur.com/RwejU4G.jpg
http://i.imgur.com/3vCBdSM.jpg

The framerate doesn't go down, but I can see that something is "slowing down", it's hard to explain, maybe people who have similar problems will be able to tell what happen.

With the 2 other PCs, the framerate will go down no matter what, 120-125, if I look at these spots.

And the funny thing is that all graphics are low, and two of these PCs can run BF3 or BF4 on high/ultra with +50fps (AA 2x no Vsync).

Hopefully this happens only on Asylum for me. I already asked many people, apparently there is nothing they can do, unless someone fixes the map itself...

Sad.

there are some default settings that can make quakelive slower\laggy\etc. for example HPET OFF, vsync OFF, threaded optimization OFF, ati powerplay or nvidia powermizer OFF....

What is HPET please?
And where do I find the threaded optimization option D: ??

(I have an ATI card, I'll try to look in the drivers and Ati tray tools)

By the way I just tried 250 fps on asylum and it's so smoooooth I can't wait for the update! I don't understand why 125 fps feels so "slow" :/

Edit: ok HPET is Hyper threading, now I gotta look later.

HPET is just a high precision timer found in newer PCs. I'd also like to know why and how does it trouble QL.

u have bad google skills HPET is not a Hyper Threading....
http://en.wikipedia.org/wiki/HPET

Ok thanks, but as anvi said...

How can this affect QL?

disabling HPET will give less internal delay. it's not so big problem for QL but on some PCs HPET can cause problems. u r free to google it.
for example some info about HPET and quakelive: http://www.quakelive.com/forum/showthread.php...ters/page4

HPET on or off should have no impact (although new OSes are supposed to make good use of it) but I have seen some bad implementations (IIRC on Asus motherboards mostly) that caused various issues.

Thanks for sharing this mate. Yeah, stuff like this is what I mean. You can try to see if the solution the guys here under wrote, works for you. Good luck man.

framerate varies between 100- 250 all the time. Doesn't this make you harder to hit for the opponent?

I think same (when com_maxfps 125)

Yes but if you increase cap from 125 to 250 you will put alot more players in the equation than you would've had with 125cap. Ain't I right?

no, they could still use maxfps 125!? by raising a cap you are not forcing anyone to use the max value.

Yeah. But the thing is, most people won't cap @ 125fps, even if they should. That's what I'm implying.

I'm trying to imply here, that people would use this feature to exploit the inconsistent nature of the game. Read the rest of my posts.

Then the same should be possible to achieve now by intentionally underclocking CPU/GPU or by using older hardware. How is this situtation different from having a 250 fps maximum?

Not sure if serious...

:')

sadly enough, i did read the rest of your posts. every single one as incoherent as this one.

i don't understand what you are implying. afaik (and please go along and prove me wrong) there is no way to exploit a maxfps raise.

there are also existent ways, far easier to achive and impossible to prevent, to exploit the game in a very similar way, eg. make you lag and warp as you please.

Alright. We'll see.

But what problem do you imply would happen? People being harder to hit because of sending same amount of packets (125) sometimes containing more frames (up to 2 per packet, but sometimes 1 as usual)? What's the logic behind that theory?

Main reasons why people are harder to hit:
1. they dodge
2. they warp
3. you're drunk

Assuming FPS-independent physics, you won't be able to dodge better.

Higher maxpackets would help a fraction of warpers and make them warp less (not more), but maxpackets won't be bumped, only maxfps. Hence no change here.

Higher FPS on someone else's monitor can't make you drunk.

I guess you will now try to reply that with 250 FPS, my GPU will overheat and start dropping to 30 FPS or something. Spare me ;)

Conclusion: you will still miss the same shots and still blame netcode, and it will still be bullshit.

But what problem do you imply would happen? People being harder to hit because of sending same amount of packets (125) sometimes containing more frames (up to 2 per packet, but sometimes 1 as usual)? What's the logic behind that theory?

Higher maxpackets would help a fraction of warpers and make them warp less (not more), but maxpackets won't be bumped, only maxfps. Hence no change here.

Thanks for the insight. Makes more sense now.

Then you can still use com_maxfps 125. It's the same like now - we don't limit max fps to 50 because there's someone with hardware that allows only that much.

My worst spot in asylum (in the corner and looking exactly there) - I had 112-125 on Pentium IV / Athlon XP processor. Now on a quad core Sandy bridge at 3.8GHz max it's stable 500 (so it's somewhere above 500, below 1000), with CPU use 10-15% (which is up to 60% as QL uses only one core). A 2GHz dual core +proper config should be plenty for 250 fps.
http://img163.imageshack.us/img163/1791/arsd.jpg

Then you can still use 125fps

Except no one will use that after it gets capped to 250 fps, you know this better than me. And QL responds differently to various set-ups. You have people with high-end PC's having framedrops for no reason and people with Athlon XP2800+ (13 yo) running the game 125fps all the time. I'd say idSoftware was on good terms locking the (cmd)rate. I think bringing 250fps in the equation just makes things more complicated and less consistent. But we'd have to see.

nothing wrong with upping the limit, as long as the default stays on 125. 95% of the players dont even realise this command exists anyway ;)

Yeah, except that 5% of the players, that know this, do actually matter. And there is a very big room (between 125 and 250 fps) to exploit if you don't have consistent framerate. The latter could create more inconsistency like through rails, bad reg and result in more Q_Q'ing.

I guess we can all agree that Quake feels super inconsistent and random at times, why not keeping it clean & simple?

The latter could create more inconsistency like through rails, bad reg and result in more Q_Q'ing.

How about netcode?

I guess we can all agree that Quake feels super inconsistent and random at times, why not keeping it clean & simple?

For me QL is fuck as stable. I dont remember when my rail goes thru enemy and didnt hit. May be coz i have playing actively ql from 2010 at good setup(120hz with stable 125fps without packetloss and with stable ping, etc) and good feeling what setting are good and are bad?

Much more than all of this settings is just 60hz vs 120hz monitors
BUT it's quake when decisions >>> any aim or hardware.

Indeed, we will see. I bet most will be happy after the change. 250fps should remove stuttering, page tearing and reduce display latency - so the in game experience will be more consistent and enjoyable.
Also most warping exists because of the network not com_maxfps settings. I doubt low-high framerate can cause this, it's more likely when single core computer almost hangs for a fraction of second because of some background process.

and your framerate varies between 100- 250 all the time. Doesn't this make you harder to hit for the opponent?

No. Why would it? It's not like if your client was gonna send a packet for the first "cl_maxpackets" packets in a second and stop sending until the next second or something.

I'm just gonna leave it here
https://github.com/TTimo/es_core

Isn't that wrong direction anyway? I think that in general video card industry shall improve vertical sync or introduce new way of synchronization of output. Nothing can give you as smooth image as r_swapinterval 1, but with a cost of unplayable lag.

I expect it is technological difficulty, so can someone explain me why it is impossible to separate video rendering from input and physics calculation? Render the frame just at a time it is needed by you screen and show most recent game state. If it is not possible now, what can be changed in GPU interface to resolve that?

G-sync is on its way, google that or check the ESR thread :)

Meanwhile 250fps gives extreme smoothness and responsiveness with very very small tearing (even on 60hz it looks close to perfection without any lag)

Thanks man, that is what I was going to invent :). Late as always.

Nothing can give you as smooth image as r_swapinterval 1

Not exactly :)
I play on a CRT at 155fps. If I just enable swapinterval 1 - it removes page tearing, but still displays only 125 fps. so there is some very noticeable stuttering. I have to use timedemo 1 (to unlock com_maxfps) so it renders 155 fps synced with the monitor.
Surprisingly, uncapped fps alone (with swap interval 0) gives the same smoothness. Actually even better, as swap interval 1 when testing with +left or +right gives me a single position skip (stutter) once a second or two.

Surprisingly, uncapped fps alone (with swap interval 0) gives the same smoothness.

When tearing occurs, parts of the last two (or sometimes more?) rendered frames are displayed. If frames are rendered with high frequency, the difference between two adjacent frames should be minimal. Thus, while technically tearing is still there without vsync, it's so small that it's unnoticeable at very high FPS values.

Not sure if I understood you correctly but are you saying your monitor is running at 155hz? Cos then yes it's normal that it's not too smooth since 155/125 = big poo and repeated/dropped frames.
This is btw exactly the "stutter" that g-sync will finally solve.

With games that don't have a 125fps cap you should be getting unmatched smoothness though :)

Yes, I meant 155Hz on the monitor. But lower than 125 refresh like 1600x1200@100Hz with com_maxfps 125 is not smooth as well... I wish I had 1000fps camera to record the screen and analyze this, measure total response time etc. :)
I hope AMD will come with something similar to g-sync in future radeon drivers, so far the only way to smoothness without extra vsync lag is brute force - very high fps.

Yes 125+100 is not going to be better since 125/100 = 1.25 so every 5th frame will be dropped to fit within 100hz.

It's all about integers as far as "smoothness" goes.

And this has nothing to do with software or drivers btw, AMD can't remedy this with software, neither can nvidia - it's only a combination of supporting hardware and supporting software that will do the trick. I do hope that the whole "g-sync" idea will spread and reach all monitors and all gpus though, but sadly this might take a while.

Right, software solution is adaptive v-sync and similar stuff (I don't use that anyway).
"A: Adaptive V-Sync is a solution to V-Sync’s issue of stuttering, but input lag issues still persist. NVIDIA G-SYNC solves both the stutter and input lag issue."
http://www.geforce.co.uk/hardware/technology/g-sync/technology
"Industry luminaries John Carmack, Tim Sweeney, Johan Andersson and Mark Rein have been bowled over by NVIDIA G-SYNC’s game-enhancing technology."
And SyncError developed 250-fps-gaming with similar effect at no cost ;)

Please do, it sucks playing at 125fps with a 160hz crt it's a very noticeable difference between 125fps and uncapped games.

All hz abuse must stop include #pierow #jigglywiggly

These are no devices for skill devices

Rapha win +24 jigglywiggly -2
Zero4 +24 jigglywiggly -2

Faceit NA

I'm not saying it will make people better. I'm saying it's a noticeable difference and is easier on my eyes so it's more enjoyable.

waiting for 250 FPS Month League then :)