Are you avoiding the plugin because it doesn’t work for you? If so, the solution Bealobo offered (who, incidentally, works for Next Limit), is something they’ve come across before that has cured the problems with the plugin.
If you can get the plugin working then replacing objects internally using LWs native tools, or DStorm’s tools is unnecessary.
Personally I’ve had no luck with object replacement in LW and never figured out why. One contributor in the LW thread of the realflow forum had it working using the durfrep plugin, renaming the referencenull object the NL plugin creates (although I dont know what to) and it all worked for him.
So a mixture of half workaround and half “normal” procedure may be the solution. If you haven’t tried it, give it a go.
If you have, then I dont know what to suggest I’m afraid and I dont know why the object replacement plugin in LW doesn’t seem to work. Perhaps someone’s had some joy with it.
Current issues with the NL plugins for LW include, most notably, not being able to F10 a sequence and the mesh hold it’s texture from frame to frame. However, this seems to be problematic to track down. I, for one, have two 32 bit machines, one of which the plugin works fine on using both nodes and layer textures, and the other system refuses to even recognise the .p file as a set of plugins (hence the .NET framework suggestion I guess). I also have a 64 bit system where the 64 bit plugin works, and the 32 bit plugin doesn’t.
Very odd.
Shaun