I'd rather have 64 tick.

[The7th]

At least it is somewhat understandable this new tick rate system is awful. Dying from behind walls and missing blatant hits.

[Reuben]

The game is using a tick-rate of 64, the only difference is the shots register before the next tick, not after.

[Avid]

I'd rather have 124tick for the whole game. Instead of this subtick nonsense

[The7th]

Originally posted by Reuben:

It's using 64 tick, the only difference is the shot register before the next tick, not after.

Oh that makes sense. Not.

[Reuben]

Originally posted by 7th⁷:

Originally posted by Reuben:

It's using 64 tick, the only difference is the shot register before the next tick, not after.

Oh that makes sense. Not.

Then educate yourself, there's an in-depth video on YouTube about it.

[The7th]

Originally posted by Reuben:

Originally posted by 7th⁷:

Oh that makes sense. Not.

Then educate yourself, there's an in-depth video on YouTube about it.

This guys is defending the new tick rate. SMH.

[Saedelaerex]

Originally posted by Reuben:

Originally posted by 7th⁷:

Oh that makes sense. Not.

Then educate yourself, there's an in-depth video on YouTube about it.

why would he it's much easier to whine about sth you have no clue about :)

[Saedelaerex]

Originally posted by 7th⁷:

Originally posted by Reuben:

Then educate yourself, there's an in-depth video on YouTube about it.

This guys is defending the new tick rate. SMH.

yeah because not everyone is as incapable to adapt to something new as a few on these forums

[The7th]

Originally posted by saedelaerex:

Originally posted by 7th⁷:

This guys is defending the new tick rate. SMH.

yeah because not everyone is as incapable to adapt to something new as a few on these forums

Adapt to deez. Sit.

[Renos]

part of it adaption
part of it is subtick being wack
heres a quick break down of how hitreg is cs2 works compared to go

in cs2 when you click mouse 1 your shot gets fired instantly and hitreg is done in that same moment. NO MATTER WHAT YOUR SHOT WILL LAND IN THE EXACT SPOT YOUR CROSSHAIR WAS WHEN THE GAME GOT THE +ATTACK COMMAND

(in csgo hitreg calculations would occur the next available tick after you clicked mouse 1 meaning you could have moved your crosshair away. meaning you may have clicked mouse 1 but your shot would never landed where your aiming when you clicked. It would always land were you were aiming 1 tick later which could be 15 milliseconds later)
This pretty much destroys any muscle memory you may have from csgo.

in cs2 if you shoot in between rendered frames the game will use where your crosshair was in the last rendered frame for hitreg
(in csgo it would use the next rendered frame)
this isnt an issue unless your framerate is 60 or below

now the part where i list the subtick oddities
because hit reg is so fast in cs2 it is now out of sync with the firing animation
hitreg happens instantly but the firing animation waits until the next available tick to play
this can lead to the visual or missing shots that should be dead on but in reality you likely clicked mouse 1 too early and actually missed,

subtick now allows you to die or kill players between ticks
basically a player can kill you in between a tick but the server waits until the next tick to tell you it happened. meaning you can technically be dead according to the server but still move on your end because the server has not gotten back to you yet.
leading to the dying behind walls that everyone is yelling about,
this also leads to you getting a kill but your crosshair was no longer on the enemy.
(basically you killed them but the server has not gotten back to you yet that they died).

[𝖒𝖔𝖔𝖓𝖋𝖚𝖑]

THATS THE THING MAN ITS NOT EVEN 128!

[𝖒𝖔𝖔𝖓𝖋𝖚𝖑]

♥♥♥♥♥♥♥ VALVE ACTING ALL CHEAPSKATEY THEY HAVE MONEY ITS EZ PEASY FOR THEM TO HAVE 128 TICK SERVERS THEYRE ♥♥♥♥♥♥♥ GREEDY
ALL MAJORS HELD ON 128 TICK SERVERS WHY CANT WE HAVE THAT?!

[NW/RL]

Originally posted by Reuben:

Originally posted by 7th⁷:

Oh that makes sense. Not.

Then educate yourself, there's an in-depth video on YouTube about it.

Could you offer a link instead of "go find it lol"?

[𝖒𝖔𝖔𝖓𝖋𝖚𝖑]

Originally posted by Renos:

part of it adaption
part of it is subtick being wack
heres a quick break down of how hitreg is cs2 works compared to go

in cs2 when you click mouse 1 your shot gets fired instantly and hitreg is done in that same moment. NO MATTER WHAT YOUR SHOT WILL LAND IN THE EXACT SPOT YOUR CROSSHAIR WAS WHEN THE GAME GOT THE +ATTACK COMMAND

(in csgo hitreg calculations would occur the next available tick after you clicked mouse 1 meaning you could have moved your crosshair away. meaning you may have clicked mouse 1 but your shot would never landed where your aiming when you clicked. It would always land were you were aiming 1 tick later which could be 15 milliseconds later)
This pretty much destroys any muscle memory you may have from csgo.

in cs2 if you shoot in between rendered frames the game will use where your crosshair was in the last rendered frame for hitreg
(in csgo it would use the next rendered frame)
this isnt an issue unless your framerate is 60 or below

now the part where i list the subtick oddities
because hit reg is so fast in cs2 it is now out of sync with the firing animation
hitreg happens instantly but the firing animation waits until the next available tick to play
this can lead to the visual or missing shots that should be dead on but in reality you likely clicked mouse 1 too early and actually missed,

subtick now allows you to die or kill players between ticks
basically a player can kill you in between a tick but the server waits until the next tick to tell you it happened. meaning you can technically be dead according to the server but still move on your end because the server has not gotten back to you yet.
leading to the dying behind walls that everyone is yelling about,
this also leads to you getting a kill but your crosshair was no longer on the enemy.
(basically you killed them but the server has not gotten back to you yet that they died).

Yeah? and how will you explain half of the shots just being sent to the ♥♥♥♥♥♥♥ void? ITS FKN POINTBLANK THERES NO PLACE FOR EM TO GO ONLY THE ENEMY YET I GET 24 in 1. explaing that. point blank. literally almost ♥♥♥♥♥♥♥ eye to eye

[Reuben]

Originally posted by NW/RL:

Originally posted by Reuben:

Then educate yourself, there's an in-depth video on YouTube about it.

Could you offer a link instead of "go find it lol"?

https://youtu.be/aD9I3YD3Wys

[Renos]

Originally posted by meilyr:

Originally posted by Renos:

part of it adaption
part of it is subtick being wack
heres a quick break down of how hitreg is cs2 works compared to go

in cs2 when you click mouse 1 your shot gets fired instantly and hitreg is done in that same moment. NO MATTER WHAT YOUR SHOT WILL LAND IN THE EXACT SPOT YOUR CROSSHAIR WAS WHEN THE GAME GOT THE +ATTACK COMMAND

(in csgo hitreg calculations would occur the next available tick after you clicked mouse 1 meaning you could have moved your crosshair away. meaning you may have clicked mouse 1 but your shot would never landed where your aiming when you clicked. It would always land were you were aiming 1 tick later which could be 15 milliseconds later)
This pretty much destroys any muscle memory you may have from csgo.

in cs2 if you shoot in between rendered frames the game will use where your crosshair was in the last rendered frame for hitreg
(in csgo it would use the next rendered frame)
this isnt an issue unless your framerate is 60 or below

now the part where i list the subtick oddities
because hit reg is so fast in cs2 it is now out of sync with the firing animation
hitreg happens instantly but the firing animation waits until the next available tick to play
this can lead to the visual or missing shots that should be dead on but in reality you likely clicked mouse 1 too early and actually missed,

subtick now allows you to die or kill players between ticks
basically a player can kill you in between a tick but the server waits until the next tick to tell you it happened. meaning you can technically be dead according to the server but still move on your end because the server has not gotten back to you yet.
leading to the dying behind walls that everyone is yelling about,
this also leads to you getting a kill but your crosshair was no longer on the enemy.
(basically you killed them but the server has not gotten back to you yet that they died).

Yeah? and how will you explain half of the shots just being sent to the ♥♥♥♥♥♥♥ void? ITS FKN POINTBLANK THERES NO PLACE FOR EM TO GO ONLY THE ENEMY YET I GET 24 in 1. explaing that. point blank. literally almost ♥♥♥♥♥♥♥ eye to eye

simple
packet loss or connection issues on your end
and to keep the game somewhat fair the server denies your hits.