Current problem is with an MP5 that easily fits within the 1M size, as soon as you attach a scope it will always fail to link whichever part is last in the link order, no matter which part.
You can however unlink the entire thing, drag select it and it will link fine. It will also link if you select it in a specific order, however I can't replicate this with scripted linking which will always fail on the last piece.
I can in fact squash the entire thing into something that fits in a 0.1x0.1x0.1 box and it still won't link due to distance problems. Here's the code if you want to see how,
CODE
default
{
state_entry()
{
integer x = llGetNumberOfPrims();
integer y;
llSetPos(<211.070, 29.802, 50.161>); // Central pos
for (y = 2; y <= x; y++)
{
llOwnerSay((string)y);
llSetLinkPrimitiveParams(y, [PRIM_POSITION, <0, 0, 0>]);
}
}
}
Andrew Linden's description of the link system ( /111/62/11883/1.html ) says...
The astute may have noticed that there is a slight order-of-operations failure for collections of clumps of very small primitives where the clumps rhemselves are spaced such that they just barely link, and each clump barely links itself. For such a scenario the link will succeed or fail depending on the order in which the primitives are selected. This is a known problem, however all of these objects sparse (mostly empty space) and barely fit into the set of objects that we wanted to support for linking.
However it is also pointed out there that: * All prims, no matter how small, with centers within 1 meter of each other are linkable. So does the 1M minimum not really mean anything if you make an "unsupported" shape?
For an idea, the white box is a 1M cube: