There might be times during development when you need to obtain information from the logs of the standalone player you’ve built, the target device, or the Editor. Usually you need to see these files when you have experienced a problem, to find out exactly where the problem occurred.
On macOS, the player and Editor logs can be accessed uniformly through the standard Console.app utility.
On Windows, the Editor logs are placed in folders which are not shown in the Windows Explorer by default. See below.
To view the Editor log, select Open Editor Log in Unity’s Console window.
OS | Log files |
---|---|
macOS | ~/Library/Logs/Unity/Editor.log |
Windows XP | C:\Documents and Settings\username\Local Settings\Application Data_\Unity\Editor\Editor.log |
Windows Vista/7 | C:\Users\username\AppData\Local\Unity\Editor\Editor.log |
On macOS, all the logs can be accessed uniformly through the standard Console.app utility.
On Windows, the Editor log file is stored in the local application data folder <LOCALAPPDATA>\Unity\Editor\Editor.log, where <LOCALAPPDATA> is defined by CSIDL_LOCAL_APPDATA.
OS | Log files |
---|---|
macOS | ~/Library/Logs/Unity/Player.log |
Windows | _EXECNAME_Data_\output_log.txt |
Windows (Low Integrity Level) |
%USERPROFILE%\AppData\LocalLow\CompanyName\ProductName\output_log.txt |
Linux | ~/.config/unity3d/CompanyName/ProductName/Player.log |
On Windows, EXECNAME_Data is a folder next to the executable with your game.
Note that on Windows and Linux standalones, the location of the log file can be changed (or logging suppressed). See documenttion on Command line arguments for further details.
Access the device log in XCode via the GDB console or the Organizer Console. The latter is useful for getting crashlogs when your application was not running through the XCode debugger.
The Troubleshooting and Reporting crash bugs guides may be useful for you.
Access the device log using the logcat console. Use the adb application found in Android SDK/platform-tools directory with a trailing logcat parameter:
$ adb logcat
Another way to inspect the LogCat is to use the Dalvik Debug Monitor Server (DDMS). DDMS can be started either from Eclipse or from inside the Android SDK/tools. DDMS also provides a number of other debug related tools.
Access the device log using the Smart Devlopment Bridge console. Use the sdb application found in Tizen SDK/tools directory with a trailing dlog parameter:
$ sdb dlog
If you only want to see messages from Unity, you may add a filter. The filter specification is similar to that for Android. The following command only displays messages for the Unity log.
$ sdb dlog Unity:*
Device | Log files |
---|---|
Windows Store Apps (On desktop) | %USERPROFILE%\AppData\Local\Packages<productname>\TempState\UnityPlayer.log |
Windows Phone | Can be retrieved with Windows Phone Power Tools. The Windows Phone IsoStoreSpy can also be helpful. |
On WebGL, log output is written to the browser’s JavaScript console.
On Windows, the log files are stored in locations that are hidden by default. In Windows XP, make hidden folders visible in Windows Explorer using Tools > Folder Options… > View (tab).
On Windows Vista/7, make the AppData folder visible in Windows Explorer using Tools > Folder Options… > View (tab). The Tools menu is hidden by default; press the Alt key once to display it.
Is something described here not working as you expect it to? It might be a Known Issue. Please check with the Issue Tracker at issuetracker.unity3d.com.
When you visit any website, it may store or retrieve information on your browser, mostly in the form of cookies. This information might be about you, your preferences or your device and is mostly used to make the site work as you expect it to. The information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies. Click on the different category headings to find out more and change our default settings. However, blocking some types of cookies may impact your experience of the site and the services we are able to offer.
More information
These cookies enable the website to provide enhanced functionality and personalisation. They may be set by us or by third party providers whose services we have added to our pages. If you do not allow these cookies then some or all of these services may not function properly.
These cookies allow us to count visits and traffic sources so we can measure and improve the performance of our site. They help us to know which pages are the most and least popular and see how visitors move around the site. All information these cookies collect is aggregated and therefore anonymous. If you do not allow these cookies we will not know when you have visited our site, and will not be able to monitor its performance.
These cookies may be set through our site by our advertising partners. They may be used by those companies to build a profile of your interests and show you relevant adverts on other sites. They do not store directly personal information, but are based on uniquely identifying your browser and internet device. If you do not allow these cookies, you will experience less targeted advertising. Some 3rd party video providers do not allow video views without targeting cookies. If you are experiencing difficulty viewing a video, you will need to set your cookie preferences for targeting to yes if you wish to view videos from these providers. Unity does not control this.
These cookies are necessary for the website to function and cannot be switched off in our systems. They are usually only set in response to actions made by you which amount to a request for services, such as setting your privacy preferences, logging in or filling in forms. You can set your browser to block or alert you about these cookies, but some parts of the site will not then work. These cookies do not store any personally identifiable information.