Welcome to the Second Life Forums Archive

These forums are CLOSED. Please visit the new forums HERE

Weired Unlinking Bug w/ Attachments, blocking progress. Who can I report this to?

Rez Gray
Registered User
Join date: 2 Apr 2007
Posts: 23
07-15-2007 20:53
Bug Reported in Jira: http://jira.secondlife.com/browse/SVC-420

'm working on a parachute. The 'opened chute' assembly is meant to move and compress into the pack (for camera/dork purposes).
The scripts involved movement of child prims, One example is at the bottom of the post.
They would work a few times. "deploying" and "packing", but after a I would try and reattach the pack (for main script debugging),
I will get the error "You can't attach multiple objects to one spot."

If I rez the object, which when attached was all in it's place, but the prims featuring movement scripts will be spread out
so far I can't even relink them without dragging the peices back to the center of mass.
This is not detactable until AFTER detaching to inventory and attempting to re-wear or rez.

I've tried the following...
- Removing llSetLocalRot from attachments
- Removing llSetPos and sticking to llSetScale
It's still happening.

I don't know if this is something I'm doing or SL acting up. But it seems to have started in the last couple of hours, I've only been working with type of attachment movement today.

CODE

//////////////////////////////////////////////
// Field Programmable Pos/Rot/Scale Script //

list deployed =[<4.28949, -0.02610, -0.01436>,<9.00000, 9.00000, 4.61999>,1.000000];
list packed =[<0.12380, -0.02630, -0.01370>,<0.01000, 0.01000, 0.01000>,0.000000];

set(list params)
{
llSetScale((vector)llList2String(params,1)); llSetPos((vector)llList2String(params,0));
llSetAlpha(llList2Integer(params,2),ALL_SIDES);}


default
{on_rez(integer hmm){set(packed);}

link_message(integer sender, integer num, string str, key id){
if(str=="deploy"){set(deployed);}
if(str=="pack"){set(packed);}
}}


This is just really freaking me out to see this after having been hard-core balls to the wall developing and having this pop up. I'll happily send a not-yet broken model to anyone that IMs and asks me. Who can i show this to to see if this is just something I'm doing or a major issue?

Thanks.
Nina Stepford
was lied to by LL
Join date: 26 Mar 2007
Posts: 3,373
07-16-2007 06:50
if it been reported in jira why does it need to be reported again?
its already reported hey.
Elex Dusk
Bunneh
Join date: 19 Oct 2004
Posts: 800
07-16-2007 06:58
Did you read through known annoyances and "gotchas" on the LSL wiki? Also, browse the comments below functions as sometimes "gotcha" information will reside there.

Go through the Scripting Mentor list and see if one of them _might_ be able to help steer you in the right direction for a possible workaround.

When all else fails file a detailed Support Ticket.

As you're presently stalled on your project go through your scripts and add comments/documentation.