|
|
|
I noticed that two of the IMs were the same length, so added a "!" to one, and tested using:
///////////////////////////////////////////// default { touch_start(integer num) { llSetObjectName("PCS Monitor"); llInstantMessage(llGetOwner(),"Sending..."); llInstantMessage(llGetOwner(),"08-26T20:17:PCSAttachment Scanner:Chorazin Allen has scripted attachments\n"); llInstantMessage(llGetOwner(),"08-26T20:17:PCS Attachment Scanner:Chorazin Allen has scripted attachments\n"); llInstantMessage(llGetOwner(),"08-26T20:17:PCS Attachment Scanner:Chorazin Allen has scripted attachments!\n"); llInstantMessage(llGetOwner(),"Sent"); } } On Second Life 1.20.15 (92456) [no Mono available] Observe: Sometimes all IMs are received, but more often than not [in 15 out of 20 attempts] , the 4th IM (the one with the "!") is NOT received: [14:46] PCS Monitor: Sending... [14:46] PCS Monitor: 08-26T20:17:PCS Attachment Scanner:Chorazin Allen has scripted attachments [14:46] PCS Monitor: Sent Second Life 1.20.15 (92456) Jul 18 2008 10:58:42 (Second Life Release) You are at 231294.3, 242977.0, 39.6 in Misery located at sim8054.agni.lindenlab.com (8.10.149.121:13000) CPU: Intel Core 2 Series Processor (2327 MHz) Tested on some more regions, all running Second Life Server 1.24.1.94908:
Gothlanth, Deitide, Sandbox Island Extension, Sandbox Wanderton For each of these, the 3rd IM was sometimes missing. The script seems to succeed/fail in "waves"... several tries without error, followed by several tries where an IM is missed. Example: Sandbox Wanderton Similar behaviour observed, running Second Life 1.21.0 (94985) Aug 22 2008 19:05:00 (Second Life Public Nightly)
Sandbox Wanderton: 4th IM now missing It does indeed fail, both LSL and Mono compiled versions on the nightly build Second Life 1.21.0 (94985)
I notice that the server's IM throttling makes the messages appear at a nice regular interval, when the middle one is missed there is a pause of the correct length but the message is "eaten" by the server. This is a strange bug. We've been running this script, to scan for stringlength:
// (Objectname : "PCS Monitor") test += "x"; } -The message doesn't arrive when stringlength + objectname is 85 or 86 on the sims we tried. Second Life 1.20.15 (92456) Jul 18 2008 10:58:42 (Second Life Release) Uh oh, I just TPed to two 1.23 sims, and it reproduces there too.
Second Life 1.20.15 (92456) Jul 18 2008 10:58:42 (Second Life Release) Second Life 1.20.15 (92456) Jul 18 2008 10:58:42 (Second Life Release) Mea culpa... I admit I didn't bother doing a check for pre-existing reports because I didn't think it'd have been allowed to live if it had been in the code for any length of time, plus first checks (now disproved) suggested it was ok for 1.23
Gothlauth just got loaded with Second Life Server 1.24.2.95174 so I retested... now it's the last of the group of three that vanishes (was the second)
Second Life Beta Server 1.24.5.96115
It looks like it's fixed I tried this just now and it didn't fail for me, either in lsl or Mono.
edited - maybe it's the relationship between the 1.24 server code and the 1.20 client code?? edited - I did get it to repo but only the first time I ran it. Also if I took the object into inventory when it was rerezzed after a period of time it would repo but only once. I used : default } Second Life 1.21.1 (95603) Sep 3 2008 10:09:14 (Second Life Release Candidate) So I guess
I would LOVE to find out what was causing this one. http://wiki.secondlife.com/wiki/Release_Notes/Second_Life_Beta_Server/1.26
It's really fixed. Yep, tested and verified fixed in Second Life Beta Server 1.26.0.116361
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
 |
|
Bug
Resolved
Critical
Instant Messages of certain lengths (object name + IM text) are not delivered with 1.24.1
In IM# 2 it should read ...PCSAtt
In IM# 3 it should read PCS<one space>Att
In IM# 4 it should read PCS<two spaces>Att
The three strings are identical otherwise...
Thanks to Gellan Glenelg for noticing...