nanaxwisconsin.blogg.se - Vray for c4d team render

#VRAY FOR C4D TEAM RENDER SOFTWARE#
#VRAY FOR C4D TEAM RENDER FREE#

I also see in the road map that nothing has changed since the. Especially now with the new cheap AMD 1950x threadtripper, and the upcoming intel 18 core chips - It makes the costs of a small home render farm (1-3 machines) much much cheaper.just my 2 cents of course :) This way I won't need to use dedicated vray shaders and will be able to work with corona DR when implemented.ītw, looking at your c4d roadmap, I would implement DR before Node material editor. I'm beginning to see that for best workflow (on any renderer) will be to own c4d that has team render. I wrote to maxon support about those 2 options (about costs and to see if any of those options are relevant to me)

They also have a multi-seat license, but their site doesn't mention how much it costs. Not sure it's the ideal solution for just 2 machines. But (and it's a big but), because the slave machine has the standalone vray that comes directly from chaos group,and not from the vray for c4d developers - I can't use any native c4d shaders or 3rd party shaders - I have to use the dedicated vray shaders (and there are many dozens of them.without any good documentation).

#VRAY FOR C4D TEAM RENDER FREE#

Well, Vray for c4d uses something between option 2 and 3 - it has a standalone version (which comes directly from chaos group) which is installed on the slave machine, and in the main machine I only put the ip of the slave machine ( I think we get up to 10 free nodes in vrayforc4d).

Team Render not being able to work with C4D Prime) when the plugin becomes commercial, so thank you for bringing the issue up! We should definitely mention the licencing issues (i.e.

#VRAY FOR C4D TEAM RENDER SOFTWARE#

But then again - it has the drawbacks of not allowing to use any 3rd party shaders unless we reimplement them.Īnd I don't know about Chaos policies regarding the team render of VRay, but the Render Legion policy for Corona is clear - just buy as many licences for render nodes as you need and that should be it! But if the host software requires it, we cannot really do much to prevent them from requiring additional licences. Corona went with the 1st option, but we will be implementing the 2nd or 3rd one later on (probably the 3rd one). The client machines then run a special standalone version of your renderer.įrom what you say, it seems to me like VRay is using the 3rd option. This is the most laborous way, which entails reimplementing all the shaders from C4D (and of course, any 3rd party shaders that you don't reimplement will not work in this case), but it allows you to only require one licence.

Use your own DR and reimplement all shaders.

From what a colleague told me, C4D might have some special mini licence for only command-line rendering, which the render farms use. But then the user has to have a normal licence on every computer.

Use your own implementation of distributed rendering.

In this case, the user has to buy a C4D version, which has extra render node licences for the render clients In C4D however, you (as a renderer programmer) have basically three options:

This is the reason, why it works in 3dsMax without any additional licences (and I was wrong about it the first time). Just a clarification - I just talked to guys from the 3dsMax plugin team and they said that for running the client in 3ds, the user doesn't need a licence for another 3ds.