PDA

View Full Version : issue configuring LWSN with Matt Gorner's tuto



lasco
08-02-2004, 05:21 AM
Hi,
Just beginning to follow the tuto and already
something I'm not able to do :
setting the targets of both the shorcuts
for the config files, with the "C:\Program Files\LightWave\programs\lightwav.exe -cc:\LightWave\config" line

I've checked ten times my paths and file names
but still Windows does'nt accept this entry,
answering this path is not correct.
(as soon as I delete the "-cc:\LightWave\config" part it works…
I also tried replacing it by "-cc:\Program Files\LightWave\config" but it does not change anything.

(running Windows XP Pro)

please help:(

Lightwolf
08-02-2004, 05:57 AM
Originally posted by lasco
Hi,
Just beginning to follow the tuto and already
something I'm not able to do :
setting the targets of both the shorcuts
for the config files, with the "C:\Program Files\LightWave\programs\lightwav.exe -cc:\LightWave\config" line

Well, that can't work, it should be:

"C:\Program Files\LightWave\programs\lightwav.exe" -cc:\LightWave\config

or

"C:\Program Files\LightWave\programs\lightwav.exe" -c"c:\LightWave\config"

if the path to the configs contains spaces.
Mind you, the other nodes _must_ have the savme c:\lightwave... bla bla bla directory structure in your case.

Cheers,
Mike

lasco
08-02-2004, 06:23 AM
it should be:

"C:\Program Files\LightWave\programs\lightwav.exe" -cc:\LightWave\config


ha yes ! I just noticed this was accepted by Windows but was not sure it would work for
LWSN.

Hem, last question about the second solution you give, you talk about "spaces".
I don't have any except the directory
"Program Files". Has this to be considered
as a space and so should I chose your second solution ?

thanx anyway

Lightwolf
08-02-2004, 06:47 AM
No, the first one is enough.

Think of it this way: Windows tries to break up what you enter according to the following sheme:

command argument1 argument2 argument3 ....

It uses the space to break up your command line.
So, if you're "command", or "argument" contain spaces as well, you have to quote them so that windows sees them as one "entity".

Actually, botj -c"c:\path with spaces" and "-cc:\path with spaces" should work, the former will however make sure that lwsn will actually see "c:\path with spaces", and not "c:\path".

Cheers,
Mike

lasco
08-02-2004, 06:52 AM
ok thank you very much…
I must say I'm really newbie with Windows
(was on Mac before) and start directly
with the management of a 4 nodes based
network for LW…

will see this evenning if it works…

Lightwolf
08-02-2004, 06:58 AM
O.k., you'll have problems with your c:\... path, unless you make sure that all machines in your network have the same content there, including the lw executable and all plugins, config files etc... Mind you, if you add a plugin to Layout on your workstation, you'll have to update the nodes as well !

Cheers,
Mike

Matt
08-02-2004, 08:58 AM
Well, I would've answered that but LightWolf beat me to it! (**** he's quick off the mark!)

Yes, a lot of people have fallen foul to problem because when I wrote the tutorial I didn't need to use the quotes " " because my path name didn't have any spaces.

So when people follow the tutorial to the letter and have spaces in their pathnames it fails.

Think I might update the PDF, it's been asked enough to be a problem I think!

Cheers
Matt

Lightwolf
08-02-2004, 09:05 AM
Originally posted by Matt
Well, I would've answered that but LightWolf beat me to it! (**** he's quick off the mark!)

And ****, ****, **** does the board censor cursing now, darn it ;)

Cheers,
Mike

lasco
08-02-2004, 09:51 AM
Well I finished to configure but at this step
the messages I got are :
- Lightwave command: init
in the nodes (.bat file I opened)

and in Lightwave when I try to initialise Screamer
Net it says no CPU are found (should be 4).

I'm gonna check everything, though
I have one more question, still about these
quote signs "".

In the sn_init.bat file
I followed what Matt wrote but added quotes
at the following line :

cd "c:\Program Files\lightwave\programs\"

(here the directory "lightwave" is actually
the "screamernet" directory in your tuto Matt.)

I added these quotes because of the space
in the name "Program Files", did I do wrong ?
However I'm not sure it does not work because
of that but tell me if it does.

later.

Lightwolf
08-02-2004, 09:55 AM
I'm not too familier with Matt's tutorial, but:
If you get lwsn.exe to start and get a message from the nodes, that path should be fine.

Now you need to check the command path for both LW (prefernces I believe) and the nodes (the ones with ack# and job#), it seems that they are off.

Mind you, every machine has to have a unique # there, and Layout has to be set to a number equal or higher than the largest # in the Screamernet panel.

Cheers,
Mike

lasco
08-02-2004, 09:59 AM
ok sorry I mistaked in the path for ack files
now I just see it's OK, LW recognized my 4 CPUs.

OK I continue and give you some feedback :)

Lightwolf
08-02-2004, 10:09 AM
Originally posted by lasco
OK I continue and give you some feedback :)
Do that, we're here ;)

Cheers,
Mike

lasco
08-02-2004, 10:10 AM
now it works !

hehehe …
well I must say there's something wrong though:
I launched the rendering on 4 machines,
a scene with 150 frames and only
are rendered frames :
3, 28, 71, 111 and 139

But what is strange is that now the process seems
stopped. The nodes display again the message
Lightwave command : wait

The most strange is that I saw in the Network Rendering that things" happened with all the frames, but only these ones are finished.
(of course according to my setting they should
all be written in the same directory and are in no
case hidden on other disks).

Lightwolf
08-02-2004, 10:13 AM
Originally posted by lasco
well I must say there's something wrong though:
I launched the rendering on 4 machines,
a scene with 150 frames and only
are rendered frames :
3, 28, 71, 111 and 139

Were these rendered on the same machine, or on different ones?

Cheers,
Mike

lasco
08-02-2004, 10:15 AM
how can I know that ?

Tom Wood
08-02-2004, 10:19 AM
I guess it was my dumb luck not to make any paths with spaces in them, so I assume I can ignore the quotes stuff.

I have LW 7.5c that came with VT3. I made desktop shortcuts for both Modeler and Layout, and added the -c switch to the config locations. What I have noticed however, is that if I open these programs from any other place than the desktop shortcuts, they will create new configs in either the Documents and Settings folder, the Program Files folder, or the VT3 folder. I have to be careful to delete those configs since they can occasionally confuzzle the programs.

TW

Lightwolf
08-02-2004, 10:20 AM
Originally posted by lasco
how can I know that ?
Watch the render process ;)

Try a scene that takes a couple of seconds per frame (or more) to render.
If some of the nodes render very fast, and other don't, then the fast ones presumably have a problem (can't find their plugins for example).

In the LW 8, you can I think add -l to the lwsn command line to create a log file to check, basically it write all the output into a text file.

-lc:\lwsn_log.txt

will for example create on on c:\, that you can easily openin a text editor to analyze the output of a node.

Cheers,
Mike

lasco
08-02-2004, 10:27 AM
Originally posted by Lightwolf
[B]Watch the render process ;)

well that's what I did,
ok I try again…

(I run LW 7.5 only so can't edit any txt log file)

Lightwolf
08-02-2004, 10:33 AM
Originally posted by lasco
(I run LW 7.5 only so can't edit any txt log file)
Try this:

<your complete lwsn path and arguments withough these angled brackets> >c:\lwsn_log.txt

so, basically add >c:\lwsn_log.txt to the end of the command line. Mind you, you won't be able to see the output of lwsn.exe then...

Cheers,
Mike

lasco
08-02-2004, 10:35 AM
OK I made a second test with the same scene
(very simple one with radiosity, each frame
should take a bit less than 1 minute to render).

I this time only launched 3 nodes
(I excluded the node that is on the same machine
that my workstation)

Now it's already finished, not an image was
written on my HD.

For what I saw during the rendering process :
- in the Network rendering of LW I saw that
all CPUs were working

- in the nodes (.bat files) I saw was displayed the
process of all the frames, one after the other,
but noticed at the end of each frame the rendering time displayed was 0,0 seconds…

Must add that the scene contains no plugs,
nothing special, no procedural, no spreadsheet
or whatever, it's just a set of 4 cubes and spheres I made for the test…


(run LW 7.5 c)

Lightwolf
08-02-2004, 10:38 AM
O.k., let's run this down:

1) do you have the same lw3.cfg on all machines? The content directory in all of these should point to the same directory.
2) Is that content directory visible from all machines?
3) Do all machines have access to a full LW installation and plugins?
4) does the lwext3.cfg on all machines point to the right plugins?

You can open all of the .cfg files in a text editor btw.

Cheers,
Mike

lasco
08-02-2004, 10:58 AM
1) do you have the same lw3.cfg on all machines?

where the hell did I read I had to copy this file on all my nodes ??? No, I only have one lw3.cfg file
(Matt are you there, did I missed something in your tuto ?)




2) Is that content directory visible from all machines?

yes, I'm sure of that



3) Do all machines have access to a full LW installation and plugins?

well yes they all have the "programs" folder
of LW, and should find the configs file
(including the LWEXT3.CFG for the plugs)
in the .bat files I made on each machine,
still according to Matt's tuto…



4) does the lwext3.cfg on all machines point to the right plugins?

again, I have only one lwext3.cfg file on my
main machine, and each machine should point
to this file via the network.
Of course the directory of this file is shared…

PS :
I tried your log stuff.
The result is that at the begining
I have the following lines :
Loading "D:\Content\scenes\myscene.lws"
(which shows me the path is OK)

then :
Error : can't open scene file

then :
Scene loaded

then
Lightwave command : wait

and then :
Lightwave command : render

…followed by descriptions about the
rendering, frame by frame, that looks fine
except that the time for each frame is 0:0 second.

Lightwolf
08-02-2004, 11:02 AM
Originally posted by lasco
PS :
I tried your log stuff.
The result is that at the begining
I have the following lines :
Loading "D:\Content\scenes\myscene.lws"
(which shows me the path is OK)

then :
Error : can't open scene file

then :
Scene loaded

O.k., this is weird, but probably gets us further.

O.k., I didn't know you had a shared directory.

1) All machines can access d:\Content ?
2) d:\content is the content directory in lw3.cfg?

Cheers,
Mike

lasco
08-02-2004, 11:12 AM
1) All machines can access d:\Content

Yes, of course…
via the network, following this path
\\Tour\Content\

("Tour" is the name of the main computer.
It has a "separated" disk, sorry I don't know the
english term, means the same disk is
separated in C: with programs and D: with Content and files)
"Content" is a shared directory.



2) d:\content is the content directory in lw3.cfg?

Yes, in both versions of my lw3.cfg file
(in Matt's tuto you make 2 versions of these
config files, one for working and one for
screamernet)

lasco
08-02-2004, 11:18 AM
mmm… maybe a begining of solution ?
The lw3.cfg file points to d:\Content,
as this file is on the same computer than
the content itself (even if not on the same disk)

while I typed in the .bat files of the nodes the
following line

-c\\Tour\lightwave\config_sn
(while "config_sn" contains the lw3.cfg file)

and also :

-d\\Tour\Content

could there be an issue
between :d\Content and \\Tour\Content

(should not for me but…)

Lightwolf
08-02-2004, 11:18 AM
O.k. I see, so you're using UNC file names for the content (i.e. \\machine\share).

Are you also using UNC for lwsn.exe?

If you are, and the plugins are accessed using UNC as well (in lwext3.cfg), make sure to use double slahes, i.e. instead of
\\computer\share\lw\plugins\plugin.p
it should be
\\\\computer\\share\\lw\\plugins\\plugin.p

But that doesn't seem to be the problem, because LW doesn't even load the scene.

O.k., one last thing. You use the option "-c" to tell LW where the config is. Does the path end with \? It shouldn't. I should be:
lwsn.exe -c\\machine\share\lw\config
instead of
lwsn.exe -c\\machine\share\lw\config\
or
lwsn.exe -c\\machine\share\lw\config\lw3.cfg

the last two won't work.

Cheers,
Mike

BTW, what you mean is a "partition" on your disc.

Lightwolf
08-02-2004, 11:20 AM
Originally posted by lasco
mmm… maybe a begining of solution ?
The lw3.cfg file points to d:\Content,
as this file is on the same computer than
the content itself (even if not on the same disk)

Well, try \\tour\content in all lw3.cfg files, and see if it works then.

I might be that Lw tells the nodes to load

d:\content\scene\test.lws (for example)

so they won't be able to find it.

Cheers,
Mike

lasco
08-02-2004, 11:58 AM
O.k., one last thing. You use the option "-c" to tell LW where the config is. Does the path end with \?
no, it's correct : end by config without \



BTW, what you mean is a "partition" on your disc.
haha ! ****'it it's the same word than in french :)

OK I just tried again after having replaced the
path for the Content in lw3.cfg (both files)
by \\Tour\Content instead of d:\Content,
but the result is the same :(
all the nodes still seem to compute an empty scene…

Lightwolf
08-02-2004, 12:03 PM
Originally posted by lasco
OK I just tried again after having replaced the
path for the Content in lw3.cfg (both files)
by \\Tour\Content instead of d:\Content,
but the result is the same :(
all the nodes still seem to compute an empty scene…
Sh*t, now I'm running out of ideas, sorry to say.

You could try the lwsnController from DStorm ( http://www.dstorm.co.jp/dslib/index-e.html ) on a render only machine to quickly check your configs.

But this to be very weird.

I'm sorry, but I don't really know what else you could do except for re-checking everything :(

Cheers,
Mike

Matt
08-02-2004, 01:36 PM
I dunno, I don't check this site for a day and all 'ell is breakin' loose!!! :)

Lasco, are you using the PDF or watching the video tutorial?

If it looks like it's rendering but you end up with black frames it becuase it can't find the content files, or can't access them (user rights).

I haven't read all of the respones so apologies if I'm repeating something LightWolf has already suggested.

Watch the video tutorial, it's easier to see by understand! (Hopefully!)

It'll be something really daft that's not set / pointing in the wrong place, we'll get there in the end!

If you're still stuck post here again!

Cheers
Matt

Lightwolf
08-02-2004, 01:43 PM
Originally posted by Matt
I haven't read all of the respones so apologies if I'm repeating something LightWolf has already suggested.

Not really, I just suggested just about everything else ;)
I also assume it has to do with the content directory...

Oh well, off for dinner :D

Cheers,
Mike

lasco
08-02-2004, 02:53 PM
Matt + Lightwolf
About the tuto I use the PDF, I don't remember if I downloaded once
the video but I'm afraid I didn't and currently I unfortunately have only
a low connexion… however the PDF is very clear and I usually prefer to browse
within pages like this…

About the path to the content directory it's no surprise actually
that the fact I typed \\Tour\Content instead of D:\Content in the lw3.cfg file
did not change anything. Because if the "D:\etc" solution had be wrong
then I wouldn't have been able even to render with 1 node (the node
on the main machine, which is the only one that loads scenes correctly).

Plus, from the moment every nodes point to the same lw3 and lwext3 files
it should be "everthing or nothing", should'nt it ? Means a mistake in a path
would then affect every nodes…

On the other hand there are enough "things" that work that
shows me that the network runs regularly so I really don't understand what can happpen…

Hope you'll be there tomorrow morning, I'll check everything again and try…

Lightwolf
08-03-2004, 04:02 AM
Originally posted by lasco
About the path to the content directory it's no surprise actually
that the fact I typed \\Tour\Content instead of D:\Content in the lw3.cfg file
did not change anything. Because if the "D:\etc" solution had be wrong
then I wouldn't have been able even to render with 1 node (the node
on the main machine, which is the only one that loads scenes correctly).
Actually, in that case you would have _only_ be able to render with the local machine in the case of d:\... since the other machines don't have access to that, but the local one does.

I hope we can make this work :)

Cheers,
Mike

lasco
08-03-2004, 06:38 AM
ok some more news today :
I found out one of the items that were disturbing.
I changed in the lw3.cfg file the path not only of the Content
directory but also of sub-directories.
ie I replaced D:\Content\scenes by \\tour\Content\scenes,
and so on for objects, images folders etc.

Now I see that the CPUs really work, their rendering
process take around 30 seconds per frame which is
regular on this scene.
But still have an issue with the writing of the images :
only the "main" CPU writes the images rendered
although I can read on other nodes that
they write frames at the correct place (at least that's what
they say) which should be D:\screamer_sn\frame_XXX.png
(where "screamer_sn" is of course a shared folder)

So thinking the issue could here also be due tu a wrong
path I opened my scene file in text editor and replaced
the path of the rendered images by \\Tour\screamer_sn\frame_XXX.png

Unfortunately if now nodes "tell" me that they are writing the
frames at this place they don't do the job…

so gentlemen if you have any idea…

Lightwolf
08-03-2004, 06:46 AM
Originally posted by lasco
so gentlemen if you have any idea…
...well, we're getting closer now ;)

O.k., try this as a start, change the scene to write out .flx files, since they are native to LW and don't require a plugin.
If that works, re-check your lwext3.cfg and make sure the nodes can all access the plugins there.

If not, well, erm, keep trying then... ;)

Cheers,
Mike

lasco
08-03-2004, 06:52 AM
Lightwolf,

I'm in love with U


(ok now let's see how I can help those dam'
nodes to find the images format plugs…)

Lightwolf
08-03-2004, 06:55 AM
Originally posted by lasco
Lightwolf,

I'm in love with U

Lol, I surely do hope this is only platonical ;)

Cheers,
Mike

lasco
08-03-2004, 07:07 AM
be sure my friend :)

now let's keep serious, everything's not finished.
You were right, all frames are correctly written
in .flx format.

So I guess what I should change is the lwext3.cfg file should'nt I ?

Paths there are written with double slashes
so I'm not sure of what I should type.

What for example should I hit instead of :

Class "ImageSaver"
Name "LW_JPEG(.jpg)"
Module "C:\\Program Files\\Lightwave\\Plugins\\Input-Output\\JPEG.p"

I guess I might replace 'C:' by 'Tour' as 'Tour'
is the name of the machine on the network,
but then should I share the folder 'Plugins'
and then have a path looking like this :

"Tour\\Plugins\\Input-Output\\JPEG.p" ???

PS :
I must say I don't understand very well why
from the beginning the regular way does not
work : according to what I've read everywhere
including of course Matt's tuto all my nodes
should point to the config files of the main
machine and then find themselves the path
for the files. Instead of this it seems the only way to make this work is to share my directories one after the other and re-type
every path everywhere… I did not see
anywhere setting LWSN needed all this, though
I can only see for the moment that it's the
only thing that works…

Lightwolf
08-03-2004, 07:22 AM
Ok, since you have the identical Lw installation on all nodes, in C:\Program Files\Lightwave\... , this is where lwext3.cfg should point to.
The simplest way to do it is to open your main LW, remove all plugins and re-add them. Then copy lwext3.cfg over to the other machines. They should then find the plugins if they are on exactly the same location locally.

I only mentioned the double \\ if you use UNC file names for the plugins as well, but it seems you don't.

Let me just as an example tell you how I set up LW over, we do have it installed in a server though.

LW is installed on:
\\gadget-hq\lightwave\lw75
In there I have a directory called
\\gadget-hq\lightwave\lw75\config
where I store all the config files.
The plugins are in
\\gadget-hq\lightwave\lw75\plugins

But, I start my working copy of LW from that directory as well, so it shares the config with the render nodes, and I don't have to worry about UNC file names in the config, LW handles that for me.

This is how I start lightwave:
\\gadget-hq\lightwave\lw75\programs\lightwav.exe -c\\gadget-hq\lightwave\lw75\config
-> telling it to use the config on the server
Nodes would be started like this:
\\gadget-hq\lightwave\lw75\programs\lwsn.exe -c\\gadget-hq\lightwave\lw75\config ...other arguments

This way I never get confused by C:, d: and whatever driver letters, because _everything_ is UNC.

Cheers,
Mike

...as a side note:
In Lightwav.exe and Modeler.exe you can specify where you want the lw#.cfg/lwm#.cfg to be saved (-c), and, optionally, lwext#.cfg (-p) , which only stores the plugin path.
Since we only have one installation directory, but multiple users, I call LW like this:
\\gadget-hq\lightwave\lw75\programs\lightwav.exe -c\\gadget-hq\lightwave\lw75\config\%username% -p
\\gadget-hq\lightwave\lw75\config

This stores the plugin config (lwext#.cfg) in \\gadget-hq\lightwave\lw75\config, but my personal configs in \\gadget-hq\lightwave\lw75\config\lightwolf (if lightwolf is my login name, you'll have to create the directory manually though).

...Sorry for the long explanation, but someone might find this to be useful ;)

lasco
08-03-2004, 08:07 AM
now I'm not sure we understand well each other…



[B]Ok, since you have the identical Lw installation on all nodes, in C:\Program Files\Lightwave\... , this is where lwext3.cfg should point to.
I DO NOT have the same LW installation on all
nodes. LW is installed on my main machine,
only the "programs" directory of LW is
copied on each node. Plugins directory is not.



They should then find the plugins if they are on exactly the same location locally.
They're not, precisely !
I followed the tuto IN ORDER not to have to
copy all the plug'ins on each node…



I only mentioned the double \\ if you use UNC file names for the plugins as well, but it seems you don't.
I know that, I just talked about these \\ above
because I saw they were used in the paths
of the lwext3.cfg file… So just wondered
how I had to manage them exactly if I had
to change parts of these paths.





This is how I start lightwave:
\\gadget-hq\lightwave\lw75\programs\lightwav.exe -c\\gadget-hq\lightwave\lw75\config
-> telling it to use the config on the server
Nodes would be started like this:
\\gadget-hq\lightwave\lw75\programs\lwsn.exe -c\\gadget-hq\lightwave\lw75\config ...other arguments

Now this is really where we misunderstand…
I am exactly trying to do the same thing than
you, which means (tell me if I'm wrong) that
you don't need to copy all your plugs on your nodes do you ?
Where it does not work is that whether you
start LW (main) or nodes, it points to
a 'config' folder all right ? Just at the end
of your own paths…
I have the same settings.
BUT in this 'config' folders there are the
files lw3.cfg and lwext3.cfg, still agree ?
And the fact is that my nodes don't understand
what is writtend in the lwext3.cfg file !!!!
Until this morning it was the same issue
but with the lw3.cfg file so nodes could'nt find
the Content. I solved it changing the paths.


Just tell me for example what YOU have
as paths in your lwext3.cfg ?

(The 'general' issue is that while just organizing
files like you say and like Matt says it should
work and one should'nt have to modify
paths in config files… Why does it happen
to me I don't know but that's it).

Lightwolf
08-03-2004, 08:14 AM
Originally posted by lasco
now I'm not sure we understand well each other…
...
Just tell me for example what YOU have
as paths in your lwext3.cfg ?

(The 'general' issue is that while just organizing
files like you say and like Matt says it should
work and one should'nt have to modify
paths in config files… Why does it happen
to me I don't know but that's it).
Well, it should work like Matt said if all machines can reach the same files using the same path, so, if you install LW on, hm, drive l:\ , and connect that to all other machines as l:\, it will work.

This is a line out of my config:


{ Entry
Class "AnimLoaderHandler"
Name "QuickTime"
Module "\\\\Gadget-hq\\Lightwave\\LW75\\Plugins\\Input-output\\Qttools.p"
}

Can you show me your .bat files? May be copy&paste one of them, and then we'll see and find out.

I'll fix it for you so you don't need any local copy of LW, but this will only work if you have an lwext#.cfg that uses UNC.

Cheers,
Mike

Matt
08-03-2004, 08:35 AM
Okay, let's start over! Lasco, can you answer these please:


1) Where is your main LightWave installed?

2) Where have you put all your Content files?

3) Where did you put the config file folders?

4) Where have you put the 'Command' folder?


Cheers
Matt

lasco
08-03-2004, 09:06 AM
OK thanx to you guys,
I appreciate your help…
Now one after the other :)

Lightwolf >

OK the line you gave me looks much like
I think I should hit too, I'm gonna try this
right now. According to all I did until now
I guessed it should work with something
like this…

mm… hard to give you immediatly a .bat file,
I'm here on a Mac (for internet) that is not connected to the network so should burn
a CD. However I'll do this if necessary but
let me know what do you need :
- the .bat file when "not working" ? Which is
actually few paths according to Matt's tuto

or
- what is displayed by the .bat file when the
node works (all instructions on rendering process) - in that second case I have to
re-save it with a log file using the way you
gave me yesterday…


Now Matt >
1/ Main Lightwave is installed on HD "C:",
in the directory "Program Files" (default Windows directory) on a machine called "Tour" on the network. I copied on all other machines (nodes) just the "programs" directory of LW, directly on each node, on HD that are also called "C:"
So I have in "Tour" this :
C:\Program Files\Lightwave\[full LW installation, including "config" and "config_sn" folders, as well as sn_init.bat file for the case I
use this machine itself as a node]

And on other machines :
C:\Program Files\lightwave\programs
and also
C:\Program Files\lightwave\sn_init1.bat


2/ Content is on another partition of my HD
on my main machine, called D:
Which gives us :
D:\Content


3/ As I said, my config folders ('config' and 'config_sn') are both located in the folder
"Lightwave" on my main machine.
C:\Program Files\Lightwave\config
and
C\Program Files\Lightwave\config_sn
Of course there are copies of lw3.cfg and
lwext3.cfg in both 'config' and 'config_sn'
directories, as well as I followed exactly
your tip to switch the paths with Layout
shortcuts depending on the working use
or the screamernet rendering use.

4/ The command folder is also in the "Lightwave" folder of my main machine.

Now I must say as long as was making tests
I at the end finished by sharing almost all
my directories of the main machine.
Which means that are shared :
Lightwave directory (as 'lightwave' on the network)
Content directory
config and config_sn directories
command directory
and even the rendering directory where
frames should be written (and which is
located on disk D: of my main machine.

Note : the partition of the disk is made so that
I have a small partition for OS and programs (C)
and a large one for files (Content and renderings).
Nodes are also partitioned disks but
I think these partitions are not concerned,
I at present only used for them the
disks "C" to copy my LW programs directory,
that's all.

Lightwolf
08-03-2004, 09:18 AM
...I meant your sc_init1.bat file.

If your lwext#.cfg contains all UNC paths to the plugins with double slashes, and you use somthing like:



LWSN.exe -2 -d\\Tour\content -c\\tour\lightwave\config
\\tour\lightwave\command\job# \\tour\lightwave\command\ack#

should all one line

then it should work.

You could also just use this:


\\tour\lightwave\programs\LWSN.exe -2 -d\\Tour\content
-c\\tour\lightwave\config \\tour\lightwave\command\job# \\tour\lightwave\command\ack#

should all one line

Cheers,
Mike

lasco
08-03-2004, 09:23 AM
OK as I thought… it works now, perfectly.

I just changed a line in the lwext3.cfg file,
according to the line Lightwolf just gave
and now it's OK.

I typed for the plugin PNG image saver

\\\\Tour\\lightwave\\Plugins…etc.

Instead of
C:\\Program Files\\Lightwave\\Plugins…etc.

(where 'lightwave' is the network name
of the directory 'Lightwave' on my main machine)

I'm not sure now I understand why only this
way works but that's it.
The fact is that from the moment
the disks with programs on all machines
are called 'C:' I could expect that LWSN
would not be able to make the difference
between them while it is able to now
that I changed all my paths using
a 'network' naming and shared folders names.
But the strange thing is that Matt you did not
seem to point this in your tuto while
it's very often that by default HD are
called 'C:'
So what or when did I something wrong that
forced me to change all these paths ???

Lightwolf
08-03-2004, 09:30 AM
Originally posted by lasco
OK as I thought… it works now, perfectly.

I just changed a line in the lwext3.cfg file,
according to the line Lightwolf just gave
and now it's OK.

I typed for the plugin PNG image saver

\\\\Tour\\lightwave\\Plugins…etc.

Instead of
C:\\Program Files\\Lightwave\\Plugins…etc.


Great, good to see you got it to work.

The thing is, C:\ is always (well, in 99% of all cases) the drive letter for the starting partition of a system, and if I try to open something from C:\, it will always be from the _local_ disk. And since you don't have the plugins there, lwsn can't find them.

I can't remember Matt's tute, but did he have LW on c:\ or on another drive?

Cheers,
Mike

lasco
08-03-2004, 09:30 AM
If your lwext#.cfg contains all UNC paths to the plugins with double slashes, and you use somthing like:

code:
LWSN.exe -2 -d\\Tour\content -c\\tour\lightwave\config \\tour\lightwave\command\job# \\tour\lightwave\command\ack#


You pointed right… but just in the 'wrong' sense.
I mean that from the beginning my .bat file was
written exactly the way you just typed here,
BUT my lwext3.cfg was NOT made of
UNC paths… I have to change them all now.

But - question for Matt, maybe - why Matt
did'nt you talk about this UNC stuff for
config files in you tuto ?
Am I the first one meeting this issue ?

lasco
08-03-2004, 09:33 AM
I can't remember Matt's tute, but did he have LW on c:\ or on another drive?


Precisely !
Matt's tuto, even if very clear, does not
talk about any C:\ or whatever DRIVE,
he only uses what you call UNC paths,
just like your 'gadget' machine or my 'Tour' one,
but on the other hand he does not mention
the fact that config files themselfs do not
'update' automatically according to this kind of paths !!

Lightwolf
08-03-2004, 09:40 AM
Originally posted by lasco
Matt's tuto, even if very clear, does not
talk about any C:\ or whatever DRIVE,
he only uses what you call UNC paths,
just like your 'gadget' machine or my 'Tour' one,
but on the other hand he does not mention
the fact that config files themselfs do not
'update' automatically according to this kind of paths !!
Well, in that case give him a good whipping when he comes into this thread the next time ;)

But it is good to see you got it to work, and I'm sure Matt will use the information we gathered next time he updates his Tutorial (if he does, right Matt?).

Cheers,
Mike - who's never seen a thread with that many \\'s ;)

lasco
08-03-2004, 09:46 AM
Well, in that case give him a good whipping when he comes into this thread the next time

be sure we won't ever see him anymore here,
shame on him must be terrific now and
I guess he just read these last posts and
is now crying beyond his computer…

Lightwolf
08-03-2004, 10:02 AM
Originally posted by lasco
be sure we won't ever see him anymore here,
shame on him must be terrific now and
I guess he just read these last posts and
is now crying beyond his computer…
lasco, you forgot the :) and ;) as well as the :p and :D

I'm sure Matt isn't that easily scared off ;), he's :cool:

Cheers,
Mike

lasco
08-03-2004, 10:06 AM
ok just kidding,

now folks let me thank you very much for your help.
If this can help you to see how helpfull it was
I'll just tell you that I decided to switch from Mac
to PC more than 3 months ago, precisely to
be able to render on a network (yes it's possible
on Mac too but not exactly for the same price, hem…).

I started to buy pieces of PC in may,
it took me more than 1 month to get everything
+ had many troubles with the hardware question.
Then took weeks to built everything waiting
for friends that could help me,
and at the end I just spend the last 10 days
fighting with the nodes to try to make
Amleto work (Amleto that is supposed
to configure 'simply' the LWSN rendering…).
Although Amleto's developpers were kind
and did their best their soft did not stop
bugging and of course they were assuming
that MY network and MY OS was having issues…

And now, after 2 days here at LAST everything
works fine…fffiuuuuu !
Thanx to you Lightwolf and Matt,
I was almost to give up with 3D, sincerly ;)

Lightwolf
08-03-2004, 10:13 AM
Originally posted by lasco
Thanx to you Lightwolf and Matt,
I was almost to give up with 3D, sincerly ;)
Hehe, you're welcome.
And don't worry, doing decent 3D ius much harder than setting up screamernet, and takes even more time to learn, but I'm sure you know that ;)

Now, as a next step, you could try Spider or LightNet to free your LW license from the hard work of controlling the nodes ;)

Cheers,
Mike

lasco
08-03-2004, 10:25 AM
And don't worry, doing decent 3D ius much harder than setting up screamernet, and takes even more time to learn, but I'm sure you know that ;)

I know, I know :)
Though there was emmergency on rendering times, especiallly because I see more and more
big companies (well I say 'big', relatively to me
since I'm alone) challenging me, that have
much more machines and equipements…
it was really time to speed up and not
staying with my dual 800 Mhz G4 while
the others have render farms with tens of Ghz
hehe…

Matt
08-03-2004, 12:59 PM
I did talk about UNC naming! Page 4!

I didn't talk about UNC naming within the LWEXT.cfg file because you don't need to open up your LWEXT.cfg file and edit anything! (Although you can do it that way if you want!)

Page 11 of the tutorial tells you to load your 'ScreamerNet' version of LightWave (so you're editing the config files inside config_sn) and scan your plugins/lscripts using a network aware path (page 12) this saves the location of your plugins in LWEXT.cfg (inside config_sn) using UNC pathnames and not hardcoded ones.

However you MUST scan from 'Entire Network' down otherwise the pathnames are resolved to local hardcoded ones! (It does say that in the tutorial too!)

Then when the nodes are told to use the config files in:

\\YOUR_COMPUTER_NAME\ScreamerNet\config_sn
(if you shared your main LW folder as screamernet)

They will use the LWEXT.cfg file that has all the plugins stored with the UNC (network-aware) naming.

Hope that makes sense!

Matt

lasco
08-04-2004, 03:26 AM
Shame on me Matt,
I missed that point…

Now I must say that yesterday I was really finding
strange I did not see it regarding the quality
of your tuto…
Just did not zoom at the screenshot on this
page 11 of the PDF !

Apologizes man, if I had look more accurately
this thread would not had even exist
(must say also I often miss points on manuals
due to the english language I don't speak perfectly)

thanx 1000 times for all this help.

Matt
08-04-2004, 04:59 AM
No worries, glad you got it working!

:)