Can't Save Prefs In Nuke 4.7

[thedott]

Hey folks, we are now running Nuke 4.7 here and there is an odd behavior, we can't save our prefs anymore. We get a message of "Can't create U://.nuke". Nuke 4.6 saved to:

C:\Documents and Settings\user.nuke

This new version doesn't seem to save a prefs file anywhere. I looked in the release notes and it says that there is a change in behavior with the prefs for Nuke 4.7 and the new prefs file is called "preferences4.7.nk" while the old one didn't have a version number. Uh, but it's not saving at all anymore.

Anybody else have this issue? Find a way around it?

Barry

[user_deleted]

mine kinda works ok, it now saves it into my ~/.nuke/tcl-commands/ directory where before it would just save to ~/.nuke I think.
Do you have any environment variables set pointing to "U:/"?
what do you get when you hit x in Nuke and type "getenv home" and "plugin_path"?

[thedott]

Thanks Frank, this is pretty annoying since this didn't happen in 4.6. I tried those scripts and I get the following results.

getenv home gives me:

U:\

plugin path gives me:

{C:/Program Files/Nuke4.7v1/plugins}
{C:/Program Files/Nuke4.7v1/plugins/icons}
{C:/Program Files/Nuke4.7v1/plugins/user}
{C:\Program Files\Common Files\OFX\plugins}
U://.nuke

Any ideas as to what to direct my IT guys to fix there?

Barry

[user_deleted]

there is your answer. for some reason your home path is "U:". Do one of the following:

A: change the HOME env variable to "C:\Documents and Settings\user\" (unless of course this is your proper pipeline set up)
B: In U:/.nuke create a text file called init.tcl that contains the line (without the arrow heads)
C: set up an env variable called NUKE_PATH with the value of "C:\Documents and Settings\user.nuke"

I would personally recommend having a user home dir that people can save their preferences and stuff in (if this is U:/ I'd actually use that), then have a company wide repository that you point to withe the NUKE_PATH as outlined in option C.

This should all be backward compatible.

cheers,
frank

[goee]

Here I have set the NUKE_PATH to "D:\Prefs\Nuke" and the HOME is set to the default place "C:\Documents and Settings\%USER%\Application Data"

In that preferences folder I have the following structure

fonts
gizmos
icons
plugins
tcl_commands
formats.tcl
init.tcl
menu.tcl

init.tcl is basically this

CODE
    plugin_addpath [file dirname $program_name]/plugins
    plugin_addpath "D:/Prefs/nuke/gizmos"
    plugin_addpath "D:/Prefs/nuke/icons"
    plugin_addpath "D:/Prefs/nuke/plugins"
    plugin_addpath "D:/Prefs/nuke/tcl-commands"
    plugin_addpath "G:/Projetos/[getenv JOB]/Comp/Gizmos/"

And on the menu.tcl I have

CODE
load [file dirname $program_name]/plugins/menu.tcl

as my first line so menus load on the correct order plus all the custom menus and default knob values.

By the way does anyone know how to effectively use Enviroment Variables to store project data?

[user_deleted]

Hi Diogo,

you shouldn't need these anymore if you're on 4.6 or later:
plugin_addpath [file dirname $program_name]/plugins
load [file dirname $program_name]/plugins/menu.tcl

That should be fixed now.

Another small tip:
You can use relative paths like
plugin_addpath ./gizmos
instead of
plugin_addpath "D:/Prefs/nuke/gizmos"

which makes it easier should you ever move stuff or rename directories.

By the way does anyone know how to effectively use Enviroment Variables to store project data?
Looks like you're already doing that with your JOB variable.
You can simply extend this by using more variables that hold values for all sorts of project related infos (scene, shot, frame range, etc..). I guess the trick is to have a helper application that sets all these environment variables for you when you tell it what shot you are going to work on. Of course this requires a bit of data base management.
Is that what you meant or am I talking crap?

cheers,
frank

[goee]

Hi Frank,

QUOTE
You can use relative paths like
plugin_addpath ./gizmos

This will be relative to my HOME or to my NUKE_PATH?

I'm lost 8)

QUOTE
You can simply extend this by using more variables that hold values for all sorts of project related infos (scene, shot, frame range, etc..). I guess the trick is to have a helper application that sets all these environment variables for you when you tell it what shot you are going to work on. Of course this requires a bit of data base management.
Is that what you meant or am I talking crap?

No man, you're not talking crap, it's exactly that. For now I'm using the setx command from the Windows Resource Kit to manage this variables in a very primitive way but the problem is that these variables persist during a session so I have to logoff/login to have them updated. But probably I'm the problem

Maybe retrieving this data from a MySQL database would be smarter and easier to manage using a PHP front. Have you tried anything in that sense?

Thanks for you feedback man

[user_deleted]

This will be relative to my HOME or to my NUKE_PATH?
relative to where the init.tcl lives that carries those lines.

I don't know much about MySQL and PHP, I just hook up to whatever is out there via tcl and suck all the info out of it that I need .

the whole environment variable thing is way easier to deal with on linux than on windows and I don't know if you can just swap sets of environment variables via a helper application without having to log in again. It should be possible but having workd on linux for the past few years I'm a bit out of my depths here, sorry.

[goee]

Hi Frank,

Thanks a bunch for all the help.

I think that the environment variables in windows have some limitations if compared to Linux, I'll look deeper on that.

Cheers,
diogo