Is LWSN made to SLOW the renderings ?


Enhanced Low
Now after the bug of Shadow Map Caching that is not
understood by LWSN, which makes you loose up to 15% of your
rendering times, I noticed another interesting bug :

Once on three times I see that when you add several scenes
in the render queue, LWSN crashes at the loading of the second scene…

While everyone knows that to speed up rendering times it's recommended
to separate your animation scene in parts and delete in each of them
the items that are not seen by the camera.

I just did this tuesday evening, created about 8 scenes for 800 frames
in whole to render.
I see this morning that LWSN only rendered 90 frames (the first scene),
then crashed. I lost 24 hours of computing which disturbs all my plans.

It's not the first time that happens.

Anyone knows if there's something that can be done to be sure
that LWSN will render the frames, apart by loading one only whole scene
(which takes much more time to render) ?


obfuscated SDK hacker
I think we've discussed this before, but did you try a different, more robust rendering controller like Spider or LightNet?

Especially LightNet should be a breeze to set up once you got the Layout rendering to work.

Spider has the advantage of handling crashes extremely well...



Enhanced Low
Hi Mike,

well we actually did'nt talk that much about these controllers,
mean that I did'nt know they could be "stronger" than LW.
I only used to think they could provide more options but I'm surprised
that they can handle crashes better than the Layout.

OK I'll try one of them when I have some time left,
though I must say I'm a bit tired of configuring and testing tools,
I for example wasted 2 weeks in july to test Amleto that is supposed
to be quite powerfull and simple, but it's bugged and did not
work on my machine, the developpers could not help me…

ps : what do you mean by "breeze" ?


obfuscated SDK hacker
Hi lasco,
the problem is that Layout can't restart a node if it crashes.
Spider for example does that, can detect crashes and tries to re-start the node a number of times (before it finally gives up). It also checks if frames are actually rendered (and saved...) or not, and if not re-sends them to the nodes.
Of course, if the scene is flaky, then that doesn't help either, but if a node is "shaky" (not enough memory, whatever...), restarts do help.
Also, Spider uses a different way to let the nodes render, which means that lwsn is started more often (so crashes due to, for example, buggy memory management in lwsn, are less likely).

With "breeze" I mean easy :)

What kind of network set-up do you have (OS, server, user management?). Spider might be a decent alternative for you (I've used ot for years and I'm extremely happy with it).



Enhanced Low
Lightwolf said:
What kind of network set-up do you have (OS, server, user management?).

Windows XP Pro
Not sur I can give you much info about the network set-up,
I don't know anything about it, a friend configured it for me few months
ago. What I can say is that I launch every nodes from the same
machine directly in WindowsXP, I don't need any tool to display the screens
of the nodes "in" the main one, it's even more easy because I have a dual monitor display.

About the user management I can't tell you, I don't think there's anything particular
as I work alone there, the network is not even connected to internet (browsing
with a Macinstosh is safer…)

thanx for your help anyway :)


obfuscated SDK hacker
Hi lasco,
I'd say, if you have the spare time, go and try out spider (nay may be get your friend to help you with the user set-up).

Top Bottom