Corona for Cinema 4D Beta 1 daily build

[bgolds99]

I keep getting Corona crashes straight after i adjust the Multipass settings. Like if i go in and add some lightmix passes, or zdepth, or Material ID, or whatever..... during the scene parsing stage, Corona crashes and Cinema shuts down. Is this a common bug? It seems to be happening across my 3 machines.

Cheers,
Brad

[TomG]

I keep getting Corona crashes straight after i adjust the Multipass settings. Like if i go in and add some lightmix passes, or zdepth, or Material ID, or whatever..... during the scene parsing stage, Corona crashes and Cinema shuts down. Is this a common bug? It seems to be happening across my 3 machines.

Cheers,
Brad

Not been able to duplicate here - Build dated Jul 18th, Windows, C4D R18, I tried rendering, stopping, adding Multipass elements, rendering - no problem. Then tried rendering, and while in the scene parsing, adding some new multipass elements (as I wasn't sure from your description when you were adding the multipass elements), and also no problem. I was rendering in the Corona VFB. Could you share what Corona build you are using, what C4D version, whether it's with every scene, what steps you follow to reproduce?

[mrittman]

Hi,

Not pushing or anything, but do we have an estimation on the next update release ?
We basically have a big animation render coming at the end of next week and and after a lot of test i think that we can't make without a stable team render.
Again, not pushing, just need to start planning a bit and weighting the options :)

Thanks in advance

Yeah...seems like the development pace has been pretty slow for the C4D version :/ Interactive Rendering seems to be getting delayed a lot. I definitely don't see it getting finished by the end of September, unfortunately. With ProRender coming out for R19, it's very tempting to resort to this route...

[kmwhitt]

I have had the same crash issues using the last few builds.  It happens when I add a new light to the scene and the subsequent lightmix element.  It only occurs if I have previously rendered the view without this new element.  It is also known to happen when I change the resolution of the image under render settings before rendering in VFB.  Tom - please let me know if you're able to reproduce.  Thanks.

[TomG]

Not been able to duplicate in my initial testing, admittedly just in one scene

- Open scene, add LightMix, LightSelect, add one light to the LightSelect (other lights in the scene not added to anything), render, stop render, add light, add new LightSelect, add the new light to the new LightSelect, render - all ok.

- Continuing directly from the above, changed the render resolution, hit render - all ok

[kmwhitt]

Thanks for checking.  May be something specific to my machine as I can reproduce it consistently.  I can send a file if directed to the right place.  It will have to be a few days, but am willing if that will help.

[TomG]

A sample scene where the problem is known to occur is always useful! There's the private uploader for such things if the scene can't be shared publicly - https://corona-renderer.com/upload/ Thanks!

[snifferdog]

Thanks for checking.  May be something specific to my machine as I can reproduce it consistently.  I can send a file if directed to the right place.  It will have to be a few days, but am willing if that will help.

Are you Windows or Mac?

[kmwhitt]

Sorry, should have mentioned I am using a PC w/ Windows 7 Pro.

[bgolds99]

Yep. I'm Windows 7 Ultimate with C4D R18 (latest update)... it happens most often with Lightmix updates to multipass. It seems as if corona has to crash once before it can go forward after making an update. Once i crash and restart c4d and reload the scene it behave as normal until i need to add more passes.

[kmwhitt]

bgolds99 - same exact situation here.  I have been restarting C4D after such a change to lightmix.  I am also using R18 with the latest Corona build.  I'll send the file to support in the next couple of days.

[Marvey]

Rendering at 11811x8105 resolutions when applying the denoising C4D crash, these happened in 2 different and complex scenes at this high resolutions.

[RED LAB]

I had this problem before. The only solution i found is to render it in two parts and merge them in photoshop.

[TomG]

For the crash during denoising, how much memory do your machines have? I tested on a 12K x 8.5K render, just 2 passes, which used 27Gb on rendering, and peaked at about 52Gb during Denoising (varying  between 31Gb and 50Gb for most of the Denoising). This was on a 64Gb machine, and it completed with no crashes.

One possible option for large images is to save as CXR with denoising set to gather for later, and use the Corona Image Editor to do the Denoising outside of the 3D application (as then there is much less memory overhead required without C4D running and the scene loaded etc).

[Marian]

One possible option for large images is to save as CXR with denoising set to gather for later, and use the Corona Image Editor to do the Denoising outside of the 3D application (as then there is much less memory overhead required without C4D running and the scene loaded etc).

Nice, I didn't know about this option. I'm struggling with 32 GB all the time and this could be nice workaround...