Corona 1.6 hotfix 1 - scene rendered black (nothing)

[vrauwena]

Hi,

I'm using corona 1.6 hotfix 1 with 3ds max 2017.

Encountered this strange behaviour when my scene which previously rendered normally, suddenly turn black when rendered.
even the render element is not rendered (black).

Tried to restart max, and reset the corona render setting, which gave me normal behaviour, but for once only. Next render it started turn to black again. This time resetting doesn't result in anything.
I tried change the number of passes to unlimited, and the rendering will even go up to 18k in just 19 seconds.
Will upload the scene through private uploader.

[alexyork]

I wonder if you have an "invisible" corona render region somewhere way way off the VFB. We had this recently. Try to zoom out as much as possible and see if there's one there. Or just hit the remove all regions button.

[vrauwena]

I wonder if you have an "invisible" corona render region somewhere way way off the VFB. We had this recently. Try to zoom out as much as possible and see if there's one there. Or just hit the remove all regions button.

Thank you Alex! You are right! i can't see if there are any region way off the vfb though so just hit the remove all regions .

[alexyork]

I wonder if you have an "invisible" corona render region somewhere way way off the VFB. We had this recently. Try to zoom out as much as possible and see if there's one there. Or just hit the remove all regions button.

Thank you Alex! You are right! i can't see if there are any region way off the vfb though so just hit the remove all regions .

No worries! For what it's worth, Corona devs, could you please somehow fix this so that regions outside VFB are impossible?

[maru]

Don't worry, it's already on Mantis.
I think a good temporary solution would be to catch this with error messaging, with an option to reset regions.
(moving to resolved to avoid duplicates - already on mantis - private report id=2514)

[alexyork]

Don't worry, it's already on Mantis.
I think a good temporary solution would be to catch this with error messaging, with an option to reset regions.
(moving to resolved to avoid duplicates - already on mantis - private report id=2514)

Cool. Maybe a warning, but then why not automatically reset regions? Can't see any case where you'd want it to still render black/outside the VFB.

[Frood]

but then why not automatically reset regions? Can't see any case where you'd want it to still render black/outside the VFB.

Because this could also happen when temporarily using native max crop rendering. And if you switch back to (full) view rendering and want your regions back, they would be gone.


Good Luck