Unreal Engine

Introduction
Before integrating a new BugSplat SDK with your application, make sure to review the Getting Started resources and complete the simple startup tasks listed below.
​Sign up for a BugSplat account
​Log in using your email address
Create a new database for your application
Need any further help? Check out the full BugSplat documentation here, or email the team at [email protected].
Overview
BugSplat’s Unreal Engine integration supports most Unreal platforms including desktop computers, the Steam platform, and Linux servers. Support for additional platforms will be provided in the future.
Step 1
Sending crash reports to BugSplat can be done via a simple configuration change to Unreal Engine's CrashReportClient. To configure crash upload to your BugSplat database, create a file named DefaultEngine.ini with the following contents:
1
[CrashReportClient]
2
CrashReportClientVersion=1.0
3
DataRouterUrl="https://{database}.bugsplat.com/post/ue4/{appName}/{appVersion}"
Copied!
Replace {database}, {appName}, and {appVersion} with the names of your BugSplat database, application name, and version.
Remember the values you use for {database}, {appName}, and {appVersion}. You will need to use the same values when uploading Symbols in order to get crash reports with function names and line numbers in the call stack.
Unreal Engine 4.25 and older
For capturing crashes in packaged games in Unreal Engine 4.25 and earlier, copy DefaultEngine.ini to {{output directory}}\Engine\Programs\CrashReportClient\Config\NoRedist making sure to create folders that don't exist.
Unreal Engine 4.26 and newer
For capturing crashes in packaged games in Unreal Engine 4.26 and newer, copyDefaultEngine.ini to {{output directory}}\Engine\Restricted\NoRedist\Programs\CrashReportClient\Config  making sure to create folders that don't exist.
If DefaultEngine.ini already exists, add the snippet above anywhere in the file. There are multiple DefaultEngine.ini files in your tree, make sure you edit the right one otherwise crash reports will not be sent to BugSplat.
Step 2
Package your game, check that the Include Crash Reporter and Include Debug Files options are selected in your build configuration:
Integrating Unreal with BugSplat
UE4_PackagingSetttings
Step 3
To create symbolic call stacks on Windows platforms you will need to upload symbol and executable files. The easiest way to upload files is to use our SendPdbs command line utility. SendPdbs can be downloaded either by clicking here or via the SendPDBs doc. Run it from your build folder using the following commands.
1
cd {your build folder}
2
SendPdbs.exe /u {username} /p {password} /b {database} /a {appName} /v {appVersion} /s /f "*.pdb;*.dll;*.exe"
Copied!
Step 4
Run your game. For testing, a crash can be forced from the console using the command "debug crash". After posting the crash report, log in to BugSplat to view the report.
Step 5
Eventually, you will want to rebuild CrashReportClient so that its user interface describes the crash reporting changes above. However, this isn't required to successfully post crash reports.
Step 6
Special instructions for Linux servers:
Package the crash reporter with your Linux server build by adding the -CrashReporter flag to PackageBuildLinuxServer.bat
Force a test crash by running your server executable with the option -ExecCmds="debug crash"
Forwarding Crashes to Epic Games
If you'd like to forward crashes to the original DataRouterUrl specified in DefaultEngine.ini you can enable the Forward Crashes option under the Privacy tab on the Options page. Forwarding crash reports to Epic is useful when a crash in your game is caused by the underlying engine and you are working with Epic Games to resolve the issue. If the Forward to Epic option is enabled, an Epic Correlation-ID will be added to the description of all Unreal Engine crashes that were successfully forwarded to Epic.
PlayStation
Unity
Last modified 30d ago
Copy link
Contents
Forwarding Crashes to Epic Games