|
Nexus Laguna
Registered User
Join date: 20 Dec 2006
Posts: 40
|
02-27-2007 15:22
Well I did briefly mention my use of llInstantMessage in another thread of this forum but was wondering now if the great scripting community might be of some assistance. You see for my uses llInstantMessage seems perfect .. except it lags ... sometimes really damn badly  . The purpose of the script without going into much detail is to take text entered into a channel and "broadcast" it to other avatars whose keys are stored in a list. Before anyone gets uppity about griefing, all the avatars concerend consent to it. I was thinking of an alternative would be if it was possible to change the object ownership to each avatar in the list and then use llOwnerSay ... but another thread really clearly pointed out that changing the owner of an object in a script was impossible. The point is .. the text cannot be broadcast publicly using llSay or llWhisper .. but llInstantMessage is just too darn slow.... Any ideas anyone?
|
|
Thraxis Epsilon
Registered User
Join date: 31 Aug 2005
Posts: 211
|
02-27-2007 15:31
Threaded llInstantMessage using seperate scripts with linkmessages
|
|
RobbyRacoon Olmstead
Red warrior is hungry!
Join date: 20 Sep 2006
Posts: 1,821
|
02-27-2007 16:01
From: Thraxis Epsilon Threaded llInstantMessage using seperate scripts with linkmessages That is one way, and will work. For complete privacy it might be your best bet, but will require more scripts and prims than possible alternatives. Another would be that the message is broadcast with llSay() or it's ilk, on a private channel like -23424245, and each of the consenting avatars wears an attachment listening on that channel that does llOwnerSay() with whatever text comes in during the listen. You say that you cannot use llSay() but do not specify why. If it is just a privacy issue, the above alternative can be modified to be somewhat more private, but even as it is presented here it won't spam anyone not wearing the attachment. And I would like to make a nitpicky point about the original post.... llInstantMessage is not lagging, in the most commonly used technical sense. It is pausing for two seconds, and while that is very frustrating, is not quite the same as lag. Just dont want newer scripters to form the opinion that llInstantMessage is a major cause of lag, is all 
|
|
Thraxis Epsilon
Registered User
Join date: 31 Aug 2005
Posts: 211
|
02-27-2007 17:15
linkmessages do not require additional prims for a threaded llInstantMessage
|
|
Osgeld Barmy
Registered User
Join date: 22 Mar 2005
Posts: 3,336
|
02-27-2007 22:17
could use llDialog its a 1 second delay
|
|
Mitzpatrick Fitzsimmons
Neurotican Mage
Join date: 20 Sep 2004
Posts: 62
|
Just do this...
02-28-2007 01:25
Sounds like you're looking for a Star Trek type com link thingy...
Here is a descent workaround...
Make a "comm" badge that each of your peeps can wear. You wear a hud that has a prim for each person. Inside that prim is a script to send the message via llEmail() to the corresponding comm UUID of that person.
Your Hud can have just 1 MasterScript for the listen (so as not to overstack listens) and then LinkMessage the prims in the Hud.. instant mass emails simultaneously.
Good Luck!
BTW: Your peeps comm badges can periodically update their UUIDS to a Master HUB-Prim set stationary somewhere that in turn can update your HUD with new UUID's as they change.
_____________________
 I dont know it all...just enough to be "Dangerous!"
|