Copyright: Lightnet Help v1.23


Overview

Help file Version 2.00 beta 4

LightNet is an advanced replacement for Newtek’s Lightwave ScreamerNet.

It's a standalone program that allows you to render multiple Lightwave scenes on multiple computers in a network. The completely object-oriented approach allows a maximum of flexibility in adding, moving and removing scenes, as well as launching, killing and crashing computers, from any computer in the network.

Currently LightNet is only available for Windows 95/NT on Intel or Alpha (using FX/32) platforms.

Greetings, Schoenmaekers Raf

Komkom Doorn

web site	www.komkomdoorn.com

e-mail	raf@komkomdoorn.com

telephone	+32  |  9  |  234 22 15

address	St.-Pietersniewstraat 134

9000 Gent

Belgium

Europe


Features

Some of the main features are:

Flexibility

While LightNet is rendering you can…add, move and remove scenes and start, shut down and ‘crash’ computers. Screamers can be started from within LightNet.

Unlimited

Contrary to some other programs, LightNet supports unlimited scenes, unlimited frames in scenes and an unlimited number of computers (Screamers)

Selective rendering

A wide variety of selection criteria are available to specify which computers you want your scene to render on: minimum memory, specified percentage, specified Screamers, …. You have the possibility to create groups, for easy selecting.

ScreamSaver

LightNet monitors the processor activity and can start Screamer automatically when the computer is found idle for a specified time.

Editing

The ability to edit all the render settings of a scene (camera settings are for the near future.

Remote operation

All users in the network have constant overview of the scene list and computer list. They can all add, move and remove scenes as well as start, kill and crash computers from their own computer.

Night- and weekend-proof

Automatic verification of frames and re-rendering of skipped or crashed ones. Automatic crash detection of Screamers.

Frame manager

An integrated frame manager allows easy copying, moving and deleting of frames. This is especially useful in combination with a DPS Perception/Hollywood, where copying images to the appropriate directory means turning them into a video sequence.

Automatic copying of frames when they are rendered is recently added. When you arrive in the morning or after the weekend, all your animations are immediately ready to be viewed. (This is an experimental feature, so use it on your own risk.)

Full Screen Interface

No fixed windows, but a full screen or sizeable interface.


What’s new?

Version 2.00 beta 6	11 | 6 | 2000

General

Config File

Better Screamer configuration file parsing to find the image file types installed. This is obviously required to do proper "image verification" (the thing making scenes getting re-rendered a few (5) times, if not working properly)

Master

Program | Check config …

Check here which content directory and image saver plugins LightNet found in the Screamer configuration file you selected (lw.cfg or lw3.cfg). You can not change anything here; it's for verification only.


Special thanks…

… goes to Grid and the people working there. From the very beginning up till now, they provided the ‘beta-site’ (Remember the days only half of the frames were rendered overnight…) and the feedback. Many of the ideas and features originated from their daily use of and comments on that ‘LightNet Thing’.


Basics

Though LightNet has quite some options more than Newtek’s ScreamerNet, the basic principle is the same. If you want to know more about ‘low-level’ network rendering, I’d like to refer to Newtek’s documentation. Here I’ll discuss only the things that are LightNet specific.

LightNet is organized around three lists (Scenes, Computer and Events). View the different lists by clicking on the speedbuttons or using the shortcuts (S, C and E).

Selecting

Selecting one scene or computer in the lists is done by simply clicking on it. Selecting multiple items is done by clicking on the first item, holding down the SHIFT button, and clicking on the last one.

Scene list

The scenes in the list are rendered from the top down. Moving of the scenes is done by dragging the first column (scene number) to the place you want it to. This is always allowed, even if scenes are rendering already.

In the scene list you’ll find

1. Number of the scene

2. The priority of a scene (ranging from 0 to 4)

3. An empty box if the scene is going to be copied. A full box if the scene is copied.

4. An empty box if the scene is going to be verified. A full box if the scene is verified.

5. The percentage of frames send to a Screamer (which not necessarily means they are already rendered)

6. The name of the file.

7. The directory of the file.

8. The frames to be rendered.

9. The last frame sent to a Screamer.

Information

When your cursor is not moving over a scene, the total amount of scenes and frames is shown under the list.

When moving over a scene, the info panel changes to the data related to that scene.

Color codes

Darker (gray) scenes are normal scenes.

Bright (white) scenes are of which some frames have to be rendered again (after verifying the scene or the crashing of a Screamer).

Red scenes have a warning attached to them. Move over the scene and look at the info panel at the bottom to get more details.

Commands

The commands to add, remove, edit,… scenes are found under the Scenes menu item.

Computer list

The computer list contains the Screamers currently rendering.

In the list you’ll find

1. Screamer number.

2. Screamer CPU type.

3. The amount of physical RAM installed on the Screamer’s computer followed by the number of Screamers installed (if more then one)

4. Screamer/Computer name.

5. Screamer status.

6. Scene filename of the currently rendering scene.

7. First frame, last frame and frame step, rendering on the Screamer.

Color code

Bright (white) Screamers are rendering on the computer you’re looking at. Darker (gray) Screamers are rendering on other computers in the network.

If a Screamer is red, it means there's a warning attached to it. Check out the info panel for more details.

Event list

The event list gives an overview of the (recent) events.

In the list you’ll find

1. Event number

2. Event level (the more dots, the more important)

3. Time of the event.

4. Origin of the event.

5. Type of the event.

6. Extra comments.

Info panel

The information panel (Program | Info) gives information about the item you move your mouse over. In the scene list, this means general scene information, render and camera settings and the options set. For the computer list this are some statistics about the computer your on.


Setting the options

In the menu, under  Program | Options you will find the options to set.

The options under ‘Master’ and ‘Screamer’ are the only options you really should set correctly before using LightNet. The rest of the options have the most  reasonable default value.

Depending on whether you’re setting up the Master or a Remote, you will find…

Master

Master

Highest number of Screamers

Enter here the highest Screamer number in the network (or more).

Number of frames send at a time

Screamer has the ability to render multiple frames ‘at once’. This is especially useful to avoid the network-overhead which occurs with fast-rendering frames (less then a minute). Normally this is set to ‘1’.

Old style screamer

Because ‘old’ Screamers use a different format to control, this must be checked for them.

Scan for remote commands

Allows remote users, to edit the scene- and computer lists.

Check interval for Screamer and remote commands

Here you set the time there is between every command check. On a command check, the LightNet Master will.

•	see if one of the Screamers has finished loading, rendering, ... and therefore needs to get a new command.

•	see if one of the Remote Lightnets has sent a command (if the above option is checked)

•	verify scenes if they are finished rendering (and the verify option of the scene is set)

Remove rendered scenes from scene list

Removes rendered scenes after a given time from the scene list. (If scene verifying is on, scenes aren’t removed until rendered and verified.)

When all scenes are rendered, verify, …

If checked, the Master verifies all scenes, even if some Screamers might still be rendering their last frame. This results in idle Screamers double rendering some of the frames. This might be interesting if  some Screamers are ‘crashed’ without  the Master knowing it. Not crashed Screamers will then take over their frames.

Screamer*

Screamer name*

Enter here the name of this computer.

Screamer processor number*

Enter here a unique number for this Screamer. If you want the possibility of running more than one Screamer on a single computer (which might be useful on a multiple processor computer) enter here multiple numbers, separated by spaces.

Commands directory*

Enter here the common directory used by all LightNets and Screamers for passing through the commands.

Screamer file*

The Screamer file (lwsn.exe) is the core renderer as delivered by Newtek.

Screamer config file*

Select here which config file you want to use. For Lightwave 5.x this is typically the lw.cfg file, and for Lightwave 6.x this is lw3.cfg.

Hide Screamer

You can now hide the Screamer window from your desktop if you want to.

Set Screamer priority to ‘idle’

Here you can set Screamer priority to idle. This means you can have a Screamer running in the background while working, and it will only take processor time if you don’t need it (theoretically). It will still eat the necessary memory however.

Events*

Log events in file*

Saves the event-list  to the specified file

Remove major events *

Removes major events from the list after the given time.

Clear minor events *

Removes minor events after the given time.

ScreamSaver*

Start ScreamSaver*

Starts Screamer if a processor is found idle for the given time.

Idle time percentage*

As ‘idle’ is a relative measure, you can configure this to you personal taste. Check out the activity meter under the event list. The red bar indicates the level under which the computer is considered idle. This can be changed setting this idle time percentage. A higher percentage means more idle time must be available before the computer is considered ‘not-used’, this means Screamer will not so easily start. Experiment to find the correct percentage for you.

Make noise*

When checked, ScreamSaver will announce itself ten seconds before launching, with a beep every second.

Communication

Send status and warnings

Set here the interval at which reports must be send by this LightNet.

Email

Check if you want LightNet to send you a duplicate of the Scene & computer list at the above interval time.

Dial account Windows NT only

Check this if you don’t have a permanent connection to your mail server. The name to enter is the name if the phonebook entry in your ‘Dialup Networking’ phonebook.

SMTP-server

The name of the SMTP-server. Check your regular mail program if you’re not sure.

Email-address(es)

The address(es) you want the reports send to (separated by comma’s)

Remote

Remote

Update after every command

When checked, the remote will (try to) update after every command (add scene, remove scene, …)

Update automatically

Updates after the specified time. This is required if you want the computer to copy/import frames.

Allow this computer to copy/import frames

As it says: allows this computer to copy/import frames

The rest

You will find settings for Screamer, Events and ScreamSaver. Refer to the Master settings above for more details; the options are marked with an *.

Notes

Only one master

There should only be one computer acting as Master in the network, unless you set them up using a different Commands Directory.

Unique numbers

Use different numbers for every processor in the network. Multiple processor computers can have multiple Screamers running. (cfr. above)


Tips

Master

Commands Directory

To minimize network overhead, place the Commands Directory on the same computer as the Master. Access this directory by it’s local hard-disk name. (e.g. D:\Commands\ )


Menus

Common

Program

Master

Switches the program into Master-mode. As mentioned before, there should only be one Master in the network.

Remote

Switches the program into Remote-mode.

Options 	[Ctrl-O]

Shows the Options panel.

Exit	 [Ctrl-X]

Scenes

Add	Ins

Adds one ore multiple scenes to the scene list.

Remove	Del

Removes the selected scenes from the scene list.

Duplicate

Duplicates the selected scenes and adds them to the end of the list.

Edit

Edits one or more selected scenes.

Verify	[Ctrl-V]

Verifies which frames of the selected scenes are (still) missing. When using this command on the Master, you have the option of rendering the missing frames again, which are added to the missing frame list. (See editing scenes)

Reset	[Ctrl-T]

Sets the selected scenes back to ‘completely unrendered’.

Frame Manager	[Ctrl-F]

A tool to manage (delete, move, copy) frames of the selected scenes.

Select All	[Ctrl-A]

Selects all the scenes in the scene list.

Save List

Saves the current scenes list to a specified file.

Computers

Rescan	[Ctrl-R]

Rescans the network to look for newly added computers.

Start | Screamer X	[Ctrl-S]

Starts Screamer with number X (as you entered in the Option panel) and rescans immediately thereafter. If after a few seconds the (black) Screamer window still shows ‘init’, perform a rescan manually.

Kill	[Ctrl-K]

Kills the selected computers. This means that the computers will continue rendering the frame they are currently rendering and self-destroy afterwards.

Crashed	[Ctrl-C]

If a Screamer is crashed (by program error, or by closing it manually), this must be told to the Master. Select the crashed computers and execute this command to keep the computer list up to date. By default the ‘crashed frame’ will be added to the missing frames list (See editing scenes)

Events

Clear All

Removes all events from the list (except the really big ones)

Clear Minor

Removes minor events from the list, which mostly originate from user commands.

Help

Contents	F1

This help file

About

Some basic information about the program.

Master

Program

LightNet Remotes Overview TCP/IP only

Gives an overview off all LightNet Remotes currently connected by TCP/IP.

LightNet Remotes Close All TCP/IP only

Closes all connected LightNet Remotes

Scenes

Open List

Adds the scenes of a previously saved list to the current list.

Computers

Start | Other TCP/IP only

Gives an overview off all Screamers in the network and allows to start Screamers on LightNet Remotes currently connected by TCP/IP.

Remote

Program

Update	[Ctrl-U]

Updates the scene- and computer lists with the current lists on the Master.

Events

Message

Sends a message to the Master.


Scenes | Edit

The options marked with an * are not available when editing multiple scenes.

Render

Mode

Refer to the Lightwave manual for more details.

Frames*

This is not available when editing multiple scenes at once.

Range

The range specifies the frames to be rendered. The little button under the checkbox resets the range to the original values (as specified) in the scene file.

Singles

Singles specifies the numbers of individual frame

Frames to render again

These frames originate from crashing computers or verifying scenes. Manual editing is allowed.

Output*

Refer to the Lightwave manual for more details.

Camera

Only available when running in debug mode.

0	Refer to the Lightwave manual for more details.

Options

Priority

Sets the priority of the scene. (Who would have thought that?)

Platform

Intel | Alpha | Macintosh | Silicon

The checked platforms are the only ones the scene will be rendered on.

Render On…

Sets restrictions to the Screamers to render the scene on. There might be two reasons:

•	technical: the scene can only render on the specified Screamers, because it needs the specified memory, needs to have certain plug-ins installed, …

•	management: you prefer to spread the scenes over different computers, so you have already ‘some’ frames of two or more different scenes.

On selecting Screamers (the little button left to the edit box), you have also the possibility to select groups. Remember the options to create and delete groups is only available on the Master.

Automatic

Verify scenes

Verifying scenes means LightNet is going to check whether the frames are really on the disk where they’re supposed to be after rendering.

0	If there are frames missing, a new scene with only these frames is added to the list.

1	This automatic verifying is only done under these conditions:

•	When the scene is rendered a 100 percent (this means all frames are send to a Screamer for rendering)

•	When no Screamer is rendering on a frame of this scene

•	When no other scenes (manual or automatic) with the same filename is still in the list.

Copy/import frames (experimental feature)

When a scene is rendered, the frames can automatically be copied to another directory, for safety or turning them into an animation (DPS Perception/Hollywood, …).

The computer on which this has to happen, must be a ‘Remote’ one and can be set to the current one by pushing the little button.

Verification (see above) is necessary, before LightNet will start copying  frames. Also ‘Allow this computer to copy/import’ for the specified LightNet (see Options), must be switched on before LightNet even thinks about copying a frame

Log*

Only available on the Master

Log file

If for one reason or another, some Screamers fail to load a scene, don’t save their frames or render wrong output (missing plug-ins, …) you can generate a detailed log file to find out were and on which Screamer it went wrong.


Other Features

General

Closing the master

When you close LightNet and restart afterwards, it will continue rendering as if nothing happened. This is especially useful when upgrading LightNet in  the middle of a project.

Scene list

Moving of scenes

Dragging the first column of the list (the one with the scene numbers) allows for moving the scenes in the list. The scenes are always rendered from top to bottom.


Frequently asked Questions

How do I install LightNet?

Q . I have unzipped my LightNet file, what now?

A . Copy the files to a directory of your choice and make a shortcut to it.

You can put one copy on a network drive and make a shortcut to that LightNet from all your computers in the network. This way, later upgrading, just means replacing these files once.

How do I start rendering?

Q . I’ve added some scenes and started some Screamers (which were successfully found by LightNet), how do I start rendering?

A . LightNet is always rendering. No special actions required here.

Screamer doesn’t start?

Q . If I start Screamer (Computers - Start), Screamer launches, but keeps displaying ‘init’ repeatedly.

A . Due to slow starting of Screamer, the Master might have rescanned before Screamer was actually started. Press Computers - Rescan again.

Where do the *.lns files come from?

Q . What are these *.lns files for?

A. Each time you add a scene to the scene list LightNet makes a copy of it with the extension ‘lns’.  If you edit render or camera setting, these changes are only made to the *.lns file, not your original scene file. The ‘lns’ file is the one that actually gets rendered by the Screamers.

If you add a scene more then once to the scene list, ‘_0’, ‘_1’, … will be added to the *.lns file, so they can be edited individually.

Q . What if I remove them?

A .  You should never remove the *.lns file. LightNet cleans it’s own mess, and removes the *.lns file if the scene is removed from the list.

If you accidentally remove the *.lns file anyway, remove your original scene from the list and add it again. A new *.lns will be created.

If you forget, and LightNet still doesn’t find  the *.lns file, the Screamers will render the original scene, with the original render and camera settings.

Configuring the network?

Q . If I start a Screamer, it renders extremely fast and saves nothing.

A . The Screamer probably didn’t find the scene and renders an empty one.

First, make sure your scenes use only network drives and they are mapped the same on every computer in the network.

If you use Ligthwave’s ‘content directory’ make sure the Screamers can find it in their config file (lw.cfg) which should be in the same directory as the Screamer program (lwsn.exe), unless you change this directory in the Options panel (Program | Options | Screamer)

When a scene has finished rendering, LightNet starts all over again.

Q. After rendering all the frames,  LightNet restarts rendering completely. Why?

A. LightNet has build in an 'automatic verification' option. This means that, after finishing a scene, the Master will go and look for the frames to see if they are really on the disk. If you want it to work properly, you must however be sure the LightNet Master 'sees' the images in the same way as the Screamers do.

Sometimes the images aren't on the disk at all, sometimes the images are there but LightNet isn't able to find them.

Bellow is a checklist you could follow to find out where the trouble comes from:

-	Are all the network drives you use mapped properly? If you write your images to let's say drive J, is it mapped on all your computers as drive J? This shouldn't  be a problem if you use UNC (Network Neighborhood)

-	Are all your drives, accessed at least once? Check if there's no little red cross over the drive icon in Explorer. As long as a drive isn't accessed at least once LightNet nor Screamer will be able to access it. Again, this shouldn't  be a problem if you use UNC (Network Neighborhood)

-	Is your content directory set properly? The content directory is not saved in your scene file but in the LW.CFG file. You can check the info panel to see what LightNet thinks is the content directory. If the LW.CFG isn't in your Screamer directory, be sure to set the proper directory in the options panel (Program | Options | Screamer)

-	Have all your Screamers the same saver plug-ins installed? The image type (recognized by the file extension) is saved in your scene file as a number: the number of the saver plug-in installed. If you have different plug-ins installed on different computers, all the Screamers might end up saving different frame formats.

-	Don't use verification if you render straight to Perception or Hollywood.

A good way to find out what the LightNet Master is looking for on verifying frames is the info panel (Programs | Info). If you move over the scenes and have the 'Render' tab checked, you should see the full path of the first image, including network drive and content directory (if you use it).

If this is wrong, you should be able to isolate the problem by checking what is wrong: content directory, filename or file extension. Another way to know if the LightNet Master finds the frames is the Frame Manager (Scene | Frame Manager).

At the end of the scenelist LightNet keeps going.

Q . At the end of the scene list, LightNet renders double frames. Why?

A . This is a kind of  safetynet. At the end of the list, idle Screamers start rendering frames LightNet couldn’t find on the disk (automatic verification) but which might be rendering by other Screamers. However, these ‘other’ Screamers might also be crashed, and - in this case - its pretty nice the other Screamers give it a go (since they have nothing else to do).

Q . How can I avoid this ?

A . In the options (Program | Options | Master) panel, switch of ‘When all scenes are at 100%…’

Why is there no native Alpha version?

Q . Why is there no native (Compaq/Dec) Alpha version and do we have to use FX32 to run LightNet on these machines?

A . LightNet is written in Delphi (Pascal) and a such isn’t easy to port to Alpha. Rewriting it in C++ is in it’s initial fase but probably won’t really take off until I’m sure what Newtek is up to with Lightwave 6.0.

Q . So, why, stupid asshole, did you write it in Delphi in the first place?

A . Well, in the early days (1996) I felt a lot more comfortable writing it in Delphi than C++. At the time, I didn’t think of this worldwide success. If only I could predict the future.


Known Problems

General

The possibility of starting more then one Screamer with the same number. Some more checking will be build in soon.

Master

Remote

Commands

If two remote commands are sent to the master within one second, the possibility exists that the first one is lost (not executed).

View | Update

Only after two times updating, the lists are really updated to the latest situation. (On ‘Update’ the Remote requests the Master to publish the latest lists, but doesn’t really wait before starting to retrieve these lists from disk. This means the lists are often not ‘really’ up to date on first retrieval.)


Coming Soon?

The wish list of current users… (and after it the version I hope to put it in)

Master

Safety

Frames storage

Checking of disk capacity and in case of overflow, redirect frames to other disks. (v2.10)

Scene loading

Checking to see whether a Screamer is really rendering a scene and not just ‘zipping’ through. (v2.10)

Remote

Security

Restricted remote options

The options to limit remote actions to avoid abuse by dominant animators or ignorant network users. (v2.10)


History

Version 2.00 beta 4	8 | 5 | 2000

General

New splash screen

Very important.

"Could not open ... file" popups

Hopefully killed...

Master

Program | Options | Screamer  | Config File …

As you can now select a config "file" instead of a config "directory" you can choose between Lightwave 5.x (lw.cfg) or Lightwave 6.0 (lw3.cfg)

Version 2.00 beta 3	12 | 4 | 1999

General

Only one LightNet

Now a warning is given when you start more then one LightNet on a single computer.

Status bar

The status bar now shows TCP/IP information. Check this place to see if everything goes well, when using this new way of communication between LightNets (more details below).

Help file

An updated help file and especially an new topic in the section 'Frequently Asked Questions' on: what if LightNet keeps rendering a scene over and over. (The question most asked)

Master

Program | Options | Master | Check for …

Beside the 'classic' file based commands, the Master can now accept TCP/IP commands. Facts to consider:

- TCP/IP is preferred to avoid network overhead

- File based commands will probably disappear in a future version of LightNet

- TCP/IP allows two way traffic (Remote to Master and back) and therefore allows commands not available if using only 'files'

- If all LightNet Remotes send TCP/IP commands, be sure to uncheck the 'file based commands' here.

Automatic Rescan

Now the Master will rescan automatically every 5 minutes, in order to pick up the unlucky Screamer that wasn't found immediately after it started.

Computers | Start | Others TCP/IP only

Here you can start Screamers on remote computers. Only make sure that LightNet is running on every computer you want to respond to this command.

Program | LightNet Remotes | Overview TCP/IP only

Gives an overview of LightNet Remotes currently online and connected by TCP/IP to the Master.

Program | LightNet Remotes | Close all TCP/IP only

The possibility to close all LightNet Remotes, for easy upgrading.

Remote

Program | Options | Remote | Send …

As mentioned above, now you have the option between 'file' and 'TCP/IP' commands. Make sure you set the Master to accept whichever you choose.

If you go for TCP/IP, make sure you properly set the Master IP address: four numbers separated by dots.

Of course, if the Master goes offline, the connection will be broken. Thereafter, the Remote will attempt every 30 seconds to establish a new connection.

Program | Update TCP/IP only

Now updates immediately to the latest status.

Program | Options | Remote | Update after every command

Now redundant when using TCP/IP, as you get an immediate update anyway.

Version 1.50b	20 | 3 | 1999

Computer list

On multiprocessor machines, the amount of memory is now divided by the number of processors installed. It’s a more accurate solution, but still far from perfect. In the future, the amount of available memory will be passed on to the Master, not the amount of installed memory.

Scene | Edit | Options | Render on…

Only … Screamers for multiprocessor computers should now work properly

Computers | Start | Screamer

The famous black Screamer window now shows the number of the Screamer.

ScreamSaver

Now it's less likely , ScreamSaver will start more then the allowed number of  Screamers.

Version 1.50a	15 | 3 | 1999

General

Communication

Reports are extended with scene and computer statistics (same as info window)

Program | Options | Screamer

There now is a big button, which gives you an overview of all the Screamers.

Scenes | Edit | Options | Platform

You have the option of rendering on:

•	a maximum amount/percentage of the available computers

•	a selection of Screamers
Here you also have the ability to create groups

•	Screamers with a certain amount of memory only

•	A limited number of Screamers for each multiprocessor machines (some plug-ins make a Screamer crash if you render with two Screamers together on one machine.)

Be sure however there’s at least one Screamer capable of doing the job.

Proper warnings will be built in later.

Programs | Info

The 'general info' you could find at the bottom of the lists, now also sits in the info panel. The info panel now also remembers the last tab selected if you switch between ‘Scenes’, ‘Computers’ and ‘Events’.

Program | Options | Screamer

The Screamer name default value now automatically is the computer name.

Scenes | Add

After selecting the scenes, you now get the complete options panel to set priority, platform, … There’s also a button to set the default options.

Computer list

Computers are now automatically sorted by number. What more do you want?

Version 1.46a	4 | 2 | 1999

General

Startup

LightNet should now start, even on machines where the TCP/IP network protocol is not installed.

Program | Options | Look

Now LightNet (by default) minimizes to a system tray icon, which can be switched off here.

Program | Options | Screamer

You can now hide the Screamer window from your desktop if you want to.

Here you can set Screamer priority to idle. This means you can have a Screamer running in the background while working, and it will only take processor time if you don’t need it (theoretically). It will still eat the necessary memory however.

Version 1.45a-c	10 | 1 | 1999

General

DVD-ware

LightNet is no longer freeware but DVD-ware

Automatic crash detection.

 If a Screamer quits LightNet will automatically perform the ‘Computers-Crashed’-command. This feature requires LightNet to be active permanently.

LightNet maintains a ‘ link’ to the local Screamer and checks for activity. If Screamer crashes LightNet will alert the Master. Combine it with ScreamSaver to ensure permanent renderings.

Program | Options | Communication | E-mail

At regular intervals LightNet can send you a report (scene and computer list). If you use this on a remote (preferred), be sure you have automatic updating switched on. This is a ‘beta’ feature. I’m not responsible for high phone bills (after LightNet not hanging after on trying to send an e-mail).

Mind you that dialing only work on Windows NT (LightNet uses RASPHONE.EXE to dial in to your server. Windows 9x is under development.)

Scene list

Computer name of the one who added the scene is now again properly set.

Scene list

Column widths are (again) properly set.

Scene | Verify

Manual verification now always checks for missing frames even if the scene has already by successfully verified once. This allows for easy re-rendering of frames, which you have deleted manually.

Program | Options | Look

The oldest hidden feature is now out of beta status… You can now change the main interface color (but leave it up to LightNet to choose the aesthetic variations). Choose something neither too light nor too dark. Experimentation is free.

Program | Help

Updated helpfile.

Master

Program | Options | Master

Check interval for Screamer and remote commands now allows to set the time there is between every command check (see Options)

Version 1.41	26 | 10 | 1998

General

Scene list

Priorities added to better organize long scene lists. Scenes with a higher priority are always higher in the list. Scenes can not be moved beyond their priority.

Scenes | Add

After selecting a scene, priority and render platform can be set immediately.

Scenes | Edit | Options

The option to change priority.

Remote

Scene | Edit | Render

Some small bugs fixed on editing output settings which were not properly passed on to the master.

Version 1.40	20 | 07 | 1998

General

Program | Info | Scene list

Extended information on scenes.

Program | Info | Computer list

Statistics on the computer you move your mouse over.

Scene list

Mentioning of Content Directory in info panel

Scenes | Edit

Rearrangement of information to better reflect Lightwave’s ‘render’ and ‘camera’ settings

Scenes | Edit | Render

Extended information on scenes

Master

Scene list

Better end behavior, when all scenes are rendered.

Program | Options | Master

The option to disable ‘double’ rendering of last frames, even when the Screamers don’t have anything else to do. (Leave enabled if you want to catch crashed Screamer frames)

Version 1.34	10 | 06 | 1998

General

Removal of (extra) automatic scenes

Now missing frames (verify/crashed) are always kept with the original scene.

General

Region independent date/time handling (for people with mixed regional settings across their network).

Support for ‘content directory’ retrieved from the Screamer config file.

Verifying take into account extra extensions from plug-ins (found in the Screamer config file.)

Some better exception handling

Scene list

New color codes: gray scenes are normal, white ones have some missing frames to render and red ones have a warning.

Better scene statistics

Scenes | Edit | Frames

Now has the extra ‘missing frames’ edit box, were you can see the rerendered frames.

Scenes | Edit | Help

The help button really helps now

Scenes | Edit | Output

The ability to change or (effectively) remove output paths. Other scene settings will follow.

Computers | Select the one you look at

Does what it says

Master

Program | Options | Master

Removal of ‘automatic’ scenes is no longer required, so this checkbox is removed too.

Version 1.33	8 | 06 | 1998

Long filenames

Problems with long filenames for Screamer should be solved

Version 1.32	8 | 05 | 1998

General

Scene list

Extended warnings about output settings

Scenes | Frame Manager

Info in status bar. New progress window.

Scenes | Edit

Log tab. Makes it possible for crashing scenes to check out, which computers (Screamers) are problematic: missing plugins, wrong content directory, …

Version 1.31	1 | 05 | 1998

General

Scene List

Rearranging of the columns.

Scenes | Edit

If not necessary then the scenes will not be reset after editing.

Version 1.30	1 | 05 | 1998

General

ScreamSaver

ScreamSaver won’t start if Master is offline (not in the network). Previously multiple Screamers with a same number would be started.

Scene List

Build in warnings (Red scenes) for:

No ‘image output’ set

Stereoscopic

Program | Options

Streamlining of the different option panels.

Scenes | Edit

Editing of multiple scenes settings at the same time. From now on when you select more then one scene and edit them, all scenes will be changed at once (frame settings are not available) in stead of you editing them one by one.

Scenes | Edit

The ‘Automatic’ tab and the associated settings: Automatic Verification (and its time). For every individual scene can specified whether or not the scene must be verified and how many times.

Scenes | Edit

Automatic Copy (and its computer and directory).

Master

Scene List

Scenes originating from a ‘verify’ (manual or automatic) are now added right above the scene and not at the top of the list. This keeps a better priority order.

Program | Options

Automatic verifying is removed (see Scenes | Edit)

Program | Render

Removed (The master is now always rendering. In the future, individual computers will have the option to be paused)

Computers | Initialize

Removed (This classic style initialize became overruled by the rescan command)

Remote

Program | Options | Remote

Allow automatic update after every command.

Allow automatic update every … minutes

Allow copying of frames when they are rendered

Scenes | Duplicate

Remote duplication of scenes.

Scenes | Edit

Remote editing of scenes.

Version 1.24	12 | 04 | 1998

General

Scenes | Frame Manager

A utility which allow easy deleting, moving, copying of frames. Useful to import (copy) frames to Perception/Hollywood using it’s virtual file system. Or just to keep your disks tidy.

Messages

If a message is onscreen for more than a minute, LightNet takes a decision by itself. (Artificial Intelligence!)

Version 1.23	12 | 04 | 1998

General

Help | Contents

This very help-file gets introduced

Help | What’s New

Removed

View | Scenes, Computers, Events

Removed

View | Options

Moved to Program | Options

Program | Options | Events

Automatic removal of events (which have now different levels) after a specified time (if wanted).

Remote

View | Update

Moved to Program | Update

Version 1.22	08 | 04 | 1998

General

Scene list

Automatic scenes are more grey then others

Computer list

Screamers on local computer are brighter then others

Master

Computers | Name

Removed. Names are now passed through by the remote servers.

Version 1.21	08 | 04 | 1998

General

Screen layout

Redesigned: removal of the separate info-window. Info now sits on the bottom of the list.

Computer  | Crashed

The option to NOT re-render the frames when a computer crashed.

More subtle ScreamSaver (only one screamer started at a time).

Especially useful for multiple processor machines.

Version 1.20	04 | 04 | 1998

General

ScreamSaver

Automatic rendering when system idle for a given time

Master

View | Options | Screamer

Adding of old and new type Lightwave Screamer commands

Version 1.17	31 | 03 | 1998

General

View Options

Added screamer config-directory

New file format and small bug fixing

Improved automatic scenes verification

View | Update

Improved (faster)

Version 1.16	09 | 03 | 1998

Remote

Scene list

Moving of scenes

Version 1.15	08 | 02 | 1998

General

Event-list

More details

Message-window

The 'Ok'-button is now always the default button

Scene list

Support of Stereoscopic Rendering (The 'Red' Scenes)

View | Info

Extended info on scenes under the mouse cursor

Master

Program | Render

Render button at bottom of the screen has been removed

Version 1.14	11 | 11 | 1997

Master

Removal of annoying message popping up on remote rescan.

Remote

Event | Message

Sends a message to the master

Status bar | Last Update

Version 1.13	12 | 10 | 1997

Master

Scene list

Scenes are verified immediately after rendering

Scenes  Edit

Platform on which must be rendered can be selected

Remote

View | Update

No longer an event

Version 1.12	01 | 10 | 1997

General

Some redundant messages removed

Some nasty bugs fixed

Improved scene file browsing

Master

Scene list

Removal of automatic scenes when rendered

Remote

View Update

A little improved

Version 1.11	29 | 09 | 1997

Remote

Scenes | Remove

View | Options

Version 1.10	28 | 09 | 1997

General

Scene list | Computer list | Event-list

Popup menu's | Right mouse button

Scene list

Visualization of verified scenes

Program | Master  |  Remote

Computers | Start

Starts screamer

View | Scenes | Computers | Events

View | Info

Remote

Scenes | Add

Scenes | Verify

Scenes | Select All

Computers | Rescan

Computers | Kill

Computers | Crashed

Version 1.08	18 | 09 | 1997

General

Scenelist

Correct scene moving by drag and drop

Scenes | Verify

Verification of singles

Scenes | Select All

Computers | Crashed

Immediate rendering of crashed frames

Version 1.07	17 | 09 | 1997

General

Render | Frame skipping probably solved.

Computer | Names

Version 1.06	16 | 09 | 1997

General

Scenes |  Add

Multiple select

Scenes | Remove

Warning before removing

Scenes | Verify

Correct date and comment with automatic added scenes

Computers | Rescan

Scroll-through avoidance of remote screamers

Computers | Kill

Effective dying

Help |  What's New

Version 1.05	16 | 09 | 1997

General

Computers | Crashed

Selective crashing

Version 1.00 | 1.04	25 | 08 | 1997

General

Basic stuff and general bug fixing