Settings

Run LightNet-Cloud.exe  and click "Settings -> "Change Settings" (LightNet-Watcher.exe uses the same configuration file, but all of the settings are controlled by LightNet-Cloud.exe, so run it first). Here you'll see four tabs:

General Settings

You need to give your screamer a name, this is used to generate logs. Be sure it has a unique name to prevent confusion if you need to review logs.

You need to give your screamer a name, this is used to generate logs. Be sure it has a unique name to prevent confusion if you need to review logs.

If you have multiple offsite computers on one network, the Local Network Cache can be used to ensure only one computer at a time is downloading the content archive rather than every computer downloading it at once and bogging down the network and FTP server.

To use it, select a directory that all of the computers on the local network can see with read and write access. The first computer to attempt to download the content archive will create a small text file (within a newly created directory named after the scene file) in the Local Network Cache directory with the time it initiated the download and it's name. It will then download the archive and copy it to the Local Network Cache. From there, all of the other computers on the network will simply copy the file from the Local Network Cache rather than download it directly from the FTP server.

The other computers on the network running LnC will check the download information file periodically, if the content archive is not downloaded within an hour, then another computer will initiate the download.

If the Local Network Cache is blank, set to [none] by default, or does not exists LnC will simply download the content archive as usual.

Choose a group or groups you want the computer to be part of. Groups are separated by spaces. Scenes setup with LnC's LScript will have a group list as well, when LnC loads the scene it will see if their is a match between the two group lists and if it finds any matches, it will render the scene. If it doesn't find any matches, it will move on to the next scene,

For example you can set the first computer up with the groups: default 32bit 64bit. And set a second computer up with the groups: default 32bit. With these two computers any scene with 32bit and/or default listed in the groups will render, however only the first computer will render scenes that only lists 64bit in the group field.

Check onsite, offsite or both.

Choose if you would like to use Adaptive Frame Loading (HIGHLY RECOMMENDED). Adaptive Frame Loading will render a number of frames based on the FTP check interval. If you set the FTP check interval to 5 minutes (300 seconds) and a frame takes 1 minutes to render, then with Adaptive Frame Loading, it will render 5 frames at a time. It does this by first rendering one frame of a new scene and recording the time, then adjusts accordingly as the scene continues to render. If you have a scene that takes only a few minute or less to render, it will put a lot of pressure on the server as multiple PCs are checking in and uploading images in very short intervals.

Choose if you would like to Autostart when the system is idle and set an auto start interval.

Finally, choose if you'd like to run in "Silent Mode". In Silent Mode, LightNet: Cloud will launch ScreamerNet at low priority and if it is started by autostart, it will start minimized.

FTP Server Settings

On the FTP Tab you can enter all of your FTP server's settings. A FTP server is required for central information storage.

Under the FTP Sub Directory, if it is root, leave it blank. Do not put a /

LW3D Settings

On the Lightwave3D tab you need to select the directory that contains the Lightwave programs and the config files as well as the suffix on the end of the config files (this is used for diagnostics).

Watcher settings

On the Watcher tab you can select a Watch Folder, select whether or not this watcher should manage the server and set a check interval. Only one computer per  Watch Folder should manage the server and a good practice is to have only one watched folder per network.  If "Manage the server" is not checked, the Watcher application can still get the status of the server at the interval settings.  If you do not intent to use the Watcher on a PC, you do not need to setup this tab on that PC.

Silent Mode for LightNet: Watcher v1.5 does nothing, I only left the settings in place in case I want to use it for something in a future version.