Quote -
 That been said, and despite bad vibes everywhere, I'm still willing to check out what it might be (if anybody asks me to). Whatever it is, it is sure to crop up again any time, Faveral is a skilled merchant, with quite some flight hours, so I don't think he did any stupid thing.

It's not meant this way. For sure.

We are here to find out where the bugs are. But it's sometimes not easy to find out just by a description.

The background is: Each Poser node has a Value(). So one could be sure if it is a node, a Value() has to be there (a node without the possibility to change things isn't useful). If it is really not there, it's best to find out why. This could be a "trick" done by the creator of this nodeset, as odf said, or simply a piece of code somewhere deep inside the Exporter with a side effect. Making sure it's not a simple thing while inspecting the nodes in question is the easiest way to find out what happens. This is the reason why bagginsbill asked. Your answer didn't help mutch, but this is not your fault. It's just - because.

If you could find out what the exporter "says" before the error occurs may help to find a startpoint to search for the reason.

---