I had a very similar problem last week, I checked the usual suspects in the environment variables and didn't find anything, then eventually found out the nuke.sh (Linux) had been modified to include plugins, so just launching a "nuke" command would load some plugins. That's probably not what happened to you as it's not very standard but worth a check.
On Feb 14, 2017 9:03 AM, "Mads Lund" <madshl...@gmail.com> wrote: > I have recently switched workstation, > > I started up by removing the .Nuke and .Hiero folder. > I deleted the HIERO_PLUGIN_PATH and the NUKE_PATH environment variables > Fresh reinstall of Nuke. > > Yet, for some reason nuke still loads a old custom plugin path into its > > hiero.core.pluginPath() list. > > > And I just can't figure where this custom path is being set. > > > Is there something that I have missed and/or is there a way to see where > Nuke will get its pluginpath list from? > > > > > > _______________________________________________ > Nuke-python mailing list > Nuke-python@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/ > http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-python > >
_______________________________________________ Nuke-python mailing list Nuke-python@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/ http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-python
