Create a ticket
Follow

Q100035: Does your problem occur in Vanilla Modo?

SUMMARY

To help rule out if a problem is due to a 3rd party kit, plug-in, or a user customisation, it is useful to run Modo in vanilla mode. 
 
Starting with Modo 11, the safe mode functionality has been introduced which allows running Modo without loading any kits, plug-ins, or custom configurations. More information on using this can be found in the Q100288: Launching Modo in safe mode article. 

MORE INFORMATION 

NOTE: Before doing this, we would advise you backup all files and directories mentioned below.

The following steps will revert MODO to a freshly installed state.

  1. Close all instances of MODO on your machine.
  2. Reveal the hidden directories
    OSX: Finder->Home->Show View Options->Show Library Folder
    Windows: Windows Explorer->View->Options->View->Show hidden files, folders, and drives
  3. Remove or rename the Configs, Scripts and Kits directories and the configuration file found in the following places.

NOTE: Switch '<USER>' with your actual username

 

Configuration File:

Windows: C:\Users\<USER>\AppData\Roaming\Luxology\MODO10.2.CFG
OSX: /Users/<USER>/Library/Preferences/com.luxology.modo10.2
Linux: /home/<USER>/.luxology/.modo10.2rc (this is a hidden file)

NOTE: The config file is version specific e.g. the Modo 10.0v1 config file is called MODO10.0.CFG

Configs directory:

Windows: C:\Users\<USER>\AppData\Roaming\Luxology\Configs
OSX: /Users/<USER>/Library/Application Support/Luxology/Configs
Linux: /home/<USER>/.luxology/Configs

Scripts directory:

Windows: C:\Users\<USER>\AppData\Roaming\Luxology\Scripts
OSX: /Users/<USER>/Library/Application Support/Luxology/Scripts
Linux: /home/<USER>/.luxology/Scripts

Kits directory:

Windows: C:\Users\<USER>\Documents\Luxology\Content\Kits
OSX: /Library/Application Support/Luxology/Content/Kits
Linux: /usr/share/Luxology/Content/Kits

 

Now launch MODO and it will run as if it is a fresh install. If the problem no longer happens, please re-add your kits and plug-ins one by one until the problem reappears.  This should identify where the problem is occurring.

If the configuration file is the culprit, you can attempt to export config fragments before deleting the main config file, to keep certain settings such as hotkeys or layouts. Please see Q100182: How to export/backup MODO config fragments

 

FURTHER HELP

If you continue to encounter problems after performing these steps, please open a Support ticket and let us know the issue that you are encountering and the troubleshooting steps you have taken so far.

For more information on how to open a Support ticket, please refer to our article: Q100064: How to raise a support ticket 

 

 
Was this article helpful?

We're sorry to hear that

Please tell us why
6 out of 6 found this helpful