OctaneRender 2023.1 for Houdini production (2023.1.0.1) Tweet

[heimlich]

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.

Its simply because you renamed in the new plugin, instead of using HO_img_fileFormat as the parm name, you chose HO_img_fileFormat_v2. That breaks compatibility

[adrianr]

Can we please get a push to fix the Deadline issue if it is indeed a case of reverting the parm name? I'll take a back alley version via dropbox.

[PDivision1]

Can we please get a push to fix the Deadline issue if it is indeed a case of reverting the parm name? I'll take a back alley version via dropbox.

Yes we can revert that change. I'll look into pushing the revert in a day or two.

[Renbry]

To be clear - The submission issue is still there in 2023.1

I believe it DID work in the BETA - you may be able to confirm a change entered into the 2023.1.0 build from the BETA.

[PDivision1]

To be clear - The submission issue is still there in 2023.1

I believe it DID work in the BETA - you may be able to confirm a change entered into the 2023.1.0 build from the BETA.

A little update: I installed deadline locally and was able to reproduce the submission issue. Will revert the name change and whatever else is broken in the next release this week.

[adrianr]

Nice one, thanks PDivision1.

[lavrenovlad]

I think this version is somewhat not stable, I get crashes here and there when rendering overnight. Didn't happen with the beta as I remember, everything was good.
One time it stopped rendering on a certain frame and just stayed there counting render time, another time it finished rendering one ROP node and didn't switch to another.
Can be a false alarm though, I just have a somewhat heavy scene, maybe it would happen in beta too.

[lavrenovlad]

Also you really need to fix ai upscaler, it doesn't work when rendering to disk, only in IPR. On top of that the ROP node gets reset itself, I already rendered out pngs twice because of that, it just switches to PNG like what..

[ricky_otoy]

Also you really need to fix ai upscaler, it doesn't work when rendering to disk, only in IPR

Hey there, I seem to have the same results in both IPR and Render to Disk. Is it a specific format, also are you using OCIO?

Please PM me a simple scene again and the output renders. (the IPR output as you expect and the other result from Render to Disk so I can properly compare)

Thanks!

EDIT:
The ROP output reverting to PNG has been fixed for an upcoming build.

[lavrenovlad]

Rendering out 16bit exr in ACEScg, are you sure it's working on your end?
Maybe you could send me your result saved from the IPR and from the disk to compare?