Describing the NRC interface
NRC is a network-rendering tool, which presupposes you have some experience with networks. If you have none at all, it will be easy to get lost and frustrated that NRC "isn't working". Knowing just enough about networking to get NRC xxx
Once installed on the machines in your network, the next thing to do is feed your Network Renderer with nodes and scenes. Nodes are the machines on your network running LightWave 2018 or that have the LightWave 2018 rendernode installation. If the rendernode hasn't been automatically started by the installer, or is not running for whatever reason, find the Network Render Controller Service 2018.x (64-bit) (NRC Tasker) in your Start menu.
The Service puts a green LightWave icon in your Task Tray. Right-clicking it offers two options:
The NRC has three menus, File, View and Help. The File menu contains just the Quit command (Ctrl-Q) and the NRC can also normally be quit by closing the window. The Help menu contains the links to the pages you are reading now.
The View menu contains two options:
Shows the Log window.
The icons at the bottom left indicate the severity of information messages presented. From the left they are:
Here is where you will set your initial paths - for content and for plugins. Care should be taken to use a path that all nodes in your network can access. The use of UNC-style path naming is strongly recommended as it is unambiguous, reliable and will work across Windows and OS X machines for NRC. Mapped network drives are also permissible for Windows-only farms provided the same drive name has been used across the network.
The Shared Plugin Directory is where the plugins your render nodes will use live. If the field has a red tint, check your plugins using the Manage Plugins button. This needs careful attention when you are working in a rendering environment with both Windows machines and Macs. More detail is given on the Shared Plugins Directory page.
Once your nodes have been set up and tasked with scenes to render, clicking the Validate Environment button should hopefully get you green across the board for your nodes, plugins, configs and content. Any time you get a red dot you should verify before starting the render.
For the Validate Environment button to be available the following conditions must be met:
Contains the machines on your network that are running the LightWave NRC service. There are four columns here:
At the bottom of this section are four buttons:
Note that stopping nodes also clears their render queues
The scene queue. Scenes in here are setup for rendering and are tasked to selected nodes by dragging the scene onto them.
The Scene Content Directory should be filled in automatically for each scene but can be overridden. Likewise the Image Output Directory will normally be blank for using the scene's own path, but can equally be overridden. There are four buttons here:
When a scene is loaded into the NRC, there are several options for rendering it in addition to scene settings.
The first is a Framing checkbox. This will render the first and last frames of the sequence before any of the others to set the bounds of the rendered sequence. The second is the fact that the frame start and end point can be double-clicked and modified. Render sequences can be in reverse or arbitrary frames rendered.
Normally you want to take full advantage of the machines in your network to render your scene at full speed. However, if said machines also perform other functions, rather than taking them over completely, you can throttle LightWave's use. It will make renders slower - and the machines - but it won't use all their resources. When setting up the scene, visit the Render Tab in Render Properties and turn off Automatic Multithreading. Set the number of cores to whatever you think will be safe to allow continued use of the nodes for other purposes.