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

Pages: [1]
1
Hi bnji,
thanks for testing and your reply. I will try your recommendations on optimizing the scene file.

Unfortunately I cannot upgrade the Mac Mini M1 regarding RAM – it is stuck with 16GB.
Well…it looks like a new render workstation is needed…and definitely it will be no Apple. ;))))

Regarding RAM…128GB is of course better than 64GB…but are there any restrictions or constraints concerning Corona Renderer or Cinema4D?
Has anybody good suggestions or is here in the forum a post which shows the best current PC workstation configurations? (price-performance-winner)



2
UPDATE: after cleaning up the scene in simplyfying some geometry and change some light material, still the rendertime didn’t change at all. It stayed sooooo slow, close to nothingness.

But then I had an idea: Don’t use the VFB renderwindow (what the normal way should be), but use the interactive renderer to see if the scene would act differently…and YES -> it is rendering the passes…!! I couldn’t believe! I used the same render settings like I used before with the VFB…so what is this?

ca. 19 hours of rendertime = 92 passes = 3,69% Noise Level
Rays/s total = ~110.000
Rays/s actual = ~25.000

I mean still it is quite slow (it’s a Mac Mini M1) but at least it is rendering.
Unfortunately I cannot do anything else because the program is blocked with the interactive rendering. And I also don’t dare to click anything because then it would start again from the beginning…ahhhh

So please - what kind of bug is that? Can anybody conclude? Did anybody experienced something similar? How can I fix that?

Thanks! Doc

3
Hi bnji,
did you find anything?

Could you read the file properly? I just saw that I did't integrate two IES-Lights with the TEX-Folder.
I could also re-upload the file the right way: "save project with assets"?!

Thanks!

4
Quote
I don't think it's crazy geometry, just too much of sane one :)
Hahahahaha…thank you very much, I'm sure, it is exactly that!! I hope! ;))

5
Hi bnji,
the name of the scene file is:
DRWZDC_Scene Check_Corona7_plus TEX.zip

It is the C4D R21 file and the TEX folder.
Thanks a lot for checking!

6
Quote
If you're already paying for Corona, why not update to v7?
Yes, I updated to Corona 7 yesterday but still the render process stays looooooong – tooooooooo long with that scene.

Quote
Open up the texture folder for that scene and sort by SIZE. See what you have lurking in there and see how large it's being used in the scene. You might be surprised
I also did that but unfortunately wasnt surprised at all. ;) Only the concrete woodstamp texture is quite big (100MB) but is also an important and main material in the scene. But still, maybe I should size it a bit down.

Quote
Is this project a paid client for you? I'd love to see the room to get a better feel.
Yes it is. But because of privacy reasons I cannot yet post it here. It is a beautiful interior for a beautiful villa in switzerland.

Quote
It would be handy if you can share the scene with us.
You can use our private uploader here: https://corona-renderer.com/upload
Let me know the outcome.
I uploaded the file in C4D R21 and Corona 7 inclusive the textures of course. So I am very curious what the Corona-Team will find.
Me too, I will check the scene for some crazy geometry and materials…hopefully we will get a result so I can render the images out.

By the way, has anybody suggestions about a HP Workstation to use for the renderjobs instead of the Mac Mini M1 what can do the layout but not the renderjob.
What specifications are the best for cost effectiveness?

Thanks!!

7
Quote
Your best remedy? Upgrade to more RAM if possible or try to optimize your scenes so that they fit into your RAM (smaller textures / HDRIs, less subdivided geometry etc...).

Unfortunately I cannot upgrade the MacMini M1 in terms of RAM. I also tried to optimize the scene.
Well…I shared the scene with the private Uploader and hope that you guys find the mistake which causes the problem.

And if its "only" the RAM…what else can I do to get those Renderings out of the machine?
Should I use a Renderfarm?
Should I in general look for a better "Rendering-Machine"?



8
I got the maximum possible RAM installed in the Mac Mini M1: 16 GB.
This sounds low but because of the new M1-Chip the performance was normally very good.

9
Yes, I got that error message "Running out of RAM"…but I got it in earlier projects from time to time too and it never caused so much trouble like in that project now.
And yes, it could be a material or object that causes the trouble but I cant identify it.
I have no idea anymore – so I will send you the file via the private uploader for checking. Thanks!

10
Hi all,
I am rendering a complex interior scene and it took already 24 hours to get 3-4 passes with very noisy and low quality (see attachments).

My specifications are:
- Mac Mini M1
- C4D R21
- Corona 5
- File Size ca. 1 GB

In previous projects I did not have so crazy problems. It is the first time.

I tried already that:
- cleaning up the scene in deleting all unnecessary objects and materials
- There are some complexer materials like the woodstamp concrete with displacements…or the rug…or 5 spotlights with an IES-Light. But can that be the problem?
- checking all portal light objects that they fit perfectly into the window holes
- using the default render settings with the GI/AA Balance
- Yes, I have a lot of lights there…also in the multi-pass lightMix Channel…should I reduce that to a minimum and/or use instances?

General questions:
- Could it be that Cinema R21 and Corona 5 are too "old" to do the job…and I should update it?
- Or/and are there mistakes I did so that it slowed down so massively?

I know that computers are only ever as intelligent as the person sitting in front of them! So please help me!! ;)))

Thanks!!
Best Doc



Pages: [1]