Jump to content

Trying out PRIM_LINK_TARGET and getting errors


You are about to reply to a thread that has been inactive for 4065 days.

Please take a moment to consider if this thread is worth bumping.

Recommended Posts

I am trying out PRIM_LINK_TARGET and getting the rule error...

llSetPrimitiveParams error running rule #3 (PRIM_LINK_TARGET): bounds error; 40 is not in (-4, 0).

with the line...

llSetLinkPrimitiveParams(R_HAND, [PRIM_POSITION, rwrist_pos, PRIM_LINK_TARGET, R_WRIST, PRIM_POSITION, rwrist_pos]);

Is this a bug or am just not understanding the correct usage of PRIM_LINK_TARGET? My Variable R_WRIST is 40.

 

Link to comment
Share on other sites

Yeah, I've just tested it in the Blue Steel sandbox.

default{    state_entry()    {       llSetLinkPrimitiveParamsFast(       1,[PRIM_COLOR,ALL_SIDES,<1.0,0.0,0.0>,1.0,       PRIM_LINK_TARGET,2,PRIM_COLOR,ALL_SIDES,<0.0,1.0,0.0>,1.0,       PRIM_LINK_TARGET,3,PRIM_COLOR,ALL_SIDES,<0.0,0.0,1.0>,1.0]);    }}

 works as expected if it's in the root prim but gives that error in a child prim.

Link to comment
Share on other sites

For that matter, calling llSetLinkPrimitiveParamsFast() on a prim that doesn't exist (such as

llSetLinkPrimitiveParamsFast(90, [PRIM_COLOR, -1, <1,1,1>, 1.]);

 

on a single prim object) silently fails, and doesn't generate an error. I don't think PRIM_LINK_TARGET should throw a bounds error at all, just silently fail if the prim it's targeting isn't there.

Link to comment
Share on other sites

You are about to reply to a thread that has been inactive for 4065 days.

Please take a moment to consider if this thread is worth bumping.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share

×
×
  • Create New...