exe program sitting on each node.
When a node is activated, it looks for its first job file. However, there won??™t be any there
until you initialize ScreamerNet in the Network Rendering panel, but it??™s pointless initializing
it until you??™ve activated all the nodes!
When you run ScreamerNet, a node does two things: It looks for job files and sticks its
hand in the air, saying ???I??™m here, I??™m over here!???Well, not quite, but it??™s waiting to be
found by the controller part of ScreamerNet. This is where some confusion lies with
ScreamerNet. Nodes complain they can??™t find job files when they??™re first run. This is perfectly
normal. Bearing this in mind, double-click each render batch file to activate it.You??™ll
see output like that shown in Figure 15.48.
Figure 15.48 The current directory is identified.
The first thing the node should tell you is where it??™s looking for the content files. If this is
wrong or if it comes up with an error, close it down and check the script for errors in the
pathnames.
The next thing you should see is the node complaining that it can??™t open a job file (see
Figure 15.
Pages:
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792