

Use the sdb application found in Tizen SDK/tools directory with a trailing dlog parameter: The device log can be viewed by using the sdb console. DDMS also provides a number of other debug related tools. DDMS can be started either from Eclipse or from inside the Android SDK/tools. Use the adb application found in Android SDK/platform-tools directory with a trailing logcat parameter:Īnother way to inspect the LogCat is to use the Dalvik Debug Monitor Server (DDMS). The device log can be viewed by using the logcat console. The Troubleshooting and Bugreporting guides may be useful for you. The latter is useful for getting crashlogs when your application was not running through the XCode debugger. The device log can be accessed in XCode via GDB console or the Organizer Console. Note that on Windows and Linux standalones the location of the log file can be changed (or logging suppressed.) See the command line page for further details. On Windows, EXECNAME_Data is a folder next to the executable with your game. ~/.config/unit圓d/CompanyName/ProductName/Player.log On Windows the webplayer log is stored in a temporary folder: %TEMP%\UnityWebPlayer\log\log_UNIQUEID.txt, where TEMP is defined by GetTempPath. ~/Library/Logs/Unity/WebPlayer.log and Player.logĬ:\Documents and Settings\username\Local Settings\Temp\UnityWebPlayer\log\log_UNIQUEID.txtĬ:\Users\username\AppData\Local\Temp\UnityWebPlayer\log\log_UNIQUEID.txtĬ:\Users\username\AppData\Local\Temp\Low\UnityWebPlayer\log\log_UNIQUEID.txt On Mac 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. The editor log can be brought up through the Open Editor Log button in Unity’s Console window.Ĭ:\Documents and Settings\username\Local Settings\Application Data_\Unity\Editor\Editor.logĬ:\Users\username\AppData\Local\Unity\Editor\Editor.log On Windows the webplayer and editor logs are placed in folders which are not shown in the Windows Explorer by default. On Mac the webplayer, player and editor logs can be accessed uniformly through the standard Console.app utility. Usually you need to see these files when you have experienced a problem and you have to know where exactly the problem occurred. There might be times during development when you need to obtain information from the logs of the webplayer you’ve built, your standalone player, the target device or the editor.
