In case somebody else has this problem, this is the developers' reply:
To include the path into the template, you need to set it in the format:
SET ENVIRONMENT_BLOCK DERIVED , this goes into the ENGINE_WIN or
ENGINE_LINUX or ENGINE_MAC section,
then into the DECLARE CUSTOM_ENVIRONMENT
SET NUKE_PATH /the/path/to/nuke,
or batter making it configurable with
SET NUKE_PATH %ATTR(NUKEPATH)
and add into the DECLARE CONFIGURABLE_TAGS , a folder selector in the for of
ADD NUKEPATH FOLDER_SELECTOR "default/path" "description" NOTACTIVABLE
MANDATORY
On 29/05/12 1:00 PM, Frank Rueter wrote:
Hi guys,
sorry for the OT:
I'm currently at a company that uses Muster for rendering Nuke and I
am trying to figure out how to tell Muster about the NUKE_PATH.
I've tried setting it in the Nuke template like this:
...
DECLARE CUSTOM_ENVIRONMENT
{
SET NUKE_PATH "/path/to/nuke/stuff"
}
...
I've also tried:
DECLARE CUSTOM_ENVIRONMENT
{
SET PATH=NUKE_PATH "/path/to/nuke/stuff"
}
...
and:
DECLARE CUSTOM_ENVIRONMENT
{
MAP NUKE_PATH "/path/to/nuke/stuff"
}
None of the above seem to have any effect on the environment of the
render clients.
I can't find any flags in the help to set a custom environment on
submission time (via mrtool) either.
does anybody have an idea what I'm missing?
Cheers,
frank
_______________________________________________
Nuke-users mailing list
[email protected], http://forums.thefoundry.co.uk/
http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
_______________________________________________
Nuke-users mailing list
[email protected], http://forums.thefoundry.co.uk/
http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
