0
I have set the "NUKE_PATH" environment variable which is recognized and loads without issue when running nuke from an open terminal but when I submit a remote render job using RUSH, it is being ignored.
Even running Nuke in -V verbose mode from the terminal shows where it loads the environment variable and looking at the logs, that's being skipped when submitting remotely.
I have set the NUKE_PATH in the following 3 places:
- /etc/environment (NUKE_PATH=/path/to/scripts)
- ~/.bashrc (export NUKE_PATH='/path/to/scripts')
- ~/.bash_profile (export NUKE_PATH='/path/to/scripts')
None of these are being recognized with a command line execution of a render but all work fine in the GUI.
Any help would be greatly appreciated.