Tickrate Stuff
I think it's kind of safe to say that the tickrate for Apex is around 60Hz. Clients send their updates 60 times per second, while servers send game data up to 60 times per second. "Wait, but everyo...
Forum Discussion
@apostolateofDOOMIf you want a proper comparison, please provide the following ( for Battlefield & Apex):
- average number of shots or projectiles / server update;
- hit calculation formula;
- number of different characters (usually distinguished by shape, size, animations types);
- average number of hitboxes / map;
- average number of interactibles / map;
There are more that can be added to the list, but these will suffice to prove how different these games are under the hood. Note: all of the above affect the amount of data being sent / received
@DoYaSeeMe I'm not searching that but feel free to share if you have it. xD
Battlefield has more interactable stuff, weapons, vehicles and a generally more complex environment compared to Apex with more players that was at a lower rate but got increased with noticeable performance gains.
None of this changes the fact it's currently bad here and could be improved. Maybe not worth it from a business perspective, but it's entirely possible.
Battlefield has more interactable stuff, weapons, vehicles and a generally more complex environment compared to Apex with more players that was at a lower rate but got increased with noticeable performance gains.
None of this changes the fact it's currently bad here and could be improved. Maybe not worth it from a business perspective, but it's entirely possible.
@apostolateofDOOMWell, you brought Battlefield in, should be your task to do a detailed research to support your statement. Let me give you one basic comparison though:
- An explosion/destruction in Battlefield is visually more complex than an Apex deathbox, right? Well, yes, but this has a client side impact. Netcode wise, the explosion is calling an item to change state (which then plays the related animation on the client) or an animation to be played at a certain coordinate and moment in time, data which can be sent only once, in a single update. A deathbox is a simple object, but which is affected by the game's physics engine, so its position, rotation, skin id have to be sent continuously while the box is falling or carried by a flyer, while its owner banner id, list of item ids, amount per item, ping /dibsed flags per items, etc. have to be sent continuously to the players that loot the box. Already easy to conclude that this deathbox takes many times more data space in an update, for a longer period of time,so many ticks or updates.@DoYaSeeMeThat's why i suggested in my thread to remove them (think i just put flyers and prowlers but deathboxes too if that's the case) as it doesn't really enhance the experience and it's an unnecessary drain on server resources when performance is already lacking.
The logic applied in improving performance is the same as waiting for 8 seasons for them to balance wraith and change her hitbox when anyone could have told them that's where the problem is. Then they release Horizon.. 😛@apostolateofDOOMI'm totally against butchering the game for the sake of esport level of performance. The vast majority of players don't care about that or don't have devices powerful enough to support it anyway. I would prefer them to keep experimenting stuff rather than prioritizing esports, which implies a lot of rigidity.
Respawn didn't "wait" for 8 seasons to nerf Wraith properly, they just had more important priorities and goals to achieve that go way back, well beyond the launch of Apex. Also, fiddling with a legend's hitbox after players have already put thousands of hours in mastering that legend is pretty dangerous, so it's understandable why they tried to avoid it for so long.
Community Highlights
- EA_Mako2 months ago
Community Manager
