Rising Nodes Number in Export Log every new frame

Forums: Rising Nodes Number in Export Log every new frame
Maxon Cinema 4D (Export script developed by abstrax, Integrated Plugin developed by aoktar)

Moderator: aoktar

Rising Nodes Number in Export Log every new frame

Postby Gpix » Fri Oct 22, 2021 2:20 pm

Gpix Fri Oct 22, 2021 2:20 pm
Hi everyone,

I recently discover some issue while I was rendering a 500 frames Animation. (Just a Hi-Poly-modelled object with a camera spinning one time for 360 degrees, no background, 20 different materials)

Usually I could estimate the rendertime for a whole animation with rendering the most intense frame and multiply it by the frame count. But in this animation (which is the first I did since the 2020.2.4 update) the render time starts to grow with every frame.
So for example frame 1 is about 17 sec. and frame 100 was about 2 minutes.

I tried to disable any other plugin in Cinema 4d, and I also uninstalled every Windows 10 Update I felt that could cause an delay in saving the frames.

So i checked the Export Log in the console.
The render time per frame doesn't really change. The only thing that changes is how long it takes for cinema 4d to save the frame when the rendering process is finished, and in the export log, I could dsicover that the only value that rises the most from frame to frameis the "NODES"-Value.

Can somebody explain it to me, and has anybody else that problem with animation rendering? Didn't have that problem anywhere in the past. Can't really work with these unsafe estimated rendering times on any punctual deadline.

Here is an excerpt out of the Export Log if that helps:

--------------------------- EXPORT LOG ---------------------------
Multi-threaded material conversion, thread count=38
Export materials time= 133.131 ms
Collect objects time= 11.464 ms
Mesh creation time = 4435.066 ms.
MB:0/0 ST/MOV:0/1054 Nodes:2627 Tris:20.68m DispTris:0 Hairs:0 Meshes:1k
Textures Grey8/16:0/1 Rgb32/64:0/2
VRAM used/free/max:3.898Gb/4.38Gb/11Gb Out-of-core used:0Kb RAM used:24.529Gb total:127.887Gb OpenGL free/total:0/0
mblurTM=0sec. createTM=0sec. updateTM=0sec. renderTM:6.143sec. totalTM:25.106sec.

FRAME:181 fps:25
createTM=2.75sec. 2749.704
MB:0/0 ST/MOV:0/1054 Nodes:2629 Tris:20.68m DispTris:0 Hairs:0 Meshes:1k
Textures Grey8/16:0/1 Rgb32/64:0/2
VRAM used/free/max:4.384Gb/3.382Gb/11Gb Out-of-core used:0Kb RAM used:23.526Gb total:127.887Gb OpenGL free/total:0/0
mblurTM=0sec. createTM=2.75sec. updateTM=6.42sec. renderTM:6.511sec. totalTM:15.681sec.

FRAME:182 fps:25
createTM=2.782sec. 2782.414
MB:0/0 ST/MOV:0/1054 Nodes:3116 Tris:20.68m DispTris:0 Hairs:0 Meshes:1k
Textures Grey8/16:0/1 Rgb32/64:0/2
VRAM used/free/max:4.518Gb/3.245Gb/11Gb Out-of-core used:0Kb RAM used:23.384Gb total:127.887Gb OpenGL free/total:0/0
mblurTM=0sec. createTM=2.782sec. updateTM=3.205sec. renderTM:7.632sec. totalTM:13.62sec.

FRAME:183 fps:25
createTM=2.821sec. 2821.037
MB:0/0 ST/MOV:0/1054 Nodes:3603 Tris:20.68m DispTris:0 Hairs:0 Meshes:1k
Textures Grey8/16:0/1 Rgb32/64:0/2
VRAM used/free/max:4.518Gb/3.245Gb/11Gb Out-of-core used:0Kb RAM used:24.118Gb total:127.887Gb OpenGL free/total:0/0
mblurTM=0sec. createTM=2.821sec. updateTM=3.322sec. renderTM:7.368sec. totalTM:13.512sec.

FRAME:184 fps:25
createTM=2.875sec. 2874.78
MB:0/0 ST/MOV:0/1054 Nodes:4090 Tris:20.68m DispTris:0 Hairs:0 Meshes:1k
Textures Grey8/16:0/1 Rgb32/64:0/2
VRAM used/free/max:4.518Gb/3.245Gb/11Gb Out-of-core used:0Kb RAM used:23.849Gb total:127.887Gb OpenGL free/total:0/0
mblurTM=0sec. createTM=2.875sec. updateTM=3.139sec. renderTM:7.507sec. totalTM:13.521sec.

FRAME:185 fps:25
createTM=2.884sec. 2884.069
MB:0/0 ST/MOV:0/1054 Nodes:4577 Tris:20.68m DispTris:0 Hairs:0 Meshes:1k
Textures Grey8/16:0/1 Rgb32/64:0/2
VRAM used/free/max:4.518Gb/3.245Gb/11Gb Out-of-core used:0Kb RAM used:23.888Gb total:127.887Gb OpenGL free/total:0/0
mblurTM=0sec. createTM=2.884sec. updateTM=3.302sec. renderTM:7.213sec. totalTM:13.4sec.

FRAME:186 fps:25
createTM=2.935sec. 2934.921
MB:0/0 ST/MOV:0/1054 Nodes:5064 Tris:20.68m DispTris:0 Hairs:0 Meshes:1k
Textures Grey8/16:0/1 Rgb32/64:0/2
VRAM used/free/max:4.518Gb/3.245Gb/11Gb Out-of-core used:0Kb RAM used:24.324Gb total:127.887Gb OpenGL free/total:0/0
mblurTM=0sec. createTM=2.935sec. updateTM=3.197sec. renderTM:7.007sec. totalTM:13.139sec.

FRAME:187 fps:25
createTM=2.938sec. 2937.594
MB:0/0 ST/MOV:0/1054 Nodes:5551 Tris:20.68m DispTris:0 Hairs:0 Meshes:1k
Textures Grey8/16:0/1 Rgb32/64:0/2
VRAM used/free/max:4.518Gb/3.879Gb/11Gb Out-of-core used:0Kb RAM used:24.061Gb total:127.887Gb OpenGL free/total:0/0
mblurTM=0sec. createTM=2.938sec. updateTM=3.35sec. renderTM:7.142sec. totalTM:13.431sec.

FRAME:188 fps:25
createTM=2.979sec. 2979.004
MB:0/0 ST/MOV:0/1054 Nodes:6038 Tris:20.68m DispTris:0 Hairs:0 Meshes:1k
Textures Grey8/16:0/1 Rgb32/64:0/2
VRAM used/free/max:4.518Gb/3.879Gb/11Gb Out-of-core used:0Kb RAM used:24.507Gb total:127.887Gb OpenGL free/total:0/0
mblurTM=0sec. createTM=2.979sec. updateTM=3.305sec. renderTM:7.308sec. totalTM:13.593sec.

FRAME:189 fps:25
createTM=3.002sec. 3002.36
MB:0/0 ST/MOV:0/1054 Nodes:6525 Tris:20.68m DispTris:0 Hairs:0 Meshes:1k
Textures Grey8/16:0/1 Rgb32/64:0/2
VRAM used/free/max:4.518Gb/3.879Gb/11Gb Out-of-core used:0Kb RAM used:24.576Gb total:127.887Gb OpenGL free/total:0/0
mblurTM=0sec. createTM=3.002sec. updateTM=3.21sec. renderTM:6.762sec. totalTM:12.975sec.

FRAME:190 fps:25
createTM=3.024sec. 3023.609
MB:0/0 ST/MOV:0/1054 Nodes:7012 Tris:20.68m DispTris:0 Hairs:0 Meshes:1k
Textures Grey8/16:0/1 Rgb32/64:0/2
VRAM used/free/max:4.518Gb/3.879Gb/11Gb Out-of-core used:0Kb RAM used:24.752Gb total:127.887Gb OpenGL free/total:0/0
mblurTM=0sec. createTM=3.024sec. updateTM=3.237sec. renderTM:7.24sec. totalTM:13.502sec.

FRAME:191 fps:25
createTM=2.99sec. 2990.011
MB:0/0 ST/MOV:0/1054 Nodes:7499 Tris:20.68m DispTris:0 Hairs:0 Meshes:1k
Textures Grey8/16:0/1 Rgb32/64:0/2
VRAM used/free/max:4.518Gb/3.879Gb/11Gb Out-of-core used:0Kb RAM used:24.268Gb total:127.887Gb OpenGL free/total:0/0
mblurTM=0sec. createTM=2.99sec. updateTM=3.311sec. renderTM:5.889sec. totalTM:12.191sec.

FRAME:192 fps:25
createTM=3.139sec. 3138.746
MB:0/0 ST/MOV:0/1054 Nodes:7986 Tris:20.68m DispTris:0 Hairs:0 Meshes:1k
Textures Grey8/16:0/1 Rgb32/64:0/2
VRAM used/free/max:4.518Gb/3.879Gb/11Gb Out-of-core used:0Kb RAM used:24.811Gb total:127.887Gb OpenGL free/total:0/0
mblurTM=0sec. createTM=3.139sec. updateTM=3.253sec. renderTM:5.801sec. totalTM:12.194sec.

FRAME:193 fps:25
createTM=3.075sec. 3075.052
MB:0/0 ST/MOV:0/1054 Nodes:8473 Tris:20.68m DispTris:0 Hairs:0 Meshes:1k
Textures Grey8/16:0/1 Rgb32/64:0/2
VRAM used/free/max:4.458Gb/3.941Gb/11Gb Out-of-core used:0Kb RAM used:24.554Gb total:127.887Gb OpenGL free/total:0/0
mblurTM=0sec. createTM=3.075sec. updateTM=3.437sec. renderTM:5.901sec. totalTM:12.414sec.

FRAME:194 fps:25
createTM=3.176sec. 3176.088
MB:0/0 ST/MOV:0/1054 Nodes:8960 Tris:20.68m DispTris:0 Hairs:0 Meshes:1k
Textures Grey8/16:0/1 Rgb32/64:0/2
VRAM used/free/max:4.518Gb/3.311Gb/11Gb Out-of-core used:0Kb RAM used:24.991Gb total:127.887Gb OpenGL free/total:0/0
mblurTM=0sec. createTM=3.176sec. updateTM=3.278sec. renderTM:6.726sec. totalTM:13.181sec.

FRAME:195 fps:25
createTM=3.297sec. 3297.246
MB:0/0 ST/MOV:0/1054 Nodes:9447 Tris:20.68m DispTris:0 Hairs:0 Meshes:1k
Textures Grey8/16:0/1 Rgb32/64:0/2
VRAM used/free/max:4.518Gb/3.311Gb/11Gb Out-of-core used:0Kb RAM used:24.703Gb total:127.887Gb OpenGL free/total:0/0
mblurTM=0sec. createTM=3.297sec. updateTM=3.467sec. renderTM:5.793sec. totalTM:12.559sec.

FRAME:196 fps:25
createTM=3.735sec. 3734.502
MB:0/0 ST/MOV:0/1054 Nodes:9934 Tris:20.68m DispTris:0 Hairs:0 Meshes:1k
Textures Grey8/16:0/1 Rgb32/64:0/2
VRAM used/free/max:4.518Gb/3.311Gb/11Gb Out-of-core used:0Kb RAM used:25.485Gb total:127.887Gb OpenGL free/total:0/0
mblurTM=0sec. createTM=3.735sec. updateTM=3.486sec. renderTM:6.864sec. totalTM:14.087sec.

FRAME:197 fps:25
createTM=3.324sec. 3323.892
MB:0/0 ST/MOV:0/1054 Nodes:10421 Tris:20.68m DispTris:0 Hairs:0 Meshes:1k
Textures Grey8/16:0/1 Rgb32/64:0/2
VRAM used/free/max:4.518Gb/3.879Gb/11Gb Out-of-core used:0Kb RAM used:25.679Gb total:127.887Gb OpenGL free/total:0/0
mblurTM=0sec. createTM=3.324sec. updateTM=3.494sec. renderTM:7.313sec. totalTM:14.132sec.

FRAME:198 fps:25
createTM=3.47sec. 3470.217
MB:0/0 ST/MOV:0/1054 Nodes:10908 Tris:20.68m DispTris:0 Hairs:0 Meshes:1k
Textures Grey8/16:0/1 Rgb32/64:0/2
VRAM used/free/max:4.518Gb/3.879Gb/11Gb Out-of-core used:0Kb RAM used:25.249Gb total:127.887Gb OpenGL free/total:0/0
mblurTM=0sec. createTM=3.47sec. updateTM=3.531sec. renderTM:7.223sec. totalTM:14.225sec.

FRAME:199 fps:25
createTM=3.449sec. 3448.792
MB:0/0 ST/MOV:0/1054 Nodes:11395 Tris:20.68m DispTris:0 Hairs:0 Meshes:1k
Textures Grey8/16:0/1 Rgb32/64:0/2
VRAM used/free/max:4.518Gb/3.879Gb/11Gb Out-of-core used:0Kb RAM used:25.373Gb total:127.887Gb OpenGL free/total:0/0
mblurTM=0sec. createTM=3.449sec. updateTM=3.553sec. renderTM:7.439sec. totalTM:14.442sec.

FRAME:200 fps:25
createTM=3.346sec. 3345.74
MB:0/0 ST/MOV:0/1054 Nodes:11882 Tris:20.68m DispTris:0 Hairs:0 Meshes:1k
Textures Grey8/16:0/1 Rgb32/64:0/2
VRAM used/free/max:4.518Gb/3.879Gb/11Gb Out-of-core used:0Kb RAM used:26.137Gb total:127.887Gb OpenGL free/total:0/0
mblurTM=0sec. createTM=3.346sec. updateTM=3.297sec. renderTM:6.179sec. totalTM:12.823sec.

------------

I am really confused, because I didn't had this behaviour in the past. Does anybody have a solution or any idea where the problem could be?

Thank you in advance!

Best regards.
Gpix
Licensed Customer
Licensed Customer
 
Posts: 25
Joined: Mon Dec 17, 2018 12:22 pm

Re: Rising Nodes Number in Export Log every new frame

Postby Gpix » Fri Oct 22, 2021 3:38 pm

Gpix Fri Oct 22, 2021 3:38 pm
After some troubleshooting, I found the problem causing this issue:

If I use a material on a polygon selection on an symmetry generator object with an image texture in the opacity channel it causes the rising nodes numbers and though the rising rendering times per frame (other channels in a material doesn't seem to have that behaviour, it's only the opacity channel).

When I convert the symmetry object into a not symmatrized polygon object (cinema 4d shortcut c), I can use a texture with opacity without any rising Node numbers in the Export Log and the frame render times stay the same.


Maybe that helps someone, and aoktar can look into that case and it helps.

Or maybe I didn't see any warning note, that opacity isn't supported within an symmetry generator on a polygon-selection in Cinema 4d.
Last edited by Gpix on Fri Oct 22, 2021 3:40 pm, edited 1 time in total.
Gpix
Licensed Customer
Licensed Customer
 
Posts: 25
Joined: Mon Dec 17, 2018 12:22 pm

Re: Rising Nodes Number in Export Log every new frame

Postby frankmci » Fri Oct 22, 2021 3:40 pm

frankmci Fri Oct 22, 2021 3:40 pm
Interesting that the node count is increasing by exactly 487 with each frame. Sounds like a memory leak to me.
Technical Director - C4D, Maya, AE, - Washington DC
frankmci
Licensed Customer
Licensed Customer
 
Posts: 820
Joined: Fri May 26, 2017 2:00 pm

Re: Rising Nodes Number in Export Log every new frame

Postby Gpix » Fri Oct 22, 2021 3:45 pm

Gpix Fri Oct 22, 2021 3:45 pm
Hi Frankmci,

oh yes a memory leak or some memory problem was also the first thing that came to my mind. (Even my thought shoot in the direction of faulty hardware, but thank god, it wasn't)

But as you can read in my other answer, it is the opacity channel in combination with an polygon selection within an symmetry object.

Seems to have anything to do with exakt 487 nodes.

Would be interesting to know what correlation this number has, maybe with the count of polygons you got in one selection and applied that texture with opacity to it.
Gpix
Licensed Customer
Licensed Customer
 
Posts: 25
Joined: Mon Dec 17, 2018 12:22 pm

Re: Rising Nodes Number in Export Log every new frame

Postby aoktar » Sat Oct 23, 2021 7:42 pm

aoktar Sat Oct 23, 2021 7:42 pm
Hi Gpix! Why don't you send me a scene with issue then I can easily test it?
Octane For Cinema 4D developer / 3d generalist

3930k / 16gb / 780ti + 1070/1080 / psu 1600w / numerous hw
User avatar
aoktar
Octane Plugin Developer
Octane Plugin Developer
 
Posts: 15957
Joined: Tue Mar 23, 2010 8:28 pm
Location: Türkiye

Re: Rising Nodes Number in Export Log every new frame

Postby Gpix » Sun Oct 24, 2021 4:59 pm

Gpix Sun Oct 24, 2021 4:59 pm
Hi aoktar,

I send you a scene file as PM.

Hope that helps!

Thank you in advance!
Gpix
Licensed Customer
Licensed Customer
 
Posts: 25
Joined: Mon Dec 17, 2018 12:22 pm

Return to Maxon Cinema 4D


Who is online

Users browsing this forum: Google [Bot], jayroth2020 and 23 guests

Tue Apr 16, 2024 11:14 pm [ UTC ]