Backburner stops rendering although noise level threshold is not met

[pokoy]

Max 2016 / Corona 1.4 stable

I have a problem where BB will stop rendering frames (rendering locally doesn't show the problem). It happens with two scenes where I'm using a noise limit, however the noise limit is not met on either of them, both visibly and by the noise level displayed in the stats.

I am pretty sure adaptivity is the problem here since both scenes will finish after recalculating adaptivity (recalc is left to the default of 5 passes). One scene will stop after 5 passes, the other after 10. Noise limit is set to 3%, both display a noise level of ~6.5 when Corona decides to stop rendering.

I am seeing at least 2 other reports mentioning something similar when using BB. Though none of them mentions adaptivity, so I thought it's ok to create a new thread.

[Frood]

 I´m not quite sure if I had exactly that using BB or DR last time and if it was 1.4 dailies or final, but I encountered this one at least two times.

I am seeing at least 2 other reports mentioning something similar when using BB.

Would you mind to link them here?

Thank you!

[pokoy]

Sure, though it looks like one of them (or both?) were related to the 600 minutes timeout. Doesn't apply in my case, rendering ends after less than 1 hour:

https://forum.corona-renderer.com/index.php/topic,11186.msg71508.html#msg71508
https://forum.corona-renderer.com/index.php/topic,11450.15.html

As for my original issue, re-submitting the scene without a noise limit and setting a time limit instead works just fine. Would be nice though to get noise limit working otherwise adaptivity is useless for animations as long as noise level doesn't work properly.

[Frood]

Thank you, yes those don´t seem to be related directly.

But to clarify this one:

In your original post, you are talking about submitting a job to BB without using DR coincidental, so one frame is rendered by one node, right? No slaves involved?

Good Luck

[pokoy]

Thank you, yes those don´t seem to be related directly.

But to clarify this one:

In your original post, you are talking about submitting a job to BB without using DR coincidental, so one frame is rendered by one node, right? No slaves involved?

Good Luck

It's rendered on a single slave through BB, no DR involved.

[maru]

Are you rendering the whole frame, or just some area? (strips/regions)
Do you know what is the reason why the node is stopping? Can you share your BB logs? https://knowledge.autodesk.com/support/3ds-max/troubleshooting/caas/sfdcarticles/sfdcarticles/How-to-find-and-analyze-your-backburner-error-logs.html

[pokoy]

It's the whole image, no regions, no crops.

As for an error or a log - I don't think it's a BB issue and there's no error at all, it's obviously a Corona problem. Corona considers the image 'done' and it seems to do so immediately after adaptivity recalc phase, so in this case after 5 or 10 passes respectively. It'll stop rendering the image prematurely although noise limit is not met.

Without specifying a noise limit the images render fine.

[Frood]

As for an error or a log - I don't think it's a BB issue and there's no error at all

Somewhat glad to read that. When I met this issue, there was also no hint in any log about what´s going on. Rendering just stopped after x passes, saved as if that pass number x has been set in the scene settings.

We should try to reproduce that, it just doesn´t happen with every scene.

Good Luck

[maru]

Hmm.. I am sure there were already reports exactly like this, but I cannot find them. Will take a closer look, though I think it was during the 1.4 RC times.

[Frood]

Yes, during 1.4 dailies there have been similar issues using DR, for example

https://corona-renderer.com/bugs/view.php?id=1730

what sounds exactly like this one but using DR not BB. This is BB single frame rendering and this is something new :-/

Good Luck

[Ondra]

old bug report; corona now uses totally reworked DR/net rendering system. I am moving this to resolved as it is probably no longer relevant. Feel free to create a new thread if you have any further similar problems