AWS Thinkbox Discussion Forums

Houdini Submission DL9 "fetch" handling

Just curious. Is there a reason why the submitter doesn’t handle “fetch” nodes (alone or connected to merge node) as output?

It’s easy enough to fix, but is there some reason why it shouldn’t be?

in SubmitHoudiniToDeadline.py line 1392 (or there abouts)

        # Check the output file    
        output = GetOutputPath( renderNode )

It could be fixed like:

        # Check the output file
        if renderNode.type().name() == "fetch":
            source = renderNode.evalParm("source")
            renderNode = hou.node(source)
            
        output = GetOutputPath( renderNode )    

Edit. Oh and this is from version 9.0.4.0

Not that I’m aware of. I’ll ask the dev team quickly, but I say use it for awhile and see what happens! If it works for a few studios, it’ll be worth adding in for everyone.

Quick update: Since it’s kind of a pointer, we’d want to follow until we hit a real ROP. I don’t know why anyone would point a fetch node at another fetch node, but it’s technically possible. I think the team are going to work on that officially, but this may work better for you:

        # Check the output file
        while renderNode.type().name() == "fetch":
            source = renderNode.evalParm("source")
            renderNode = hou.node(source)
            
        output = GetOutputPath( renderNode )

Thanks!

You’re right, it would be better to handle the off chance that someone will stack them.
I’ll probably end up adding some kind of nag just in case one of my guys goes crazy with stacking them. :laughing:

Privacy | Site terms | Cookie preferences