Child Object Not Moving

llSetPos(llGetLocalPos() + <5,0,0>);

This works in a touch_start() event but I for some reason cannot get this work in a link_message() event. The link_message() event is being triggered because I confirmed this with an llOwnerSay(). Any ideas why I can't get the child object to move?

Here's my exact code straight from the child prim.

default
{
	link_message(integer sender_num, integer num, string str, key id)
	{
		llOwnerSay("Message Link Heard");
		
		list mlist = llParseString2List(str, [" "], []);
		
		llSetPos(llGetLocalPos() + <5,0,0>);
	}
}

Is it in an attachment? If so you're gonna hafta wait for 1.7 (next week hopefully )

It's not an attachment.

I pasted your code into a default box, made another default box, did a messagelinked to linknumber 2 in the touch event - the child prim with your code in it did move.

This worked in regular grid and preview grid.

How many prims are you trying to move in the object?

Trying to move the child prim out of the 2 that were linked. So a Parent and Child, 2 prim linkage.

Okk, here is the script again but now including the parent script. I toned this script down to basics and still having the issue.

PARENT SCRIPT

default
{
    state_entry()
    {
        llListen(1, "", llGetOwner(), "");
    }

    listen(integer channel, string name, key id, string message)
    {
        llMessageLinked(2, 0, "test", NULL_KEY);
    }
}

CHILD SCRIPT

default
{
    link_message(integer sender_num, integer num, string str, key id)
    {
        llOwnerSay("Message Link Heard");
        llSetPos(llGetLocalPos() + <5,0,0>);
    }
}

This is a 2 prim linkage. Give it a try please. I was thinking it might be bugged or something so I tried recreating it and still same issue. The child prim acknowledged it heard the link message with the "Message Link Heard" message but llSetPos() did not take effect.

Just type "/1 test" and see what happens.

I had a friend of mine try something out of the ordinary. She sat on it then did a "/1 test" and IT WORKED. She stood up from it and tried again and did NOT work again. What the heck? lol

It's the link distance constraints. The max link distance is inversely proportionate to the size of the largest side of all the prims in the set. Course link distance code is buggy so there are ways to cheat (which i won't mention).

When the changed link distance is greater then the max then it silently fails.

Link distance constraints? Weird. My prim link was not even that far apart. I left little gap between the two. And this even happend with the two prims being default wood cubes. Hrm. Doesn't make too much sense to me but I take this is a known bug from what you are saying?

I heard link distance constraint was less than 10m. Your script lets it move a child prim 5m once. It is natural it cannot work but once.

But it doesn't even move once. The only time it works is if someone sits on the linked object.

Let me also add that when sitting on it I can move it farther than 10m. That is executing the script more than two times.

Kurshie, sorry, I told that without making sure.

There might be another constraint refered to the distance.
I tested it by the default cube and found it was at most 4.7m that the child prim could move by llSetPos. It might be different due to the size. So try to find the limit movement of your own prim.

Hi, I am told that if you are moving a child prim you just use llSetPos(<0,0,0>; As the prim always refers to the "adult" prim.