Network rendering inside C4D doesn't work

[BCres]

Okay, I tested rendering times today exporting a scene/animation within C4D compared to the same scene exported to the standalone and then rendered.

Inside C4D the scenes take 2-3 minutes to render each frame.
In the standalone, 30 seconds a frame.

I grabbed two shots just a few seconds apart from the frame appearing on the Picture Viewer as it rendered. Notice how the gpus don't show as working then suddenly show.

Yes, everything is set up properly for network rendering inside C4D. The slaves show fine and the LV works fantastic—it always shows both slave gpups active and rendering.

I was suspicious when I traded posts with aoktar and he said "in theory and practice" it should render the same as Team Render (which requires another plugin license on the remote system.) I don't believe it does. (topic: viewtopic.php?f=30&t=59905)

I thought the problem was fixed, but I did some tests with my main scene and it's not. Either the gpus are dropping offline... or the entire scene file is being reuploaded each time. Whatever the case, I'm defintely not getting the same performance inside and outside C4D.

[BCres]

Okay, another post on the forum led me to a partial solution where aoktar mentioned "rendering by commandline is simply same procedure as it's done in Picture Viewer" (viewtopic.php?f=30&t=60083)

So I ran the same scene through the Cinema4d commandline.exe and the project exports as quickly as it does within the Octane standalone.

Yet if I try the exact same project within Cinema 4d it goes back to almost 4 minutes a frame (rather than 30 seconds a frame.)

Any ideas what might be set up wrong inside C4D that is causing the slowdown?

Thanks.

[aoktar]

Your description and attached images confuse me. I see in picture it ended around 30sec in LV or PV whatever. Note that red text means network tranfer is still in progress. 0/2 means that 0 slave gpu is rendering. You should exactly define how you measure times in C4D vs. Standalone. Both Includes preparations/transfer times?

[BCres]

Yes, that is confusing. Ignore that.

But let me show this. Frames 236-243 are rendered through the commandline.exe. Frames 244-246 is the same scene opened and rendered inside of C4D. That's the problem. Why the huge difference? It's the exact same scene.

The LV speed = commandline speed = standlone speed = fast!

C4D batch render or Picture Viewer = much slower. Same settings nothing else changed.

BTW, I'm not upset, just trying to understand why there's such a big difference.

[aoktar]

Picture Viewer=slow is not making any sense on me. It should be at same speed of LV if resulted data diagram of objects are same. Just note that first frame takes more time because preparing all data for renderer. Next frames are generally much shorter on render times because just some data is refreshed. Of course this depends how is your scene and and how your set this.
Making a decision with one scene is common mistake in this forum. My advice that you check it on different scenes. If you still have same impression show me/us some scene and ask for assistancing. We may find better ways to optimise or some issues on your system.

[BCres]

aoktar,

First, I appreciate your help. Yes, I understand that first frame takes a while and then rendering speed should be the same once it starts. It just never is.

Also, I have tested this on several scenes, they all behave the same way. LV is super fast, PV (and batch render) is very slow.

I'm quite familar with computers and software and usually troubleshoot stuff on my own, but this one just leaves me scrathing my head.

But as I mentioned, the command line version is my workaround so no worries. I'll take it from here, and if I find what it is I'll let you know.

Thanks again,
BC