The LightWave Render Farm
Page 4 of 5
LWSN Host Setup--Run LWSN
Once you've quit LightWave so the Configs are written correctly, you can re-run it straight away and open up the Network Rendering window once more.[an error occurred while processing this directive] We're now ready to test the LWSN instance in the folder [LWSN01]. So find it and run it on the Host. We don't recommend using your Host as an additional Node--it jams up the CPU and can cause crashes--but for now, we just want to test that everything is located and running correctly.
If everything is present and correct, you should see something like the screen below. If you get an error such as, Error: Can't open job file "job 1" go to the Trouble Shooting section for more information.
Quit LWSN. Now you just have to replicate your folder [LWSN01] once for each Node on your network. Give each folder a similarly sensible name such as,[LWSN02], [LWSN03] etc.
Fig. 4.4 This is what LWSN tells you when it's running correctly.
LWSN Host Setup--Conclusions
You should now have as many LWSN folders as there are Nodes on your network, each with its own set of files. We are using just three, so our Programsfolder looks like fig 4.6.
- Inside each folder is a separate copy of LWSNcmdLine. They need to be almost identical, except that we need to assigneach instance a differentCPU number. So open up the LWSN cmdLine file in the folder [LWSN02].
- Alter the last partof the line as we have done in fig 4.5. For [LWSN03] alter its LWSN cmdLine file so it ends "job3 ack3" etc..Once this is done for each Node folder, you've successfully primed your Host for network rendering. Phew!
-2-c"WOA_System:Applications:LightWave 3D 7.5:Configs" -d"WOA_System:**PROJECTS**:the-worm" job2ack2
Fig. 4.5--The cmdLine for [LWSN02]
Fig. 4.6--Our Programs folder has three LWSN folders inside.
They each contain all the necessary files for a Node to run successfully.
LWSNNode Setup
Network and Sharing
You've now set up a folder for each rendering Node on your Host and checked that both LightWave and LWSN are set up correctly by running one instance of LWSN on the Host machine.
You can now leave the Host for a while and concentrate on getting Node1 working. Once you've done this, simply duplicate the process on all your other Nodes.
As with the Host, your Node machine needs a couple of active Sharing options (fig 5.1). Remote Apple Events are particularly important on Node machines,as this is a method LightWave uses to communicate as the controller.
- Oncethese are set, try connecting to your Host machine (Command + 'K' - "Connect to Server").
- Make sure you log on as a Registered User NOT a Guest. Guest access onlyallows you to see the Host's [Public] folder.
- Mount any volumes required for rendering. If you are using a mult-partitioned drive on the Host and have yourContent Directory in a different partitionto your LightWave installation, then you need to mount both Volumes. Alsomake surethis is reflected in your cmdLine files.
Hopefully, you now have the Host'sdisk icon(s) on your desktop.
Fig. 5.1--Highlight these settings in your Sharingcontrol panel. This is located in System Preference.
LWSN Node Setup--Install and Go!
Although we're not going to run any software that's actually on our Node machine, we still need to perform a basic installation of the LightWave Programs on each Node. This is because there are certain library files and extensions that LightWave needs to operate successfully and these only get installedwith LightWave itself.
- Go ahead and perform a 'Custom Install' of LightWave on Node1, installingjust the Programs and their related files.
- Once you've done this, delve into your mounted Host Volume(s) fromthe Node and search out the folder [LWSN01].
- Select the LWSN app inside [LWSN01] and add it to your Node's Favouritesby pressing (Command-T).
- Open your Favorites (Command-Shift-F). Rename the "LWSN" aliasas "LWSN01." From now on you'll be able to run this instance of LWSNdirect from your Favourites.
- Run the application LWSN by double-clicking its Favorite Alias.The app should run and you will see "LightWave Command Init" written continuously down the screen.
This Node is now ready to render. See, not so bad after all! Simply duplicate the steps described in this section for each Node on your network.
NOTE: If your Host's Volume name is the same as a Volume on your Node, you'll now have two identically named disk icons on your desktop. LWSN cmdLine does not distinguish between them and so will by default look on the local drive. This will confuse it and may cause it to bring up a Console Window, thus confusing you! This is why it's a good idea to uniquely name your Host's Partition(s).
Rendering
Rack 'em Up!
If you wish to test your network rendering using multiple Nodes, go ahead and set them all up as you did Node1. Run each Node's instance of LWSN across thenetwork.
Once this is done, return to your Host machine and bring LightWave to the front, opening the Network Rendering window if it's not alreadyopen.
You're now going to see if LightWave detects all your Node machines by hitting the "Screamer Init" button once more. Hopefully you should see something like fig 6.1. We are using just3 Nodes, so LightWave detects our 3 satellite machines, each running LWSN.
Fig. 6.1--Our 3 Nodes should appear when we hit 'Screamer Init.' The CPU number on the left
corresponds to the 'Job' numbers we typed into the LWSN cmdLine files.
Rendering--Let 'em Go!
With our Nodes detected from the Host machine, we add a test scene to the render queue. We've created a fast rendering scene called "WormTest.lws." We've already checked that this file has its Output Image saving options correctly pathed. Remember that you can only save out Image Sequences while network rendering,not QuickTime movies.
With our scene loaded up, we can go ahead and render by hitting "Screamer Render." The Node machines should now begin loading up the scene file and renderingaway. That really is it!
Check that images are being saved into the desired folder as each frame finishes. If there are problems at this late stage, check out the Trouble Shooting section, as there are some common issues tackled there. Once you have your teething troubles sorted, you only ever have to alter your LWSN cmdLine each time you change Content Directory. Everything else can stay the same.
Good luck and may your crashes be few.
Fig. 6.2 Add a scene file to the list. It shows some information about the scene.
Now you are really ready, so go ahead and hit 'Screamer Render.' That'sit!
Prev 1 2 3 4 5 Next
[an error occurred while processing this directive]
