Respawn Entertainment have released a major update in Apex Legends, and we're here to make sure you're caught up on everything there is to know.
The Apex Legends v1.13 update went live on May 20, implementing several fixes and improvements to core aspects of the game.
The full patch notes for the update had actually been revealed by Respawn several days prior, and nothing new was added when the update was officially released.
Audio has been one of the biggest inconsistent facets of Apex Legends, and this upcoming patch will work towards continuing to fix its issues and improve that aspect of the game overall.
According to the notes, the update will increase the volume of close proximity enemy footsteps, as well as lower the volume of the game during the sequence that starts with the character screen to the end of the drop sequence, which most players have complained about.
Another aspect of Apex Legends that has had its fair share of issues is hit detection, which Respawn had previously addressed several days prior.
Their announcement revealed that this upcoming update will include fixes that should take care of most instances where bullets were not registering properly.
In addition, the update will also feature tracking data for bullet damage, so that Respawn can better determine whether most of the issues are being caused by the coding or players' internet connection problems.
Below, you can find the full patch notes for today's update, as provided by Respawn in their May 17 Reddit post. At this point, it's not clear whether this will be the entirety of the notes, or if there will be more added once the update goes live next week.
AUDIO FIXES AND IMPROVEMENTS
One of our biggest issues to tackle was improving the audio performance to address issues reported of sounds dropping out, sounds missing for extended time, 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 for others, at least lower the amount and length of time they encounter audio issues.
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 of improvements we’ve included in today’s patch and we’re continuing to work on future improvements.
QUALITY OF LIFE
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 have put some time into refining 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 for us 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.
FIX FOR LIFELINE “PICK ME UP” BANNER BUG ON PS4
[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!
ADDITIONAL BUG FIXES AND CHANGES