A 3Delight Collective allows you to render a single image, including with IPR, faster by using several computers from your network. It is selected through the 3Delight Preferences (in the sidebar of 3Delight Display) or, when rendering using renderdl, though a command line option. For the 3Delight Collective option to be available, it must be defined first. There are three steps for defining collectives:
- Make a JSON file to list the computers to be used in each collectives;
- Inform 3Delight of the location of that file through the 3delight.config;
- Install a mall "service" program (or daemon in Linux) on each machine that is part of the collectives.
This is done by providing a list of computers/servers and giving it a name. In this same manner, you can define several distinct collectives. Here is an example of 5 collectives that can be defined in a hypothetical production facility:
...
With this information, the 3Delight Collective option will be available among the 3Delight Preferences and accompanied with a menu to select which collective to use:
Additional Installation Requirements
In order to used 3Delight Collective, a small "service" program (or daemon in Linux)need to be installed on each machine that is part of a collective. To install the program on a Windows workstation, run the following command:
C:\> collective -installservice
On macOS run the following two commands:
% mv /Applications/3Delight/com.3delight.collective.plist ~/Library/LaunchAgents/ ← to launch the licence server when the current user logs in
% sudo mv /Applications/3Delight/com.3delight.collective.plist /Library/LaunchDaemons/ ← to launch the license server when the system is started.
On Linux (WIP .... ) :
Additional Notes
- A server/computer can be part of one or more collectives. As is the case in the example above ("server01" is part of 3 out of the 5 collectives).
- With each server/computer name, you can specify a number of cores, eg. "server01,16". This limits the number of cores that will be used when rendering using this computer by invoking the collective it is part of. If the number is not specified, eg. "server01", then all the cores will be used.