Cinema4d (Octane) / bad EXRs / submitting takes

Hello,

I’m currently trying to evaluate Deadline(8.0.4.1) for our small studio. So far, it looks like a solid piece of software - straightforward installation and all. But still we’re having some weird issues.

The Cinema4D batch plugin and EXR Files
This one nearly drove me mad, but I think I narrowed the issue down to the batch plugin. When rendering using the batch plugin I get messed up EXRs, they are not floating any more but clip at 1 and even worse they have a weird pixelated pattern in dark areas of the image. I get these results with octane AND with the C4D internal renderer. Picture Viewer renders fine and so does the non-batch plugin. I uploaded some jpgs to illustrate this behavior. Please note the upper and left sides of the cube. I think we also had the issue when trying 32-bit TIFF export.

The C4d Submitter and Takes
Is it possible to have all the marked takes AND their respective frame ranges submitted in one go? I can select various takes from the drop-down menu but Deadline doesn’t use the frames ranges set in the corresponding render settings. It always takes the frame range (unless I enter something else) from the active take and renders all selected takes for that duration. If this is not already possible (how?) it would be highly appreciated for the future!

cheers,
jan


Yes that would be awesome if you could implement this. Just stumbled upon this yesterday.

-b

Regarding the second point, I will send this over to the devs. For the first one, could you share a sample scene file so we can try to replicate the issue? Thanks.

Thanks for looking into this.
I’ll send you my test scene when I get to work tomorrow.

Please find a test file attached. I just checked, it’s still producing the error.
I submit this file via the cinema4d batch plugin and get this weird pattern in the exr. As I said before, it’s most obvious on the dark sides of the cube.
If I submit via the regular plugin everything is fine.
160705_Figuren_JS_v006.zip (165 KB)

Hey,

Thanks for the file! I am going to try to test this right away, but noticed a few plugins we don’t have licenses for here. Hopefully this won’t affect my testing, but I might need a very basic, plugin free scene file. I’ll let you know.

Hello,

So, as I suspected, I think the lack of Octane is causing me to get no output at all, and the sadly customary lack of useful outputting of problems that comes with C4D is not telling Deadline there is any issues. Can you send over a plugin free scene file where your issue still happens? Thanks.

FYI, looks like we’ve got the takes using their respective frame ranges done. Should be in the next service pack!