|
|
|
|
View Forum Thread
Anyone can view the forums, but you need to log in in order to post messages.
> Forum Home >
Support >
2015 Nuke module
|
|
Thu, 09/Apr/2015 9:19 AM |
Martin
69 Posts
|
I noticed different behaviour of our setup for Nuke renders.
After 2015 install I set path executable to my .bat file which handles version on Nuke to run and environment variables in System Command -> Configure Master -> Product Options
But Smedge is not running my batch but first Nuke.exe it finds on each node.
In log file I can see it searches for Nuke.exe when SmedgeEngine starts and it probably overrides my settings.
Engine log:
15.04.08 12:04:48.768 [ Info ] <0x00001884: System Thread> Nuke Module found executable: C:\Program Files\Nuke8.0v5\Nuke8.0.exe
My setup for Nuke executable:
\\server\path_to\smedge\Nuke.Hiero\Nuke.bat
but it renders using:
"C:\Program Files\Nuke8.0v5\Nuke8.0.exe" -X Write_dpx -m 12 -V -- P:\path_to\13_05_040_v001.nk 101,110
I tested UNC paths with smedge and it was working so this should be ok.
Still a bit unsure how to reach a clean system wide setup for different products.
|
| |
|
|
|
Tue, 14/Apr/2015 1:54 AM |
Robin
1138 Posts
|
Hi
You should be able to override the path that it automatically detected from the Configure Engine dialog. If it is not correctly over-riding, can you allow me to view the problem directly with remote support?
I will double check that the path system is working with Nuke. If I find anything I will post an update and get the problem resolved.
If you can set up remote support, please contact me at .
Thanks,
-robin
|
| |
|
|
|
|
. |
