I see, thanks for the quick reply. I will try it and if doesn't work I'll open a new thread about the topic.
Okay, my guess is that the Windows tool requires the user to press ENTER when the tool has finished its work. Is this correct? It would explain why the tool runs forever on the build server.
And if it is the reason: Would it be possible to remove this behaviour from the tool? As I see it it is not really uncommon to run the project tool automatically rather than being executed by a human user.
Thanks a lot @rsodre for your investigations! We are trying to build our plugins using Azure Pipelines and I had the same issue (project tool not executing correctly) there. Copying the DLLs into the executable folder solved the issue :)
Unfortunately the tool now runs forever, I'll have to investigate myself a bit more why. If you got some more hints, let me know!
Thanks for your quick answer. I saw it just now because I wasn't informed via mail :/
I sent my question to the support center now. I'm not sure if they can answer such technical question, that's why I hoped that a fellow developer might know about it :)
I discovered the command line page already, there is unfortunately no command line parameter to explicitly enable TeamRender.
We are trying to add Cinema 4D to our custom rendering pipeline. We are already able to render projects with Cinema 4D by using the command line.
What we are missing is the ability to render those projects with Team Render. Although the team render clients are added on the PC where we trigger the rendering, it does not distribute the rendering onto them. When rendering the project via the GUI, Team Render is available and works as expected.
Is there a flag on the command line which enables Team Render?