Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - houska

Pages: [1] 2 3 ... 69
I need help Cinema 4D / Re: Preparing geometry
« on: Yesterday at 10:37:00 »
Are you running the file from Dropbox?

I suppose they're not. The mentioned Dropbox folder is our private folder for users to share their scenes :-)

That's actually a good idea and it shouldn't be difficult to implement! I will add it to our bullet list. Thanks!

The problem with aliasing on bright edges will be still there, if you render in bigger resolution. But, what you can do is render in higher resolution and then scale the image down in post.

I need help Cinema 4D / Re: Preparing geometry
« on: 2019-05-21, 17:41:43 »
Hi, could we see your scene so that we can figure out what is causing these delays? You can use our private uploader (see my signature below) if the project needs to stay private.

Otherwise, it's a shot in the dark... Actually - are you using any plugins other than Corona? It could also be that some of them is misbehaving

No, unfortunately, tweaking the AA vs. GI setting won't help with the bright jagged edges either, because they are an inherent feature of the physically-based rendering. In the second link that I posted in my first post, you can see what can be done to help with the issue. It's written from the point of view of 3dsMax, but it should be applicable to C4D too.

Well, I can't speak for C4D, but we integrate spectral response over the domain of the physically-correct theoretical blackbody radiation function and convert that to RGB with maximal component being 1. The color should thus be precise up to a multiplicative constant (i.e. the light can be lighter or darker)

Please do note that more passes will not help you when you want to solve aliasing on the bright edges! Read that first link that I linked in the first reply above to see why.

As for the AI denoisers, they can be surprisingly good in some cases, yet fail in others. The key point is that no-one (not even the developers themselves) understands why they denoise a single given image the way they do. They are just trained on a huge set of reference pictures and then they use that information to denoise new images. And often they "hallucinate" detail where there shouldn't be any, so I'd be careful here. That's the only reason why we don't recommend the AI denoisers for production - their inherent unpredictability.

Since you doubt in the comparison of the two renders, I am going to set up a scene in Core 1.7 and open it in Core 4Beta to render both as A/B-comparison.

If your only point is the reduced denoising on rounded edges, then don't do the comparisons. We're aware of that and it's intentional, because it brings more detail into surfaces with bump-mapping. We might change that in the future, but I cannot make any promises, sorry :-(

If you want to compare the images to compare the speed of rendering, then you can do it, but you need to do it on the same PC, exact same scene and ideally with noise limit (because the newer versions can be slower, but better quality)

Renders look washed out... ( AI denoiser on about 0.5 - 0.7 )

Thanks for the images, but the images are uncomparable. They are from different points of view.

From what I can see, the second image uses AI denoising, whereas the first one doesn't? If so, then splotches are expected. AI denoisers are meant for preview only and can never be used as final render solution unless you want to compromise image quality! Also note that longer rendering won't get rid of the splotches - even if you apply an AI denoiser on a perfectly clear image, it will produce splotches! That's the nature of the AI denoisers.

As for the speed, it's nearly impossible to compare two different viewpoints on two different PCs with two different versions of Corona.

Edit: That said, there's one feature that can make images appear more blurred (though very subtly, hardly perceivable actually) - the HQ image filtering, as can be seen here: But again, you have to compare two exact same renders

Hi, there is no definite roadmap as of now, but we're currently in the process of getting a new developer on the project. There will be more information and progress soon, don't worry ;-)

Hi Designerman77,

thanks for your feedback.

As for the noise, it's really hard to tell what the issue is without seeing the specific scene or the render at least.

But the aliasing on bright edges is a well-known and well-understood issue and there's not much to do about it. It's well described in this thread in an old discussion about another renderer, but it's very precisely written and applies to Corona as well. (You're looking for MasterZap's answer):

Otherwise, I suggest you look at this article on our Freshdesk help:

Hi Designerman77,

I just tried the Interactive Render Region in a medium-size scene in R20 and everything was fine for me - I was able to resize the IRR just fine. Do all the scenes have this problem or just this one?

That's too bad :-( We'll have to try to replicate it ourselves then.

Corona Renderer for Cinema 4D - general / Re: Team render
« on: 2019-05-16, 16:40:54 »
That's interesting. So you have some standalone team render client? Cause the way my C4D is installed, I have C4D Team Render client in the same fodler as C4D itself. And then everything works of course...

But what you can do: extract the installation package yourself to a temporary directory using the "Unpack Files" option and then just copy the corresponding "corona" folder (for the right C4D version) from the extracted folder to the "plugins" folder that you'll create next to the TR client executable. That should do it.

Feature requests Cinema 4D / Re: VDB
« on: 2019-05-16, 15:37:55 »
Nope, VDB is still not supported. We do however support volumetric shaders in the newest daily build, so you can try that out at least!

Pages: [1] 2 3 ... 69