Page 1 of 1

TEAMRENDER in C4D and SLAVE do not work in indigo

Posted: Thu Apr 14, 2016 10:47 pm
by det1971_
hello everyone ;)

i hope i can get some help...

i use c4d r16... and my teamrender works very fine.

but not with indigo render setup in c4d.

if i click on the icon in c4d to render my scene in indogo... the software pops up and start to build...
on the master my slave is connected and its showing in the network manager and in my networkrender.

on my slave its loading the scene but after:

"finished initialisation (time taken 6.19s)
starting threads... (numxxxx)
uploading frame:

FRAME UPLOADED. (transfer 0.00s) <---- this continue all the time

my slave is not working... i see this in my speedfan.

so... here are my question:

how can i get my slave to work in indigo software...?
how is it posibel to render it direct in teamrender in C4D with indigo?

thank you :)

Re: TEAMRENDER in C4D and SLAVE do not work in indigo

Posted: Thu Apr 14, 2016 11:20 pm
by Juju
you can try 3rd party render manager, supports both C4D and Indigo

http://www.renderpal.com/features/supported-renderers

Re: TEAMRENDER in C4D and SLAVE do not work in indigo

Posted: Fri Apr 15, 2016 12:06 am
by det1971_
im sorry to say... but this is not the help i need :)

Re: TEAMRENDER in C4D and SLAVE do not work in indigo

Posted: Fri Apr 15, 2016 12:22 am
by Zom-B
det1971_ wrote:FRAME UPLOADED. (transfer 0.00s) <---- this continue all the time
Do you have GPU acceleration enabled? Try disabling it if yes :)

Re: TEAMRENDER in C4D and SLAVE do not work in indigo

Posted: Fri Apr 15, 2016 2:59 am
by det1971_
this is what i get... out of indigo slave

Re: TEAMRENDER in C4D and SLAVE do not work in indigo

Posted: Fri Apr 15, 2016 3:58 am
by lycium
Some quick checklist items:

Are both master and slave running the same Indigo versions? I recommend the latest Indigo 3.8.31 version.

Has the Windows firewall exception successfully been made on both master and slave computers?

Indigo doesn't actually support the C4D TeamRender feature, it has its own network rendering.


Regarding the last point, I think we could isolate the problem if you quickly run through the network rendering tutorial, and let us know at which step it fails: http://www.indigorenderer.com/documenta ... g-tutorial