I need to set a per render node parameter for Nuke.
I have tried setting this in the setup_nuke.cmd
SET NUKE_AF_RENDER="nuke -i -m 2"
but this is ignored.
The command seems to be set by the submission
eg. block1.setCommand('nuke -X Write1 -F @#@-@#@ -x "X:\Test\RenderTest.nk" ')
on a Windows7 workstation.
Working well otherwise.
Michael
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Actually, I need to set this on a per render node basis. Some machines work better with different threads. I also want to be able to set workstations to use their Interactive license vs. a render license. ("nuke -ix" vs. "nuke -x"). Won't setting this in the job submission force it for every machine?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Such feature is not implemented (yet).
But in future plans it will be.
Each render can have some custom data, and that data can be used in service python class in any custom way. And that python class can change task command.
Right now there are already service python classes. You can write custom service service class - create your own unique service. That service class can identify a machine and change task command in your own way.
There is a lack of documentation http://cgru.info/afanasy/doc/services.html
But you can look at that base class code.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I need to set a per render node parameter for Nuke.
I have tried setting this in the setup_nuke.cmd
SET NUKE_AF_RENDER="nuke -i -m 2"
but this is ignored.
The command seems to be set by the submission
eg. block1.setCommand('nuke -X Write1 -F @#@-@#@ -x "X:\Test\RenderTest.nk" ')
on a Windows7 workstation.
Working well otherwise.
Michael
Hi. Afanasy nuke gizmo will launch a script:
... cmd = os.getenv('NUKE_AF_RENDER', 'nuke -i') ... cmd += ' -X %s -F@#@-@#@x%d -x \"%s\"' % ( self.writename, self.frameinc, scenename) ...Also you can try to use variable capacity (but it is not well tested, as used rarely).
Standalone dialog has "Extra Arguments" parameter and a more global "Tasks Command" field, where you can specify your custom .cmd (.sh) file.
Actually, I need to set this on a per render node basis. Some machines work better with different threads. I also want to be able to set workstations to use their Interactive license vs. a render license. ("nuke -ix" vs. "nuke -x"). Won't setting this in the job submission force it for every machine?
Such feature is not implemented (yet).
But in future plans it will be.
Each render can have some custom data, and that data can be used in service python class in any custom way. And that python class can change task command.
Right now there are already service python classes. You can write custom service service class - create your own unique service. That service class can identify a machine and change task command in your own way.
There is a lack of documentation http://cgru.info/afanasy/doc/services.html
But you can look at that base class code.
I did it by setting
SET NUKE_EXEC=%NUKE_DIR%\"Nuke6.3.exe -i"
in the software_setup/setup_nuke.cmd