The RebusFarm 2.0 software is a completely new approach to submitting render jobs to a render farm. In contrast to all previous systems, the render job is sent from inside your 3D application. Thanks to our One-Click-Technology you don't need to quit your 3D software, and you hardly notice a difference between rendering locally and rendering on the render farm. The only difference is that rendering large projects on the render farm is a couple of hundred times faster.
Compatibility check and adjustments
The RebusFarm 2.0 software examines your project inside your 3D application for possible conflicts with the render farm, thereby guaranteeing a much higher compatibility to the render farm than other solutions. The intelligent plugin normally enables your project to be rendered on the render farm with no changes whatsoever.
Please see our Render Farm Specs page for further informations.
All of the most commonly used plugins are supported by Rebus. A list of all plugin would be too long, and hard to update. That's why the RebusFarm 2.0 software takes care of that and gives you an error message in case your scene uses a plugin not supported by Rebus. If that happens just contact our support and we will see what we can do.
A rough overview: VrayScatter, Multiscatter; Autograss, color correct, Realflow, Blur Studio Plug´s, Ivy, ForestPro, m4d and dozends more.
That's indeed difficult. Try to bake or cache your geometry to file. Collapse the modifier stacks. If that doesn't succeed, remove the plugin from your PC, restart your 3D application and "merge" the scene into a fresh new one.
For 3ds max you can try this script: http://scripts.breidt.net/#removeMissingPlugins
By default, Rebus generate invoices 3 days after last payment. If you do another payment within 3 days the counter restarts and you get one invoice including both payments.
Just go to "My Rebus" and correct your profile, save profile and go to invoices. Behind each invoice is a little "R" - press it and the PDF will be regenerated using the new profile details.
Some email providers corrupt the PDF on delivery - just go to "My Rebus" and find your invoice
Imagine the very worst case: your image is 99% finished and your renderpoints run out. If we stop rendering immediately you lose your render, all renderpoints and a lot of time! That's why we carry on rendering.
There can be several causes. The most common cause is the firewall. Open port 21, 22 and 80 to IP 18.104.22.168 (simply disable it for a quick connection test to make sure the firewall is the reason).
If you use a proxy server, you have to setup RebusDrop to use your proxy server in the RebusDrop Preferences.
You don't have write permission for your Cinema plugin folder (if you copy a random file to the folder you get a permission popup). Make sure you set permissions to user and system for the Cinema folder as well as the plugin folder.Open the "information" for your C4D folder by pressing "cmd + i". Change the settings to "read and write" for all subfolders of the parent folder. After that you can install the Plugin.
If one P4 CPU of 1 core and 1 Ghz render for 1 hour, that equals 1 Ghz hour.
That's the big question that no one can answer for sure. Since Rebus doesn't know your scene we can't give an accurate quote in advance.
Rendering is a step by step process and lots of little things like displacement, scene size, particles, fur and much more can affect the render process a During render we update the job costs in real time and you can see the situation live. We recommend using our online cost calculator. Input your PC details and your render time per image. If you do not know the time yet make a best guess! If you have 2m44sec on your PC input 3 min instead to have a "buffer" in the estimate.
Make sure you can render frames on your PC! Do not "send and hope".
Yes we can - we use 100pc to render your image.