Chaos Corona Forum
Chaos Corona for Cinema 4D => [C4D] General Discussion => Topic started by: iacdxb on 2018-02-10, 14:55:09
-
Hi,
Displacement works by stacking materials to object... first displacement and then any other object. This is nice....!
Back to coin displacement, displacement works fine... much better and flawless...!
IR at 3200 works fine... all looks ok but when rendering.... then something goes wrong, 20 min and 1 pass, activity like dead.... system goes crazy, force quit screen appears... and after sometime I do c4d force quit.
IR shows preview but when renders.... noisy screen till 20 min and 1 pass.
....
-
Are you running out of RAM?
-
Are you running out of RAM?
I don't think.... 64gb it is.
...
-
Depending on your displacement settings, also 64 GB can easily be too little. But without more information (in general), it is hard to say what could be the problem.
-
It's very likely that you're out of RAM. Typical behavior.
Displacements eat up A LOT and if you have a huge image, like A3 and have the displacement still set to 2px, you'll get very very fine displacements but it will also drastically increase the hunger for memory.
For example, You have an image that is 500*500, the disp. size is 2px and it's detailed enough. If you raise the resolution to 1k*1k, you have an image 4 times larger and if the disp. value is not changed, you might get crisper displacements but the memory amount will also increase by that factor.
If you'd now render the image as 4k², you'll need 64 times the memory compared to the initial 500² resolution.
(Not sure if the values are accurate, it might be a different factor, I just assumed it to be similar to subdivisions)
Anyhow, the higher the resolution, the higher you can go with the screen-space displacement to achieve the same look.
Try what works best and don't enter unnecessary small values.
Switching to unit size(cm) displacement might be the better option for large images.
BTW, it doesn't have to be the displacement in your case. There are other things that also eat a lot of memory. some of the most recent threads are about that topic.
-
(Not sure if the values are accurate, it might be a different factor, I just assumed it to be similar to subdivisions)
The logic in your calculations is correct.
-
Thanks Eddoron for detailed reply.
I was using 0.5 screen size... and sure it was taking time to calculate... but the issue was when IR runs at 4K why not then render...! IR calculates and run passes in 4 to 5 min, and when start render.... wow... it goes crazy, in 20 min 1 pass, I think it should that same time as IR started.
Later I set to 1 screen size and finished that...! happy ever after.
...