Problem : "When I run LWSN it tells me: Can't open job file 'job1.'"
This is by the far the most common problem people encounter. It has many causes, making ithard to diagnose, but here are some possibilities.
Solution 1:Make sure your cmdLine file is formatted correctly and pathed correctly. It's obvious, but by far the most common cause of this error. If in doubt, download our LWSN cmdLine from 'LWSNHost Setup' in the Shockwave version of this tutorial.
Solution 2:Go into LightWave -> Rendering -> Network Rendering and hit the 'Screamer Init' button.
This creates a blank set of 'job' files that you will see in your current Content Directory. These can easily get corrupted, so initializing ScreamerNet is always a good idea.
Solution 3:Ensure that your Command Directory is set to the same asyour Content Directory.

Problem: "My LWSN's launch properly, but my Host doesn't see themwhen I 'Init ScreamerNet.'"
Solution: Ensure that your Host and Nodes are able toreceive 'Remote Apple Events.' This can be enabled from within your Sharingcontrol panel(System Preferences).

Problem: "My LWSN's render fine, but they don't save anything."
Solution1: If you're running OSX.2 you may be experiencing a problemidentified by Catalyst Productions. They produce a commercial screamernetcontroller and noticed a new feature in the OS which allows files to be both read and written at the same time. This unfortunately causes a problem with ScreamerNet's Job files. The problem has been rectified in Mac OS 10.2.3, so make sure you're running this OS version or later on your Host when using ScreamerNet to render.
Solution 2: Re-open your scene file in LightWave and make sure you have the correct output options in the Render Options window. You cannot save Quicktime movies with LWSN, so save out image sequences instead.
Solution 3: If you are using a multi-partitioned drive, make sure your Nodes mount any Host Volumes to
which you want to save renders.

Problem: "My LWSNs render fine, but save all my images in .flx format."
Solution: LWSN is not able to see the plugins configfile [LightWave Extensions 3 Prefs]. Make sure that ALL your cmdLinefiles path to the same place, including the Hub cmdLine. Also make sure that each Node mounts any Host Volumes that contain Config files. If this doesn't work, try re-scanning all the pluginswithin LightWave and then quitting to re-write the Config files.

Problem: "I run LWSN from a Node, but a strange console windowappears with a type box!"
Solution: Your Node's hard disk or partition name isthe same as your Host's. This confuses LWSN and so, by default it lookson the local drive for a Cmdline file. It doesn't find one and so kindly asks you to type in the command text yourself. As this is not generally a good way of working, simply rename thedisk/partition of your Host to something unique.

This tutorial was created by The Worms of Art. TheWormsof Art is the home of Pshelf--professionalsurface collections for Lightwave3D--as well as the best Lightwave tutorials online. You can visit them online or contact them at info@the-worms-of-art.com.