Node Item Motion Stability

[CF01]

Does anyone else have a lot of stability issues with DPont's Node Item Motion plugin? I'm running it on Win XP 32 and LW 9.6.

[evenflcw]

Seems pretty stable to me. The motion modifier plugin itself is likely not the culprit, but rather a particular node. Most nodes were never meant to be running under a motion modifier and out of render-context.

What nodes might you be using?

[CF01]

DP item info, DP particle info seem to be common ones. I haven't tried it without them.

[Sensei]

Item Info and Particle Info have a lot outputs, so specify one that are causing troubles..

Motion Modifier plug-in class probably has not so often called Init/Cleanup call-backs (I would expect them to be called once after pressing F9 in LWINIT_RENDER mode, then second time after finished rendering in LWINIT_PREVIEW mode, and kept that way for entire work) which these nodes might use to initialize data, such as particle system identifier (LWPSysID).

[CF01]

Here's a sample file.

I created the node flow with the motion modifier turned off.

I closed the node editor window and turned on the motion modifier.

If I tried to set this up with the Modifier turned on it would crash.

If I try to open the node editor again I get an immediate crash. It doesn't matter if the modifier is turned on or off.

[3DGFXStudios]

Does not crash here. Do you have the last version of DPnodes. If you update the node's you need to first remove them and than install the new one's. If you overwrite the old version it doesn't work for some reason.

[CF01]

Yes, I am using the latest version of his plugins. I'm trying this on my notebook. In a couple days I'll try it on my desktop system.

[Sensei]

Do you have more than one LW version installed? Like both v9.6 and v9.3 and/or 32 bit/64 bit? Did you use -c parameter to redirect config directory for each Layout/Modeler per version?

[dpont]

With this kind of setup,
a Item Info ID input for a Motion NE input,
I would rather use the "ID" mode in Particle Info node,
this is also the only way to get an Object
parented to one unique particle (unique ID)
when emitter is animated.

Denis.

[CF01]

I'm only using the one version of LW on this machine, although I did try 9.6.1 but removed it when it didn't help. I tried clearing my configs and that didn't work. I deleted all my plugins and reinstalled them, and that didn't work. Windows has all it's updates and I have tried a couple different graphics drivers. Nothing seems to work. I'm just going to have to wait until I can get back to my workstation to see if things work there.

Thanks for the tip Denis. It doesn't seem to crash when I do it that way. I'm still curious thou as to why the sample I posted works for other people but is so unstable on my machine.

Thanks for the help everyone.

[olivier MICHON]

CF01, your scenes also crashes here on LW 9.6-32-bit but not on the 64-bit version, using the same build of DPKit (12.20.09).

[dpont]

This is a special case in Particle Info node used in Item Motion node editor in layout preview and opened Node Editor, Item Info node output an undefined ID.
As I said above, the ID mode is better for this kind of setup, but this has been fixed today in Particle Info node for the x32 version of DP Kit.

Denis.

[olivier MICHON]

Thanks for the fix, Denis :thumbsup: