Sometimes things don’t work how you expect them to. This page describes how you can retrieve logs to troubleshoot your app and request help.
OculusLogGatherer is included with every instance of the install and can be used when you have issues with the Oculus Run Time. Navigate to the .exe file and run the application (C:\Program Files (x86)\Oculus\Support\oculus-diagnostics\OculusLogGatherer.exe).
The application will launch and ask how much log data you want to export, the default is 24 hours. “Get All Logs” will export all available logs.
The export, a .zip file, will be copied to the clipboard and saved to your desktop. The .zip export organizes the files by log type.
If you're having issues with the Unity Editor, please review Unity's How to Report Bugs page for information about reporting bugs to Unity.
The Issue Tracker has information about known issues, check to see if what you are experiencing has already been reported. If the issue is not already known, you can report the bug in the Unity Editor (Help->Report).
Using Log Files
If your issue exists with the Unity/Oculus software integration, please review the Unity Log Files page for information on how to retrieve the logs.
The log file for your unity project can be retrieved by using the command %LOCALAPPDATA%\Unity\Editor\Editor.log.
If you experience a crash, retrieve the log and search for "tombstone", which is written and logged after the crash. If you scroll up from there, there will be a callstack, which describes the process that were occurring at the time of the crash.
Using Crash/Dump Files
When Unity or an app encounters a failed state, please ctr-alt-delete (windows only), right click on the failed process, and select "create dump file" from the menu. The dump file's location will be displayed to you upon successful creation.
If you're unable to diagnose the issue yourself using the information you retrieved, there are two ways to request help.