Hi
beta 5, 6.1
Just updated to 6.1, and our nuke renders are now failing due to our import calls in init.py trying to import from the Deadline path, ie the traceback lists:
File “C:\Program Files\Thinkbox\Deadline6\bin\lib\socket.py”
I thought this was the sort of thing 6.1 was meant to sort out…
From the readme:
- The slave now caches the system’s Python environment varilables (PYTHONHOME and PYTHONPATH) and passes them to the rendering process. This should prevent the slave’s Python environment from affecting the renderer’s Python environment.
If one didn’t have these variables assigned would that mean that deadline passes it’s own in their place? I haven’t done a print of the variables that init.py has visible as yet, that’s for the morning.
We have some slaves that are luckily still on 6.0, and they render the job fine so as long as they don’t update we’ll be ok.
cheers,
grant
Hey Grant,
This should be fixed in beta 6, which we’re going to try and release this week. It turns out that the slave is caching those python variables AFTER it has already modified the environment, which is why it ends up passing it’s own. This actually worked during testing, but then a somewhat unrelated change we made somewhere else before beta 5 was released broke it again.
Cheers,
Ok, though can I downgrade to beta 4 (ie you are saying it is new to beta 5?) , or should I roll back to 6.0 and just not render maya 2014?
thanks,
grant
Looks like clearing out those variables ourselves in the nuke.py sorted the issue out for us in beta 5.
thanks,
grant
Also, when starting monitor via a python call (with 6.1 beta 5) it’s printing:
Deadline Monitor 6.1 [v6.1.0.52776 R]
The current PYTHONPATH environment variable will be modified to avoid potential Python conflicts
Exception on Startup: Python Error: ImportError : DLL load failed: The specified module could not be found. (Python.Runtime.PythonException)
Can it could simply not mess with PYTHONPATH if it isn’t set?
thanks,
grant
The monitor error will probably also be fixed in beta 6. It looks like all the Deadline applications were fudging this up like the slave was.
That could definitely be an option if necessary. If you’re still having issues with beta 6 once it’s released, let us know and we can explore this.
Cheers,