over 5 years ago - /u/Jayfresh_Respawn - Direct link

https://i.redd.it/bkzbs345apn21.png

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.

Those of you still experiencing crashes, please submit your apex_crash.txt file to our forums here: https://answers.ea.com/t5/Technical-Issues/Crash-after-update-Season-1/td-p/7704502. Our customer service team is helping us gather the info and it’s super helpful to our team.

External link →
over 5 years ago - /u/Scriptacus - Direct link

Originally posted by SamBBMe

Ayy that's why Im here lol

To clarify, crashed after the update, or because it was released while you were playing?

over 5 years ago - /u/Scriptacus - Direct link

Originally posted by naxiu

this update just caused my game to crash midgame, ironically :D

To clarify, crashed after the update, or because it was released while you were playing?

over 5 years ago - /u/Scriptacus - Direct link

Originally posted by puddledux

For the crash that you think you have a handle on, can we know what error code it was?

Biggest offender was the following, though some others are related and should be fixed as well.

R5Apex: 000000000035A6E6

EXCEPTION_ACCESS_VIOLATION(read): 0000000001000019

over 5 years ago - /u/Scriptacus - Direct link

Originally posted by orange0401

If this will be helpful, I’ve found a way to consistently crash.

If I tab out during legend select and tab back in during the transition banner from champion squad to being in the drop ship, the game will freeze during the closing of the rings on the 3 banners, audio will continue but not show anything that’s actually going on (jumpmaster quips, etc) for a few seconds then it kicks me out of the game.

Can you let us know if this happens after the patch?

over 5 years ago - /u/Scriptacus - Direct link

Originally posted by Yorunokage

After this patch the game consistently crashes after about 40 seconds from starting it :/

Can you send along crash logs?

over 5 years ago - /u/Scriptacus - Direct link

Originally posted by robertmt88

2 Games played since this update, 2 crashes within 1 minute.....

Can you send along crash logs?

over 5 years ago - /u/Scriptacus - Direct link

Originally posted by [deleted]

[deleted]

If a crash log was generated, can you send it along to me?

over 5 years ago - /u/Jayfresh_Respawn - Direct link

We'll do more in depth updates next week but wanted to touch on a few things I can speak to:

  • FPS capped to 144: It was the intent to cap to 300 but a bug is keeping it at 144. We're aware and looking into it and I'll provide an update when I can.
  • Hit reg issues: we are aware and testing a fix locally.
  • Audio issues - we've heard the feedback on numerous issues you folks have been reporting. Working with audio guys to address the stuff we can answer next week.
over 5 years ago - /u/Scriptacus - Direct link

Originally posted by GuardTheGrey

Not sure if this is something you guys can answer, but I'm really curious about how you keep 60 players synchronized.

The solution I've been able to come up with is that the one by players who are truly synched up are the ones closest to each other, since if you can't interact with a player you don't care if they're synchronized with you.

Or is the infrastructure you're running on so robust that you just don't care about the overhead of keeping everyone on the same page?

Generally speaking, it's fairly standard stuff across most games. Google "client server game architecture" for lots of info. Short version is, the server knows what each client was seeing and the time that they saw it; when the client sends input to the server, the server simulates the state as it was on the clients machine at the point the input happened.

over 5 years ago - /u/glutinousriceball - Direct link

Originally posted by SNAFUesports

Can we get no collision on the first 4-5 seconds of the starting drop? I know its not the most glamourous fix but should help until its fixed.

This is fixed locally. I''ll try to get it into the next patch.

over 5 years ago - /u/glutinousriceball - Direct link

Originally posted by SNAFUesports

Can we get no collision on the first 4-5 seconds of the starting drop? I know its not the most glamourous fix but should help until its fixed.

Yep, that's fixed locally. I'll try to get it into the next patch.

over 5 years ago - /u/thezilch - Direct link

Originally posted by GREE-IS-A-HEXAGON

Thank you so much. Genuinely. Been playing all night with zero crashes after weeks and weeks of crashing roughly 1/3 of my games. I can finally just PLAY. Thank you guys, awesome job.

🤘

over 5 years ago - /u/thezilch - Direct link

Originally posted by Martyks

Do you plan to add a option for the logs to be send to you right after they are being created via a button?

It's "planned", but we wanted to get this version out ASAP, as with just <100 reports that we got, we were able to narrow down the most significant culprit(s). If anything, we're hoping Origin can help aggregate it and other system information (eg. what other software is running, if the client so chooses to share it) that our game may not have a chance to capture. That is, when crashing (eg. OS ran out of memory), we can't do much without crashing the crash handler. Or if it's another process crashing (eg. GPU drivers, EAC, overlays, etc), it can take our process with it, and the game has no time or knowledge to capture that.

over 5 years ago - /u/Scriptacus - Direct link

Originally posted by QuincyB92

Going to fix window mode issue anytime soon?

What's the issue?

over 5 years ago - /u/Scriptacus - Direct link

Originally posted by alwysonthatokiedokie

I had this crash after the season 1 update but there was no crash log anywhere in my PC.

That's a different kind of issue. Those are usually triggered by bugs in the gameplay logic as opposed to hardware or memory issues.

over 5 years ago - /u/thezilch - Direct link

Originally posted by amrk94

How about the crashes without any information? It just shuts down without a reason. I’ve been on a holiday since you launched this and I just hope that I won’t crash anymore. Many people are complaining that they are crashing way more now compared to before.

Are you saying you are crashing without writing an apex_crash.txt? Writing this text file is different than not receiving a Windows dialogue with an error. That error is rarely useful to us, and as we know, Windows won't always show it. This is why we write the txt file that has useful information about what code was executing and is more reliably written when crashing.

over 5 years ago - /u/Scriptacus - Direct link

Originally posted by CaracolGranjero

I know you guys are very selective on what you reply to but can you at least let me know if you are aware of this? /u/Scriptacus

https://answers.ea.com/t5/Technical-Issues/AMD-Server-timeout-amp-crash-fix-fx-series/m-p/7496943#M25553

Can you summarize the issue, the thread is marked solved and it's kind of huge

over 5 years ago - /u/Scriptacus - Direct link

Originally posted by thpkht524

I have never crashed a single time before in apex, after hundreds of hours playing it. Crashed 3 times when I updated the game and played it yesterday.

Can you send along any crash logs?

over 5 years ago - /u/Scriptacus - Direct link

Originally posted by thpkht524

How do you get crash logs?

See the most recent patch notes for details. If they were generated, they'll be in your documents folder as apex_crash.txt

over 5 years ago - /u/Scriptacus - Direct link

Originally posted by thpkht524

I've found it. How do i send it to you?

You can just copy paste it here, it's pretty small