Submitted by Joe Justice on Sun, 03/18/2012 - 20:56
Submitted by Joe Justice on Sat, 03/12/2011 - 22:24
LightNet: Watcher is a separate application used for sending commands to the server, managing the server and viewing it's state. It is configured on the Watcher tab in LightNet: Cloud.
Submitted by Joe Justice on Sat, 03/12/2011 - 20:07
No known bugs at this time.
Submitted by Joe Justice on Sat, 03/12/2011 - 20:06
Submitted by Joe Justice on Sat, 03/12/2011 - 20:05
Submitted by Joe Justice on Sat, 03/12/2011 - 19:58
Submitted by Joe Justice on Sat, 03/12/2011 - 19:54
Frequently asked questions.
Submitted by Joe Justice on Sat, 03/12/2011 - 19:52
Submitted by Joe Justice on Sat, 03/12/2011 - 19:50
I have had many email conversation with people that try to relate LightNet: Cloud to how other render farm controllers work. This is very problematic because LightNet: Cloud works differently.
I really hate to front-load a how-to with a lot of background information. I'm sure you're looking for a nice recipe style step by step experience. Unfortunately, there are a few things I need to lay out so that I'm sure everyone is on the same page.
Submitted by Joe Justice on Sat, 03/12/2011 - 19:46
For an onsite scene, the content information is simply a path, you do not need to package and zip the content for onsite rendering. However, this does mean that all onsite PCs must have access to this path. The easiest way to accomplish this is to have a mapped network drive to the content's location. Full network paths with also work. So \\FileServer\CDrive\MyContent will work or Z:\MyContent will work as long as Z:\ is mapped to \\FileServer\CDrive
