We are living in the golden age of cloud render services. We choose these services instead of doing it on our computers where we work with a huge amount of render loads. Thanks to these services, which offer both speed and price advantages, we are able to finish the renders in a few hours which will normally take days on our own computer. Here, Octane Cloud Render (ORC) offers GPU render farm service only for your scenes you created with Octane. If you have a lot of frames to render and you have a tight deadline, you can consider the ORC.


First, get the necessary information about Octane Render Cloud using this link.


Before using Cloud render, you should definitely pay attention to the scene optimization. All 3D softwares loves optimized scenes, real polygons and absolute data (baked data) during rendering. If you have a calculation process happening in your scene at any time (for example Cinema 4D's Delay Effector) you should bake it. Because systems such as mograph, dynamics, particles, hair or cloth work according to the principle of "Sensitive dependence on initial conditionLink". In such systems, the frame must start from zero for accurate calculation. However, cloud renderers work separately and render different frames. In this way, all simulations or background processes will be incorrect (thus, all frames). So baking is an inevitable process. This is a golden rule. And unfortunately Cinema 4D has a bad reputation in this matter. Especially if you are using some of the Mograph tools, particles, dynamics, cloth etc., bake all of them before you do the cloud render. In addition, do not leave anything unnecessary things in your scene. A very sloppy and messed up scenes are always a problem. So, the optimization is inevitable even in the simplest scene.  


Before using Cloud render you need to subscribe to ORC system and buy some credits. Also you need to understand the OB/Hours system completely. Details are here

double check

Double check and be sure of everything before sending the scene to the ORC. Cloud render services never forgive user error. Check your scene in the Octane Standalone after you've made the scene ready for the cloud. Since you are going to export in Orbx format, the relative file problem is gone. Orbx keeps everything in itself. So it's pretty easy to open and control the scene in Standalone. If the output you see on the Standalone differs from what you seen on Cinema 4D, there are things you need to check or correct. This is why double check is very important.

A lot of money :)

It's just a joke but in case of emergency you may need to backup some cash. In general, cloud estimators and the real world renders prices will not match. Be sure to make 5-10 frames test render in the ORC before making a full render. You can then adjust your budget accordingly.