*Solved*... someone had a dev .bashrc file running that for whatever reason
did not appear in in my terminal.
On Tue, Feb 14, 2017 at 3:32 PM, Igor Majdandzic wrote:
> Or someone has been a naughty kid and wrote some code into the .py's in
> the app's installation folder.
>
>
>
Or someone has been a naughty kid and wrote some code into the .py's in the app's installation folder.Send from the RoadIgor MajdandzicCompositor, TD, Supervisor@Chimney FrankfurtAm 14.02.2017 3:29 nachm. schrieb Igor Majdandzic :So you've gone through all init.py's and menu.py's in
no init's or menu's, no python/startup's or startupui's
On Tue, Feb 14, 2017 at 3:29 PM, Igor Majdandzic wrote:
> So you've gone through all init.py's and menu.py's in the plugin paths?
>
>
> Send from the Road
>
> Igor Majdandzic
> Compositor, TD, Supervisor
> @Chimney Frankfur
So you've gone through all init.py's and menu.py's in the plugin paths?Send from the RoadIgor MajdandzicCompositor, TD, Supervisor@Chimney FrankfurtAm 14.02.2017 3:20 nachm. schrieb Fredrik Averpil :Perhaps there’s something in OFX_PLUGIN_PATH?
__
Not sure if Nuke looks at it but what about the good old PATH then?
___
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
Never thought of the OFX plugin path.. but sadly that ain't it.
On Tue, Feb 14, 2017 at 3:20 PM, Fredrik Averpil
wrote:
> Perhaps there’s something in OFX_PLUGIN_PATH?
>
>
> ___
> Nuke-python mailing list
> Nuke-python@support.thefoundry.co.uk, http:
Perhaps there’s something in OFX_PLUGIN_PATH?
___
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
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 happen
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
