Game Performance Reporting is a brand new service currently in preview. Exception Logging is one of the first features available with Game Performance Reporting. Exception Logging captures exceptions in editor, development builds and release builds, and provides detailed reports that can be read via a web dashboard.
Game Performance Reporting is currently in preview mode, to get your feedback on the features that will help you build great performing games. We plan to add additional performance reporting features in the future.
Who can use it?
Game Performance Reporting is currently available to Unity 5 Pro customers, at no charge.
For Unity 5.3 and before: Download and install the unity package from http://public.cloud.unity3d.com/UnityCrashLog.unitypackage
For Unity 5.4 and on, Game Performance Reporting is built into the editor. Just select it from the Services Panel to get started.
Click Getting Started on your recently created project for integration steps
What platforms are supported?
We currently support iOS, Android, Mac, Windows, Linux, and Web Player.
How long does it take to see our reports?
Depending on traffic, it should take no more than ten minutes for exceptions to be reported on the web.
How do I report a bug or issue with the Game Performance preview?
Feel free to post in the forum and we will respond to you as soon as possible.
Does Exception Logging currently only cover exceptions from managed code? If so, are there plans to have crash dumps from native code, and log files, available through the Game Performance Reporting system? Or, should I be looking at other Unity features to report crashes in native code to our servers?
Currently, yes, it only covers exceptions from managed code. We are looking at other types of data (logging, etc) to be added to the service, but currently it’s only managed code.
Cool. Yes we have Unity 5 Pro licenses… like 20 of them for the team. But our project is still 4.6.3. Going to be a few patch releases before our project is able to work in 5 probably.
I would like to see errors and warnings as well. Debug.LogError doesn’t look conceptually different from throw new Exception but doesn’t terminate code execution.
I have a question. In the CrashReporting.Init(“1”); you can provide three params (project ID, Version and user ID). Are Version and user ID already working as the ThrowMeAnException.cs example only shows usage for the 1st param.
We don’t populate the version and user fields in that script, but on the “Getting started” page for your project, we have an example you can use down at the bottom (Step 5)
