Respawn programmer explained the real reason behind all the recent hit reg issues in Apex Legends

A Respawn dev finally explained how it happened

-

With the launch of the season 5 of Apex Legends, Respawn introduced us with “no reg” issues.

Apparently things got so bad that players would casually empty a whole clip into someone without even one bullet ever registering as a valid hit. After many complaints from the community, Respawn finally issued a client-side patch, that has allegedly fixed all the major hit detection issues.

Apex hit reg issues
Image Via EssentiallySports

However some players were still a bit curious about how these actually happened. So a Respawn programmer happily obliged and simply explained the whole scenario in an “explain to me like I’m 5” type of way.

Dev explained all the no reg issues

“The way it works is that you send an input to the game to “fire“. That input is processed on both your client, and the server (also known as prediction. The processing on the server is slightly delayed due to ping, which is where lag compensation comes in, but that’s another topic)

The client runs all of the same logic that the server runs for your position, the angle you fired at, projectile velocity, enemy location, etc… and determines that you hit your target. The client then plays blood effects, hit sounds, etc… Meanwhile, the server is running the same logic with the same parameters, and it’s expected that it will get the same result. Except with this bug, one of the variables used by the server and the client for the calculations was different, meaning the server was getting a different result, leading to no-regs. In APEX (and a lot of other games) certain parts of a hit are client side, (blood, audio) and certain parts are server side (crosshair “X” and damage numbers). You’ll notice that the X and damage numbers are always slightly delayed, depending on your ping.

As for lag compensation; when the server receives the “fire” command from the client, it also receives a timestamp that lets it determine where all of the relevant entities were on the client’s machine at the time they fired. The server then “rewinds” time for all of the entities to match the client’s view at that moment, and simulates all of the projectiles, movement, angles, etc… to determine if the client scored a hit.”, Respawn dev explained.

Thanks to the developers for explaining the ins and outs of how a bullet actually registers despite all the variables that exist when playing online. After learning how it actually works, it might give players a different perspective on how challenging game development really is. Therefore maybe next time we can all sit a little bit more patiently while the devs are doing their job.

LATEST

Riot Games plans to bring Volibear into a healthy, sustainable spot with patch 10.12 buffs

More Volibear buffs, bug fixes, and misc updates are incoming in the upcoming patch 10.12 in order to make his more healthy,...

Riot Games revealed 2020 Champion Roadmap featuring new jungler, assassin, and marksman

Buckle Up League of Legends fans, Riot Games is introducing three new champions in the 2020 Champion Roadmap featuring new jungler, assassin,...

Dr. Mundo Rework confirmed by Riot Games, hitting live servers in 2021

After Fiddlesticks and Volibear's rework, Riot Games confirms the next champion to get rework is Dr. Mundo. Today, on...

4 Microsoft Game Studios games on Steam’s Top Seller

4 of previously Xbox/Microsoft Store games is making it big on Steam. After a disappointing and a rough first...

FOLLOW US

419FansLike
143FollowersFollow