CSGO Sticky thread

I hope I don't become spoiled with the high tick rate community servers.

It is not that big of an adjustment going from 128 to 64, you will be much more confident in landing your shots even if you do question the server of whether your shot has landed or not on 64 tick. Most people going from 64 to 128 falls in a dismay of their sudden inferiority. It just shows, how a single update rate may influence the user’s experience. Why optimal netcode is so bloody important.
 
It is not that big of an adjustment going from 128 to 64, you will be much more confident in landing your shots even if you do question the server of whether your shot has landed or not on 64 tick. Most people going from 64 to 128 falls in a dismay of their sudden inferiority. It just shows, how a single update rate may influence the user’s experience. Why optimal netcode is so bloody important.

I love it, the server I've been forced to play on is a CSGO Free for All 196 tick rate deathmatch server with headshots only.

The last one I played I went something like 110 kills 64 deaths and ended up being second overall after joining late.
 
Message from Steam Support on Mar 26, 2017 @ 4:35pm | 3 hours ago
Thanks for writing in to report this issue.

We are aware of the problem and are investigating the issue further.

Best Regards,
Chris
 
Message from Steam Support on Mar 26, 2017 @ 4:35pm | 3 hours ago
Thanks for writing in to report this issue.

We are aware of the problem and are investigating the issue further.

Best Regards,
Chris

I'll take it.

As long as we have official confirmation that they're aware of the issue I'm sure it will be sorted in hopefully not Valve time.
 
Last edited:
I joined a Deathmatch game someone on my friends list was playing on, he joined using the edited network config file.

I played for ~15 seconds and killed 3 people before a vote was started to kick me, exact quote "Soul Assassin is try harding, someone CT please kick him." The vote basically immediately passed.

Great community we have in South Africa.
 
Last edited:
it has also not worked for me, edit, i managed to get it working. open the network_config.json file and search for where it shows

“cpt”: {
“ping_only”: true,
“addresses”: [
“152.111.192.243:27015-27016”,
“152.111.192.244:27015-27016”
]
},

and remove the “ping_only”: true, till it shows like this

“cpt”: {
“addresses”: [
“152.111.192.243:27015-27016”,
“152.111.192.244:27015-27016”
]
},
 
Last edited:
I don't have the unofficial fix applied and I was just able to join a local server, the ping kept jumping from 60ms to 100ms leading me to believe they are working on the servers as I type this.
 
Last edited:
So what else was in this update? Ran around with some bots for 10 minutes and sounds have been changed again, the Negev has been turned into a longer range sawed-off shotgun (in accuracy)...am I going to get any nasty surprises next time I play with people?
 
So what else was in this update? Ran around with some bots for 10 minutes and sounds have been changed again, the Negev has been turned into a longer range sawed-off shotgun (in accuracy)...am I going to get any nasty surprises next time I play with people?
The R8 trigger pull has been reduced from 0.4s to 0.2s and the Negev after the first ~20 bullets becomes a laser gun with how accurate it is.

Both of them have been removed from competitive for the time being.
 
Top
Sign up to the MyBroadband newsletter
X