Jump to content
Artaxiad300062

0.3 Update killed the game

Recommended Posts

1 hour ago, sivkon said:

Once the game crashes and we have the ability to send crash reports, does it send a dump / debug file with the text from the players or just the text that is written in the crash report? 

Answer for you and other people that know how this works: yes.

As for more detailed explanation for those interested:

It sends a .dmp file with the crash log (call stack) and saved variable state, so we know exactly which line of code is having problems and what was the state of the memory when it crashed. It also sends basic info about the PC (cpu, ram, windows version, gfx card and so on). We have all of them saved on our server and we check them periodically (takes some time, but it's totally worth it).

Some .dmp files are not as useful, especially very low level crashes, like physX or bugs with serialization, since we don't know which mesh or structure caused it. This is because when the game crashed, what was the cause was for example a list of vertices (so a mesh). We know why it crashed, but not which mesh it was - this is something that was happening on one of the maps for some time - we had a mesh that in certain situations would crash PhysX, but we didn't know which one it was, so we had to look around and try finding it more or less manually.

That said, with the description most people are filling out, it's not that bad 99% of the time.

  • Like 1
  • Thanks 2

Share this post


Link to post
Share on other sites
On 1/14/2019 at 6:25 PM, sivkon said:

Thanks for the info. One small question about the reporting:

Once the game crashes and we have the ability to send crash reports, does it send a dump / debug file with the text from the players or just the text that is written in the crash report? 

dump file is attached to the report

Share this post


Link to post
Share on other sites
Guest
This topic is now closed to further replies.

×
×
  • Create New...