SUMMARY
This article will explain how to generate a log file for troubleshooting graphical errors in Modo. If you are seeing any artifacts in the 3D Viewport or any issues with the UI of Modo, you can manually generate a log file to send to us by launching Modo from a command line with several flags enabled.
This log file will capture information relevant to understanding the cause of the problem.
MORE INFORMATION
The commands listed below are examples you can run on each operating system, and they will create a text file on your Desktop called modoLog.txt.
This is the log file we require for troubleshooting a Modo crash report.
PLEASE NOTE: In the commands written below, replace the <username> field with your username (for example: /Users/Smith/Desktop/). Additionally, replace any instances of "##.#v#" with the current Modo version number (I.e. 16.1v7).
Windows:
For Modo 16.1v1 and above:
"C:\Program Files\Modo[version]\modo\modo.exe" -dbon:qt -dbon:ogl -dbon:gnz -dbon:agl -dblog:C:\Users\<username>\Desktop\modoLog.txt
For Modo 11.2v1 to 16.0v4:
Open the Command Prompt and run the following command:
"C:\Program Files\Foundry\Modo\[version]\modo.exe" -dbon:qt -dbon:ogl -dbon:gnz -dbon:agl -dblog:C:\Users\<username>\Desktop\modoLog.txt
For versions of Modo released prior to Modo 11.2v1:
Open the Command Prompt and run the following command:
"C:\Program Files\Luxology\modo\[version]\modo.exe" -dbon:qt -dbon:ogl -dbon:gnz -dbon:agl -dblog:C:\Users\<username>\Desktop\modoLog.txt
macOS:
Open Terminal and run the following command:
For 16.0v4 and below:
/Applications/Modo[version].app/Contents/MacOS/modo -dbon:qt -dbon:ogl -dbon:gnz -dbon:agl -dblog:/Users/<username>/Desktop/modoLog.txt
For 16.1v1 and above:
/Applications/Modo[version].app/Contents/MacOS/Modo[version] -dbon:qt -dbon:ogl -dbon:gnz -dbon:agl -dblog:/Users/<username>/Desktop/modoLog.txt
Linux:
Open a Terminal session and run the following command:
/usr/local/Modo[version]/Modo[version] -dbon:qt -dbon:ogl -dbon:gnz -dbon:agl -dblog:$HOME/Desktop/modoLog.txt
PLEASE NOTE: The examples above use the default installation paths for Modo. If you have a custom installation path, you will need to update the command including the correct location. You will also need to change [version] to the specific version of Modo that you are using.
NEXT STEPS
After launching Modo with these flags enabled, please continue to use Modo until the issue occurs. If it's a crashing issue a .txt report will be generated automatically, if it's not a crashing issue close Modo for this report to be generated.
Once this is done open a Support ticket and send us the modoLog.txt file generated together with the following information:
- Your system spec including graphics card and driver version
- Step by step instructions on how you are reproducing the crash
- The example .lxo file that you can reliably reproduce the problem with
FURTHER HELP
To send us this log file or if you encounter any issues performing the steps outlined in this article, then please open a Support ticket and let us know the issue you are encountering, and the troubleshooting steps you have taken so far. For more information on how to do this, please see the following article: Q1000064: How to raise a support ticket.
We're sorry to hear that
Please tell us why