Apex Legends March 22 update addresses crashing on PC – Patch notes
Respawn is looking to sort out problems with crashing on PC in Apex Legends and has now released a patch addressing those problems.
Apex Legends has a bit of a crashing problem on PC but Respawn is looking to iron that out with a patch.
A new patch was pushed through on March 19 and it was designed to capture information when the game crashes so the team is better able to identify the problems.
The release of Season 1 still hadn’t fixed many of the crashing issues Apex Legends players faced.The information was essential as the team was able to push another patch on March 22 that helped fix that issue and now Respawn things everything is solved.
If you’re on PC the patch is now live and it should address most of the concerns you had with crashing. It does require a client restart so you’ll have to get that out of the way first.
Apex Legends’ crashing problems are well documented on PC, almost as well as the hacking problems.
There are a variety of troubleshooting options you can go through to stop this problem but with the new update, it seems like you’ll no longer have to go through the trouble of doing that.
With the latest Apex Legends update, players should be able to get back to playing without experiencing many crashes.Respawn picked a good time to push this patch through as Season 1 is still in its infancy and you want to make sure all of the major game-breaking bugs are worked out before players buckle down for new content.
While there are still bugs to go through and fix, it looks like a major one is now out of the way with this update. Expect to see more fixes in an upcoming update, whenever that may be.
You can read the full post from Respawn about the update below:
March 22 Apex Legends Patch Notes
PC Patch Live Now: An Update on PC Crashes
Hey!
In the patch we released on Tuesday, we included a way to better capture information when Apex crashes on PC. The game should now write an apex_crash.txt file to your My Documents folder when it crashes. Since then we got many submissions of apex_crash.txt directly from our fans, searching the Internet, and from the forums.
The good news is they have been giving us great info and revealed a few crash locations, and we discovered that many of these are related. One of the issues appeared to be caused by one part of the program changing memory used by another part. These bugs are the most difficult to find!
As an analogy, imagine you’ve got thousands of robots tasked with painting different parts of an entire city, where each robot is given one of a dozen colors of paint. Occasionally, somebody complains that one of the rooms that was supposed to be red has some blue on the wall, but they don’t tell you which room. Based on that information, your job is to go fix it! This is why it’s been difficult to quickly identify, reproduce, fix, and test fixes.
But the apex_crash.txt files we got from players had a lot of information that we needed. In our analogy, those clues let our engineering team figure out which building had the bug, and a way to temporarily make the robots in that building a million times more likely to interfere with each other. We had never seen the crash in any of our internal testing before, but now we could finally reproduce the bug and that meant we could find it and fix it! To finish our analogy, our robots didn’t interfere even in this temporary test case, and we knew the bug was fixed.
A patch for PC is live now that includes a fix that when we tested locally, improved stability and you will need to update the client to grab it.
This is progress, but we don’t expect this patch to be the end all solution for all the crashes and we still have work to do. There are still some issues we’re seeing from the reports that we’re continuing to investigate to understand and address:
- Other crashes we’ve seen are related to out-of-memory issues. This is much less common. It’s not clear yet whether this is a memory leak in Apex or an improperly configured PC.
- There may be other, rarer crashes still to fix that we just haven’t identified yet.