We didn’t experience any trouble publishing it to Steam, however we did have a number of required customizations to the framework such as adding 3d sound, full screen and mouse hover. We were able to get a lot of help from this forum with those features which have made our PC release go well.
Crashreporter is a win32 component that makes it very easy to get crash reports via e-mail. Those crash reports can be loaded in Visual Studio and debugged down to a line number, which makes fixing bugs much faster.
What’s your experience with Crashreporter? Do you have any numbers/statistics regarding the ratio of crashes and actual sent reports, which you are able to share?
Our experience with Crashreporter is great. On Steam, 82% of people who experience a crash report that crash to us via Crash Reporter. This can be good, this can be bad. Sometimes I wake up with 50+ e-mails from the same user with a broken video card driver. Around 30% of users submitting via CrashReporter send their e-mail and details about the crash.
On the games where we are deployed to Steam, iTunes, Amazon and Google Play we use statistical analysis and Google Analytics to measure cross-platform crash performance.
The least reliable way to collect crash reports is Google Play. It collects almost no useful crash reports. Google Play catches and stores the stack traces of less than 2% of all crashes that occur on Android. iTunes/Apple collects around 70%. HockeyApp collects around 94% when using the automatic submission system, and around 50% when using user-guided submission.
What this seems to indicate is
PC users are very accustomed to clicking the “Report Crash” button
Google Play cannot be trusted to measure application performance
Mobile users do not report crashes to developers as often when prompted
Automatic crash submission is good
Analytics and Crash Reporting are CRITICAL to a good user experience
After a few years of doing this full time, I can safely say that I would never even consider releasing a game without rock solid crash reporting and analytics to measure behaviors, crashes and quality events.