CS:GO - 64 VS 128 Tick 

I come here to watch about tick rate, came out with Bachelor of Computer Science

if you have a monitor that is at least maybe ~85hz or so you can cheat the test by exploiting the crouching in mid air bug. when you jump and crouch mid air, the interpolation between movements seemingly shuts off entirely and you judder through the air at the server tick rate. if you're on a 60hz monitor you can't notice this because it's ticking at 64 ticks so it won't be any different to your framerate, but if you are on anything higher like 144hz then the drop to 64 movements per second as you fly through the air is an immediate giveaway that you're on 64 tick.

I've had situation where I took a shot with an AWP right in the middle of the head of an enemy, and.... He got away! We need 2048 ticks.

Valve could just make net_graph always show fake 128 tick rate in matchmaking, when real tick rate is 64, and everyone would be happy

The real world technically also has a Tick rate. You could say that the Planck Time (en.wikipedia.org/wiki/Planck_time) is the absolute unit of time. It's the time that it takes the speed of light to move 1 Planck Length, which is 1.616*10^-35 meters. So a tick takes 5.39×10^−44 seconds, or in other words, by taking the reciprocal (1/(5.39×10^−44)) we get a tick rate of 1.85*10^43 = 18,500,000,000,000,000,000,000,000,000,000,000,000,000,000 per second. Of course, some might still complain that it's too slow...

Almost thought there was no lens flair in the thumbnail

Perfect tickrate: 1/PlanckTime

Meanwhile Apex season 5 out here with 20 tick servers handing out generous no regs to everybody

9:28 I'm suprised nobody pointed this out yet.

A Tickrate vs FPS vs Refresh rate video would be awesome; how they influance eachother for example.

Dude shows a surf clip and casually gets messaged by the gamemode's creator

128 tick makes a huge difference when surfing or hopping because the server gets to apply the air acceleration 2x as often (if you're consistent)

Real pros play with cinematic 24 fps and 30 tickrate for stunning visual cinema like experience.

Im just glad we moved past 32 tick. Cleared the sniper line of sight on your end? According to the server you sat in the middle of the crossing for 70 hours begging for a headshot.

CSGO: Thinks they need a 128 Ticks server Minecraft: 20

11:34 The last point you make is actually in line with your earlier assertion that the higher tick rate increased the effect of skill difference. Meaning, that more people are able to have high kill count when the difference in skill is less important. To make it more clear , on a low tickrate server more people are able to get 5+ kills because they don't just get killed by the high performers.

I live in Stockholm and we have servers hosted in Stockholm and playing on German servers don't make a big difference until you start looking for it, but in most cases you can't see. But when I play on a server where I have 50+ ping I clearly see the difference between 5 and 50 ping. But I can't see the difference between 128 tick and 64 tick. Valve is should prioritise lower latency.

My top 3 favorite youtubers: 2kliksphilip 3kliksphilip kliksphilip Keep it up with a great job Philip

I think when you start getting to higher level play, having a better quality server, is very important. And that's not just tickrate, that's the server varience, packet loss caused by the data centre and so on.

8:11 "jews" oh, okay.

128 tick is so rubbish, CSGO should upgrade to 512 tick

Valve: here are 128 tick servers for you! community: we demand 256 tick

the server should stay at 64 ticks because uf they whould be 128 tick we cant say "fuck this 64 tick server, on 128 i would have hit that"

6:58 now theres a program I haven't seen in a long time, good old Xfire

clocks should have 128 ticks per second edit: some people just have probably tested on nades that only work on 64 or 128

Most situations you cant see the difference between 64 and 128 tick servers. But there are always those situations where your bullet couldve hit if it was 128 tick. You need alot more than 4 rounds to be in those situations.

Dude i freaking love you!! You go so deep into topics unless others. And you explain it so fucking well!

Wonderful work. With all of this great data I feel like this should be put into written form as well, not just a video, where it's easier to closely study the data and the explanations.

How is it not 800k yet. I've been checking for days. Pre-emptive congrats on 800k Philip :) edit : WE 800K NOW BOIS!

Note that for bunnyhopping and surfing the acceleration is mathematically limited and a higher tickrate actually means you accelerate faster by a significant amount. For example the maximum speed you can get in 6 Jumps on auto/1000aa is ~650u/s on 100tick and ~710u/s on 128tick.

Maybe, we should have 76 tick rate servers.

This was the first 3kliksphilip video I watched, this was the video that caught me attention and made me subscribe.

Holy shit, 1080p is back!

Oh man, I miss these CS:S Flashbacks

as soon as I heard "let's go back in time" and the music started playing i smiled a bit

what chat program was that at 6:58?

900 people can't tell the difference between 64 tickrate to 47 Activision: Yes

7:59 Ha ha ha ha. Used to host Killing Floor servers on my laptop all the time, worked well enough... I guess I had a good gaming toothbrush.

How many of them used a 144Hz Monitor? I guess there is no reason to use 120tick when everyone is playing @60Hz or can't hit 120FpS.

I have the net graph always on but its position offscreen, when I press tab it moves to onscreen. some of those net_graph users may have not done it on purpose or even looked at it

8:14 Ahhh XFire and HL ServerWatch, thems were the days. Where's me cane?

Minecraft runs at 20 ticks/s and believe it or not, there is a competitive PvP scene

Nades do actually function differently in 128. For example on mirage you have to throw totally different lineups to smoke snipers nest and you have to change your aim a little for all of the jumpthrow nades.

i know im a little late to the party but i felt like adding this: in surfing, the tickrate makes a great difference. when strafing in a circle, there is a "sweetspot" for how fast you should turn to gain maximum acceleration. if you turn faster than this sweetspot, you actually start losing speed. in the upcoming source movement-game collection "momentum mod", there is actually an option to visualize this. the tickrate greatly influences where this sweetspot is. higher tickrates have a much "faster" sweetspot, which lets you (a) make tighter turns without losing speed and (b) gain more speed through being able to strafe harder. for surf there are usually two tickrates, 66t which is what competitive surfing runs on and 100t which is more geared towards casuals. hope this helps :)

It's not about better players being able to tell the difference, it's about people actually trying to feel the game instead of just guessing, i bet that most people just randomly guessed or thought 'oh i'm hitting my shots this must be 128 tick'. Let's be honest this test only shows to us that most people can't tell the difference, not that it's good enough for them, you'll miss the same amount of perfect hit's whether you care about it or not. And if anything, Valve could at least make 128 tick servers for higher ranks. Say you get access to them when you hit LE ? That would be fucking great.

More CSS flashbacks Phillip please maybe even some 1.6 ones xD "Let's go back in time........Back....back, back......"

Extremely interesting analysis of the available data. Thanks :)

I have a question about the c4. Does the explosion come from the c4 itself? Like the c4 being planted close to say library in Inferno make a difference on where the bomb will reach and also the dmg it will do or is it fixed no matter where you plant?

64 thicc vs 128 thicc

As a redditor once said: The tickrate is less important than the performance of the server.

Congrats on 800 000!

I can give a good example of an easily noticeable difference, at a specific occasion. Strafe-shots are based on that you counteract your movement and stop to a standstill. In cases of 64 tick, you have to stop longer to more consistently get an accurate shot, because of the update rate means there is a leniency in which within the server sees your character as fully stopped. In an optimal scenario, assuming perfect strafes, 128 tick will yield a far better net results of hits being accurate, in contrast to 64-tick. This is highly noticeable when peeking out corners, or similar situations that could use a strafe-shot, with the AWP, to fire Only having one shot, you do notice that your bullets hits better, to more where you are aiming, when you play on 128 tick, and you can also adapt a slightly faster playstyle.

Congratulations for 800k in advance❤

Why didn't RU-vid notify me that Philip uploaded? I need to see his uploads as soon as possible!

The biggest problem with the tickrate in Source was the Hitbox lagging far behind the player Model at a tick of 33. You actually had to shoot behind the enemy running by to get the kill. A higher Tickrate had the Playermodel and Hitbox in better Sync, thus letting "skill" count more than spraying and praying.

NICE philip this is a great document and resource. fantastic video :) :)

"with a match load of salt" But that'd be enough to kill thousands!

I have not played a counter strike game since 1.6 but I love these videos

Hi @3kliksphilip, thx for the Video! While I don´t follow your conculsions I am happy to see that some people are trying to demystify the tickrate and your explanations of the technical details are good. The data is not enough to draw conlusions but it´s more data than we had before and the idea for the testing scenario is interesting. For a, in my opinion, better dataset you´d need more rules for the test. A few, I can think of atm, could be 1. Hardwaresurvey --> Player --> tickrate --> performance(K/D/A/Plants) * Skillgroupmodifier(Normalize Data for all Skillgroups) 2. Test Groups/Scenarios with different scopes --> Scenario A, Players of the same/comparable Skillgroup low end HW; Group B, Players of the same/comparable Skillgroup Mid/High End HW, Group C Players of Skillgroups with 3-4 Groups difference, low end HW; Group D Players of Skillgroups with 3-4 Groups difference, Mid/High End HW; More Scenarios possible 3. Player must be of the same or comparable time zone to prevent skill difference because of daytime 4. Gameserver Position( How far from each player --> Ping modifier needed?) 5. Larger Playerbase 6. No Bunnyhops :) This could be interesting for different science fields maybe it could even be made into a thesis --> Perception and performance of workers(players) in different environments based on assumed properties of the environment or, Does it tickrate?. :-D

how can i know the tick rate of a game like PUBG ???

Watching a kliks video without subtitles is a whole other experience...

Project X sucks. Needs 256tick servers or dead game. Love your vids kliks. Much love from Lowestoft.

with the recent valorant release (128 tick) and this conversation sparking back up, i hope you redo this test!. im sure sample size will be much bigger with everyone at home atm too

Nostalgic reminiscing _Synchobonk PLAYS_

_xfire_ ...GOD DAMN, WE'RE GETTING OLD! *AHHHHHHHHHHHHHHHHH*

If someone play on 47 ticks, and then in 60ticks, he would probably think he's on 128 ticks because the logic would be that it was either 64 or 128

the question i have is, did everyone who played on the 124tick servers get automaticly the right net settings? when you have 64 tick settings on the 128 tick server you will only experience 64 tick right?

is there something about 60hz monitors,and if i have 60hz monitor is it same to play on 128 tick and 64?

0:06 this is what it looks like when I try to play cs go on my PC I really need to buy a graphics card

53% 5/3= 1.6 CS 1.6 1.6 = Golden Ratio Set Sensitivity to 1.6 = Golden AimWant some 1 taps? Ditch the duality and get with the Singularity brother.OH YEAH!

I can say from experience that lower ticks get in the way of surf servers. Each tick is valuable since you'll be using it to ever so slightly adjust your angle, so if the tick rate isn't right you'll end up lower/higher on the ramp as you should. Other issues are collision detection. Lower tick servers sometimes believe you've collided with the seam of the ramp when you shouldn't have and stops you dead in your track. Another problem is ramp steepness. In lower tick levels ramps that are less steep than normal end up not even counting as surfable, and you have to walk/bunny hop them if you want to progress.

I don’t understand, are they not allowed to use nades or rifles during the test? I mean nades land at different position in different tickrate. And my spray also changes along with tickrate

4:30 love those legs xD

It's basically the performance of server which makes the difference and not tickrate.

Xfire, What a wonderful program that was at the time. Keeping track of all your games and all of the modern day features like steam has... back in 2009

My I ask, is the tick rate the reason why in an awp 1v1 on my screen I will be crouched, and dead in the centre of their chest, and will hear the shot go off, but I will still lose the duel?

Pretty sure most of the test result is trash, due to too many conflicting variables. At least for the 900 person blind tickrate test. People thinking they did better because they had a lucky day is massively skewing the interpretation of data. But it's not completely useless as you showed, and should be respec'd for another test group.

I think one of the best ways to see 128 vs 64 is in extremely fast encounters such as peaking long doors with an awp. Very often on 64 tick I will shoot and die, but my teammates say I didn't even shoot. I think they should run this test again but use a 1v1 map instead of a DM.

Can anyone explain what that surf map is? I've played once, and I just falling down and it restarts. Again and again. I have no idea how it works.

The music @7:25 sounds like something that was on GTA V but sort of too different to be the same actual soundtrack. What song/artist is it?

6:57 oh my, haven't seen xfire in years

Maybe is only a placebo effect but I can use deagle on 128 tick and I can't on 64 🤷‍♂️

I would like to know how far a player moves every tick on a 64 tick server while being runboosted. If the distance travelled per tick gets close to about half a heads width, you may get into slight problems with 64 tick servers. Also, some people say that weapons shoot slightly different and their spray patterns vary a little depending on if they are on 64 or 128 tick servers. It would be great to know if there is any truth to that.

This video is a pain to watch, couldn't stand a minute. And I'm a huge fan of your content.

Play CSS you can tell. Jumping on a box. Aka d2 lower tun. Jumping on the corner was easier on higher tick. Harder on lower as you would have to add a flick to the jump. Should probably have a look.

"Let's go back in time...." When you say this i always feel so nostalgic and remember all the ol' days.! Dsltn

It depends if your pc is high end and you have 120, 144 hz monitor, in 64 tic servers when i crouch my monitor shows im in crouch but the server shows im still standing

@3kliksphilip what would happen if Valve would duplicate the number of tick rate by 2? From 128 tickrate to = 256 tickrate? it would fix the hit registration problem?

No more tickrates apparently with CS2

I would have tried to guess the ticrate by bunny-hopping, because it's in my opinion the only way to distinguish it. You can't tell the difference in regards to shooting people/hitting headshot, you don't have a computer inside your head to calculate all the variables and randomness. But the greater consistency and smoothness of bunny-hopping on 128-tick server is recognizable by a human.

Wouldn't it depend a lot on your monitor? IF you have a 60hz monitor can you only feel/see the 64 tick? or 60 tick rather and if you have a 144 can you see the 128 tick? Or does this not matter?

what about net_graph 1? they can just turn it on when they were testing.

7:47 where can I find this music? I love it!

"I'm not bad it's the server"

often on 64 tick when you duel another awper and you both shoot but he kills you and then you ask "where did my shot go" then your friends say that you didnt even shoot, and you can see that you lost a bullet in the mag. but when someone else pick it up its still there. i dont think ive had that happen to me in 128 tick servers. but i feel like it has more to do with ping than tickrate since its the same tickrate for both of us? anyone know? im guessing his shot got to the server before my client knew i was actually dead? is this just a 5 ping swedish problem? i almost always have the best ping on the server so i feel like this shouldnt happen to me but to them. also alot of jumpthrow smokes that are designed on 128 tick dont work on 64 tick or are alot harder without tweeking it, the "astralis" mirage window smoke on mirage for example where u strafe right and jump and throw, ending up on the trashcan

Great vid 3kliksphilip

I've lost my head way too many times after a) hearing my gun go off and b) seeing muzzle flash and c) seeing enemy's blood on the wall ending up without any damage done to said enemy to believe that it wouldn't have registered as both killing each others in a faster tick rate servers.

The 20 dislikes are people who think that 64 tick servers are the only reason they're bad.

Awesome video man, cheers! btw, I loved your microphone's quality, could you say which model/brand is it? Thank you so much, greetings from Brazil!