Wow, I thought this was happening later this year. Great news. One question though, let’s say we buy two seats, but both artists are busy on other, non-C4D projects. Can one of those seat be used by a third artist on another computer temporarily? Otherwise, the project will have to wait until one of the two systems are available or have to buy a new seat just for a couple of small jobs.
Thanks.
I also have a licensing question.
I just bought C 3 but didn’t yet activate it. Once i activate Corona 3, will I be able to go back to Beta 2 stable if I need to?
You’ll see that when you go to the buy page that it says “Floating License”. What that means is that you can essentially move that license to whatever workstation you’d like as long as its only running on that computer - So basically you can use it anywhere and you can move it around freely you just can’t use one license to run two workstations.
Hello friends, happy year for everyone.
Great news to know that we already have Corona ready and without errors.
However!! I have 2 doubts
Excuse my ignorance on this subject … what are the nodes?
I see that there are licenses with 3 nodes, 5 nodes and 10 nodes.
Another question I have is …
I have 2 computers, in one I do all the work, modeling, lighting … etc, and when the work is already approved, I pass it to the other computer to render it.
This to not stop my work and keep doing other scenes.
Which license do you recommend to buy?
Hello 
I guess I’m acting like a support guy today, ha! The workstation license is where you have c4d opened and you are using Corona in Cinema 4D, like the UI and stuff.
The nodes refer to render nodes. So basically if you have 1 workstation license and 3 nodes you can work in c4d with Corona and you can have 3 machines rendering without actually using the UI - So thats for things like Team Render and DR in general.
Hope that helps.
I have also one question…
Got Corona 3, installed at home WS but not installed yet in office. Can I use Corona on both machines while one is in render…?
Thanks.
…
Not if it is running in Workstation mode to render, ie if C4D proper is open and rendering. You’d have to render using the C4D Client and not in the full Cinema 4D, using Team Render should be possible to use the web manager submission system for Team Render to send the rendering to the C4D client without needing Cinema 4D proper running, then you can close C4D proper and so not be using the Workstation license.
So long as you are using Cinema 4D Client and Team Render to render on the second machine, just a standard single license of 1 WS + 3 Nodes would work. The Workstation would let you run Cinema 4D with Corona on the main machine, then you could submit to the C4D client which would be one of the 3 render nodes licenses that you have (see previous post just before this one - just like there, your second machine would have to be NOT running Cinema 4D in full mode, as that would require a second Workstation license to do).
It would be nice to have a renderer for other computers, in this way while the other computer renders in which we have installed a crown we can continue working in other scenes.
It can be a system that only renders and does not allow modifications.
It would be something spectacular that other rendering engines do not have.
It can make the difference of Corona to the other render engines.
Because it would not be profitable to buy 2 licenses, and use only one to render.
Well, it’s my opinion.
Some of us can not waste time while the machine renders
This can probably be done via the command line version of C4D. I presume that one will stay in render node mode. Would be interesting to know. Tom?
Seems complicated answer, and goes around me…! I think it will help you in easy reply.
I have one system Mac pro at home and iMac in my small office. there is no render system, both system for work and render. Mostly I do renders at night. If I am at home do from home , if in office do from office. Do I need two licenses…? if It is, I am sorry for that…!
Even can not use if both systems are in different locations…?
…
Hi, I wonder why would you need to go to Beta 2? Is there a bug that Beta 2 didn’t have? If so, we’ll fix it ASAP. Corona 3 is the new stable version for C4D currently. I saw in the other thread that you have issues with the Image editor. We’re looking at it right now…
But to answer your question: Activation of Corona 3 will not influence, whether you can go back to Beta 2 or not. The reason is that they have a separate licencing. Be warned though, that Beta 2 will stop working after 21th of February (45 days after the release of the commercial version).
seems a lot of us are in the same situation…. i use 2 cinema4d in 2 diferente computers but only working in one and render in other…
That’s right, in many cases clients do not wait and jobs must be delivered quickly.
Waiting for the render to finish with another scene is not a good option.
2 computers, one to work, create scenes and another to render.
it is the ideal.
If Corona creates a system that only makes the render it would be spectacular.
It can be a license with installation in a single computer, but with a rendering system in other computers, without using the resources of the computer where it was installed.
Corona would be the first to do it, it would be great.
Imran, as long as you run only one C4D at a time, you only need one License. But two full copies of Cinema4D (so not just a team render client) running at the same time, even if one is only rendering, will need two licenses, I’m afraid.
Isn’t that exactly what Team Render is intended for? With only one machine rendering (and the workstation working as a server) this should work perfectly, because that’s the scenario that we often test in the office.
Should all be possible using Team Render. There are two ways to use Team Render:
Team Render to Picture Viewer
This makes the Workstation you are on, and any render nodes running the C4D Client, all work on the same image at the same time. This will tie up your Workstation (you can still run a second C4D, but your machine will be spending processor power on rendering).
Team Render using it’s web manager
Using this approach, you should be able to send a render job to a node running just the C4D Client, and it will render, leaving your Workstation out of the equation so you can keep on using it. Since it’s just using the C4D Client, it just needs one of the Node licenses of Corona Renderer, so the regular “1 Workstation and 3 Render Nodes” would be all you need.
Best bet is to look up tutorials on using Team Render, as it’s all part of that functionality so tutorials about Cinema 4D will explain it all (and it works the same for Corona - other than the extra step of running the Corona Licensing Server).
Here are my notes on the second approach - but I still recommend looking up Team Render tutorials, to make sure my information is accurate and complete
Run the C4D Client on any nodes you want to contribute. Since this will be submitted as a job, you’d need to run it on the main machine too if you want it to take part in the rendering (or not, if you want to keep using it at full speed for working on without it doing any rendering)
Run the C4D Server on the machine that will control it all
Click on the “World” icon in the C4D Server application to open the web interface. This is where jobs can be scheduled.
Do not use “Submit Job” in C4D itself. Not really sure what that does.
In the C4D Server, click the folder icon. This will open the jobs folder. Go into the “admin” folder, and copy the address to this folder.
Save the project from C4D, using Save Project With Assets, and save it to a new folder under the Cinema4DTeam admin folder (the address copied from the step above). This will create a job in the Web Monitor application, with the name set by the name of the new folder.
Click on Start in the Jobs list of the Web Server.
while team render is in function, can you continue working on other scenes, even doing render tests?
Pardon my ignorance.
I think that team render is just to speed up the render.
I think we are talking about 2 different things.
See my previous reply - using regular TR to PV, you can run a second C4D, but yes the machine will be slower. Using the web manager for TR, you can send rendering to another machine and leave the machine you are working on out of rendering that (by not running the C4D Client on the main machine).
Yes.
…Pardon my ignorance.
I think that team render is just to speed up the render.
Cinema 4D Team Render at Cineversity [Video Tutorial Playlist]