Messages

31

[C4D] General Discussion / Re: Corona for Apple Silicon M1?

« on: 2021-12-17, 17:18:48 »

Thanks for the info about Graswald. I'm looking into them now :-)

Also, forgove my ignorance, but what do you mean by 'SL' ?

Cheers

32

[C4D] General Discussion / Re: Corona for Apple Silicon M1?

« on: 2021-12-16, 18:27:13 »

I just rendered this on my macbook air m1 with 16Gb. After a minute or so you have a decent image to work with but this image up to SL16 at 3600x3600 took about 6 hours.

6 Hours! Blimey! I've never had anything in Corona take that long. I regulary render out 10000x10000 images on my mini M1 and they take about 1.5 hrs. An image like yours at that size on my 64Gb Macbook with the M1 Max would probably take 10-15 mins... I always use pass limit of 12 and Corona high quality denoise of 0.5.. Even the 16Gb mini would only take 15-20mins tops I'd guess.
I'm doing scenes with tons of Laubwerk & Forester trees and plants and I've never ever had to wait more than an hour for a 6000x4000 image.

33

[C4D] I need help! / Re: Should I use Corona Bitmap for all my material maps?

« on: 2021-12-15, 09:29:27 »

Almost seems like Corona should, by default, always add the Bitmap shader whenever you add an image. I mean, why not?

Because it doesn't support layered PSDs.

34

[C4D] I need help! / Re: Team render with differing RAM

« on: 2021-12-15, 09:28:34 »

Thanks. That's what I hoped was supposed to happen. So it's probably not the RAM issue. The mini used to render just fine with its tiny 16Gb. So TR must be dropping nodes for some other reason.. It's always been problematic for me. For example none of my Laubwerk trees work over team render unless I freeze them and I have no idea why. LW can't reproduce it and they used to work fine in R20... (weirdly now that I've installed R25 they no longer work in R20!)...
As a work-around I'm having to unplug my render machines from the network and run Cinema on each one to render different parts of a sequence. Major pain in the backside but the only way I can get it to work. Ho hum..

35

[C4D] General Discussion / Re: Corona + Forester, can anyone advise

« on: 2021-12-13, 09:34:41 »

I use both Laubwerk and Forester on a pretty much daily basis and they are both great with Corona. I've recently hit an issue with Laubwerk trees not working over Team render since I upgraded to R25 running on M1 macs but that's probably just me. I can work-around it by freezing the trees too so not a bigggie. Highly recommend both systems really. SurfaceSpread is great and so it Multicloner. I tend to use the SS for Laubwerk trees and MC for Forester just because they are made for each other but both work with either.

36

[C4D] I need help! / Re: Should I use Corona Bitmap for all my material maps?

« on: 2021-12-10, 09:35:43 »

So I've just discovered one reason not to use it. If I drop in a photoshop file I can't choose which layer set to use like I can with a normal C4D bitmap. I like to create my maps with all the diffuse/gloss/bump/alpha etc in the one layered file (it's just quicker). Seems like I can't do this with the Corona bitmap.

37

[C4D] I need help! / Re: Should I use Corona Bitmap for all my material maps?

« on: 2021-12-10, 09:17:31 »

I too would be interested to know this. I've been using Corona for years and have never once used the Corona Bitmap... Hmmmm. curious.

38

[C4D] I need help! / Team render with differing RAM

« on: 2021-12-09, 10:36:18 »

Hi Folks,

I've just bought a new M1 Max laptop with 64Gb RAM in it to use as my main Corona machine. It's very nice but I'm fingin that when I try and team render with my other previous mac mini with only 16Gb Ram I'm getting very slow render times and sometimes the info message says 'rendering on 2 nodes' then drops to '1 node'... Is this because of the RAM difference? Is there a way I can have TR send smaller 'slices' to the mini so it handles them better?
Weirdly, when I had just the mini and an old PC (which had 64GB RAM), I could TR to the PC from the mini and I never had this problem, I got speedy renders and the node count was always 2.... I've even tried TR to the PC from the laptop, so both machines have 64GB but rendertimes are MUCH slower than with just the M! Max on its own (The PC is a 1st Gen Threadripper).
I've tried changing the TR settings to Arbitrated 20/256 packets but if anything it makes things worse...

All macs running Cinema R25 in M1 Silicon mode with lates V8 Corona build.

Any ideas?
Thanks.

39

[C4D] General Discussion / Re: How to create silk using physical Material.

« on: 2021-11-24, 10:10:17 »

The library material is legacy but just go to 'advanced>convert' to make it physical and give you a good starting point. I might be wrong but I think that's what's been done here?

40

[C4D] Daily Builds / Re: NaN Problem - latest Build

« on: 2021-11-16, 14:44:05 »

Me too on M1 Mini Monterey - Good to know you guy's are on it.

41

[C4D] Daily Builds / Re: v8 Daily Build on M1

« on: 2021-11-16, 10:30:49 »

Nope. You have to have Cinema running Native to load the native version of Corona. SO R20 won't work. I just had to update to R25 purely for this :-). R25 is very nice though, and super fast.

42

[C4D] General Discussion / Re: Corona for Apple Silicon M1?

« on: 2021-11-12, 09:33:29 »

I keep checking the forum everyday for a possible daily release :(

Ha Ha! Me too! :-)

43

[C4D] General Discussion / Re: Avoiding Sky Pinching

« on: 2021-11-11, 09:39:18 »

Most of the time I use a PG sky HDRI and always rotate the whole sky object. I never use the UV's as you don't get the control as they only go from 0-100% as opposed to 0-360 degrees. I also generally have one sky object for lighting and one for seeing the clouds etc set to a lower brightness so they look good by eye. Sometimes I use sun and sky if I want to use the nice new haze effect and can't be bothered to make a volume box, even then I'll add an HDRI in another object to use for clouds.

44

[C4D] General Discussion / Re: Corona for Apple Silicon M1?

« on: 2021-11-10, 09:47:35 »

Just to chime in here, I've been using an M1 Mini 16GB with Corona since May without any issues. I still team render big jobs to my old PC purely because it's faster (Threadripper) but tbh I rarely turn it on these days. Corona is stable and pretty fast on M1 under Rosetta. The only crashes I get are when messing with cloners or SurfaceSpread or MultiCloner.. For some reason any tweak of clones with the IPR running will crash it. I"m pretty sure it's just a memory issue.
I REALLY hope there's an M1 native version coming.
I've ordered a 64GB M1 Max Mac Pro so when it turns up later this month I'll report back on how Corona runs with all that extra RAM.

I'm using Cinema R20 by the way. Can't see any reason to upgrade until Corona goes Native M1. :-)

45

Chaos Corona for Blender / Re: Is Corona for blender dead?

« on: 2021-10-22, 15:34:46 »

no reason to wait corona while there are other suitable engines for blender. take a look to new redshift came to it. it is also a hybrid engine wich has also secondary GI calculation like corona, but all on GPU wich makes it even faster than corona.

As a Cinema user that has Redshift and Corona, there's no competition. Redshift is nowhere near as nice as Corona. In fact Corona is the only reason I still use Cinema 4D, If it was ported to blender I'd jump ship in a heartbeat. Cycles is slow and clunky and Octane is hard and cold. Only Corona (and perhaps V-Ray) can produce truly beautiful renders in my opinion. If I had the money I'd fund it myself, but I don't as I've given it all to Maxon and Adobe!!