 |
 |
OUR CLIENTS |
 |
|
 |
 |
Features
Below you will find an overview of some of the most important features found in RenderPal V2. This is by far no complete list, but should give you a good overview of what RenderPal V2 has to offer. For more information, check out the RenderPal V2 manual, take a look at some screenshots or download a free 30 days evaluation version.
| Renderers |
Supported renderers
RenderPal V2 supports all major renderers (as well as many of their plugin renderers) and compositing applications. The following list shows all renderers that are supported by RenderPal V2 out of the box:
| Maya Software |
MentalRay for Maya |
Maya Vector |
| Maya Hardware |
Turtle for Maya |
RenderMan for Maya |
| Final Render for Maya |
V-Ray for Maya |
After Effects |
| MentalRay |
Digital Fusion |
Combustion |
| 3dsMax Software |
Brazil for 3dsMax |
Final Render for 3dsMax |
| V-Ray for 3dsMax |
XSI |
Lightwave |
| Cinema 4D |
Maxwell |
Shake |
| RealFlow |
SiTex Air |
Houdini |
| 3Delight |
Blender |
|
|
Custom renderers
RenderPal V2 allows you to easily create your own renderers. Virtually any renderer (or any other kind of application) with command-line support can be added to RenderPal V2. The list of custom renderers is managed by the server, so there is no need to manually distribute new custom renderers to all users.
Our user forum also contains a section where you can download and share custom renderers. You will also find additional factory presets that are not included in the RenderPal V2 package. |
| NET JOBS |
Render sets
A render set is the base of any net job; it consists of one or more scene files to be rendered, as well as various render settings that can be set on the fly. These act as overrides to the original settings made in the scene, so you can render your files with different scenes without touching or altering them. |
Frame splitting
Frame splitting is the key to render animations across a network. RenderPal V2 lets you divide an animation into smaller chunks which will then be rendered by the various clients. |
Image slicing
Rendering large images (4096x4096 or even larger) can be troublesome, so RenderPal V2 allows you to slice down such images into smaller pieces, which will then be rendered by individual clients. |
Automatic frame checking
Unfortunately, images do not always get rendered properly. To counter this problem, RenderPal V2 offers the ability to automatically check for missing frames, so that they can be automatically resubmitted. The initial net job will not be finished until all missing frames have been rendered successfully. |
Full control
Net jobs offer numerous options that let you define how a job should be dispatched. This includes the selection of specific pools and clients which should work on the job, an advanced priority system, multiple net job dependencies, automatic chunk resubmission if rendering times are too high or too low and more. |
Net Job events
One of the most powerful features of RenderPal V2 are its net job events, which allow you to execute a program, a system command or even a Python script on certain net job events (like when a chunk has been rendered and so on). |
| RENDERING |
Parallel renderings
RenderPal V2 can perform parallel renderings on a single client. Even though most renderers these days support multi-threaded rendering, some will still only utilze a single CPU core. With todays multi-core computers, this can be a true waste of resources. This is why RenderPal V2 can perform parallel renderings on a single client, even if the renderer itself doesn't support it. |
Failsafe rendering
Renderings can fail due to many reasons. RenderPal V2 offers several features to ensure that your renderings will always be finished. This includes return-code verification and automatic frame checking. |
Intelligent dispatching
RenderPal V2 offers several methods of how the various chunks of your net jobs are dispatched across your render farm. The methods include simple sequential dispatching, grouping together net jobs of the same priority and balanced dispatching, which will distribute the available clients depending on the net jobs' priorities. Each client pool can be configured independently from all other pools, allowing you to combine the various methods to fit your needs. |
| Clients & Client Pools |
Client pools
All render clients are organized into various, user-defined pools (groups of clients). These pools are not just organization units, but also offer numerous features on its own, like scheduling, automatic shutdown of idle clients and different dispatch modes, which determine how the chunks of their assigned net jobs should be divided among the clients. |
Remote client configuration
In a render farm consisting of 250 or more clients, nobody wants to manually configure each and every client. Due to this, RenderPal V2 offers easy remote configuration of clients, which allows you to easily configure all your clients from a single workstation. |
Automatic client recognition
Clients can send so-called heartbeats to the server (or a broadcast address), so that the RenderPal V2 Server will automatically know about their existence. Clients found in this way can then be automatically assigned to a client pool and will thus be immediately ready for rendering without any user interaction. Multiple IP ranges can be defined for automatic pool assignment, enabling fully automated management of your clients. |
System control
Clients can be automatically shut down when they are no longer used, or turned on via Wake-on-LAN if the server requires them for rendering. This can save a lot of energy and money. |
| Controlling & Monitoring |
Remote Controller
The RenderPal V2 Remote Controller is used to monitor and control your render farm from any workstation, even over the internet. Users can log into the Server and manage the render farm in any way. From submitting new net jobs to modifying the client pools, it can all be done remotely. The user management allows you to create user accounts which will be used to log into the server. Each account can have its own permissions and pool access, allowing for a very precise user control. |
Full overview
The main view of RenderPal V2, the server tab, offers a detailed overview of your entire farm, including all clients, net jobs and their associated chunks. |
View filters
Having all pools, clients and net jobs visible at a time can often be hindering, so RenderPal V2 offers view filters to restrict the amount of shown items to only those that match certain user-defined criteria. |
Client control
Users can control and monitor clients in many ways from their remote workstations. This includes on the fly configuration, retrieval of event and output logs or job control. |
| AUTOMATIC UPDATES |
Automatic updates
In RenderPal V2, it is no longer necessary to update any component manually. Instead, all you have to do is to add a new update in the update management and RenderPal V2 will do the rest. All clients and remote controllers will be automatically updated. |
User-created updates
While most updates will come directly from us, it is also possible to create your own updates, which can, for example, be used to deploy new custom renderers or some Python scripts. Since the updater itself utilizes Python, you can do much more with it than just deploying new files. |
| MISCELLANEOUS |
Path maps
One of the biggest burden when working with mixed platforms are their different paths. All systems have their own path conventions, and using UNC is not always the best choice. This is why RenderPal V2 offers so-called path maps, which allow you to map an incoming path to something else. They can be defined globally, per pool or per client and drastically ease working with multiple operating systems. |
Autostart
Both the RenderPal V2 Server and Client can be configured to be automatically started on system startup (even without the need of a user to log in). Under Windows, it is also possible to let RenderPal V2 recreate your network mappings. |
Email notifications
RenderPal V2 can automatically send emails about various events, like finished or erroneous net jobs. It is even possible to periodically send status reports. |
Submitter scripts
We have written submitter scripts for several renderers and compositing applications. These offer a simple and easy-to-use graphical interface that can be used from within the renderer to submit new jobs to the RenderPal V2 Server. |
|
 |
 |