Messages

406

[C4D] General Discussion / Re: Octane X

« on: 2021-03-23, 15:32:12 »

Its available on the Apple app store for m1 mac's. But the C4D plugin doesn't install even though Otoy tries to make you waist your time on it. I asked them if they have seen it working on a m1 mac with C4D r23 but got no answer. I lost interest to be honest.

407

[C4D] General Discussion / Octane X

« on: 2021-03-19, 00:12:28 »

Hi, Maybe not for this forum but the moderator will tell me.
Tried to install Octane X from the Apple App Store for C4D R23 on my new MacBook m1 to see if it is a faster alternative for Corona Render.
Well, after three days working with the Otoy support team and several links to different updates the plugin never worked. Could neither find any reviews of users that had it working. In the end I deleted my account at Otoy, won't be back any time soon.

The whole experience with Otoy is the exact opposite of Corona Render. From the start a few years ago Corona Render was a delight. I came from Maxwell Render btw. I really wonder how Apple and Otoy came to the decision to advertise a dead on arrival for the App Store.

408

[C4D] Feature Requests / Re: Virtual memory without warnings and crashes

« on: 2021-03-18, 23:54:58 »

My system:
iMac 2015 i7 32 Gb ram
C4D R23
Running the beta CR 7 daily builds. Very happy about version 7 btw.

All my renders are VM. I use the hair tool to brush ground cover on my landscapes. Huge amounts of data :-)
VM ia around 40Gb or a little less. You can see the renders here on the top left. https://francoisverhoeven.com
Images are rendered at around 2400x2400 p. Renders up to around 200 sl. Rendertime around 12 hours but at about 10 min reasonably at 5 or 6 sl. Scene parsing 5 to 10 min before render starts. I wonder if GPU render engines or a PC (instead of a Mac) would reduce parsing times. Actually parsing times slow down my design process much more than render time. After 1 or 2 minutes rendering I can evaluate the image. But because of parsing times I can only do 4 or 5 image evaluations an hour.

409

[C4D] Feature Requests / Virtual memory without warnings and crashes

« on: 2021-03-12, 23:56:05 »

Hi,
I would love to see a option within corona where corona would use virtual memory without any warnings or crashing the system. I most often have scenes with a lot of vegetation and my systems do not have enough ram. But corona renders just fine using virtual memory. its just a hassle to get passed the warnings and crashes.
Maybe a bug still but I always need to restart before rendering a scene using virtual memory. Otherwise corona crashes.

410

[C4D] General Discussion / Re: corona cinema4d on "apple silicon"?

« on: 2021-02-19, 22:35:02 »

Your right about sending a crash report to help out.
I did not experience such a crash after that one. I normally also do not really do crash reports since I am not that frequently using corona. I never know when its the software or me at fault . The latter usually the case.

I am working with my m1 laptop a little more these days. If there anything to report I will let you know. I did notice the fonts of the corona VFB like Tone Mapping and LUT do not match the rest of the fonts on my m1.

411

[C4D] General Discussion / Re: corona cinema4d on "apple silicon"?

« on: 2021-02-10, 00:44:42 »

Off topic but Surface Spread is a lot easier and quicker to set up. I have sets of Surface Spread templates with ground cover and plants. Very easy to scale and randomise. I don't use C4D daily so I tend to forget Mograph settings much quicker than the straightforward Surface Spread settings.

412

[C4D] General Discussion / Re: corona cinema4d on "apple silicon"?

« on: 2021-02-07, 16:38:44 »

C4D crashed the MacBook when I tried zooming in for a new render.
Hopefully Laubwerk and Corona will not let us wait for long for native versions. It took Laubwerk a year to update Surface Spread for R22.
If your on a Mac and doing archviz, C4D, Corona and Laubwerk are a great combination. But I always feel that there is a mismatch with updates, version, OS etc. I am in the market for a much better workflow considering all the hassle keeping stuff tied together.

413

[C4D] General Discussion / Re: corona cinema4d on "apple silicon"?

« on: 2021-02-07, 16:25:43 »

Did just a quick test with Laubwerk trees, 21 trees in total.
The image is 1280x720
Computing GI took a long time though.
About 750 % CPU usage. The M1 does not do hyper threading.
About 30Gb of virtualised ram.

See attached image for the stats.
Macbook does not really get warm even after 10 min rendering. It actually keeps rendering just fine while I am typing this message.

For me doing some work at home in the evening, testing scenes, materials and so on the MacBook seems to do fine.
Wonder why computing GI took a little longer than what I am used to on my iMac.

414

[C4D] General Discussion / Re: corona cinema4d on "apple silicon"?

« on: 2021-02-07, 15:58:57 »

Hi, I did not really render a project but did some tests with Laubwerk trees. And it actually did fine under Rosetta. I think slightly faster than my 32Gb iMac i7 from late 2015.

415

[C4D] General Discussion / Re: corona cinema4d on "apple silicon"?

« on: 2021-01-30, 23:27:15 »

I just did and it runs fine indeed. tx

416

[C4D] General Discussion / Re: corona cinema4d on "apple silicon"?

« on: 2021-01-26, 17:54:23 »

I am just hoping the Corona team will provide some updates on developments for Apple silicon. C4D works very well and Vectorworks is great on the m1. If Corona also joines the club I might still be working with Mac's for the foreseable future. New iMac's will propbably be available around March. But I have hopes I will be able to do some work on my m1 laptop with Corona any time soon.

417

[C4D] General Discussion / Re: corona cinema4d on "apple silicon"?

« on: 2021-01-21, 01:44:37 »

@bigA
your right, I could just stay with corona on a pc.

But I see here at the office what people do with Lumion and once I go PC,  I might go for Lumion (will never be available on a Mac) as well. Its just that I am used to Apple now for over 30 years and I like the Apple ecosystem and looks of the hardware. Corona made me stay so far. I am an architect and the typical render workflow of the past 15 years is fading to easier to use and much quicker app's. Obviously with a bit of a price to pay in terms of image quality. My clients don't see the difference though. Pressing a button and wait for things to see is no longer for this generation of architects. Its all real-time now. Apple has lost it basicly with architects in general. But what kept me going on a mac was really Coronarender. If Corona is not going to support Apple silicon or new iMacs are a bit of a let down I will for sure in the second quarter of this year start investing in a PC with Lumion or get myself familiar with Unreal Engine.

Whats really funny actually, that the number one reason people are so taken with Unreal or Lumion, or even Redshift, is not even real time feed back. Its the cinematic atmospheric volumetric effects. To get something simular in Corona is possible but extremly timeconsuming. In Lumion its instant with the click of a mouse. Almost any image in Lumion looks fantastic, the sunrays through the trees and windows. Its just so very easy to do.

418

[C4D] General Discussion / Re: corona cinema4d on "apple silicon"?

« on: 2021-01-18, 13:25:15 »

Would love to see an update on progress for Apple silicon. I don't see any developments on the roadmap.

Corona is one of the few really good render options we have on Apple hardware icw C4D. The reason I might hang on to Apple for while more. But if Corona isn't going anywere on the new Apple silicon I might give up and go PC/GPU.

So, Corona team, any news to share or an update on what to expect ?

419

[C4D] General Discussion / Re: Plants in Corona

« on: 2020-12-14, 01:16:10 »

Laubwerk

420

[C4D] General Discussion / Re: corona cinema4d on "apple silicon"?

« on: 2020-11-18, 16:20:12 »

I have a number of renders with Corona that use virtual memory on a 32Gb 2015 iMac and still getting reasonable speed. So maybe the ssd on these m1 macbook's and mini's will help to render the occasional bigger file.