Normally, each user must configure the Nuke<>Mari bridge by copying files from their own Mari installation to their own local .nuke directory. The instructions to do that can be found in our documentation: Nuke <> Mari bridge Installation.
The following information shows the steps needed to setup the Nuke<>Mari bridge files in a network location accessible to all users, eliminating the need for configuring it on every single machine. The Python files that enable the Nuke<>Mari bridge just need to be somewhere in the user's
NUKE_PATHis an environment variable that points to the location where files related to Nuke customizations are stored. For more information, see Q100015: How To Set Environment Variables.
The standard .nuke folder in a user's home directory is the default location, but it only makes the Nuke<>Mari bridge available for that user. For more information about this directory, see Q100048: Nuke Directory Locations.
NUKE_PATHenvironment variable, you will need to do the following:
NUKE_PATHenvironment variable for the users so that it points to a central location. You may already have this set up for sharing other Nuke tools.
Media/Scripts/Nukesub-directory of the Mari install (or if you are on Windows, the
Bundle\Media\Scripts\Nukesub-directory) into the
NUKE_PATH. Please ensure that only one copy of each script is present.
If you are seeing any problems with getting Nuke<>Mari bridge to work, then please create a support ticket and provide us with the information requested in this article: Q100090: Reporting a Mari issue.
For more information on how to open a support request, please refer to this article: Q100064: How to raise a support ticket
We're sorry to hear thatPlease tell us why