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 - prince_jr

Pages: [1] 2 3 ... 7
1
Very interesting workaround! It's wild that this trick would reduce render times by 2/3!

Also, wow your scene is so simple - beautiful but VERY simple - I had no idea. Not even using reflections or any form of special material.

Can't really understand how it would even take you this long, having such a strong machine. I can only guess displacement for the walls? (still shouldn't be as much) What do you use as setting for displacement size? I've realized this affects times a lot and the result being only slightly affected.

only the rock and the wooden piece have displacement. walls and floor are using bump.
render settings are untouched. displacement screen size (px)= 2 (see attachment)

i don't know how to tweak the scene and settings any further to reduce render time. maybe we have to accept that apple machines more and more suck when it comes to 3d-rendering.
but i have to say...i'm very happy with the mac studio. my main work is photography (commissioned) with medium format. and the mac studio does a marvelous job handeling the big raw files respectively filesize.

2
sorry for not mentioning the noise limit. it‘s 3.0.

Got ya! Yes 3 is quite low (keep in mind noiselimit incrementes rendertimes exponentially) but regardless 15 hrs is too much.

Forgot to add 1 important point: I've never heard my fan on my m1max even while rendering heavy scenes on Corona 9. Those M chips are so good that I even forgot I had a fan since it never turned on. Now, even with simple scenes I can hear my fan kicking in on Corona 12 :(

Cheers,
Habber

@habber i did another render test. i managed to reduce the render time from 15h to 5.5h. but how...well, i was cheating a bit.

my approach:
positioning an omnidirectional light (sphere) in the room incl. compositing tag (everthing unchecked). the rendering of course is overexposed now. but in lightmix i turn off this light to get my desired exposure back. after 5 passes the rendering has 6.35% noise. in the render test with 15h the noise level was somewhere 15-20% at 5 passes. i don't know if this is the way to go, but it seems to help. does anyone have the same approach to get less noise and faster render times?

attached you will find two render test:
4000 x 6000px > 5h05min, noise level 3.0
3333 x 5000px > 3h30min, noise level 3.0
rays/s are normal. only rays/sample is high > 323.6
> specs: mac studio m2 ultra 24c, 192gb ram, 60c gpu, ssd 4tb – c4d2024.2 - corona renderer 11.2

any feedback from the corona team is welcome and appreciated.

3
Mac Studio Ultra 128GB / c4d 2024 / corona 11 daily

Original Scene: 11.30

* copied eyerything  over in new scene : 9.32

** > put all textures in Corona Bitmap:  1.38 ( sic !!)

hope that helps

I can confirm your result...~1.38min > see attachment. also have a look at the rays/s total= almost 24'000'000
> rendered on mac studio m2 ultra, 24cores, 192gb

@habber have a look here at my render times (see above) > 1:39min with cbitmaps, which is quite impressive!
the only strange thing here is...rays. almost 24'000'000 rays/s

4
i‘m on mac, too (m2 ultra, 24c)

Oh man that hurts to read ... m2 ultra 24 cores and taking 15 hrs per render is painful. that machine is a beast and so is its price. (im actually thinking of getting the same setup to complement macbook) anyhow, should be way faster than that. resolution is quite high but still...

what pass limit you use for noise limit? maybe you are even rendering too many passes? of course personal preference but maybe you are trying to reach noise limits that are just too hard to achieve within reasonable times? i'm usually more than fine with 5% for example. Actually end up adding some grain on purpose in post production. Gives it more realistic appearance and less "perfect CGI" style.

In any case, speeds are low on macs. they haven't been low before, they started getting lower after v9 which is the sad and not logic part to me. I'm now suffering on a daily basis. And since scatter brush is not out yet for v12 anyway i guess i will have to go back to v9 very soon since nobody of the devs has responded anything yet :(

Cheers,
habber

@habber
sorry for not mentioning the noise limit. it‘s 3.0.
i know, maybe 4.0-5.0 would do the job and will of course provide lower render times. but in this case i primarily have a detailed stucco surface and want the fine details to be seen. i think noise limit 3.0 isn‘t very utopic to run with.

it would be so nice to get some information or at least some attention from the corona devs about that topic, which a lot of mac users does bother.

5
hi everybody

i‘m on mac, too (m2 ultra, 24c). with version 11.2/c4d 2024.2 i can‘t confirm double render times, because i can’t run v9 on v2024.2 anymore. but…
- i sometimes see strange numbers in the vfb (rays/s etc), too
- there’s slower render speed (felt)
 
a current interior scene needs ~15h to render (resolution of 4000x6000px). all materials are setup with cbitmap, mostly bump used and only a few displacements. plus illuminated by hdr and some basic lights outside the house.
is this normal?

i really hope the devs can figure it out with apple. i don‘t work as a visual artist nor make money of it, but it‘s no fun to render one image for 15h. i mean it‘s 2024 and not 10 years ago. ;o)

6
any news here?
> just read another new interesting topic:
https://forum.corona-renderer.com/index.php?topic=43080.0;all

7
i don't even see the category "materials" in cosmos browser. cosmos browser is updated to the latest version.
system: cinema 4d 2024.2, corona renderer 11.2, mac studio m2 ultra

8
Gallery / Floor lamp "Arredoluce Triennale"
« on: 2024-06-22, 10:33:08 »
Hi everybody

I finally finished a project I'd like to share with you...
The iconic floor lamp from Arredoluce: "Triennale 1947"

Everything single 3d element is built from the ground up and every material is so, too.

Have fun looking at the renderings and don't hesitate to comment...positive and negative. ;o)

Kind redards
Mario

9
Try this one. Simple model with only Chaos Cosmos assets and materials.
Rendered in about 12 min. 20 passes on a Mac Studio 20cores, 128 Gb, C4D 2024.1.0 and CR daily build 20 oktober 2024:
https://drive.google.com/file/d/1YzHB1oXmiF_qk0jtWkM3PgPPetIEDcmS/view?usp=sharing

Hello FRV

Thank you very much for your scene. I rendered it on both my Mac Studio M2 Ultra with 192GB and my i9 10900K iMac. Both running C4D2023 and Corona V10.

The results are exactly matching the Corona Benchmarks and Cinebench. So everything perfect with this scene and the power of the two computers. See attachments.

Mac Studio: 10:19
iMac i9: 23:38

The Mac Studio speeds up to 2.29x faster than the iMac in this scene with 100% power all way through. So we can for sure exclude thermal throttling problems.

There are two things I would like to test, as I think they could have an impact :

1. Changing the Blur-Scale of the Corona Bitmaps to -100%.

2. Changing all Corona-Bitmaps of this scene to Non-Corona-Bitmaps.

I will do the tests once I have some time.

Best – A

same here...10.19mins for grass scene

10
Mac Studio Ultra 128GB / c4d 2024 / corona 11 daily

Original Scene: 11.30

* copied eyerything  over in new scene : 9.32

** > put all textures in Corona Bitmap:  1.38 ( sic !!)

hope that helps

I can confirm your result...~1.38min > see attachment. also have a look at the rays/s total= almost 24'000'000
> rendered on mac studio m2 ultra, 24cores, 192gb

11
@ASIMO the strange thing with your sample scene is...the longer the scene renders, the fewer the rays/s (total) become.
> same rendertime (see attachment)
> also copied the whole scene into a new one. rendertime makes no difference.
>in other scenes i have constantly ~11'000'000rays/s

12
[C4D] General Discussion / Re: mac studio / mac pro m2 ultra
« on: 2023-08-31, 21:50:10 »
compared to my apartment rendering (mac pro 2010, 12core, 3.46 ghz, 128gb) with 152mins in the other thread, 39mins with my new mac studio is fast :o) > 3.9x faster exactly.

13
[C4D] General Discussion / Re: mac studio / mac pro m2 ultra
« on: 2023-08-31, 21:43:34 »
some may remember this thread here:
https://forum.corona-renderer.com/index.php?PHPSESSID=53f27ps93iqd7jar9dp9fg74nv&topic=33540.0;all

there we have a comparison of an architectural scene:
https://blog.corona-renderer.com/corona-c4d-a1-1/

i share my render now (3840x2160px, noise level 3.0%) > see attachment
i'm happy with the render time result, as 3d rendering is more of a part time job than a full time job for me.

@BigAl3D: i hope you now have an idea of ​​render times for the mac studio m2 ultra.
i wasn't able to render the grapes scene, because the scene loaded weird in the newest c4d-version. that's why i decided to use the apartment scene.

14
[C4D] General Discussion / Re: mac studio / mac pro m2 ultra
« on: 2023-08-29, 21:00:01 »
hi folks
here's my result running the benchmark > see attachment

it's the same speed as the other ranked mac studio m2 ultra in the benchmark results.

15
[C4D] General Discussion / Re: mac studio / mac pro m2 ultra
« on: 2023-08-06, 21:06:14 »
@wsiew can't answer your question finally. but corona basically is cpu related. others here can provide better information than me.

to me, it was important that i have a new mac studio that i can use for a long time. so, rather more ram than gpu cores. my main work is photography with heavy mediumformat raw files (semi self-employed), cad and lastly 3d-rendering. but rendering not for a living.

btw...i don't work in the video segment, so gpu is not prior to me. and the price of mac studio m2 ultra is enormous, too. i can't afford a maxed out mac studio m2 ultra. that's why chose between 60cores/192gb ram or 76cores/128gb

maybe there are some benchmarks on the web/youtube, which focus on 60 vs 76 cores. but i guess it's not a giant leap in performance. and the m2 ultra is a hell of a machine anyway.

Pages: [1] 2 3 ... 7