Apex Legends’ latest patch is here and while it’s fairly light on content, there are quite a few important quality of life improvements to the game.
The most important change in patch 1.1.3 is all about hit detection. Hit detection determines whether or not fired bullets hit a target. With any online game there’s bound to be a problem or two with how the hit detection works, since it has to be accurate for every player in the game, no matter their location and connection. But Respawn Entertainment’s goal with this patch is to get it as close to accurate as possible. To help with this Respawn also introduced a new diagnostic system that should help them fix future hit detection issues.
“One potential cause of hit registration bugs can be simple internet connection problems. In order to determine how much of a factor this is in reality, we’ve refined the functionality behind our network problem indicator icons in the upper right of the screen. These icons are now pickier about your connection quality and may show up more frequently than they did before,” Respawn said in the notes for patch 1.1.3.
This patch also brings a few other welcome changes. Footstep volume has been updated to better convey distance with closer footsteps playing louder than they used to. Even better, enemy footsteps are now prioritized over ally footsteps, so it should be a lot harder for people to sneak up on you. The patch also updates the “no ammo” and “low ammo” sound effects for certain guns, including the R301, Hemlock, Flatline, and RE45, which were very quiet before.
To see all the changes that have been added with Apex Legends patch 1.1.3 you can see the full patch notes below.
- Improved audio engine to be around 30% more CPU efficient, lessening the chance of distortion or dropouts.
- Lowered impact on data loading through code and content changes to improve potential dropout issues.
Quality of Life
- Lowered the master volume of all sounds during the character select screen through the end of the drop sequence.
- Lowered the volume of Wraith’s ambient kunai knife sound for those who are sensitive to the sound. If it is still bothersome we will remove it in a later patch.
- Increased the volume of close proximity enemy footsteps for all Legends.
- Increased the priority of enemy footsteps to ensure the sounds play even in heavy combat situations.
- Slightly lowered the volume of Pathfinder footstep sounds heard from the first person view.
- Fixed missing or quiet dryfire (out of ammo trigger click sound) and low ammo (the progressive change in sound that the gun makes as the magazine approaches empty) sounds for the R301, Hemlok, Flatline, and RE45.
- Increased the volume of the music that plays when winning a match.
- Added more detailed audio to the Training mission.
Audio Fixes and Improvements
One of the biggest issues we had to tackle was improving the audio performance to address reports of sounds dropping out, missing sounds for an extended duration, or distortion for a period of time. We have made improvements both in our code and with our content that will hopefully fix these issues for many players, and should lower the amount and length of time they encounter audio issues for others.
We have also addressed some of the other mix issues with the game, including increasing the volume of close proximity enemy footsteps and lowering the overall volume of the game from the character select screen to the end of the drop sequence. We will continue to monitor mix issues and address them as necessary. Below are the notes on improvements we’ve included in today’s patch as we continue to work on future improvements.
- Fixed occlusion bug for the Havoc’s “wind down” sound.
- Fixed issue with automatic weapon fire sounds occasionally getting stuck on, usually after a Legend respawns.
- Fixed bug with RE45 missing tail sounds (the echo in the environment after the shot) when in close proximity.
Hit Detection Fixes and Improvements
As we talked about last week, in this patch we’ve pushed some fixes that should eliminate many cases of incorrect hit registration. This patch also includes some behind-the-scenes tracking of bullet damage logic. We expect there will still be some remaining hit registration problems, but with these fixes and diagnostic information, we are better equipped to track them down.
One potential cause of hit registration bugs can be simple internet connection problems. In order to determine how much of a factor this is in reality, we’ve refined the functionality behind our network problem indicator icons in the upper right of the screen. These icons are now pickier about your connection quality and may show up more frequently than they did before.
These icon changes will be useful in narrowing down the cause of any bugs that we continue to see. Please continue to share videos and report hit registration issues you still encounter after the patch.
Additional Bug Fixes
- Fixed issue with the Fortified Passive ability for Gibraltar and Caustic where they would take damage through shields.
- Fixed the bug that allowed players to stick objects to Gibraltar’s Gun Shield.
Admittedly, it’s been fun to see the results of this, but the behavior is not intended by design and could get out of control. Items will no longer stick to Gibraltar’s Gun Shield. However, it will now deflect Arc Stars.
Fix for Lifeline “Pick Me Up” Banner Bug on PS4
The issue has been resolved and we will be re-enabling the banner after the patch is live.
- NOTE: We made changes to client and backend to address this, and it’ll take a little time to take full effect. We’re expecting the error to resolve within a few hours after the patch is live.
[PC ONLY] Crashes specific to Intel CPUs
We investigated the crash reports from many people who were crashing frequently and found that Intel CPUs sometimes were not executing the instructions properly in one particular function. A common example was an instruction that only reads a register crashed on writing to invalid memory. With the help of many forum users, we found that lowering the clock speed always fixed the crashes, even if the CPU wasn’t overclocked or overheating. Thanks everyone, with a big shout out to Falkentyne, TEZZ0FIN0, JorPorCorTTV, and MrDakk!
This has been by far the most commonly reported PC crash over the last month or so and we’ve notified Intel about the issue. In the meantime, we’ve put a workaround in this patch to avoid the crashing at your original clock speeds just by changing the instructions used by that one function.
Please continue to send your crash logs to our forums so we can analyze and fix any issues you encounter!