What causes the extremely high package loss?
Anyone ever found out why you sometimes randomly have a game with a packageloss of 40-80%? Its always just for one game, everything before and after if perfectly fine
Forum Discussion
@hayhor If you regularly go down an abrupt unpaved road that's full of rocks, roots and pot holes with your small city car, I'm pretty sure you'll overheat the brakes badly and probably break some sensors as well, leading to a malfunctioning brake system in no time.
Most product developers are aware that at some point some people will accuse them for things that they didn't do or don't have control of. But that doesn't mean that they should take ownership of problems they don't have the ability or the permission to resolve.
Most product developers are aware that at some point some people will accuse them for things that they didn't do or don't have control of. But that doesn't mean that they should take ownership of problems they don't have the ability or the permission to resolve.
Also, here's a potential answer to why things seem to go south connection wise with almost each update.
Let's say that Apex regularly has 100-200K concurrent players on average. There are things that are tuned around these averages, for the optimal experience. Well, when there's an update, that number of concurrent players can go as high as 1-2 millions for a couple of days. This alone can cause congestion around the servers and also work bad with the configs that are made for much smaller values. Respawn tries to address these issues by adjusting the configs (e.g. increasing buffer sizes, change the way players are distributed across servers, data centers, etc.). These changes typically improve the stability, but they often alter the quality. This is a compromise, which usually stays in place until the average of concurrent players settles back down around the forecasted values.
