Corona Renderer 5 for Cinema 4D daily build

[Ales]

Hi all,

we are releasing our first daily build of Corona Renderer 5 for Cinema 4D. This build contains several new features, but it also comes with some bigger internal changes in the way we handle scene geometry. This should reduce memory usage in some scenes as well as prepare ground for some future improvements. Enjoy! :-)

Download link:
https://drive.google.com/drive/folders/1EMW3qukbimXcoijLO-ypg9__B305py38

Changelog:
https://forum.corona-renderer.com/index.php?topic=26054.msg155306#msg155306

[zbieraj]

Wow! Congratulations on the progress guys and thank you for sharing v5! I will definitely start to test it once I will finish commercial projects I need to finish this week :).

[Cinemike]

Yeah, congratulations!
The additions look and work great and as someone who is use to using the Variation shader I must say: having the multishader is a very useful addition!

[fabio81]

congratulations guys!
I'm trying it too and so far no problem. Regarding the multimap shader, isn't there the possibility to change the random mapping as a native Cinema 4d shader? I tried to add a UVW randomizer node but it didn't work well .. I'll do more tests

[frv]

Does this daily 5 build by an change run on C4D R21 ?

[TomG]

No, R21 is not supported yet (it would be in the changelog if so :) )

[leo3d]

don't forget to update your icon size with news R21 UI

Merci

[Evolist_ua]

Hi guys, this problem remains(
https://forum.corona-renderer.com/index.php?topic=24238.0

[leo3d]

One question dev
Have you got access to maxon beta ? Cause i don't understand why it take so long to get comptatible version

[TomG]

It takes so long because there are only so many of us, only so many hours in the day, and so many things that need to be worked on :) Especially with the latest update to the core that needed to be moved across not so long ago.

[Miche67]

Hello ,
Is this bug fixed in vs 5?
https://forum.corona-renderer.com/index.php?topic=10364.msg66187#msg66187

[Miche67]

https://forum.corona-renderer.com/index.php?topic=22359.0
...Is this bug fixed in vs 5?
Thank's

[minimaldesign - Blaž]

Hello,

In last daily build (Version: 5.0 daily Aug 30 2019 (core 5 (DailyBuild Aug 30 2019)) I can't save .CXR file form VFB, there is also no option save as, render interactive rendering...the tabs doesn't open in anyway.

We are on WIN7, C4D R16

[TomG]

Hello,

In last daily build (Version: 5.0 daily Aug 30 2019 (core 5 (DailyBuild Aug 30 2019)) I can't save .CXR file form VFB, there is also no option save as, render interactive rendering...the tabs doesn't open in anyway.

We are on WIN7, C4D R16

Not sure what you mean - click and hold on Save in the VFB opens the drop down for me, with the Save All and Save CXR options there (which is where they always were). Is that not happening for you?

[frv]

As I understand 4 will no longer recieve updates or R21 compatability.
So the wait is now for 5 first to be debuged and then prepared for R21. I see there are some issues still with 5 and I assume a R21 version is still a little further on the horizon than "soon".

[minimaldesign - Blaž]

Hello,

In last daily build (Version: 5.0 daily Aug 30 2019 (core 5 (DailyBuild Aug 30 2019)) I can't save .CXR file form VFB, there is also no option save as, render interactive rendering...the tabs doesn't open in anyway.

We are on WIN7, C4D R16

Not sure what you mean - click and hold on Save in the VFB opens the drop down for me, with the Save All and Save CXR options there (which is where they always were). Is that not happening for you?

this has worked to this day ... unfortunately it doesn't work in latest version
p.s. I'm attaching the c4d file if anything helps

[Beanzvision]

Hello,

In last daily build (Version: 5.0 daily Aug 30 2019 (core 5 (DailyBuild Aug 30 2019)) I can't save .CXR file form VFB, there is also no option save as, render interactive rendering...the tabs doesn't open in anyway.

We are on WIN7, C4D R16

Not sure what you mean - click and hold on Save in the VFB opens the drop down for me, with the Save All and Save CXR options there (which is where they always were). Is that not happening for you?

this has worked to this day ... unfortunately it doesn't work in latest version
p.s. I'm attaching the c4d file if anything helps

Hi, seems to be working for me with the latest V5 dailybuild. Even with your scene file.

[minimaldesign - Blaž]

Hello,

In last daily build (Version: 5.0 daily Aug 30 2019 (core 5 (DailyBuild Aug 30 2019)) I can't save .CXR file form VFB, there is also no option save as, render interactive rendering...the tabs doesn't open in anyway.

We are on WIN7, C4D R16

Not sure what you mean - click and hold on Save in the VFB opens the drop down for me, with the Save All and Save CXR options there (which is where they always were). Is that not happening for you?

this has worked to this day ... unfortunately it doesn't work in latest version
p.s. I'm attaching the c4d file if anything helps

Hi, seems to be working for me with the latest V5 dailybuild. Even with your scene file.

It also work for me till now :)

[TomG]

So what does happen when you click and hold on that button? Nothing shows up or changes? Or something else?

[fabio81]

the drop-down menu does not work for me. The Render region menu and the IR menu don't work either.
I'm working in windows 10 with the latest Corona 5 beta (August 30th) e Cinema 4d R16.
Cinema R19 instead everything works!
thanks ;)

[TomG]

TY for the info! Very strange, I'd try and uninstall and reinstall of Corona as a starting point.

[twcg]

As I understand 4 will no longer recieve updates or R21 compatability.
So the wait is now for 5 first to be debuged and then prepared for R21. I see there are some issues still with 5 and I assume a R21 version is still a little further on the horizon than "soon".

Any official info on this? Will the first Corona Version for R21 be the V5?

[TomG]

No official info on that yet, sorry. We shall have to see as we finalize compatibility whether it will be possible to have that in Corona 4 or just in Corona 5 and onward.

[minimaldesign - Blaž]

So what does happen when you click and hold on that button? Nothing shows up or changes? Or something else?

Nothing shows up on the tabs that have always opened till now :)

[mrittman]

Dang, I really thought R21 support for v4 was coming this week :(

[TomG]

It might be, or it might not, we shall have to see. Could also be that v4 won't be able to have R21 support. As soon as there is more news, we will let everyone know of course!

[prplmark]

Hi Tom,

I've been using Corona since the alpha versions and now happily pay for Corona's subscription. I use your render engine almost daily. I love it. As a C4D artist/hobbyist I was excited to upgrade to the more affordable R21 and I'm now paying for that as well. I've been refreshing these forums for the last few days in hopes of an update and frankly, you guys are being very dodgy and vague about this right now.

I'm a developer by trade so I totally get where you guys are coming from in not wanting to make any promises. I can only speak for myself but I think just a little more transparency would put my mind at ease. Right now I can only either use R21 w/out Corona or R20 with Corona, and at this point it feels like I'm just wasting my money since I can't use both on a project.

Are there any additional insights your team can provide for us plebs? Is there some sort of incompatibility issue your team is facing? From the outside looking in it appears as if the team is focusing on new features for R20 and not putting a lot of priority on R21 (I'm sure this isn't the case).

With the release of R21 being so affordable I expect a lot of enthusiasts like myself are going to be getting into C4D and Corona is a really easy to learn and accessible render engine that helped me a ton when I was first learning.

Thanks for all that you guys do!

edit: I missed one of your posts from earlier today regarding to porting version 4 vs. moving forward with 5, hoping for some good news!

[philistymon]

Well said, I'm refreshing several times a day, waiting for R21 news, I've been banging out stuff using standard and physical, wanting to use R21.
Some straight up timescale would be appreciated

[everyEnd]

Poor if we have to wait until Q4 to be able to use Corona. Rather, I will start thinking about changing the render engine. It's bad because I have an active license until 02 2020... But if I have to wait 3 months every year for the new version, I see no other option. I really like Corona, but I have no patience for such delays.

[Beanzvision]

Note to self, hire robots to work at twice the speed and without errors ;)

[Nejc Kilar]

Weird. I somehow totally get you guys wanting the R21 version but apart from certain 3ds Max plugins having 0-day render engine releases kind of ain't the norm. Personally I think there is still a lot  that can be done implementation wise (multi-instances?) and if R21 is late for a week or two I'm personally ok with that.

I guess its important to hear everyone's opinion though, maybe the list of priorities inside the team should change if there is enough want.

[prplmark]

Weird. I somehow totally get you guys wanting the R21 version but apart from certain 3ds Max plugins having 0-day render engine releases kind of ain't the norm. Personally I think there is still a lot  that can be done implementation wise (multi-instances?) and if R21 is late for a week or two I'm personally ok with that.

I guess its important to hear everyone's opinion though, maybe the list of priorities inside the team should change if there is enough want.

It's not really the wanting it now per se, I think some of us are just hoping to know when we might expect to see some news. Is it this week? Next week? Two months from now? I'd be more than happy with using the daily beta builds of 5 tbh. No one is asking the Corona Team to work faster, or without errors. Just looking forward to a date or timeline, even if it's not soon. I will wait for a year if I have to, I personally just want to know if I need to adjust my process or cancel my R21 subscription for the time being (or stop using Corona for a little bit).

Again, I love this product and the work that this team does. You all are crushing it. I am constantly trying to get other 3D artists/designers to try it. I will continue to feverishly refresh the forums for updates in the meantime :p

<3

[Nejc Kilar]

@prplmark Right on, thank you for elaborating on that. So for me the takeaway here is that a lot of the "angst" (probably not the most fitting word, sorry about that) could have been avoided with some sort of a statement on how and when the R21 is expected to drop. So yeah, hopefully there is some clarification.

[katzenwaffe]

I'm totally with prplmark on this topic. Seems like very vauge information about the R21 compability. I mean, Octane and U-render realeased updated plugins almost the same day as the R21 release. Even Vray for C4D has released updated plugin with this compability. An update from the very same company who bought Corona, "to make sure development would keep up even better". Kind of funny. I mean, you guys must have had all proper info and SDKs way before the R21 release - just to make sure all was fixed in time for the actual release? As your competitors?

Looking forward to the R21-release.

 

Weird. I somehow totally get you guys wanting the R21 version but apart from certain 3ds Max plugins having 0-day render engine releases kind of ain't the norm. Personally I think there is still a lot  that can be done implementation wise (multi-instances?) and if R21 is late for a week or two I'm personally ok with that.

I guess its important to hear everyone's opinion though, maybe the list of priorities inside the team should change if there is enough want.

It's not really the wanting it now per se, I think some of us are just hoping to know when we might expect to see some news. Is it this week? Next week? Two months from now? I'd be more than happy with using the daily beta builds of 5 tbh. No one is asking the Corona Team to work faster, or without errors. Just looking forward to a date or timeline, even if it's not soon. I will wait for a year if I have to, I personally just want to know if I need to adjust my process or cancel my R21 subscription for the time being (or stop using Corona for a little bit).

Again, I love this product and the work that this team does. You all are crushing it. I am constantly trying to get other 3D artists/designers to try it. I will continue to feverishly refresh the forums for updates in the meantime :p

<3

[swiat3d.net]

For me full support multi-instances it's more important future than R21 support. BTW C4D R21 for me don't have nothing special in compare to R20. I didnt extend my MSA first time :)

[kod3d]

Multishader is awesome!! for me in the IR window the bumb mapping doesn't work, only if I hit normal render, then it renders fine. Also the scene parsing is really slow in IR but very fast for normal render!
Great work!

[everyEnd]

BTW C4D R21 for me don't have nothing special in compare to R20. I didnt extend my MSA first time :)

I thought similarly, but I changed my mind. Another thing was that I had Prime versions, so for MSA 250 € (?) I got a Studio :) Many small things make it definitely cooler to work than on the previous one.

[iacdxb]

Sky/HDRI in multipass not working... anyone tried...?

Thanks.
...

[swiat3d.net]

Sky/HDRI in multipass not working... anyone tried...?

Thanks.
...

Confirm. I have the same problem for sky pass, only black image.

[iacdxb]

Thanks for update.

...

[mrittman]

Also displacement produces a “jagged” effect. I could upload a scene file, but then I’d have to re-install the v5 beta again. I’m kinda lazy lol. Let me know if you guys would prefer scene file.

[frv]

I do agree with the posters here that is huge frustration to wait for unknown periods of time before plugins are updated. I waited for over a year for Laubwerk to update Surface Spread for R20 and by now they seem to have given up on it. I used Maxwell for years but that was the same story. A year ago I just moved over to Corona completely.

Vray is actually completely rewritten for C4d and released  for R21. I took a look at it by the new video's the Chaos group just put on line. I think the Chaos group buying Corona has done a lot of good for Vray for C4D. I think by now Vray for C4D is just as easy to use as Corona is. The price is slightly higher but still comparable with Corona per month. I am still happy with Corona but getting interested again in Vray as of lately.

[horpa]

Thanks for update.

...
+1

[Marvey]

Sky/HDRI in multipass not working... anyone tried...?

Thanks.
...

Confirm. I have the same problem for sky pass, only black image.

same here! i confirm this bug.

[minimaldesign - Blaž]

Sky/HDRI in multipass not working... anyone tried...?

Thanks.
...

Confirm. I have the same problem for sky pass, only black image.

same here! i confirm this bug.

same here also and denoising has no effect on lightmix pass ...denoising only cleans the beauty pass
WIN7
Cinema4d R16
Corona:
Full-speed non-debug version
Build timestamp: Aug 30 2019 13:23:38
Version: 5.0 daily Aug 30 2019 (core 5 (DailyBuild Aug 30 2019))
Cinema version: R16.051 CINEMA 4D Studio (single-license)
Plugin status: Plugin successfully loaded

[BigAl3D]

Make sure this bug is properly reported in their system and not just in this daily build blog.

Sky/HDRI in multipass not working... anyone tried...?

Thanks.
...

Confirm. I have the same problem for sky pass, only black image.

same here! i confirm this bug.

[Frankco]

Note to self, hire robots to work at twice the speed and without errors ;)

Maybe this is not a really bad idea...not the robots but a buggy release with errors! Just for playing with R21. A lot of people are eager to instal the 14days trial of r21 and would like to see what they can achieve with it. But physical or provender is just no option to test it, we need some kind of corona. If it's not that hard to release a not-perfect-maybe-very-buggy Corona for r21 (next to the normal daily builds). I'm sure you have a buggy, but working version right now!.  I will be very happy.

But I also would like to express my concern about this lack of info and update for r21. Realistic information about a target release date is essential for some people. Business decisions needs to be made. So a target release date will be welcome. And updated information when the target will be missed.

[fabrica]

But I also would like to express my concern about this lack of info and update for r21. Realistic information about a target release date is essential for some people. Business decisions needs to be made. So a target release date will be welcome. And updated information when the target will be missed.
[/quote]

+1  , disappointed in the lack of response from Corona to customers , existing and potential. 

(great job on everything else though!)

[houska]

Hi all and sorry for the lack of updates. As of now, we are finalizing the v5 daily with R21 support. If all goes well, we will be able to release it today! Backport of R21 support to v4 will come later if we don't encounter any bugs with it in v5.

[lollolo]

Hi all and sorry for the lack of updates. As of now, we are finalizing the v5 daily with R21 support. If all goes well, we will be able to release it today! Backport of R21 support to v4 will come later if we don't encounter any bugs with it in v5.

Sounds good! I can't wait to test it :)

Thanks!

[frv]

Don't see it yet but good news that the promised "soon" has materialised.

[c4d019]

Hi all and sorry for the lack of updates. As of now, we are finalizing the v5 daily with R21 support. If all goes well, we will be able to release it today! Backport of R21 support to v4 will come later if we don't encounter any bugs with it in v5.

Thanks for the communication, would also like to see v4 support soon as it is the latest official stable release of Corona.

[prplmark]

Hi all and sorry for the lack of updates. As of now, we are finalizing the v5 daily with R21 support. If all goes well, we will be able to release it today! Backport of R21 support to v4 will come later if we don't encounter any bugs with it in v5.

Thank you! Looking forward to testing this weekend!

[houska]

Hi everyone!

Today, we are happy to announce the release of the next daily build of Corona Renderer 5 for Cinema 4D. It contains several new features and bugfixes, but most importantly, we added the Cinema 4D R21 support. Compatibility for Cinema 4D R21 with the stable Corona Renderer for Cinema 4D v4 release will be added next week, as that requires some further work from us. Enjoy the daily build so far!

Download link:
https://drive.google.com/drive/folders/1EMW3qukbimXcoijLO-ypg9__B305py38

Changelog:
https://forum.corona-renderer.com/index.php?topic=26054.msg156272#msg156272

[Frankco]

Thank you all for the hard work! And enjoy a well deserved weekend.

[andeltoz]

Thank you for all this work you do to keep the software updated. For all those who have been thrilled in recent days: just have a little patience!

[everyEnd]

Thank you for the last update :) Finally, I feel that my R21 is suitable for work ;)

[horpa]

Sky/HDRI in multipass not working.

[Visual Pie Workroom]

Sky/HDRI in multipass not working.

Ohh..very useful.

Corona team. Please fixit this on next build.

[fabio81]

the drop-down menu does not work for me. The Render region menu and the IR menu don't work either.
I'm working in windows 10 with the latest Corona 5 beta (August 30th) e Cinema 4d R16.
Cinema R19 instead everything works!
thanks ;)

this still does not work even in this last daily. I cannot save in cxr because the menu does not appear. I am forced to save from the Cinema picture viewer. (Cinema 4d R16 - Windows 10)
Thanks ;)

[leo3d]

No more time for you i think but a little upscale icons size will be perfect run with R21

Thx

[frv]

Solved by Frankco, TX.

Hi, I can't install this latest daily build on my iMac OSX 10.14.6
The installer installs in the R20 folder and does not recognize the "Applications/Maxon Cinema 4D R21" folder
R21 is actually differently installed by the Maxon installer in a folder that is named "Maxon Cinema 4D R21" It used to be "Applications/Maxon/Cinema 4D R20"

I tried to manually move the installed Corona Plugin folder from R20 to the R21 plugin folder but it did not work. The plugin in the R20 folder is named corona4dR20.xlib so maybe the installer does not install a R21 compatible plugin in the R20 folder.

Anyhow, hope the team fixes this asap. I feel a little left out now...

[lollolo]

Hi, I can't install this latest daily build on my iMac OSX 10.14.6
The installer installs in the R20 folder and does not recognize the "Applications/Maxon Cinema 4D R21" folder
R21 is actually differently installed by the Maxon installer in a folder that is named "Maxon Cinema 4D R21" It used to be "Applications/Maxon/Cinema 4D R20"

I tried to manually move the installed Corona Plugin folder from R20 to the R21 plugin folder but it did not work. The plugin in the R20 folder is named corona4dR20.xlib so maybe the installer does not install a R21 compatible plugin in the R20 folder.

Anyhow, hope the team fixes this asap. I feel a little left out now...

Same here. But it works fine with R20 so far :)
Thanks!

[Frankco]

Hi, I can't install this latest daily build on my iMac OSX 10.14.6
The installer installs in the R20 folder and does not recognize the "Applications/Maxon Cinema 4D R21" folder
R21 is actually differently installed by the Maxon installer in a folder that is named "Maxon Cinema 4D R21" It used to be "Applications/Maxon/Cinema 4D R20"

I tried to manually move the installed Corona Plugin folder from R20 to the R21 plugin folder but it did not work. The plugin in the R20 folder is named corona4dR20.xlib so maybe the installer does not install a R21 compatible plugin in the R20 folder.

Anyhow, hope the team fixes this asap. I feel a little left out now...

It's there. During the install at the "Installation Type" at the left-bottom there is a button "Customise". There you can check R14,15.....20 and also R21

[frv]

You're right. Tx. I should go to bed early these days...

[katzenwaffe]

THANKS!!! :)

Hi everyone!

Today, we are happy to announce the release of the next daily build of Corona Renderer 5 for Cinema 4D. It contains several new features and bugfixes, but most importantly, we added the Cinema 4D R21 support. Compatibility for Cinema 4D R21 with the stable Corona Renderer for Cinema 4D v4 release will be added next week, as that requires some further work from us. Enjoy the daily build so far!

Download link:
https://drive.google.com/drive/folders/1EMW3qukbimXcoijLO-ypg9__B305py38

Changelog:
https://forum.corona-renderer.com/index.php?topic=26054.msg156272#msg156272

[tuami]

Latest Beta, Problem with hair material in r20 and r21

[Mala]

Anyone else that cant´t get the Nvidia denoiser to work with this version?

"Failed to initialize NVIDIA AI denoiser: Maybe your graphics card doesn't support NVIDIA AI denoiser or Corona denoiser component or GPU drivers are not installed correctly. Please follow the provided link.
Missing DLL: optix.6.0.0.dll   Learn more »"

Tryied the universal installer for NvidiaAiDenoiser but it doesnt help

GTX 1080 TI
Nvidia driver 436.30

[artdude12]

Try going to your Corona folder in your Program Files and see if there is an optix folder. If there is an optix folder, look inside and it should have  four files (see attached). If it does have all four files, make sure they all have the same date. If there aren't four files or the dates don't match, try deleting the optix folder (or just move the folder somewhere else)  and re-run the Corona installer using the custom install. Make sure the nvidia AI checkbox is checked. This worked for me.

[c4d019]

Hi everyone!

Today, we are happy to announce the release of the next daily build of Corona Renderer 5 for Cinema 4D. It contains several new features and bugfixes, but most importantly, we added the Cinema 4D R21 support. Compatibility for Cinema 4D R21 with the stable Corona Renderer for Cinema 4D v4 release will be added next week, as that requires some further work from us. Enjoy the daily build so far!

Regarding R21 support for v4, are we still on track for a release this week as promised?

Thanks.

[TomG]

Umm, it was just released - it's in the News on the forum, and on our Facebook, Twitter and Instagram :)

https://forum.corona-renderer.com/index.php?topic=26331

(and in both Facebook Corona groups, and in the Cinema 4D Facebook group....)

[c4d019]

I don't use social media, might be a good idea to email your customers in order to communicate something important, you might also want to update the actual download page as it says 'Works with Cinema 4D R14-R20'.

[houska]

Hi c4d019!

Thanks for catching that little inconsistency on our webpage, we will change it!

[Beanzvision]

Latest Beta, Problem with hair material in r20 and r21

Nice catch, I can also confirm this crash. Reporting it now.

Internal ID: 403256369

[Marvey]

Latest Beta, Problem with hair material in r20 and r21

Nice catch, I can also confirm this crash. Reporting it now.

Internal ID: 403256369

please report the bug already reported but not fixed yet the "Sky/HDRI in multipass not working"
thank you

[fabio81]

I'm having problems with nodes. When I open the scene,  i see the preview red, yellow and I don't load the material. happens to you too?

[burnin]

I'm having problems with nodes. When I open the scene,  i see the preview red, yellow and I don't load the material. happens to you too?

OS, versions, screenshot... more info would be helpful ;)
Otherwise no, no such problem.
W10, R20.059, Corona5 daily (2019-09-20)

[nightwalker]

The Sky in lightmix seems don't work. C4d R19 Mac osx Mojave

[swiat3d.net]

The Sky in lightmix seems don't work. C4d R19 Mac osx Mojave

Also on Windows.
From about September 14th it is known about the bug but still quiet for fixes :/

[Tommyvfxer]

Every other render Engines support multi-instance very soon. But why Corona DO NOT ? Even now is R21. I can not render a large scene or a serious scene with multi instance and mograph and always have to switch to other renderers . This is really anoyying.

[Cinemike]

Every other render Engines support multi-instance very soon. But why Corona DO NOT ? Even now is R21. I can not render a large scene or a serious scene with multi instance and mograph and always have to switch to other renderers . This is really anoyying.

You are aware, though, that multi-instances "just" don't render in the IR, but do very well appear in "normal" VFB or viewport rendering?

[iacdxb]

Every other render Engines support multi-instance very soon. But why Corona DO NOT ? Even now is R21. I can not render a large scene or a serious scene with multi instance and mograph and always have to switch to other renderers . This is really anoyying.

Multi-instance works in Corona render but not yet in IR.

...

[tuami]

Next "small" bug

https://forum.corona-renderer.com/index.php?topic=26451.0

I've already gotten used to the corona running unsteadily, but such things are elemental ...

[Nejc Kilar]

Every other render Engines support multi-instance very soon. But why Corona DO NOT ? Even now is R21. I can not render a large scene or a serious scene with multi instance and mograph and always have to switch to other renderers . This is really anoyying.

You are aware, though, that multi-instances "just" don't render in the IR, but do very well appear in "normal" VFB or viewport rendering?

Hey Cinemike, I gotta be with the Tmmyvfxer here, sorry :) Corona being primarily an architectural renderer and not supporting multi-instances in the IR is a major drawback.

Simple example -> You can't edit materials if your grass isn't showing up and the entire color tint of the scene changes because of that. Sure, you can go the old school route without using IR but at that point you are essentially back in the '00s in terms of rendering tech :))

[Cinemike]

Hey Cinemike, I gotta be with the Tmmyvfxer here, sorry :) Corona being primarily an architectural renderer and not supporting multi-instances in the IR is a major drawback.

Simple example -> You can't edit materials if your grass isn't showing up and the entire color tint of the scene changes because of that. Sure, you can go the old school route without using IR but at that point you are essentially back in the '00s in terms of rendering tech :))

I did not say it wasn't important and I am sure it will get fixed, because it is so important. But when reading about "no multi instances with Corona", I almost instantly sense two emotions cooking up: first, there's the "I have not tried it outside of IR but I go with the stream and yell 'murder'" and/or second, I get this total "we are all going to die!" vibe.

I still think it IS possible to bridge the time with working around the issue with render instances and a lower LOD (less objects) for the time being. Multi-Instances aren't working with the IR, that's a fact, and if it were a simple fix, I am sure it would work already. I just think we should keep our cool. What would you all have done if Maxon had not introduced multi-instances at all? People worked with C4D and Corona before that, you know.

Don't panic ^^

[Nejc Kilar]

Well I agree with you there, I don't like people yelling about new features either. To an extent though, I do understand where its coming from. It is one of those features I think most arch-vizers out there expected would drop a few weeks after R20 was released but wasn't on top priority (I'm guessing) until lately when more and more people started talking about it.

Still, I'd like to reiterate, I don't like it when its said in caps or with an impressively negative tone. That being said, not fully supporting the new incredibly important system a few months after launch without much about it was bound to create uneasiness.

[swiat3d.net]

From month to month I get the impression that the C4D version is treated as a worse category product. Even for basic things you have to wait for months to be repaired, like a problem with black sky in lightmix. The sad part is that the C4D version it costs the same as the 3ds max version.

[TomG]

Let me assure you that it is not treated as a worse category product. Bear in mind that there is more to do for Cinema 4D, as the Max version has had many more years of development so has had much more time to mature (and hey, Corona 1 cost the same as Corona 4 there too, so it's not like they had "reduced pricing" early on either).

Also when implementing for C4D there are extra things that had to be tackled that Max never needed. Both development teams are separate, so there's no way it can be treated as "worse" (as in, moving devs to work on Max rather than C4D - doesn't happen). So there are a larger list of issues to be tackled for C4D than Max, including when things pop up such as R21 needing a lot of work to integrate with and backporting that to Corona 4 (which of course does take developers on the C4D team away from working on new features or other fixes - but we follow what the community is asking for the most).

[TomG]

As always, for faster development the only solution is more developers - send them to https://corona-renderer.com/about/jobs :)

[Designerman77]

As always, for faster development the only solution is more developers - send them to https://corona-renderer.com/about/jobs :)

I have a cousin who is programmer. Shall I propose him to join? :)))

Guys, what you did in the last years, optimizing Corona for C4D, is magic. Despite some improvements which are still needed.
Just 1 1/2 years ago, what came out from C4D&Corona was raw, compared to today's results.

Keep up the great work!

[TomG]

For sure, we welcome all applications! It is super hard to find good programmers (and we do need GOOD programmers, not just bodies to fill seats :) ), so the more folks that apply, the better!

[houska]

Hello fellow Coronauts!

We are releasing another daily build today. Apart from a few small fixes and changes we added the first version of our support for the C4D Enhanced OpenGL feature. Keep in mind that it is still an ongoing endeavor, so it is not feature-complete by all means. But it is a foundation that we can work on and add new features so that it looks better and is more useful. For now, we interpret the diffuse, opacity and reflection channels in the Corona Material.

A Mac-related note: this daily build is also the first build which went through the notarization process on Mac OS, so if you find any issues related to the notarization, please tell us so that we can fix it.

Download link:
https://drive.google.com/drive/folders/1EMW3qukbimXcoijLO-ypg9__B305py38

Changelog:
https://forum.corona-renderer.com/index.php?topic=26054.msg157578#msg157578

[lollolo]

I got a massiv viewport speed issue on heavy scenes with the newest daily build. 
Viewport freeze all the time when I want to move my camera.

Back to an earlier daily build fixed this for me. Or maybe I just missed something?

Mac OS 10.14.6
C4D R20

[nightwalker]

I can confirm big problems with the viewport, I also went back to using the previous build.

MacOS 10.14.6
C4d R19

[horpa]

IR is not working properly - C4D R17 - it stops working when the light color changes

[leo3d]

Same viewport problem from windows 10

[Beanzvision]

Hi guys, If you have any bugs you wish to report, can you please either use the official link here: https://help.c4d.corona-renderer.com/support/solutions/articles/12000033461-how-to-report-issues-c4d or the bug section of the forum.

On second thoughts, it's okay to report it here ;)

[xxxsalvo]

20 September Corona 5 Build - Cinema 4D R19 - Mac OS 10.14.5

Hi, I have a bug with this daily build: Hdri not recognized in Lightmix. I have a black layer. Please fix it, thanks.

[4b4]

this is listed as fixed in the latest build from 15/10

[xxxsalvo]

Oh sorry, thanks.

[fabio81]

Hi,

in the future will it be possible to see the preview of the rayswitch material?

[houska]

Hi,

in the future will it be possible to see the preview of the rayswitch material?

Yes, that is definitely planned in the future!

[Frankco]

Hi, Just a question regarding the Enhanced OpenGL. I don't get it. Obviously it's a first step with limited functionality, but I don't see any difference except black objects or object not visible at all or only wireframe.
Do I need to toggle a special switch to enable/disable things (I toggled all 'enhanced openGL' function from the options menu without any luck) But keep a messed up viewport. (MBP + Radeon pro 555X 4GB)
I understand the Radeon and the 4GB doesn't help much, but I think Corona is per definition the (only) best render option for people with no acces to GPU rendering with NVidea cards....read:allmost all Mac's

For future releases it would be nice to have a switch which turn this functionality totally off, now the viewport is not workable (also when Enhanced Open-GL is deactivated from the options-menu).
If a next daily build has the same issues people probably won't test it anymore and stay at the last 'workable' build. Which results in less feedback about other 'issues/features' in new builds.
So I guess this feature was a bit too early to release (even for daily builds)

But again, maybe there is a magic switch I need to flip for all of it to work perfectly :)
Anyway, still very much happy with Corona, keep up the good work!
Frank

[philistymon]

That version (Oct 15) does not work at all for me,
opened a fairly heavy scene that was working very well with the previous daily build and it kept hanging, objects not displaying.
R21 - Mac 10.14.6

[sylbot]

the new version enhanced opengl works on windows and nvida but with too many bugs and it is actually very incomplete.

the "constant shading" mode no longer works, only the "quick shading" or "gourau shading" mode is active.

the whole scene is much darker than before and some textures look black.

opacity mode and corona reflection is much better managed now it's great.

these improvements are very important for me because I work as a team and I show 3D scenes in opengl view before calculating.
a lot of color and aesthetic choices are made at this time in real time.

until you go integrated C4D corona?
you seem to want to go further than the competitors.
will glass and chrome materials be handled one day?

[Marvey]

Same viewport problem from windows 10

Same here, R21 windos 10

[fabio81]

Hi,
why does this happen? it happens in IR mode while I adjust the colors

[fabio81]

Hi guys,
I noticed that the light with 50% direction does not appear to be visible through a glass.
I attach the scene
this with the latest build, win10 and Cinema R16
thanks

[houska]

Hi guys,
I noticed that the light with 50% direction does not appear to be visible through a glass.
I attach the scene
this with the latest build, win10 and Cinema R16
thanks

Hi Fabio! This is a known issue and is connected with the "Prevent black appearance" option, which fakes the light's color to be white when viewed directly, although it is physically incorrect. And the fake has to be disabled for other types of rays, otherwise the light would not be directional. But as you discovered, there are some corner cases, where it does not look good - like when the light is viewed in a mirror or through glass. It might be fixable, but it's not straightforward.

(Internal ID=223075528)

[fabio81]

perfect, thanks Houska ;)

[TomG]

Meantime as a workaround, use the "two lights" approach - one set not to emit light, no directionality, visible to the camera; the other casting light, with directionality, invisible to the camera (the first light here can just be geometry with a LightMtl too if you prefer, for some reason).

[fabio81]

Meantime as a workaround, use the "two lights" approach - one set not to emit light, no directionality, visible to the camera; the other casting light, with directionality, invisible to the camera (the first light here can just be geometry with a LightMtl too if you prefer, for some reason).

yes, I had already done so :)

[koubankeo]

Version: 5.0 daily Oct 15 2019 (core 5 (DailyBuild Oct 15 2019))

A layer shader with filter shader is very slow to set up during IR rendering.

[JPeters]

Don't know if this is an issue specific to this version of Corona but:

When I plug a C4D noise in the shader as for instance diffuse, on a specific scale so it has the correct size and if I then render the image, the noise is *much* larger than it was in the viewport.

We had a similar issue months ago when we switched from Corona3 to Corona4 I believe, that suddenly the sizes of the noises were completely off when images were rendered.

Please see attached a screengrab of the noise in the viewport and the same exact noise on render-time.

[Cinemike]

Don't know if this is an issue specific to this version of Corona but:

When I plug a C4D noise in the shader as for instance diffuse, on a specific scale so it has the correct size and if I then render the image, the noise is *much* larger than it was in the viewport.

We had a similar issue months ago when we switched from Corona3 to Corona4 I believe, that suddenly the sizes of the noises were completely off when images were rendered.

Please see attached a screengrab of the noise in the viewport and the same exact noise on render-time.

Viewport (OpenGL) and rendered noise scales are only the same when you use UV space for the noise. It's a C4D thing.

[JPeters]

Viewport (OpenGL) and rendered noise scales are only the same when you use UV space for the noise. It's a C4D thing.

Odd, it used to work fine, but thanks as this indeed works as well!

[fabio81]

hi guys,

I'm trying the version (Sep 20 2019) but it is a bit slow with the node system. Whenever I open the scene it does not completely load the materials and consequently they are not displayed during the render. Does it just happen to me?
This happens only with the node system on Cinema 4d R16 and win 10.
The last build (Daily Build 2019-10-15) from too many problems and many crashes to the preview of the materials
thanks

[fabio81]

in this way I see myself forced to not be able to use the node editor of the materials, even though with a series of renderings to send in the queue, they would be wrong.
I would like to know if it is a known problem or just happens to me.
thanks

[houska]

A nice day to you all!

Today, we are releasing another daily build. As we are nearing the official release of V5, we are concentrating on bug fixes and various other improvements. Out of these, I'd like to bring your attention to the updated Corona Proxy support. We have been getting reports of scenes being unusable because of the Corona Proxy reloading all the time. The reloading should now be fixed and we also added animation support into the proxies. Moreover, we will soon improve the loading itself in case of multiple proxies that need the same data.

Also, note that the improved OpenGL viewport has been disabled by default and there is now a new option to enable it in the Corona global preferences (it needs a restart of C4D). We did this in order to address the issues that some people had with this new feature. But we will keep improving its usability so that it can be turned on by default in the future. You are welcome to keep testing it!

Download link:
https://drive.google.com/drive/folders/1EMW3qukbimXcoijLO-ypg9__B305py38

Changelog:
https://forum.corona-renderer.com/index.php?topic=26054.msg158659#msg158659

[houska]

hi guys,

I'm trying the version (Sep 20 2019) but it is a bit slow with the node system. Whenever I open the scene it does not completely load the materials and consequently they are not displayed during the render. Does it just happen to me?
This happens only with the node system on Cinema 4d R16 and win 10.
The last build (Daily Build 2019-10-15) from too many problems and many crashes to the preview of the materials
thanks

Hi Fabio! We are aware of some node editor issues and we will be fixing them soon. If you want to upload it for us, a scene for us to debug would be great!

Otherwise, I'd suggest to check the newest daily build, because the OpenGL viewport previews have been disabled there, so there shouldn't be so many crashes anymore.

[fabio81]

Hi houska!
thanks for the reply, I'll upload the scene tomorrow. Meanwhile, I download the latest build! :D

[fabio81]

the problem also gives a simple scene like this. Try to render as soon as you open the scene.
I think it's a refresh problem, if you click on the various nodes, one at a time, the material works.

Cinema 4d R16 -Win 10 - Daily Build 2019-11-05

I hope it's useful

[houska]

Thanks for the scene Fabio! There's never enough good testing scenes and this one is very good, because it's simple! I tested the issue on your scene and can confirm both the black and the yellow shader issues. We will be fixing the node editor issues at the beginning of the development cycle for v6

(Internal ID=419472009)

[fabio81]

Thanks for the scene Fabio! There's never enough good testing scenes and this one is very good, because it's simple! I tested the issue on your scene and can confirm both the black and the yellow shader issues. We will be fixing the node editor issues at the beginning of the development cycle for v6

(Internal ID=419472009)

great! I am very pleased thanks! :D

[fabio81]

Hi,

with IR I have this problem, I don't view correctly. Is it a bug?
Fast denoise AI disabled

Cinema 4d R16 -Win 10 - Daily Build 2019-11-05

[Beanzvision]

Hi,

with IR I have this problem, I don't view correctly. Is it a bug?
Fast denoise AI disabled

Cinema 4d R16 -Win 10 - Daily Build 2019-11-05

Care to share the scene with us via the private uploader?
https://corona-renderer.com/upload

[fabio81]

Hi,

with IR I have this problem, I don't view correctly. Is it a bug?
Fast denoise AI disabled

Cinema 4d R16 -Win 10 - Daily Build 2019-11-05

Care to share the scene with us via the private uploader?
https://corona-renderer.com/upload

sent now (1573214244_leaf-normal-bump.rar)
thanks

[andeltoz]

Hello.
I would like to report a problem with different display of the bump channel, between IR and VFB. The two views have different scales of the bump channel. This does not happen on the diffuse channel.
I attach the simple test scene.

Note:
iMac,   Intel Core i7 3,4 GHz
Ram: 32 GB
OS: High Sierra
Cinema 4d R21
Corona Version: 5.0 daily Nov 5 2019 (core 5 (Release Candidate 4))

[fabio81]

in the queue to render it is impossible to use the node system, shaders are not loaded .. I hope it will be resolved soon

Cinema 4d R16 -Win 10 - Daily Build 2019-11-05

thanks

[metopa]

Hi fabio81,

Can you confirm that this happens only when used with team render?

Thanks

[fabio81]

Hi fabio81,

Can you confirm that this happens only when used with team render?

Thanks

I don't use team render, but a plugin (pv render queue - NIKLAS ROSENSTEIN'S DLC) that allows me to launch c4d files, so as a render ends another file from the queue is loaded.
The problem always happens even when opening a simple file without using the plugin because it is a problem of refreshing the nodes. To solve each time i have to click on each single node and change some small value to update the node and then everything works.
Regarding the plugin and the render in queue i have always used that plugin even with 20 files and it has always worked but with shaders without a node system.
I hope it's useful

[Beanzvision]

Can you also check if the shared shader is being used in your material? If so, the workaround would be to not use it.

[fabio81]

Can you also check if the shared shader is being used in your material? If so, the workaround would be to not use it.

sure it is used, watch the video

https://drive.google.com/open?id=1hzAecJUOmKK7JBibiwN4oT2S7nIqLj0z

[houska]

I don't use team render, but a plugin (pv render queue - NIKLAS ROSENSTEIN'S DLC) that allows me to launch c4d files, so as a render ends another file from the queue is loaded.

Hi fabio81! I just tried it and everything works fine as long as I render locally. When I turn on Team Render, it suddenly doesn't work. Can you confirm that this is only happening with Niklas' plugin in TR?

[fabio81]

Hi Houska,
the plugin does nothing but take a file and launch the render, it shouldn't affect.
If I open a normal scene and immediately launch the render it doesn't work for me

[houska]

Hi Houska,
the plugin does nothing but take a file and launch the render, it shouldn't affect.
If I open a normal scene and immediately launch the render it doesn't work for me

Ah, I see. It's the same issue that you already reported here, right? As I said, we will be fixing all these node editor issues soon. Meanwhile, we are preparing some sort of a workaround for the V5 release...

[fabio81]

I had already reported, in the meantime i will have to give up the node editor.
thanks a lot See you soon

[jojorender]

Hi Corona Team,
created scene in V.4.0  Now installed V.5 RC 4 and the scene parsing went from a couple of minutes to 27 min. See screenshots attached.
All single machine rendering.
It’s the same scene, difference in render settings:
V. 4 used displacement screen 3px and 2. GI solver Path tracing
V. 5 used displacement screen 4px, 2.5 displace active and 2. GI solver UHD Cache.
Don’t think that choice of GI solver influences parsing time, and for displacement value, 4px should make parsing faster, if anything…
Tried twice including restarting the machine, same crazy long parsing time, went back to V.4.0

It’s a large scene, but if you want it for testing, I can send it to your private uploader.
If so, do you have list of installed plugins on your systems?
I use Forester Multicloner to scatter unbaked Forrester trees, grass, etc. There might also be still some unbaked “MeshBoolean” in this scene. 

[Beanzvision]

Hi Corona Team,
created scene in V.4.0  Now installed V.5 RC 4 and the scene parsing went from a couple of minutes to 27 min. See screenshots attached.
All single machine rendering.
It’s the same scene, difference in render settings:
V. 4 used displacement screen 3px and 2. GI solver Path tracing
V. 5 used displacement screen 4px, 2.5 displace active and 2. GI solver UHD Cache.
Don’t think that choice of GI solver influences parsing time, and for displacement value, 4px should make parsing faster, if anything…
Tried twice including restarting the machine, same crazy long parsing time, went back to V.4.0

It’s a large scene, but if you want it for testing, I can send it to your private uploader.
If so, do you have list of installed plugins on your systems?
I use Forester Multicloner to scatter unbaked Forrester trees, grass, etc. There might also be still some unbaked “MeshBoolean” in this scene.

Hi, sending us the scene would be great. We can get access to those plugins so no need to worry there. ;) Thanks
https://corona-renderer.com/upload

[houska]

Hello Corona aficionados!

We are pleased to present to you the first Release Candidate of your favorite rendering engine. The highlights of this release as compared to the previous daily build are support for multiple environments in LightMix, improved Corona Proxy performance with large amount of Proxies loading the same data and several important crash fixes.

With the final release of V5 closing in, we will now be focusing solely on fixing bugs and crashes, so if you need something fixed until the stable release, please don't hesitate and report the issue!

Download link:
https://drive.google.com/drive/folders/1BxlBSWEkpZSR-54EHJGkoONNW20DYPBB

Changelog:
https://forum.corona-renderer.com/index.php?topic=26054.msg159176#msg159176

[Marvey]

adding a corona sky, inside selecting shader/HDRI and then adding the HDR works ok, but if you add a "filter" to the HDRI to fix colors etc it renders black.

Version: 5.0 rc 1 (core 5 (Release Candidate 4))

[Br0nto]

A lot of good things in that changelog.

As for remaining fixes and bugs:

Non-animating corona light objects with motion blur. Did this ever get a fix?
https://forum.corona-renderer.com/index.php?topic=26296.msg156449#msg156480

Instances and motion blur (specifically old issues with objects moving weirdly when object motion blur is on, as well as random instances not showing the motion blur at all frame to frame):
https://forum.corona-renderer.com/index.php?topic=26160.msg156567

Thanks!

[houska]

adding a corona sky, inside selecting shader/HDRI and then adding the HDR works ok, but if you add a "filter" to the HDRI to fix colors etc it renders black.

Version: 5.0 rc 1 (core 5 (Release Candidate 4))

Wow, good catch! Thanks, we'll have a look at it!

[houska]

Non-animating corona light objects with motion blur. Did this ever get a fix?
https://forum.corona-renderer.com/index.php?topic=26296.msg156449#msg156480

Instances and motion blur (specifically old issues with objects moving weirdly when object motion blur is on, as well as random instances not showing the motion blur at all frame to frame):
https://forum.corona-renderer.com/index.php?topic=26160.msg156567

Hi Br0nto, these issues unfortunately haven't been fixed yet. We are planning to start working on the instance issues at the beginning of the v6 development cycle, so stay tuned for the daily builds!

[Br0nto]

Great to hear, thank you!

[Marvey]

adding a corona sky, inside selecting shader/HDRI and then adding the HDR works ok, but if you add a "filter" to the HDRI to fix colors etc it renders black.

Version: 5.0 rc 1 (core 5 (Release Candidate 4))

Wow, good catch! Thanks, we'll have a look at it!

thank you

[Studio Heisenberg]

Got some strange splotches from Corona Sun, attached image( visible in lower left corner, and you can spot it in other places too). It does not help adding corona tag to Sun and uncheck reflection and refraction.

[Nejc Kilar]

Got some strange splotches from Corona Sun, attached image( visible in lower left corner, and you can spot it in other places too). It does not help adding corona tag to Sun and uncheck reflection and refraction.

Those kind of look like Caustics issues to me. Do you have them enabled by any chance perhaps?

[TomG]

It does remind me of reflections of caustics (that is, there is a caustic result somewhere, which is showing up in the reflection of another material) - takes a while to clean up if so. Starting point would be whether or not caustics are enabled as Nejc asks :)

[iacdxb]

Hi,

May be caustics but I am not using, just one material with very low glossiness....!

Used sky with HDRI in Light material.
- See difference, new rc1 is more brighter and fireflies.... every where.
- Last beta, dark and clear.... no fireflies and caustics....!

Something goes wrong in new sky and HDRI features and which one is giving correct light, last daily build or rc1....?


Thanks.
...

p.s.
its just a screen shot from one side...!

[TomG]

Do you mean using the new Corona Sky object, vs. the old Corona Sky tag on a C4D Sky object? If so, note that you no longer need to use a Corona Light Mtl with the HDRI in it, you can simply select the HDRI / Shader mode in the Corona Sky, and load the HDRI directly in there.

If applying a Corona Light Mtl on top of the Corona Sky object (not recommended), you will need to manually change the projection of the HDRI to Spherical (I think that was done automatically before when using the Corona Sky tag on top of a native C4D Sky object).

(a screengrab of your Sky set ups would be useful here :) )

[iacdxb]

Here is screen shot and scene file.

HDRI light set by Sky rotation is easier and handy than putting offset values in Syy HDRI slot.
And if HDRI used in sky hdri slot, sky rotation shows in view port but it does not effect. HDRI used in sky hdri slot, is much brighter light than adding hdri in light material to sky, it should not be same light effect, its ny hdri slot or by light material...?
And seeing... Sky in shader also....!

Thanks.
...

[Studio Heisenberg]

It does remind me of reflections of caustics (that is, there is a caustic result somewhere, which is showing up in the reflection of another material) - takes a while to clean up if so. Starting point would be whether or not caustics are enabled as Nejc asks :)

not indeed caustics, I did had them in few materials. but this is without any caustics on

[jojorender]

Hi Corona Team,
created scene in V.4.0  Now installed V.5 RC 4 and the scene parsing went from a couple of minutes to 27 min....

Hi, sending us the scene would be great. We can get access to those plugins so no need to worry there. ;) Thanks
https://corona-renderer.com/upload

Uploaded scene to dropbox - "jojorender_V5-RC4_parsing_time.zip". Let me know if there are issues using the scene.
Thanks.
EDIT:
Getting confused by your naming convention. I tested V5 RC 4 last weekend, but you posted RC 1 yesterday.
Is this a countdown?

[TomG]

On the naming convention:

- The VFB shows the CORE that Corona is based on. The current RC1 for Cinema 4D is based on the RC4 of the core (from Max)
- The About section will show you the naming of the version for C4D (will be RC 1)

They always count up, and Corona for C4D has only had RC 1 so far (next will be RC 2); it's just that the VFB title bar shows you the core version of Corona being used :)

[iacdxb]

Hi TomG,

Have you tried file....?
In R20 its same with fireflies.

Thanks.
...

[TomG]

Hi!

No, I have not tried the file - that would be for support and developers to dive into :) I was just popping in to explain the naming conventions there.

Cheers!
   Tom

[Frankco]

Hi Corona team, thanks for the last RC. All seems pretty stable and more memory friendly. (less crashes)
One thing: When the the Corona VFB is open and I shut down C4D, C4D crashes always and becomse un-responsible (spinning beachball on Mac). I need to do a force quit.
Each and every time . But if I manually close VFB before quitting C4D there is no problem.
A small thing, but annoying.
I'm on MacOS 10.14.4, C4Dr21.022 , latest Corona build "Version: 5.0 rc 1 (core 5 (Release Candidate 4)"
(I agree the naming of the build are confusing)

[iacdxb]

Yes, I noticed also this, when IR open and quit c4d manyually.... it takes time but in my side it does not crash....!

...

[Beanzvision]

Hi TomG,

Have you tried file....?
In R20 its same with fireflies.

Thanks.
...

I've tested your scene and had no exposure differences between an HDRI light material applied to a Corona Sky vs an HDRI loaded within the Corona Sky object. Both rendered with the 100 passes that were set up in your scene.

[houska]

Hello everyone!

Release Candidate 2 of Corona Renderer for Cinema 4D is out! We fixed a few crashes and bugs this time and are busily preparing the final release. Stay tuned!

Download link:
https://drive.google.com/drive/folders/1BxlBSWEkpZSR-54EHJGkoONNW20DYPBB

Changelog:
https://forum.corona-renderer.com/index.php?topic=26054.msg159461#msg159461

[fabio81]

Hi Corona team,
thanks for the updates! for me the problem of the node editor cannot be solved, I tried also with the new tool but after the conversion the multimap node loses all the paths. Perhaps the problem is the multimap node? because it's just what gives me problems now while everything else works. I am attaching two screen shots before and after shader conversion.

I wanted to ask you something else, I'm doing an exterior animation with PT + PT with pass limit and GI / AA 8 - LSM 2 to have a more accurate AA, it is normal to have 01.45 of parsing scenes and 01.00 of geometry for each frame ?
thanks

[Studio Heisenberg]

It does remind me of reflections of caustics (that is, there is a caustic result somewhere, which is showing up in the reflection of another material) - takes a while to clean up if so. Starting point would be whether or not caustics are enabled as Nejc asks :)

not indeed caustics, I did had them in few materials. but this is without any caustics on

Found the problem, those splotches are affected by Sun seems like they disappear when we untick generate caustics in Corona Sun.

[ddaker]

Is there any chance you guys could allow people to go below the standard 10 abbe number under refraction, this request has been asked multiple times for over a year, please can you guys implement it?

please.

[Nejc Kilar]

It does remind me of reflections of caustics (that is, there is a caustic result somewhere, which is showing up in the reflection of another material) - takes a while to clean up if so. Starting point would be whether or not caustics are enabled as Nejc asks :)

not indeed caustics, I did had them in few materials. but this is without any caustics on

Found the problem, those splotches are affected by Sun seems like they disappear when we untick generate caustics in Corona Sun.

Thanks for sharing what caused it. Super weird though, you'd think if caustics are disabled then that toggle has no effect. Weird stuff.

[redpix]

Hi, crash caused by IR if i change material parameters.

[houska]

Hi, crash caused by IR if i change material parameters.

Hi, do you by any chance remember which parameters you changed before the scene crashed?

Edit: Unfortunately, I am not able to get a crash in your scene :-(

Edit: Also, would you be able to send the _BugReport.txt, as the message box states?

[Beanzvision]

Hi, I would also recommend resending the file with all the materials linked. We can't test it fully because some texture maps are missing. Please use "save project with assets" and upload it again using our private uploader. Don't forget the crash report too ;)
https://corona-renderer.com/upload

[puscyfer]

I've got this strange issue with corona, tried it with version 4 and 5. Started happening after I updated from version 3. The corona sun is invisible in render, and in a minute starts to bug out the whole plugin effectively crashing C4d. Tried it with C4D version 19 and 21. Same issue, seems to be plugin related.

Drivers are up to date... wouldn't know what the issue could possibly be. I attached the bugreport.


* Disregard this post, the issue has been fixed

 

[Beanzvision]

I've got this strange issue with corona, tried it with version 4 and 5. Started happening after I updated from version 3. The corona sun is invisible in render, and in a minute starts to bug out the whole plugin effectively crashing C4d. Tried it with C4D version 19 and 21. Same issue, seems to be plugin related.

Drivers are up to date... wouldn't know what the issue could possibly be. I attached the bugreport.


* Disregard this post, the issue has been fixed

Hi, So the disappearing sun issue has now been fixed? Was this fixed by you or have you upgraded to a newer version? We take all crashes serious and if it wasn't fixed by us then we will need to address it. On the other hand, if upgrading has solved this we can disregard as you mentioned. Thanks!

[houska]

Hi everyone!

Release Candidate 3 of Corona Renderer for Cinema 4D has been released! This time, we fixed some further issues that have been discovered with the previous release candidates. It seems like we should be able to release a stable version soon. But as always, if you encounter a crash or a bug, it will be great if you report it so that we can issue a fix, either before the release or in a possible Hotfix release.

Download link:
https://drive.google.com/drive/folders/1BxlBSWEkpZSR-54EHJGkoONNW20DYPBB

Changelog:
https://forum.corona-renderer.com/index.php?topic=26054.msg160000#msg160000

[jojorender]

Hi Corona Team,
created scene in V.4.0  Now installed V.5 RC 4 and the scene parsing went from a couple of minutes to 27 min. ...

Hi, sending us the scene would be great. We can get access to those plugins so no need to worry there. ;) Thanks
https://corona-renderer.com/upload

Hi beanz,
did you have a chance to test the scene I sent? Any idea what's causing the increase in parsing time? Did not see this addressed in the recent RC's

[Barendby]

I am not able to install the latest beta (RC3)

I get this error

[horpa]

+1

[leo3d]

+1

[bs]

+1

[houska]

-1

Should be fixed now! ;-)

[Barendby]

-1

Should be fixed now! ;-)

THANKS, will try again :)

[Pepelecrabb]

I get an instant crash when I try to select a lut in the VFB. Tried on 2 different machines so far.

[TomG]

I get an instant crash when I try to select a lut in the VFB. Tried on 2 different machines so far.

For a crash, it is always good to send the _BugReports.txt file(s), see https://help.c4d.corona-renderer.com/support/solutions/articles/12000033461-how-to-report-issues-c4d

[Pepelecrabb]

Thanks TomG, just uploaded bugreports.

To add a little more information:

Finding and selecting a lut works fine for me in the Corona Standalone.
In the Corona VFB, if I direct Corona to the lut folder and select a lut, it works.
In the VFB if I go to the dropdown list to select a lut after making sure Corona is pointed to the correct lut folder, it locks up.

[leo3d]

it wiil be perfect with Hight Icon Size for R21 and UHD Screen

A little thing

thx

[Pepelecrabb]

TomG, I upgraded from RC3 to Corona Renderer 5 final and I still have the same issue of crashing when I try to select a LUT.

So I rolled back to Corona Renderer 5rc2 and the LUTs work fine again, or at least in its old clunky, unorganized way as always.

Another bug report sent.

[TomG]

TY for the other report! BTW, just as a heads up, it won't be me investigating the issue (since I am not development or support), just so you know to expect the replies to come from another source :)

[iamjens]

Copy function out of the interactive rendering vfb does not work. c4d r21, corona 5 rc, mac os mojave

[Pepelecrabb]

Thank you TomG. Another little clue for whom it may concern, I get this error message also sometimes.

Mac OS 10.14.6 C4d R17

[Evolist_ua]

Guys, this bug with dual-processor systems and textures, which I wrote about in this thread (https://forum.corona-renderer.com/index.php?topic=24238.0), is still there(((

[lollolo]

I don't know if you know this already. Bump isn't working if a layer is used.

Example: Same Noise, on the left inside of a Layer shader, on the right without.

Mac OS 10.14.6

Build timestamp: Nov 27 2019 22:17:36
Version: 5.0
Cinema version: R20.059 CINEMA 4D Studio (single-license)
Plugin status: Plugin successfully loaded

[3DInteriors]

C4D always crash when i'm rendering with Corona 5
Daily 2019 10 15 is fine, after all crash.

[TomG]

C4D always crash when i'm rendering with Corona 5

The only good thing about crashes is that they generate a bug report.txt which tells our developers what was happening at the time of the crash. Please always include this in the case of any crash - see https://help.c4d.corona-renderer.com/support/solutions/articles/12000033461-how-to-report-issues-c4d for how to find it, and link to the private uploader. We also need to know other information like, which version of C4D, which OS, which version of the OS, whether this happens in every scene or just one (or some), what steps you were taking at the time of the crash, and an example scene never hurts (see private uploader again).

Thanks.

[3DInteriors]

Thank you for this quick reply.
C4d  freezes, cannot report.

Win 10 prof 64 bit, C4d R20 ,
Problem occurs during rendering.
Computer : ASUS ROG Strix SCAR GL703GE / 32 GB

[katzenwaffe]

Why is this happening?
Is this as it should be in R21?

[Beanzvision]

Someone correct me if I'm wrong but I do not think this is Corona related. I believe it is due to the new "format" of the R21 UI layout.

[katzenwaffe]

Ok, thanks!
I don't like it. Haha.

[Beanzvision]

Ok, thanks!
I don't like it. Haha.

hahaha, you're not alone! ;)

[TomG]

Thank you for this quick reply.
C4d  freezes, cannot report.

Win 10 prof 64 bit, C4d R20 ,
Problem occurs during rendering.
Computer : ASUS ROG Strix SCAR GL703GE / 32 GB

Ah, you had said crash rather than freeze - however the good news is that the same page (https://help.c4d.corona-renderer.com/support/solutions/articles/12000033461-how-to-report-issues-c4d) shows how to generate a dump file, under "How to generate minidump files?", this mini dump gives the same info on what is going on and can be generated if C4D has frozen rather than crashed. We'd also need to know if this is every scene or only one (or some) - plus would be good to know what stage it freezes at, after a certain number of passes, or during a phase before rendering begins (the VFB has an information message at the bottom that says what it is doing at the time, such as calculating GI and so on).

[nightwalker]

Copy function out of the interactive rendering vfb does not work. c4d r21, corona 5 rc, mac os mojave

Same here, copy past in VFB not work. Furthermore slowdowns and freezing in Corona 5 final release and RC3. No bug report. I went back to RC2, the problem seems to be solved.

MacOs Mojave, Corona 5 RC3 and final release, Cinema 4d R19

Sorry for my bad english

[3DInteriors]

Corona-5-c4d-daily-2019-10-15-win is Work Fine !

[redpix]

Crashes using translucent material and problems with the nvidia denoiser (i'd like to disable it)

[TomG]

Crashes using translucent material and problems with the nvidia denoiser (i'd like to disable it)

Not sure what you mean by "I'd like to disable it" because you can of course - turn off "Fast preview denoise during render" in Performance settings if you want it removed from IR, or select a different denoiser under Denoise mode in the General Settings if you want it removed from final renders. Unless you mean something else?

Also, we'd need more info on the crash - the BugReports.txt file, and a copy of a crashing scene, would be best.

[houska]

Hello everyone!

We are releasing Hotfix 1 of the Corona Renderer for C4D V5. Cinema 4D is now notified when the render regions in VFB change, so that you can save the change in the scene. Also, the triplanar shader now correctly sets its subshader if you place it on top of an existing shader.

For now, the hotfix is available for testing on our public Google drive and will be released and available on the official download page a few days later.

Download link:
https://drive.google.com/drive/folders/1CKfO0EniaYOHi-cfh6aqIhubeVU4JzqM

Changelog:
https://forum.corona-renderer.com/index.php?topic=26054.msg161812#msg161812

[leo3d]

Corona Distance shader please, i cant wait this feature

[TomG]

Corona Distance shader please, i cant wait this feature

For feature requests, see https://forum.corona-renderer.com/index.php?board=38.0 :)

(Also, it won't be in Corona 5, which is out and will only see hotfixes, which also makes this not a good place to post the feature request :) )

[lollolo]

When can we expect a new hotfix or daily? As far as I see is Bump still not working properly. And a render without bump... Hope you can update us soon.

Thanks!

[TomG]

When can we expect a new hotfix or daily? As far as I see is Bump still not working properly. And a render without bump... Hope you can update us soon.

Thanks!

Hi! Do you mean this report? https://forum.corona-renderer.com/index.php?topic=26055.msg160380#msg160380

If so, a couple of follow up questions - could you share the scene, or at least a screen grab of the material set up, just so we are sure what situation you are describing? (private uploader info etc. is at https://help.c4d.corona-renderer.com/support/solutions/articles/12000033461-how-to-report-issues-c4d if you want to share the scene via that route).

Also, is this only with procedural shaders like noise, and if you use bitmaps instead, it works fine?

Thanks!

[lollolo]

I don't know if you know this already. Bump isn't working if a layer is used.

Example: Same Noise, on the left inside of a Layer shader, on the right without.

Mac OS 10.14.6

Build timestamp: Nov 27 2019 22:17:36
Version: 5.0
Cinema version: R20.059 CINEMA 4D Studio (single-license)
Plugin status: Plugin successfully loaded

TomG I mean this report. Bump isn't working if a layer shader is used.

[TomG]

Right - in which case, can you fill in the extra info as requested (that was the post my thread linked to :) )

[lollolo]

I did a quick test.

Successfully uploaded as 1578410757_LayerIssues.zip

R20
Build timestamp: Nov 27 2019 22:17:36
Version: 5.0

[TomG]

TY, for the scene and the test images! Based on that, it sounds like an issue that is already being tracked, ( (Internal ID=289087240) for internal use). We'll let you know when we have more information.

[stanDM]

Hi,

we were about to render quite a big project and noticed that in multipass rendering Corona 5 Hotfix 1 deliberately turns on Use bounding box option when rendering (even if it it turned off by us) - means that all renders we get are wrong! Any idea how to turn this crazy thing off? Test file and screenshot below ...

Stan

[elaraisawhale]

got a cinema4d r19 freeze when using native render region with the latest build. anyone?

[Beanzvision]

got a cinema4d r19 freeze when using native render region with the latest build. anyone?

Hi there, does it also freeze when using Cinema's default renderer?

[elaraisawhale]

got a cinema4d r19 freeze when using native render region with the latest build. anyone?

Hi there, does it also freeze when using Cinema's default renderer?

hi houska & beanzvision, i was out of office for a couple of days so tonight i'm gonna try if it crashes with cinema's default render and with another project, but it is so unusual, it always worked since corona beta 2

[houska]

got a cinema4d r19 freeze when using native render region with the latest build. anyone?

Hi eliraisawhale!

It works for me. Could you provide some more information? Does it freeze C4D or does it downright crash?

[houska]

Hi everyone!

We are releasing Hotfix 2 of the Corona Renderer for C4D V5. We fixed the ZDepth multi pass to work correctly as well as improved the position updates of keyframed, but manually moved objects in IR.

This will probably be the last hotfix of V5. New fixes and cool new experimental features will be issued as part of V6 daily builds in another forum thread similar to this one.

For now, the hotfix is available for testing on our public Google drive and will be released and available on the official download page a bit later.

Download link:
https://drive.google.com/drive/folders/1CKfO0EniaYOHi-cfh6aqIhubeVU4JzqM

Changelog:
https://forum.corona-renderer.com/index.php?topic=26054.msg162537#msg162537

[elaraisawhale]

got a cinema4d r19 freeze when using native render region with the latest build. anyone?

Hi eliraisawhale!

It works for me. Could you provide some more information? Does it freeze C4D or does it downright crash?

Hi, had c4d freezing only on that project, nothing wrong on a new one. sorry for the post! ;)

[houska]

Hi, had c4d freezing only on that project, nothing wrong on a new one. sorry for the post! ;)

No problem. We want to catch even project-specific issues though. Maybe they might appear again for someone, which we want to avoid.

[swiat3d.net]

I don't know if this is a bug but something is wrong.
The same free texture from megascans.
Simple cube 2m x 2m x 2m and two different projection: UVW Mapping nad Cube 1m x 1m x 1m
Two versions with and w/o albedo textures. Bump with corona normal shader - 100%.
Someone can confirm this problem?

Windows 7 + Cinema 4D R20 + Corona 5 hotfix 2

[paperless]

Yes. If I disable the bump /normal everything returns ok

[swiat3d.net]

Yes. If I disable the bump /normal everything returns ok

Exactly
I think it's problem with Cube projection.

[swiat3d.net]

Maybe Corona Team confirm the problem?

[quatrosolo]

I don't know if this is a bug but something is wrong.
The same free texture from megascans.
Simple cube 2m x 2m x 2m and two different projection: UVW Mapping nad Cube 1m x 1m x 1m
Two versions with and w/o albedo textures. Bump with corona normal shader - 100%.
Someone can confirm this problem?

Windows 7 + Cinema 4D R20 + Corona 5 hotfix 2

Same here, replicated the same issue. Cubic projection seems to create some weird issues with the normal map. ( like sharp wide edges )
Maybe this a C4d issue though. In any case good to know cause I don't think you can notice if you are not looking for it.

Mac Mojave + Cinema 4D R19 + Corona 5 hotfix 2

[Beanzvision]

Hi, Has "Flip Y (green)" been enabled in the Corona normal shader?

[mrittman]

Hi, Has "Flip Y (green)" been enabled in the Corona normal shader?

I noticed this as well. Had to enable Flip Y in my normal shader...