Information
Rule & Render with some sovereignly facts
Workflow / How does it work?
Save Scene:
The artist has created a scene file. The scene file with all textures and source files is saved on the fileserver.
The data has to be on a fileserver as all machines need to access the files. (The folder C:\MySceneData is NOT located on each machine and cannot be used)
Submit Job:
The artist starts the rrSubmitter via a plugin in the menu in the 3D/comp application.
The plugin will read all required information from the scene and sends it to the rrServer.
Send Job:
The rrServer sends frames of each job to rrClients. The rrClients are either workstations or pure render farm machines.
Load Scene:
The rrClient starts the 3D/comp application and loads the scene file from the fileserver.
Write Frames:
The rrClient renders the frame numbers it has got from the rrServer.
Then it checks the frames and writes them to the fileserver.
Check Job and Frames:
The artist checks the progress of the job via RR.
In the end, the artist checks all rendered frames either via the fast rrViewer in small resolution or loads them directly from the fileserver in full resolution.
Requirements
Knowledge about networks and user accounts
You should have at least a bit knowledge about a network and user accounts in a network.
E.g. How you can save files that everyone can access them.
Hardware: Network
Fileserver/NAS for project data:
If you want to render on multiple machine, then you have do work on a fileserver. All project data (scene files, textures, output images) has to be saved on the fileserver.
You can NOT use any files that are on your local harddrive. Because the other machines do not have these files on their local drive. (Exception: You work/access your local drive via a network share name)
Note Microsoft Windows Limitation: You cannot use Windows XP/Vista/7 for a fileserver if you are using more than 4 clients. You have to use at least Microsoft Server foundation (which is not much more expensive than win7)
Caching fileserver like GPFS/Avere/Lustre are not supported at the moment, there should only be one RR folder that all machines access. (This will change with v8.1). As RR apps cache themselve onto the local harddrive, this should not be an issue.
Hardware: Royal Render
rrServer machine:
1 Windows/Linux or OSX machine for the rrServer.
OS: Windows (XP, 7, 10, any Server version, …) or Linux (CentOS, Fedora, Mandrake…)
Minimum Requirements: Ram: 2GB+ CPU: 2,5 Ghz single core, dual core recommended
This machine can be the fileserver
Fileserver/NAS for the RR applications:
1 fileserver which holds all RRender application files.
You require a network share (or directory on an existing share), which is accessible by everyone. This folder has all client and submitter executables and all config files.
It can be the same as the rrServer server and/or the same as the project fileserver.
Caching fileserver like GPFS/Avere/Lustre are not supported at the moment, there should only be one RR folder that all machines access.
