AWS Thinkbox Discussion Forums

Houdini 19 Support

Ok, thanks for the info everyone

i just notice that you have an exception, and as i remember it happen to me too, the issue is with the path, looks like the deadline cant find the files location/destination and its crashing, so i used the py from some ver of deadline from few years ago that works :frowning: dont know whats going on and why they didnt fix this issue

It can be many things, such as wrong references to external files, locked nodes that need to be modified, etc.

Hi Bazuka,

The link has expired could you repost this please/?> manny thanks

@dani_macovei mate the mirrorlinks are still working grab that one

is there any changes in that link other than the .param file?

Looking forward to the fully supported version of Deadline that’ll work with 19 along with all py2 and py3 versions.

Am also hoping the other issues with Houdini will be fixed too

  • The issue with $ names (I think there are other variables issues elsewhere too)
  • There is an issue with Frame Ranges in submission

I’m not sure if this is another issue, as 19.0.455 py3 & 10.1.20 I don’t have this issue

  • Be great to see the new license env var implemented into Deadline
  • This Redshift progress improvement that’s been written for you
  • Tiled render in redshift, or tiled render as part of the export to .rs process

https://redshift.maxon.net/topic/30971/houdini-tile-rendering-with-asw-deadline

  • Getting some kind of husk implementation?

Sure there are lots more Houdini bug fix / feature requests?

1 Like

It worked in the end. I had to go all the way down to find one that worked. Thanks!

I’ll hijack the thread just to mention, that there are so many contributions from the community that have to be scoured from the forum, instead of making it into a git repo that everyone can use, choose what to merge, etc.
There are a lot of improvements that someone made for themselves, missed because there is no way to upstream them. That’s a lot of loss of potential.
I guess there might be licensing concerns, but the plugins can be with a proprietary license and still receive outside contributions? A private git repo for customers is also an option, if public repos are out of the question.

1 Like

is it supported in 10.1.20.3? I guess not, I see nothing in the release notes about it. It’s a bit of a bummer how behind deadline gets.

Still looking forward to the official 19 release.

fingers crossed the integrated submitter will work too, I’m still getting clients having the deleted submission folder in the repo, having failed installed regardless of choice on the automated installer. It’s not really clear what the difference between ‘bundled’ and ‘repo’ version are, surely they’re all from the repo?? Also the all users / local user still fails on many versions of the installer.

I usually advise the manual route but even the documentation is a bit off with this

https://docs.thinkboxsoftware.com/products/deadline/10.1/1_User%20Manual/manual/app-houdini.html#manual-installation

Surely the second step should point to the file rather than the folder? feels a bit unclear

~/Thinkbox/Deadline10/submitters/HoudiniSubmitter/DeadlineHoudiniClient.py

so not sure why the docs miss off the python file? I’ve seen this catch a few people out

I have a better solution: use a json package, it’s so convenient for deployment!
In $HFS/packages create a file deadline_submitter.json (the name does not really matter) and in it enter

{
    "env": [
        {"SUBMITTER_ROOT": "C:/Program Files/Common Files/Houdini/HoudiniSubmitter"},
        {"PATH": "${SUBMITTER_ROOT}"},
        {"HOUDINI_MENU_PATH": "${SUBMITTER_ROOT}"},
        {"PYTHONPATH": "${SUBMITTER_ROOT}"}
    ],
    "path": [
        "${SUBMITTER_ROOT}"
    ]
}

and voila!

the deadline json file is quite nice, and OS specific, but I have the feeling it doesn’t always work.

{
    "env": [
        {
            "DEADLINE_SUBMITTER_DIR": [
                {"houdini_os == 'windows'" :"$HOME/houdini/deadline/HoudiniSubmitter" },
                {"houdini_os == 'linux'" : "$HOME/Thinkbox/Deadline10/submitters/HoudiniSubmitter"},
                {"houdini_os == 'osx'": "$HOME/Library/Application Support/Thinkbox/Deadline10/submitters/HoudiniSubmitter"}
            ]
        },
        {
            "HOUDINI_PATH": "$DEADLINE_SUBMITTER_DIR"
        },
        {
            "HOUDINI_MENU_PATH": "$DEADLINE_SUBMITTER_DIR"
        }
    ]
}

It does work, but there might be an environment issue on your setup. e.g. is $HOME set? Note that my json has one or two additional fields.

I can get it to work, I just have many people reporting issues with their set-ups for various reasons.

I checked a recent install and it seemed to drop the ‘packages’ json file into /var/lib even though it was for a local user and not global (all) users.

image

You can’t run this as a standard user, you need to be root, so the bits you need go to the root home dir or /var/lib?

It should be possible to install this without root access? similar to nuke and maya?

Is there any reference in the docs to the difference between ‘bundled’ and ‘repo’ versions of the submitter?
https://docs.thinkboxsoftware.com/products/deadline/10.1/1_User%20Manual/manual/quick-install-submitters.html

My issue here is the automated installer should make it easier for those who want to use the auto installer and aren’t using custom/centralised plugins or installing manually etc

Hi Everyone.

I am very new to deadline and Houdini but I have the task of making H19 py2 work on my enviroment.

I am on version 10.1.19.4 and I have updated my repositor files based on bazuka’s upload on this page here.

I have installed 19.0.455py2 and added the paths to the plugin configuration in deadline.

When we try to render anything this is the following error

2022-03-22 12:04:35: 0: STDOUT: Your current job config is: 25.00fps
2022-03-22 12:04:35: 0: STDOUT: I am setting this scene to the job framerate
2022-03-22 12:05:00: 0: STDOUT: Detected Houdini version: (19, 0, 455)
2022-03-22 12:05:00: 0: STDOUT: ['C:\\ProgramData\\Thinkbox\\Deadline10\\workers\\gpu-A02-b\\plugins\\6239a1045c05bb21e03b8dcf\\hrender_dl.py', '-f', '1001', '1001', '1', '-o', '$HIP/render/$HIPNAME.$OS.$F4.exr', '-d', '/out/Redshift_ROP1', '-gpu', '1', '-tempdir', 'C:\\ProgramData\\Thinkbox\\Deadline10\\workers\\gpu-A02-b\\jobsData\\6239a1045c05bb21e03b8dcf\\0_templVXMk0', '-arnoldAbortOnLicenseFail', '1', '//flabby/jobs/dev_julian_9993/films/test_film/shots/010/scenes/render/main/test_film_010_render_main_v017_julian.hip']
2022-03-22 12:05:00: 0: STDOUT: Start: 1001
2022-03-22 12:05:00: 0: STDOUT: End: 1001
2022-03-22 12:05:00: 0: STDOUT: Increment: 1
2022-03-22 12:05:00: 0: STDOUT: Ignore Inputs: False
2022-03-22 12:05:00: 0: STDOUT: Output: $HIP/render/$HIPNAME.$OS.$F4.exr
2022-03-22 12:05:00: 0: STDOUT: GPUs: 1
2022-03-22 12:05:00: 0: STDOUT: Driver: /out/Redshift_ROP1
2022-03-22 12:05:00: 0: STDOUT: Input File: //flabby/jobs/dev_julian_9993/films/test_film/shots/010/scenes/render/main/test_film_010_render_main_v017_julian.hip
2022-03-22 12:05:07: 0: STDOUT: Error: Caught exception: The attempted operation failed.
2022-03-22 12:05:07: 0: STDOUT: Error loading: //flabby/jobs/dev_julian_9993/films/test_film/shots/010/scenes/render/main/test_film_010_render_main_v017_julian.hip
2022-03-22 12:05:07: 0: STDOUT: Warning: Bad node type found: Redshift_ROP in /out.
2022-03-22 12:05:07: 0: STDOUT:
2022-03-22 12:05:07: 0: STDOUT: /out/Redshift_ROP1:
2022-03-22 12:05:07: 0: STDOUT: Unknown channel(s) "f[12]" converted to spare parameter(s).
2022-03-22 12:05:07: 0: STDOUT:
2022-03-22 12:05:07: 0: STDOUT: /out/Redshift_ROP1:
2022-03-22 12:05:07: 0: STDOUT: Skipping unrecognized parameter "RS_IPR".
2022-03-22 12:05:07: 0: STDOUT: Skipping unrecognized parameter "RS_IPRRV".
2022-03-22 12:05:07: 0: STDOUT: Skipping unrecognized parameter "RS_IPRVP".
2022-03-22 12:05:07: 0: STDOUT: Skipping unrecognized parameter "renderpreview".
2022-03-22 12:05:07: 0: STDOUT: Skipping unrecognized parameter "trange".
2022-03-22 12:05:07: 0: STDOUT: Skipping unrecognized parameter "f".
2022-03-22 12:05:07: 0: STDOUT: Skipping unrecognized parameter "take".
2022-03-22 12:05:07: 0: STDOUT: Skipping unrecognized parameter "RS_separator_rrs2".
2022-03-22 12:05:07: 0: STDOUT: Skipping unrecognized parameter "RS_rrs2".
2022-03-22 12:05:07: 0: STDOUT: Skipping unrecognized parameter "RS_mainSwitcher".
2022-03-22 12:05:07: 0: STDOUT: Skipping unrecognized parameter "RS_group_mainTabSwitcherCameras".
2022-03-22 12:05:07: 0: STDOUT: Skipping unrecognized parameter "RS_renderCamera".
2022-03-22 12:05:07: 0: STDOUT: Skipping unrecognized parameter "RS_group_mainTabSwitcherCamerasRO".

this log goes on and on.

I have uploaded the full log here in case anyone wants to see it: CodePile | Easily Share Piles of Code

now , can anyone point me to the right direction in this? we render in h18 just fine.

thank you.

Redshift is not installed correctly on the render nodes.

1 Like

Hi Mois. We do have a redshift currently installed in the nodes, and one that supports h19, as the machines can render h19 jobs locally.

I am assuming it’s some script that might not be getting the correct redshift path. I also have seen a houdini19.diff file that has been uploaded to this forum post that fixes ROP submission, is that what I am missing? but I have no idea what to do with it, Any suggestions?

I would really appreciate it. thanks!

How do you link Redshift to Houdini? Do you have package json files? Whatever it is, has not been done on Deadline.

1 Like

Hi @mois.moshev , thanks so much for the patch. Could we know exactly how to run the patch in a windows environment

Cheers,
Karthik

How do I apply a diff patch on Windows? - Stack Overflow.
here are some suggestions
If you have git already, it is easiest to use it. Some editors also have builtin diff programs. Another option is to use linux tools with MinGW or similar. A third option is this program (don’t know if it works on newer windows).

Privacy | Site terms | Cookie preferences