Messages

1

[Max] I need help! / Re: Deadline Submission and save output issue

« on: 2017-05-31, 01:43:01 »

Have u been able to solve the issue?

Unfortunately no. I tried every checkbox in the 3ds max rendering settings, but it didn't help. I think of trying to update to the latest deadline version. Hope it might help.

 Lucutus, do you use any settings in the Deadline submitter specific to Corona, or just stick to default setup?

2

[Max] I need help! / Re: Deadline Submission and save output issue

« on: 2017-05-29, 11:24:38 »

We're trying to save each render pass separately. So no multichannel EXRs.

When image is rendering on render node it shows 2 frame buffers - Corona VFB and default 3ds Max VFB. The rendering is going on in Corona VFB but Max VFB stays black. So I'm guessing that for some reason when render is finished it saves output from Max VFB (black image without any passes) instead of Corona VFB.

Is there any setting in Deadline submission or Corona render settings which controls from which VFB it should save the output at the end of the render?

3

[Max] I need help! / Re: Deadline Submission and save output issue

« on: 2017-05-29, 09:19:16 »

Thank you Lucutus!

We are using full float 32bit EXR for saving render output, but it's not helping. We also tried to save in TIFF but it saved the same completely black output and no render passes.

4

[Max] I need help! / Deadline Submission and save output issue

« on: 2017-05-29, 06:47:18 »

Dear Coronauts,

Does anyone have experience of using Corona with Deadline? We are implementing Deadline as our primary network rendering manager and having issues with Corona jobs have been submitted from 3ds Max to network rendering:

When it's rendering on the farm we can see that Corona Frame Buffer rendering image fine, but when render completed, the render output saved a completely black image only for Beauty pass, and completely ignores any render elements.
We are setting render output as a 32bit Open EXR under Render Output group in Common render settings and adding few corona render passes under Render Elements tab.

We have 3ds Max 2016, Corona 1.6 and Deadline 9.0.1.1


Would really appreciate any help on how to setup deadline submission for 3ds Max + Corona

Thanks

5

[Max] Bug Reporting / Re: DR node reporting version incorrectly

« on: 2017-05-03, 07:05:05 »

I think I've found what caused this problem. This was an issue with 2 maps which were installed with sigershaders but were missing in our network plugins folder. These maps have been used in siger materials (predominantly metals) and that caused this brightness difference between nodes which have access to these maps and nodes which haven't.

The message "Corona version mismatch. Slave version: Unknown (pre 1.3), Master version: 1.6" was a bit misleading since it wasn't an issue with Corona but with 3rd party maps.

Just as a suggestion: it would be helpful if in the future Corona updated there will be a different kind of message for this sort of issues with some maps or plugins missing. In that case, it would be easier to trace the origin of a problem.

Thank you and sorry for false alarm :)

6

[Max] Bug Reporting / Re: DR node reporting version incorrectly

« on: 2017-05-03, 03:30:14 »

I've tested DR again with other slave nodes with freshly installed Corona 1.6 and didn't get the message about "Corona version mismatch" but still have bright stripes from slaves (especially on metal materials like stainless steel). So it seems that it using older non-PBR material algorithm on the nodes.

7

[Max] Bug Reporting / Re: DR node reporting version incorrectly

« on: 2017-05-02, 10:19:46 »

I'm having the same problem. I just installed corona 1.6 on all nodes (clean installation without any previous corona versions on these nodes) and DR gives me uneven light stripes and the same message: "Corona version mismatch. Slave version: Unknown (pre 1.3), Master version: 1.6"

Do you also have different versions of 3ds Max on your nodes?

Max version (2016) and all 3rd party plugins are the same on workstation and slave nodes

Forgot to mention that I have 1.6 Demo version installed on workstation and slave nodes. May it be the case of some Demo version limitations?

8

[Max] Bug Reporting / Re: DR node reporting version incorrectly

« on: 2017-05-02, 09:27:34 »

I'm having the same problem. I just installed corona 1.6 on all nodes (clean installation without any previous corona versions on these nodes) and DR gives me uneven light stripes and the same message: "Corona version mismatch. Slave version: Unknown (pre 1.3), Master version: 1.6"

9

Gallery / Re: Barn House

« on: 2016-05-17, 17:42:14 »

Great lighting i like the mood and landscape integration,
might i ask is that falling water 3d modeled i like the effect of water hitting the stones, or is it post work?

Thank you, Giza!

Falling water is modelled (3D noise + bump on material), but splashes effect has been added in post.

10

Gallery / Barn House

« on: 2016-05-17, 14:31:22 »

Dear Coronauts,

Please allow me to share our latest commercial project done in Corona.

We knew that Corona doing an amazing job for interior renders. For this project our main focus was to try Corona as a production render for exterior renders. And may I say that we were more than satisfied with the final result.

Would be glad to hear your thoughts and questions. Thanks