Table of Contents

Log Analysis on Windows

For logs on the native (Windows) and Unity Editor (Windows), refer to the following instructions.

How to Obtain Logs

If the program has a console, logs can be obtained from the console.

log Windows

Otherwise, you need to use Log.setLogFunc to redirect logs and provide your own method for outputting logs.

Unity Built-in Logs

When developing applications with Unity, in addition to the platform's native log analysis methods, the Unity Editor provides additional debugging tools.

Unity logs are divided into Unity Editor logs and Unity Player logs, which can be obtained through the following methods.

Unity Environment Operating System Log Location
Editor Windows %LOCALAPPDATA%\Unity\Editor\Editor.log
Player Windows %USERPROFILE%\AppData\LocalLow\CompanyName\ProductName\Player.log

Editor logs can also be opened via the Open Editor Log command in the upper-right menu of the Console window.

Understanding Logs

Generally, errors with an output level of Error (displayed in red) are more critical issues that require inspection. For example, below is an error indicating that the camera cannot be found.

log Windows error

When analyzing errors, it is often necessary to clarify the conditions under which the error occurred, such as the called function, parameters, and related states.

Notes When Providing Feedback

The following information must be included when providing feedback.

  • Version numbers of EasyAR Sense and EasyAR Sense Unity Plugin

    e.g., 4.7.0.11800-cf8e24e30

  • Community/Enterprise Edition

  • Platform

    Win32

  • CPU Architecture

    x86_64/x86