Corona for Cinema 4D Beta 1 daily build

[houska]

Thank you for your reply.

i don't know if the same problem. Below 3 very simple tests.

1 : just one hdr ...  no problem, ir and final vfb show the same result. [...]
2 : just 1 corona light (sphere sector) ... gamma ? between difference. Left Ir, right final vfb (that seems to have another gamma) [...]
3 : and last ... a sphere with emi light replace the corona light of test 2. Strangely here it works [...]

Ok, this seems like a problem with corona lights! Thanks for the additional tests, we'll try it too!

[burnin]

C4D Area Light is rendered in final render (PV & VFB) but not in Interactive Rendering.


Scene file "cIR-LightRenderBug" attached bellow (just press Play :)

Also, Interactive rendering stays active even after it is stopped & buffer window closed.
Symptoms:
1. Stop Rendering button (icon) stays active (in color).
2. Starting Interactive rendering brings up the following message: "The external renderer is calculating an image. Do you want to stop it?"

[houska]

Scene file "cIR-LightRenderBug" attached bellow (just press Play :)

You're top notch, burnin! Thanks for the scene!

[burnin]

^ no problem ;)

More than one object grouped in null under symmetry (A) will not show in IR (B).  When ungrouped (C) it renders fine (D).

IIRC, had seen it somewhere, but can't remember nor find it now... some other engines also showed such inaccuracies / flaws.
To prevent such behavior start using Connect object. Also solves your issues within Corona.

ps
Don't underestimate the complexity of procedural generators & keep in mind the hierarchy of the processes is ruled by the construct / organization / structure in Object manager.

[karklinskarlis1993]

so basically for those crashing on older build scenes - should we use this new build only on fresh ones? or is there fix upcoming?

[Beanzvision]

Cinema crashes on render when adding an image to the background plate slot in the shadow catcher.

This doesn't happen to me. I can change the texture in IR too and nothing crashes. See my setup in the attachment...

Cheers houska I'll take another look shortly.

[burnin]

advised practice:
a) don't switch tools/builds/versions while in production - follow through from start to finish
b) unless something breaks - then it's necessary to run a 'test scene' & compare with 'master' to see if it achieves desired result
c) no experiments in production, unless you master the skill as if it's of your own creation or you have a planB/intervention standing by

With Corona use same build from start to finish to prevent any problems, inconsistencies, breakages...

"You never know what ya gonna get."

PS@kmwhitt
example of Connect object use

[houska]

so basically for those crashing on older build scenes - should we use this new build only on fresh ones? or is there fix upcoming?

We also have some older scenes at the office, but we don't experience any crashes. The best would be if we could get a crashing scene from any of you guys and we could have a look at it.

[houska]

advised practice:
a) don't switch tools/builds/versions while in production - follow through from start to finish
b) unless something breaks - then it's necessary to run a 'test scene' & compare with 'master' to see if it achieves desired result
c) no experiments in production, unless you master the skill as if it's of your own creation or you have a planB/intervention standing by

Thank you burnin, this is what I'd advise too! Not only with Corona, but with any piece of software that is under development. Also, all the development versions (daily builds, nightly builds, release candidates) are expected to have crashes or bugs, no matter how hard the devs try.

[TomG]

To add a note on the difference in lighting between IR and offline, seems like the Object Manager setting "Visible in render" has an effect.

Took a scene with one Sun in it, and it rendered too bright as if there was additional light with no shadows (first image). By turning off the "Visible in render" parameter (second little red circle) the IR then rendered correctly. Note that offline rendering to the VFB worked correctly no matter what this was set to.

[houska]

To add a note on the difference in lighting between IR and offline, seems like the Object Manager setting "Visible in render" has an effect.

Took a scene with one Sun in it, and it rendered too bright as if there was additional light with no shadows (first image). By turning off the "Visible in render" parameter (second little red circle) the IR then rendered correctly. Note that offline rendering to the VFB worked correctly no matter what this was set to.

Yes, we observe the setting and try to apply it consistently with C4D's renderer. That said, there can be discrepancies, but I was really surprised by the claim that some lights don't obey the setting. We'll check it nevertheless. Thanks for all the reports, guys! Keep them coming!

[kmwhitt]

burnin - thanks for the workaround.  ; )

[TomG]

Global Volumetrics no longer render (offline, or in IR).

In a test with an object with a volumetric material applied, it rendered in offline, but if I changed the absorption distance in the material and rendered in offline again, it crashed (can send crash report if useful, let me know!). It's not the value, as if I change the value before rendering, it renders fine first time. I can re-render so long as I don't change the value, too. Interestingly, I can change the value while IR is running, and there's no crash and the render updates as expected.

Thanks!

[Kost4d]

Global Volumetrics no longer render (offline, or in IR).

In a test with an object with a volumetric material applied, it rendered in offline, but if I changed the absorption distance in the material and rendered in offline again, it crashed (can send crash report if useful, let me know!). It's not the value, as if I change the value before rendering, it renders fine first time. I can re-render so long as I don't change the value, too. Interestingly, I can change the value while IR is running, and there's no crash and the render updates as expected.

Thanks!

So I was right about volumetrics! Please, check opacity channel also if it rendered for instances or not.

[nightwalker]

In some of my scenes, Daily build SEP 28 2017 crashes when it starts rendering. With the same scenes the previous version (SEP 5) seems to work properly. Macpro late 2013 and Cinema 4d R18 on MacOS Sierra.

I attach one of these scenes, very simplified but showing the problem, I hope to help you find the bug. Thanks for your great work.

Sorry for my bad English