MORE INFORMATION
The OFX API is an open C standard for visual effects plug-ins. It allows plug-ins written to the standard to work on any application that supports it, with hosts other than Nuke including tools such as Blackmagic's Davinci Resolve, Adobe’s After Effects, FilmLight's Baselight and more. More information about OFX can be found here: https://openeffects.org/
However, although these plug-ins should be universal across all OFX host applications, sometimes this is not the case, and plug-ins not designed to work with Nuke can end up causing issues.
When Nuke is launched outside of safe mode, the application will attempt to load all OFX plugins in the default OFX plugin folder, even if they were not built for Nuke.
Unfortunately, there is currently no built-in way to prevent Nuke from attempting to load all OFX plugins inside the default folder, even if they are incompatible with Nuke. However, we do have an existing feature request regarding this functionality.
You can refer to this feature request with the following ID when contacting Foundry Support, and please keep an eye on any upcoming Nuke Release Notes that may include this feature by referencing the ID:
ID 440827 - Add the ability to disable the OFX plug-ins directory in Nuke
RESOLUTION
You can follow the steps below if you would like to stop Nuke from trying to load the incompatible plugins while still being able to access these OFX plugins in other applications. However, please note that as this process involves third-party software and third-party plugins, we cannot guarantee whether they will continue to work as expected:
1) Firstly, move all incompatible OFX plugins to a new directory on your machine.
The default shared OFX plug-ins paths are:
Linux:
/usr/OFX/
macOS:
/Library/OFX
Windows:
C:\Program Files\Common Files\OFX
2) Set the OFX_PLUGIN_PATH environment variable on your machine and point it to the new folder containing the plugins. The OFX_PLUGIN_PATH environment variable is used by many different OFX host applications (including Nuke), but how it will interact with other applications and your OFX plugins may vary.
For more information about setting environment variables, please see the Support article below:
Q100015: How to set environment variables
3) Lastly, to prevent Nuke from loading OFX plugins in the new location, please add the following lines of code to your ~/.nuke/init.py file:
import os
os.environ['OFX_PLUGIN_PATH']=""This code will set the OFX_PLUGIN_PATH environment variable to a null location when launching Nuke, which means Nuke should not attempt to load the conflicting plugin(s).
FURTHER READING
For more information about the init.py file or the location of the ~/.nuke directory, please see the following Support articles:
Q100490: What are the init.py and menu.py startup script files
Q100048: Locating the default .nuke directory
Please find more information on loading OFX plugins in our online documentation here: https://learn.foundry.com/nuke/content/comp_environment/configuring_nuke/loading_ofx_plugins.html
We're sorry to hear that
Please tell us why