Show Posts

46

[C4D] General Discussion / Re: [DISCONTINUED] Cinema 4D Corona Scene Converter

« on: 2017-08-14, 13:52:17 »

Quote from: iacdxb on 2017-08-14, 13:45:03

Hi, this converter which vrayforc4d version support, I am using VrayforC4D 3.4 (3.5 beta)

Thanks.

...

I'm currently working on it. No eta. though.

47

[C4D] Daily Builds / Re: Corona for Cinema 4D Beta 1 daily build

« on: 2017-07-11, 10:02:13 »

Quote from: nesha_2 on 2017-07-11, 07:15:30

Well, personally, I prefer all of my 80 cores to work at 100% while rendering and as far as I'm concerned, this is the way it should behave. There should be feature for adjusting how many cores you'd like to dedicate to rendering, though. Not sure if that is present right now.

Simply set Thread limit in preferences. Corona also uses the C4D thread limit.

48

[C4D] Daily Builds / Re: Corona for Cinema 4D Beta 1 daily build

« on: 2017-07-09, 19:23:42 »

Quote from: Rhodesy on 2017-07-08, 00:22:24

I've not tried the Max one but the C4D VFB is quite slow when you get to large frame sizes, especially with bloom and glare still. I've had a couple of B&G no shows on the latest beta this week even with tweaking the VFB window to refresh. Fortunately I could save to CIE and get a lightmix pass with bloom out to comp back in with the rest of the multipass in PS. Is having to sync with the PV an issue perhaps? Im still hopeing to get native 16bit PSD as an output from the VFB. I still struggle to work out why the VFB would be different in Max as it would seem like a 99% pure corona controlled environment. But like Nkilar says, Im excited about the develpment too.

Are you talking about the refresh until PostProcess-Settings are applied? Or are you referring to high response times in PV (e.g. lagging while panning, etc.)
The latter might be caused by a custom monitor profile which is set in preferences. If it differs from sRGB, PV will slow down.

edit: Misread your post. You're talking about VFB, not PV. Yes, it is slower than Max.

49

[C4D] General Discussion / Re: Corona Bitmap tiling

« on: 2017-07-03, 13:51:42 »

Yup, experienced the same thing. In Cropmode, the tiling is clamped to 1.
Use the Layer-Shader with Transform so long.

50

[C4D] General Discussion / Re: No antialiasing on light material / objects

« on: 2017-06-24, 14:50:45 »

Oh well, didn't notice that one is gone. :)

51

[C4D] General Discussion / Re: No antialiasing on light material / objects

« on: 2017-06-22, 17:00:43 »

You might also increase Internal resolution to 2.

52

[C4D] General Discussion / Re: How you handle large amounts of grass in your scenes?

« on: 2017-06-02, 12:24:07 »

Yes, building a new code base is what Maxon works on for several years now (when I remember right, it began with R13) and this is progressive task. So, most likely it will take another 3-5(or even more, maybe less) releases to completely move to this basis.
Besides that, new features will also have to be built based on that, existing ones have to be rebuilt. C4D has decent and extremely good MT implementation yet, that's why Cinebench is so fast on multithreaded machines and used by chip vendors to show of their capabilites.
And to conclude this, keep in mind that there are cases where multithreading makes things slower.

By the way, writing down things like "This and that will be in next release" isn't helpful for anyone. That only leads to confusion and disappointment.

53

[C4D] General Discussion / Re: How you handle large amounts of grass in your scenes?

« on: 2017-06-01, 15:57:09 »

Quote from: Rhodesy on 2017-06-01, 12:56:53

Is that a confirmed fact, how do you know? Awesome if it is. Hope the third party plugin devs can access the same multithreading code for their scatter engines. That will make a massive difference.

No, I doubt there will be multithreaded Cloning. ;)
@Marian: Even if you might know what comes, that info is not meant for public right now.

54