SUMMARYTo help rule out if a problem is due to a 3rd party kit, plug-in, or a user customisation, it is useful to see if the problem occurs in vanilla Modo.
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
macOS: 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
Please note that Modo 16.0v1 and above now have a configuration folder instead of an individual file.
Linux: /home/<USER>/.luxology/.modo16.1rc (this is a hidden file)
PLEASE NOTE: The config file is version specific e.g. the Modo 16.1v1 config folder is called MODO16.1.CFG.
macOS: /Users/<USER>/Library/Application Support/Luxology/Configs
macOS: /Users/<USER>/Library/Application Support/Luxology/Scripts
macOS: /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 occurs, please re-add your kits and plug-ins one by one until the problem reappears. This should help to identify what may be causing this issue.
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
We're sorry to hear thatPlease tell us why