There are several components that make up your MiddleVR application, and each one has a different log file:
- MiddleVR logs
- Unity logs
- MiddleVR license logs
Being able to read the logs of MiddleVR will greatly help troubleshoot a lot of the issues you might have.
There are two ways to find the folder that contains all the logs:
- Using the Configurator:
- Using the file explorer: simply type in the address bar: %tmp%/MiddleVR
Both methods will take you to the folder containing all MiddleVR logs:
- MiddleVR_Config_Log.txt: Log of the configurator tool
- MiddleVR_UnityEditor_Log.txt: Log of MiddleVR inside the Unity editor.
- MiddleVR_UnityPlayer_Log.txt: Log of MiddleVR inside the Unity player.
- MiddleVR_ClusterServer_Log.txt: Log of MiddleVR inside the Unity player for the cluster server.
- MiddleVR_Log_Client0.txt: Log of MiddleVR inside the Unity player for a cluster client. Note that Client0 will be replaced by the name of the client specified in the cluster configuration. Also note that the logs of the cluster clients are not centralized on the master and can only be found on the computer executing this cluster client.
- MiddleVR_License_Log.txt: Log of the licensing system.
You might also need to have a look at the logs of the Unity Editor.
- Windows 10, 8, 7 and Vista:
- Windows XP:
- C:\Documents and Settings\YOUR_USERNAME\Local Settings\Application Data\Unity\Editor.
Since Unity 2017.2, the logs are store here:
(Where CompanyName and ProductName are defined in your "Project Settings > Player" settings.)
For older Unity versions:
You can find the logs of a Unity player in its “_data” folder.If your application is called “Lawnmower.exe“, you fill find its logs in the “Lawnmower_data” folder, named “output_log.txt“.
Note that to enable Unity player logs, you have to make sure the option is enabled via the Player Settings > Resolution and Presentation > Use Player Log.
The license logs is automatically created in the same folder as the other MiddleVR logs. It is named: MiddleVR_License_Log.txt
You can set the LMX_EXTENDEDLOG environment variable to change this behaviour.
For example: LMX_EXTENDEDLOG=C:\temp\client.log