Welcome to the Second Life Forums Archive

These forums are CLOSED. Please visit the new forums HERE

llSetPosAndRot()
Mark Busch
DarkLife Developer
Join date: 8 Apr 2003
Posts: 442
10-17-2003 18:45
I would like to see this function and don't say "DUHH" to quick. I know you can do the same thing with llSetPos and llSetRot seperatly, but the problem is that most of the time you can actually SEE it first rotating and then moving (or the other way around). so much for animating objects :(
Darwin Appleby
I Was Beaten With Satan
Join date: 14 Mar 2003
Posts: 2,779
10-17-2003 18:48
Well for now you can have two seperate scripts in the same object...
_____________________
Touche.
Mark Busch
DarkLife Developer
Join date: 8 Apr 2003
Posts: 442
10-17-2003 19:13
and you are telling me you can time those scripts at the right moment so you won't see that the object does reposition and rotation serially? I don't think that will work very well...
Ama Omega
Lost Wanderer
Join date: 11 Dec 2002
Posts: 1,770
10-17-2003 19:22
Sure, easy - takes three scripts.

Master script:
CODE
default
{
   state_entry()
   {
      llMessageLinked(llGetLinkNumber(),1,"MOVE!","");
   }
}


Script to rotate or move.
CODE
default
{
   link_message(integer link, integer num, string mes, key id)
   {
      if (mes == "MOVE!")
      {
         llSetRot(......); or llSetPos(....);
      }
   }
}


Put all three scripts on there, trigger that linked message when you wanna get going and bam, done. If you want to pass in some numbers to it remember that you can use the key variable to hold string data. I usually pass in the command in the key and some comma seperated values in the string variable.

Good luck.
_____________________
--
010000010110110101100001001000000100111101101101011001010110011101100001
--
Christopher Omega
Oxymoron
Join date: 28 Mar 2003
Posts: 1,828
10-18-2003 00:37
From: someone
Originally posted by Ama Omega
Sure, easy - takes three scripts.

Master script:
CODE
default
{
   state_entry()
   {
      llMessageLinked(llGetLinkNumber(),1,"MOVE!","");
   }
}


I wouldnt use llGetLinkNumber() so readily :D , 'cause it returns 0 for objects not linked, passing 0 to llMessageLinked() isnt always accurate.

CODE

integer getMyNum() //Gets sender to pass to llMessageLinked to successfully message to self.
{
    integer linkNum = llGetLinkNumber();
    if(linkNum > 0) return linkNum;
    else return LINK_SET;
}


using getMyNum() rather then llGetLinkNumber() would work slightly more reliably.
_____________________
October 3rd is the Day Against DRM (Digital Restrictions Management), learn more at http://www.defectivebydesign.org/what_is_drm
Ama Omega
Lost Wanderer
Join date: 11 Dec 2002
Posts: 1,770
10-18-2003 01:51
From: someone
using getMyNum() rather then llGetLinkNumber() would work slightly more reliably.

Hm really? Have any examples? If you have an unlinked object and want two scripts on it to talk to each other, then link 0 is where to send the messages.... I've yet to have it work unreliably, but 99% of my work is with linked objects. Seems interesting that it would be 'unreliable'.
_____________________
--
010000010110110101100001001000000100111101101101011001010110011101100001
--
Christopher Omega
Oxymoron
Join date: 28 Mar 2003
Posts: 1,828
10-18-2003 01:59
Argh... I think you may be right, I just tested using 0, and it works fine... I had thought... way back in beta and early release it didnt work so well. They must've fixed it.
_____________________
October 3rd is the Day Against DRM (Digital Restrictions Management), learn more at http://www.defectivebydesign.org/what_is_drm