CRITICAL SPEED ISSUE WITH APPLE M SYSTEMS

[frv]

Be aware that Corona bitmaps don't load in to the C4D asset browser.  And can not be copy pasted in to a new file without relinking in the project asset inspector.

[frv]

I would love to see a recent model with some assets that renders in about the same time to find out if this is specific to a certain file or really a hardware problem.

[ASIMO]

I would love to see a recent model with some assets that renders in about the same time to find out if this is specific to a certain file or really a hardware problem.

Of course it has to do with something in the scene, but it is not a scene-problem. If it would render slow on both machines (Intel and M) then it would be a scene problem. But it renders perfectly fast and fine on the Intel chip, so why not on the M ? I would also love to see a different file we could test.

[frv]

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

[ASIMO]

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

[davetwo]

Thanks for the testing! Watching with interest as you never know when something like this will trip one of us up.

[runx]

Mac Studio Ultra M1 128GB   / C4d 2026 Corona 11 daily oct.

Time: 11.08

[BigAl3D]

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

Whoa! The Corona Bitmaps made a massive difference. Care to share that scene so other can verify?

[BigAl3D]

Also ran that grass scene in the iMac Pro:  20:17 min

C4D r25, Corona 10 Hotfix 1

[prince_jr]

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

[prince_jr]

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

[CambridgeCreative]

Finally got round to running a test render for your original scene. Total render time took 2min 40 seconds

My PC spec is: (running stock)
Intel i9 13900K
64GB DDR4 3200Mhz RAM
Windows 11
MOB TUF Gaming B660M Wifi 4
Cinema 4D 2024.0.2 running Corona Renderer 11 Daily build 6 Sept 2023

[CambridgeCreative]

Re-ran rendering having added Corona Bitmap to all texture images and time came down to 1min 53 seconds.

[ASIMO]

Hello

I tested the grass-scene again by converting / using only native C4D Bitmaps.

As you can see in the image some information regarding the Corona-Bitmap (Tiling / UV / Offsets) got lost. So the materials render different, also making the scene look darker.

Anyway it takes almost three times longer for my Mac Studio to render. Timestamp is 27:21 min !

I think depending on the file-size / amount of textures used, times go up even more. It shows the same behavior as in the house-scene.

See attachment.

Best – Asimo

[frv]

It seems bitmaps have a big influence in render times.
Surprised to see the i9 13900K (24 cores ?) being so much faster than a Mac Studio.
Interesting all of it.
M3 Macs are coming Monday but I don't think we need to get excited. I wonder sometimes even how many Mac users are still there with Coronarender.