Black main beauty pass and broken beauty element

[Dippndots]

So, I've got a bit of an odd problem. Random frames from 2 different animation files are rendering black, but the non ESSENTIAL elements are still rendering correctly. Except for the extra beauty pass element I have where bloom an glare is non applied (snippet of the image attached below).

Even stranger is that if I watch the VFB while rendering, the main beauty is black, but if I switch elements and then switch back to the beauty, it is visible and correct for a few seconds, before it goes back to black.

I have uploaded the 2 problem output EXRs to corona-renderer.com/upload, I can't share the scene unfortunately.

Has anyone else experienced this? I'm not sure if its just a corrupt camera/max file, I've resent the affected animations with cloned cameras, but I won't know if its fixed until tomorrow.

EDIT: corona upload file name "1485859791_BrokenBeautyPass.zip"

[maru]

Thanks for reporting, our dev team will have to inspect this.
This looks like NaN pixels. There have been reports similar to this one, especially when bloom and glare was used, but it was happening in older versions only. Are you using 1.5.2?
Is this also happening if you disable bloom and glare?

[Dippndots]

Ok, yeah we're using 1.5.2.

I'll send another version of the anim with no bloom and glare and see how that goes. Should be able to say by Friday.

[Dippndots]

So a new camera didn't solve the problem.

However, I found out the animation was rendering to a pass limit (150) and it was reaching sub 2% noise by the time it ended (overkill in my opinion), I resent it with a 3% noise limit and everything else the same (bloom and glare enabled).

The black frame bug didn't occur anymore.

I have 1 more affected camera I will test this on this week to make sure its not just a coincidence.

[Dippndots]

So false alarm, noise limit didn't solve the problem.

Turning off B&G and deleting the render element didn't solve it either.

Testing a copy of the file with the render settings reset to default, will report back again after.

[Dippndots]

Still trying to nail down the cause of this. Though it definitely seems related to a material because using an override mat stopped the problem. Hopefully I'll have some time again this week to narrow it down.

[Ondra]

hi,
any more info, such as scene that reproduces the issue?

[Dippndots]

Hey Ondra, sorry I forgot to update this. We discovered that the machine submitting the broken frames was still on 1.5 while the rest of us and the render slaves were on 1.5.2.

[Ondra]

ok, since there was NaN-fixing bugfix in hotfixes, I am closing this down

[Ondra]

i took a look at it and indeed the images were full of NaNs