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

Pages: [1] 2
1
[Max] General Discussion / Re: license issue
« on: 2025-03-13, 21:58:24 »
Works again! Thanks team

2
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.


3
Hey all,

Very old topic but just happened to me and wanted to share my solution just in case.
In my case the animation was running, I accidently turned it on (wanting to play music and it made the animation start)
Stopped the frames, set on frame 0, back to working fine!

Cheers,
Habber

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

Hey everbody,

Just came from the other topic i opened up and downloaded the initial scene posted from asimo on 2023-10-19!
Didn't convert any bitmaps, literally just opened the file and clicked render to see what happens.

To my utmost surprise my rendertimes are faster than asimo's while my setup is much "worse"
m1max macbook pro (10 cores)
64 GB
1 TB SSD

Render time: 7:26
Rays/total: 6321310

How is it possible that my m1max macbook beats and mac studio m2 ultra? m2ultra is 24 cores, triple the ram, and a lot more expensive :D
And in both cases, the rendertimes are not great anyway for a 1200x1200 image.

The only difference I could find compared to asimos post is that he was using macOS Ventura while I run Sonoma 14.5 but that can't be the explanation.

The more I look into this the more desperate I get :(

Cheers,
Habber

5
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

6
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

7
The 24M r/sec in V12 is just wishful thinking

Hey Jojorender,

Fully agree - 24M is way too much for the m1max, and seeing the render times makes me think that this has to be a mistake. I've noticed this on all of my scenes. Depending on the scene, rays are usually between 2M (with tons of scatters and instances) vs 20M r/sec (simpler scenes), total render time with same passes still almost double though between V9 and V12.

Cheers,
habber

8
I normally don't pay attention to render times, because for me few percents slower or faster rendering is irrelevant, but out of interest i installed V9 and rendered random scene. Turns out V12 is significantly faster, which is not surprising. I noticed that the floor in V12 is rendered wrong though and that may indicate that there were some changes that affected complex materials between V9 and current version and that could possibly be the cause of slowdown in your case. Dramatic increase of rays/sample in your V12 render seems to support that guess. Other than that, it could be C4D or Mac thing as pointed by others.

Hey romullus,

I notice you are using windows. I think that this issue might be Mac / M1 related? Sometimes windows gets more programmers attention since more % are using windows.

As for speed difference: I would agree if it's "few percent" + or - but in my case it's double :(

Cheers,
habber

9
Are you all on macOS? I haven't compared render times here on Win, but it doesn't feel slower than before.
Since there is no max version for Mac, this issue seems to be a Corona for C4D (And maybe a Mac thing...)

Hey,

Yes all macOS since the start.
I am starting to think it might be C4D/Mac related.

You are windows + max?

Would be interesting to see if there's more ppl that don't face this issue.
Maybe it's just Apple / C4D.
M chips related? Would think they would test this pre release.

Cheers,
Habber

10
Hi habber,
Also, your rays/sample went up from 86 to 338 (lower is faster). Very strange.
Your mats look pretty simple but did you check if something funky goes on in your materials?
Is this your “test” scene? Maybe you can simplify the materials further? The walls have bump and not displacement correct? My r/sample are usually around 50-60.
Was there a change in UHD calculation bet. V9 and V10?

Hey!

Yes i know it's so weird that rays/sample is also so different. Just doesn't make any sense.
As for the materials: Yes, quite simple. Actually couple of them are unlinked (hence black floor). Just loaded any of my old random scenes and lost links. I realize it's not the perfect "test scene" but even setting it up properly it results in much longer render times.

Still, even having unlinked textures, the main point being is the difference between v9 and v12 (+10,+11)
I've noticed this speed difference with every single file over the past years with each new version, even if I optimize materials etc. which is why I haven't upgraded since v9, but had hoped to do so now.

Cheers,
Stefan


11
This is interesting, is it just C4D or Max also?

Hey,

Can't say about Max. Only been using C4D since the beginning.
But the difference is truly insane between V9, which seems to have been the fastest of all.
Seems like each never version has gotten just slower and slower (at least for me on M1 MAX 64GB + C4D R26).

What makes 0 sense to me is the fact that the rays are significantly higher while render times are twice as long.
I just can't understand as to why this could happen, it's soo soo frustrating :(

And seeing that this has been an issue for the past 3 versions doesn't really fill me with much hope.
It clearly has to be corona related. I'm always reading to send scenes, benchmarks etc. but to my common sense, it shouldn't really matter what kind of CPU, m1 pro, ram whatnot i am using. The fact that I am rendering the same scene 1:1 with different version on the same machine and getting such crazy different results is just insane.

At the end of the day I have such a busy schedule and the only thing that matters to me in my work is how fast I can render "X" scene and would be nice to take advantage of newer Corona versions with all its nice features without having to compromise for 2x the render times.

Let's see if anyone has found any solution or if we can get any deeper insight.

Cheers,
Habber
This is interesting, I wonder if it's Hardware related or software related (C4D).

Can you do a test of the scene in v9 and v12 but using 4% noise threshold. I would like to see if it has to do with using passes as the limiter.

Hey!

Yes, already tried and unfortunately it's not noise related. I tried earlier and actually it takes more passes to achieve same noise limit, while taking ~twice as long, while having ~ twice as many rays at the same time.

I know, it makes no sense at all.
Also, reading that over people are experiencing the same issue and that this has not yet been resolved makes me more worried there might be no solution to this.
Just a huge mystery :(

Cheers,
Habber

12
This is interesting, is it just C4D or Max also?

Hey,

Can't say about Max. Only been using C4D since the beginning.
But the difference is truly insane between V9, which seems to have been the fastest of all.
Seems like each never version has gotten just slower and slower (at least for me on M1 MAX 64GB + C4D R26).

What makes 0 sense to me is the fact that the rays are significantly higher while render times are twice as long.
I just can't understand as to why this could happen, it's soo soo frustrating :(

And seeing that this has been an issue for the past 3 versions doesn't really fill me with much hope.
It clearly has to be corona related. I'm always reading to send scenes, benchmarks etc. but to my common sense, it shouldn't really matter what kind of CPU, m1 pro, ram whatnot i am using. The fact that I am rendering the same scene 1:1 with different version on the same machine and getting such crazy different results is just insane.

At the end of the day I have such a busy schedule and the only thing that matters to me in my work is how fast I can render "X" scene and would be nice to take advantage of newer Corona versions with all its nice features without having to compromise for 2x the render times.

Let's see if anyone has found any solution or if we can get any deeper insight.

Cheers,
Habber

13
I feel your pain. When updating to C10 I've made this topic about it https://forum.corona-renderer.com/index.php?topic=40809.0

I could guess whatever the reason could be, but I don't know anything about programming or whatsoever.

I sucks nevertheless, all the new stuff is a lot of fun but finishing renders faster is the most fun :)

Hey!

Thanks for sharing my pain. Also thanks for the link.
I checked out the topic and read it all. Tried converting the whole scene to corona bitmaps and all that stuff.

Just to find out that now it took EVEN LONGER :D (now the very same scene took 2:58) compared to 1:27 with v9 and 2:28 with v12 before converting scene :(
It is so frustrating. I will have to migrate back to corona 9 very soon. For the 3rd time. Unbelievably sad.

Cheers,
Stefan

14
Hey,

So I just downloaded Corona 12 and had to find out that renders times are SO MUCH SLOWER compared to corona 9. (Yes I was still using version 9 due to having this issue in the past already)

I had already encountered this problem with Corona 10 + 11 so I always stuck with my Corona 9.
Now since 12 has some very nice new features I was hoping this issue would ve been fixed but just found out that it's not.

I use C4D R26 on M1 max Macbook Pro, 64 GB

Rendered the exact same scene with pass limit 5.
Corona 9 took 1:27 (with aprox 11 million rays total)
Corona 12 took 2:28 (with > 24 million rays total)

How is this possible? Took almost double the time, while having more than double the rays? I can't wrap my head around it.
Percentage wise this is a disaster.

It's very frustrating to have to decide if I want the new features of if I wanna keep rendering faster.
Hope you can help me. (before I go back to installing my old Corona 9)

Thanks!
Habber

15
[C4D] Daily Builds / Re: Mac M1 LOW POWER MODE bug lives on.
« on: 2023-09-20, 11:52:50 »
Did the scene that was slower on 10 use the Triplanar map?

Hi Tom,

No, it didn't use any Triplanar map. Only UVW + Cubic mapping throughout the whole scene.

In any case I was mostly astonished about the difference in rays/s compared to total render times in v9 vs. v10

Pages: [1] 2