SUMMARYTo 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.
PLEASE 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.
- Close all instances of MODO on your machine.
- 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
- Remove or rename the Configs, Scripts and Kits directories and the configuration file found in the following places:
PLEASE NOTE: Switch '<USER>' with your actual username
Linux: /home/<USER>/.luxology/.modo10.2rc (this is a hidden file)
PLEASE NOTE: The config file is version specific e.g. the Modo 10.0v1 config file is called MODO10.0.CFG
OSX: /Users/<USER>/Library/Application Support/Luxology/Configs
OSX: /Users/<USER>/Library/Application Support/Luxology/Scripts
OSX: /Library/Application Support/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
Keywords: Modo bug, problem, issue, config, kit, plugin