Topic: Crash uploader - how to check that it does its job
Battling game instability I have been referred a lot on to let a crash uploader to do its job so the devs know what they can try to fix. Sometimes when the game becomes unresponcive the main cocern is to reestablish the control to the agent (ie reconnect). However it seems that even when I let it crash "slowly" in a terribly controled way.
So what player behaviours can mess up the functionality of uploading crashes? Can I somehow check which crashes have been succesfully uploaded or not?
There are 2 big ways that perpetuum crashes for me. One is screen becoming totally unresponcive (freeze) and then turning a ligther shade as a pop-up window with "Perpetuum is not responding. Windows is checking whether the problem can be recovered from" with an indefinite progress bar and a cancel button. Soon this turns into "The program was stopped by an error" with "close program" button. Is this a controlled way of crashing or would the uploader itself crashing look also like this?
The second is having a "Visual C++ error" with "ok" which when pressed makes the program disappear and if not pressed in a midish amount of time leadds to before mentioned traditional crash.
I tried to look throught my firewall settings on whether I have blocked something relevant but nothing that would ring a bell hit my eye.