Deadline beta 3/Houdini noob Q

[bonsak]

Hi
I’ve never used Houdini with Deadline before so i’m not sure if this error is because i’ve not set up Houdini correctly. Haven’t used Houdini much either

[code]=======================================================
Error

Error in CheckExitCode: Renderer returned non-zero error code, 133. Check the log for more information.
at Deadline.Plugins.ScriptPlugin.RenderTasks (System.String taskId, Int32 startFrame, Int32 endFrame, System.String& outMessage, FranticX.Processes.AbortLevel& abortLevel) [0x00000] in :0

=======================================================
Type

RenderPluginException

=======================================================
Stack Trace

at Deadline.Plugins.Plugin.RenderTask (System.String taskId, Int32 startFrame, Int32 endFrame) [0x00000] in :0
at Deadline.Slaves.SlaveRenderThread.a (Deadline.IO.TaskLogWriter A_0) [0x00000] in :0

=======================================================
Full Log

0: Task timeout is disabled.
0: Loaded job: DSV_s01_003_v02.hipnc (52282926bd659353a53e6716)
0: INFO: Executing plugin script /Users/bonsak/Library/Application Support/Thinkbox/Deadline6/slave/Bonsak-work/plugins/Houdini.py
0: INFO: About: Houdini Plugin for Deadline
0: INFO: The current environment will be used for rendering
0: Plugin rendering frame(s): 0
0: INFO: Starting Houdini Job
0: INFO: Stdout Handling Enabled: True
0: INFO: Popup Handling Enabled: True
0: INFO: Using Process Tree: True
0: INFO: Hiding DOS Window: True
0: INFO: Creating New Console: False
0: INFO: Render Executable: “/Library/Frameworks/Houdini.framework/Resources/bin/hython”
0: INFO: Render Argument: “/Users/bonsak/Library/Application Support/Thinkbox/Deadline6/slave/Bonsak-work/plugins/hrender_dl.py” -f 0 0 1 -d /main_three_geo/ “/Volumes/PITLANE/… “bla bla bla” …/DSV_s01_003_v02.hipnc”
0: INFO: Startup Directory: “/Library/Frameworks/Houdini.framework/Resources/bin”
0: INFO: Process Priority: BelowNormal
0: INFO: Process Affinity: default
0: INFO: Process is now running
0: STDOUT: dyld: Library not loaded: @rpath/Houdini.framework/Versions/12.5.427/Houdini
0: STDOUT: Referenced from: /Library/Frameworks/Houdini.framework/Resources/bin/hython
0: STDOUT: Reason: image not found
0: INFO: Process exit code: 133

=======================================================
Details

Date: 09/05/2013 08:48:33
Frames: 0
Elapsed Time: 00:00:00:03
Job Submit Date: 09/05/2013 08:48:11
Job User: bonsak
Average RAM Usage: 14142414848 (42%)
Peak RAM Usage: 14142414848 (42%)
Average CPU Usage: 8%
Peak CPU Usage: 8%
Slave Name: Bonsak-work
Slave Version: v6.1.0.52340 R[/code]

The render argument works fine in the terminal:

/Library/Frameworks/Houdini.framework/Resources/bin/hython "/Users/bonsak/Library/Application Support/Thinkbox/Deadline6/slave/Bonsak-work/plugins/hrender_dl.py" -f 0 0 1 -d /obj/DSV_s01_003_v/main_three_geo/ "/Volumes/...  "bla bla bla"  .../DSV_s01_003_v02.hipnc"

Cheers
Bonsak

[MikeOwen]

Hi Bonsak,
Looks like the Python shipping with Deadline (DPython) is not playing nice with the default Python (Hython) that ships with Houdini. Looks like the same issue that was fixed in beta 3 for Maya needs to be done for Houdini as well? Maybe you could follow similar instructions here: viewtopic.php?f=156&t=10037
@Ryan - I wonder if any other applications which ship with their own Python have been knocked out as well but nobody has reported it yet?
Mike

[bonsak]

Hm. I thought i didn’t have to worry about the PYTHONPATH after beta 1 (viewtopic.php?f=84&t=9955&p=42866&hilit=pythonpath+osx#p42866)

-b

[rrussell]

I wonder if the solution here would be to cache the system’s PYTHONHOME and PYTHONPATH environment variables when Deadline Slave starts up, and then have the Slave push those variables to the rendering process that it starts up. This way, the Slave (or other Deadline applications) still won’t be affected by these variables if they are already set for the system, but then the rendering process would still start with the expected system environment. Of course, if PYTHONHOME and/or PYTHONPATH are specified in the job’s environment variables, they would still take precedence over the cached system variables.

This is probably something we could get working for beta 4 so you can test.

Cheers,

• Ryan

[bonsak]

Sounds good to me.

-b

[bonsak]

I’m trying to hardcode a quickfix for the path problem. I’ve added two lines to the Main Houdini submitscript:

[code]writer = open( tempFile, “w” )
writer.write( “Name=” + name )
writer.write( “\nFrames=” + frameString )
writer.write( “\nScene=” + hou.hipFile.name() )
writer.write( “\nRenderer=/out/” + renderer )
writer.write( “\nVersion=” + str(hou.applicationVersion()[0]) )
writer.write( “\nSaveIFD=” + str(ifdExport) )
writer.write( “\nIFDFilename=” + ifdFilename )

# Quick'n'dirty
writer.write( "\nEnvironmentKeyValue0=PYTHONPATH=/Library/Frameworks/Houdini.framework/Resources/bin/hython" )
writer.write( "\nUseJobEnvironmentOnly=true" )

writer.close()[/code]

But it doesn’t change anything when submiting. I’m obviously doing something wrong here

Cheers
Bonsak