Earlier quoted context omitted.
Nowadays it's more like 20 players and 80 bots, so a lot less networking stuff going on, and the bot AI is so basic that I doubt it has a significant impact on server performance unless it's very badly implemented.
AI is more expensive than a regular player.
Valorant's 128-Tick Servers (2020)
91–100 of 136 posts
Re: Valorant's 128-Tick Servers (2020)
#92Earlier quoted context omitted.
As a lifelong Valve/CS fan, I've been so disappointed with subtick. It was pitched as generational evolution to the games netcode. Yet years later they're still playing catchup to what CS:GO provided.. Hopefully competition from Valorant and others puts more pressure to make things happen at Valve.
I didn’t notice any difference between 64 and subtick.
Re: Valorant's 128-Tick Servers (2020)
#93Earlier quoted context omitted.
This is not equivalent to "lobby time or end game animations" in other games. In Valorant (similar to Counter Strike), at the start of the game you have 60 seconds to buy your weapons and abilities for the round. Valorant/CS is typically a best-of-13, and before each round is a 60 second "buy" period.
In CS you can leave the buy zone immediately. I don't necessarily believe that Valorant's decision to fence players in their spawn for the first minute during the buy period is simply to save on server costs, especially because they realized that optimization possibility after the fact. Being able to buy your weapons quickly may have an element of skill, but it doesn't make for particularly interesting gameplay. They…
Re: Valorant's 128-Tick Servers (2020)
#94I wonder if any game servers are implemented in Erlang?
You'll never get a modern FPS gameserver with good performance written in a GC language. Erlang is also pretty slow, it's Python like performance. Very far from C#, Go and Java. The other reason is that the client and the server have to be written in the same language.
Re: Valorant's 128-Tick Servers (2020)
#95Counter-Strike: Global Offensive was also able to handle 128 TPS just fine. They just chose to never implement it in official matchmaking (64 TPS). It did work very smoothly on community servers. Counter-Strike 2 implements a controversial "sub tick" system on top of 64 TPS. It is not comparable to actual 128 TPS, and often worse than standard 64 TPS in practice.
Most game servers are single threaded because the goal is to support the maximum number of players per dollar.
A community server doesn’t mind throwing more compute dollars to support more players or higher tick rate. When you have one million concurrent players - as CounterStrike sometimes does - the choice may be different.
Re: Valorant's 128-Tick Servers (2020)
#96Earlier quoted context omitted.
Also for comparison, the Runescapes (both RS3 and Oldschool Runescape) have a 0.6 tick/second system (100 ticks/minute). It works rather well for these games, which I guess highlights that some games either a) can get away with high latencies depending on their gameplay mechanics, or b) will evolve gameplay mechanics based on the inherent limitations of their engines/these latencies. RS3 initially leaned into the 0.6…
100ticks/minute is 1.666... ticks per second, not 0.6.
Re: Valorant's 128-Tick Servers (2020)
#97Take notes, Valve.
Re: Valorant's 128-Tick Servers (2020)
#98Counter-Strike: Global Offensive was also able to handle 128 TPS just fine. They just chose to never implement it in official matchmaking (64 TPS). It did work very smoothly on community servers. Counter-Strike 2 implements a controversial "sub tick" system on top of 64 TPS. It is not comparable to actual 128 TPS, and often worse than standard 64 TPS in practice.
Lots of things work fine when you throw twice as many dollars at them. It’s not a matter of it working or not. It’s a matter of economics. Most game servers are single threaded because the goal is to support the maximum number of players per dollar. A community server doesn’t mind throwing more compute dollars to support more players or higher tick rate. When you have one million concurrent players - as CounterStrike…
Re: Valorant's 128-Tick Servers (2020)
#99Take notes, Valve.
Sub tick is probably more accurate overall but I do think the cs2 animation netcode is crap and hides a lot of the positives. Hopefully moving to Animgraph 2 will help that, who knows
Re: Valorant's 128-Tick Servers (2020)
#100Earlier quoted context omitted.
And Fortnite is allegedly 30 ticks per second.
Apex Legends is at 20 IIRC (My memory is from 2-3 years back on this one tho) CSGO was at 64 for the standard servers and 128 for Faceit (IIRC CS2 is doing some dynamic tick schenanigans unless they changed back on that) Overwatch is I think at 60