Verify your game cache: https://support.steampowered.com/kb_article.php?ref=2037-QEUH-3335

If you're using Windows and have Anti-virus software running, you may need to white list some files: http://wiki.gearcity.info/doku.php?id=troubleshooting:antivirus

If it still crashes after you have done those two things, please email me the log files after you crash: http://wiki.gearcity.info/doku.php?id=troubleshooting:steam_logfile

Two files failed validation, so that's probably it.

Be sure to revalidate if it crashes again, before white listing the files. In case it's AV software blocking the program.

I'm quite sure it's not an antivirus problem - there's no notification and no record of the antivirus doing anything. Silently killing programs or deleting files is not how it behaves.

I'm now very much doubting that it's a download problem, too, because it happened again (in the R&D screen of a new game, but it was the same sudden closure and similar log entries), I validated again, got the same 'two files failed' result...and found that it had 'validated' the log files back to the empty defaults.

So I currently have no log files to send, because validation got rid of them. When I get around to launching again I'll expect to generate and send in a log of the third recurrence of the crash. From looking at the now-erased files, it seemed to be some manner of rendering exception, but that's probably not enough detail to be useful.

Do be sure to whitelist the game in your AV software. The program communicates and manages a second executable file (CEF) via GearCity Help.exe. Anti-virus's do block such piped connections between multiple executable. Sometimes without notification, and many times without file removal. Typically they do this to prevent third party programs reading data from the real web-browser you use for every day browsing. When it blocks such communications, the game will crash.


If that fails to work, and after you send the logs, I may have you bounce over to the 32-bit build. A few nvidia cards have some issues with the 64-bit build. But either way, I'll need the log files to determine the cause. If I can...