lw9 and lwsn -3

[turi]

I am using "lwsn -3" under lw9. We use qube to handle the networking part of the jobs. But I am running in to a problem with a particular user. This user has some custom plugins and she wants to use them. So I told her to modify the LW9EXT confing file to include absolute plugin path to her plugins. Now each node in the farm has the same share mounted with same share name. So typically each node should look at the plugin config and load. But it is not.

I tried to isolate this problem by going to one particular node and ran lwsn -3 on command prompt and even though all the share paths are available, it still complains that it cannot load the plugin. Any help or suggestions?

P.S: All these machines are running 64-bit windows.

[johna]

Did you manage to correct the plugin issue?

[Sensei]

Maybe plugin is in 32 bit version, and you're using LWSN 64 bit?

Did you open LW9EXT.cfg file in text editor and verified that all paths to plugins are in UNC format \\server\path\ ??

[abdelkarim]

what does that mean LWSN ???

[Dexter2999]

LWSN=LightWave ScreamerNet

And this thread was posted over four years ago...Holy Resurection! Batman!

[johna]

All plugins are 64bit as far as I know, weird thing is some work, some don't
Tried local paths as well as shared paths for plugin folder, same result.
When rendering on one of the worker machines directly in LW, plug-ins work fine.
Is there a way to tell lwsn to autoscan plug-ins folder?