OctaneRender 2023.1 for Houdini production (2023.1.0.1) Tweet

[lavrenovlad]

@Cd attribute via rgb4k_map.ppm doesn't work anymore.
If I create a bunch of instanced objects with @Cd attribute on them, using that rgb4k_map.ppm doesn't instance the colors from particles onto these instances..

[lavrenovlad]

Got it working but only through the houdini instance node, just using s@instance attribute on points in a geo node doesn't make tex_instance_color node with .ppm file in the shader to work.

[galleon27]

@Cd attribute via rgb4k_map.ppm doesn't work anymore.
If I create a bunch of instanced objects with @Cd attribute on them, using that rgb4k_map.ppm doesn't instance the colors from particles onto these instances..

Change Instance IDs from to "Packed RGBA values from 'Cd' point attribute.

[lavrenovlad]

Nice, thanks for the info! Wasn't that option the default before?

[Renbry]

We're going to roll back to the 2023.1 build. Now we're seeing images rendered out as ".exr.png" files via Deadline. Rolling back sets the format correctly and allows us to continue.

[ricky_otoy]

We're going to roll back to the 2023.1 build. Now we're seeing images rendered out as ".exr.png" files via Deadline. Rolling back sets the format correctly and allows us to continue.

Hi thanks for reporting, will be looking into it. It may be from a fix for multiple ROPS but was sure this was working.

[PDivision1]

Hello,

I seem to not be able to submit to Deadline since upgrading from the 2023 Beta. It's weird but there's language in the Python error which may be something to do with the Octane ROP; any changes that have happened in there. I recall a change to the file formats happening but not sure how this could affect the Deadline submitter. Presently hacking other submitted jobs to redirect to HIPs i need rendered.

Tested even on a new, blank, sphere test scene. Pressed Octane, Render Target, Made a camera, made a sphere, submit to Deadline.

Houdini 19.5.773

Traceback (most recent call last):
File "//192.168.0.32/DeadlineRepository10\submission/Houdini/Main\SubmitHoudiniToDeadline.py", line 1537, in SubmitJobCallback
SubmitRenderJob(job, jobOrdering, (totalJobs > 1), jigsawRegionCount, jigsawRegions )
File "//192.168.0.32/DeadlineRepository10\submission/Houdini/Main\SubmitHoudiniToDeadline.py", line 1331, in SubmitRenderJob
jobIds = SHTDFunctions.SubmitRenderJob( renderNode, jobProperties, ",".join( dependencies ) )
File "//192.168.0.32/DeadlineRepository10\submission/Houdini/Main\SubmitHoudiniToDeadlineFunctions.py", line 692, in SubmitRenderJob
output, outputFile, paddedOutputFile = get_render_output_filepath(node)
File "//192.168.0.32/DeadlineRepository10\submission/Houdini/Main\SubmitHoudiniToDeadlineFunctions.py", line 523, in get_render_output_filepath
if node.parm("HO_img_fileFormat").eval() < 2 or node.parm("HO_img_fileFormat").eval() > 3:
AttributeError: 'NoneType' object has no attribute 'eval'

Where does SubmitHoudiniToDeadlineFunctions.py come from? Is it your code, or is it something maintained by deadline?
This code needs to be updated because the parameter type and name has changed.

[Renbry]

This is the submission code from Deadline. I think it rarely changes but sending it to you to see how some of the conventions work/what's expected to happen on submission.

[PDivision1]

This is the submission code from Deadline. I think it rarely changes but sending it to you to see how some of the conventions work/what's expected to happen on submission.

Could you please send a support ticket to AWS and ask them to update this code? We are unable to talk to their developers, they told us to divert users to their (AWS) support.

As for the png issue - It's my bad, I'll push another release that fixes it.

We are also looking into setting up Deadline for testing the plugins. Hopefully it will reduce the number of regressions like this.

[Renbry]

Ok thanks,

Created the post here : https://forums.thinkboxsoftware.com/t/h ... ug/31437/2

This has been a pretty disastrous time for us with so many issues coming up during this delivery phase. The problem is we're somewhat trapped in needing recent Houdini 19.5 builds for PDG bug fixes but this prevents us from using older Octane 2022 builds which have the reliability we're used to.

I haven't been able to help with repro scenes (as the scene pulls tonnes of data into the scene and isn't easily made portable)

We're limping along, getting about 60% frames rendered and 40% CUDA crashes/requeues and hacking already submitted jobs to redirect to other HIP files we need to render for delivery.

Once I'm out of this, past delivery, I can help diagnose the myriad issues.

Matt Hermans
Electric Lens Co.