View source for Content Creation/Scripting User Group/Transcripts/2011 07 25

== List of Speakers ==
{|
|<font color=#b5005a><b>Acheron Gloom</b></font>
|-
|<font color=#0000b5><b>flexi campfire</b></font>
|-
|<font color=#5a00b5><b>Leonel Iceghost</b></font>
|-
|<font color=#b500b5><b>Liisa Runo</b></font>
|-
|<font color=#005ab5><b>NeoBokrug Elytis</b></font>
|-
|}

== Transcript ==
[08:58] <font color=#b5005a><b>Acheron Gloom</b><nowiki>: Heya Kelly</nowiki></font>

[08:58] <font color=#808080><b>Kallista Arliss (kallista.destiny)</b><nowiki>: Lail Kelly</nowiki></font>

[08:58] <font color=#808080><b>Kaluura (kaluura.boa)</b><nowiki>: Hi!</nowiki></font>

[08:59] <font color=#808080><b>Kallista Arliss (kallista.destiny)</b><nowiki>: Hail*</nowiki></font>

[08:59] <font color=#808080><b>tehKellz (kelly.linden)</b><nowiki>: good morning</nowiki></font>

[08:59] <font color=#808080><b>!< Sofa</b><nowiki>: Click the seat to change your animation or position.</nowiki></font>

[08:59] <font color=#808080><b>Nal (nalates.urriah)</b><nowiki>: Morning</nowiki></font>

[09:00] <font color=#808080><b>Ima Mechanique (nielarcher)</b><nowiki>: good afternoon ;-)</nowiki></font>

[09:00] <font color=#808080><b>Kaluura (kaluura.boa)</b><nowiki>: Evening...</nowiki></font>

[09:00] <font color=#b500b5><b>Liisa Runo</b><nowiki>: hi everybody</nowiki></font>

[09:01] <font color=#808080><b>Kaluura (kaluura.boa)</b><nowiki>: So... News about the Script Maintenance Project?</nowiki></font>

[09:02] <font color=#808080><b>tehKellz (kelly.linden)</b><nowiki>: Found a couple of bugs on aditi that I fixed on Friday. Depending on how the rest of testing goes it is *possible* it could get an RC this week, but it would be a stretch I think.</nowiki></font>

[09:04] <font color=#808080><b>tehKellz (kelly.linden)</b><nowiki>: Well, we should get started I suppose. :)</nowiki></font>

[09:04] <font color=#808080><b>tehKellz (kelly.linden)</b><nowiki>: News first.</nowiki></font>

[09:05] <font color=#808080><b>tehKellz (kelly.linden)</b><nowiki>: The Magnum RC has been looking really good performance wise.</nowiki></font>

[09:05] <font color=#808080><b>Kallista Arliss (kallista.destiny)</b><nowiki>: Yes, only the diehard 'the system is lagging' people have been complining.</nowiki></font>

[09:06] <font color=#808080><b>Kallista Arliss (kallista.destiny)</b><nowiki>: The people who cry lag when fps drops below 44.9</nowiki></font>

[09:06] <font color=#808080><b>tehKellz (kelly.linden)</b><nowiki>: I shared this graph on Friday, I think. I have a couple more data points today but it looks pretty much the same.</nowiki></font>

[09:06] <font color=#b5005a><b>Acheron Gloom</b><nowiki>: Would you be able to throw me a copy of the texture, Kelly?</nowiki></font>

[09:07] <font color=#b5005a><b>Acheron Gloom</b><nowiki>: Thanks.</nowiki></font>

[09:09] <font color=#808080><b>tehKellz (kelly.linden)</b><nowiki>: I *think* that the fixes on Magnum are up for promotion this week, though we havn't yet reviewed data from the weekend.</nowiki></font>

[09:09] <font color=#808080><b>Kallista Arliss (kallista.destiny)</b><nowiki>: So the over agressive caching id produce better perormance</nowiki></font>

[09:11] <font color=#808080><b>tehKellz (kelly.linden)</b><nowiki>: The difference there is in the range of 0.05 - 0.1 SimFPS, so maybe a touch for some regions.</nowiki></font>

[09:12] <font color=#808080><b>tehKellz (kelly.linden)</b><nowiki>: To be clear for everyone, I believe Kallista is referring to that 2days fix w/ crasher, where the crash was caused by overly aggressive caching of some data.</nowiki></font>

[09:12] <font color=#808080><b>tehKellz (kelly.linden)</b><nowiki>: And how those points are slightly higher than the 'new fix, no crasher' point.</nowiki></font>

[09:13] <font color=#808080><b>Kallista Arliss (kallista.destiny)</b><nowiki>: the twp orange dits at the tip</nowiki></font>

[09:13] <font color=#b5005a><b>Acheron Gloom</b><nowiki>: Ah</nowiki></font>

[09:13] <font color=#808080><b>tehKellz (kelly.linden)</b><nowiki>: Yes.</nowiki></font>

[09:13] <font color=#808080><b>Kallista Arliss (kallista.destiny)</b><nowiki>: which show that you were on the right track</nowiki></font>

[09:13] <font color=#808080><b>tehKellz (kelly.linden)</b><nowiki>: The dataset is really small as well, which can cloud things.</nowiki></font>

[09:14] <font color=#808080><b>Kallista Arliss (kallista.destiny)</b><nowiki>: Welome OO</nowiki></font>

[09:15] <font color=#808080><b>tehKellz (kelly.linden)</b><nowiki>: Next news is the Scripting Maintenance project which is on Aditi as DRTSIM-72</nowiki></font>

[09:16] <font color=#808080><b>tehKellz (kelly.linden)</b><nowiki>: I've run through the features before but briefly: SET_POS_LOCAL, link version of sit target and camera related functions, http-in can return html (with restrictions), you can set a lower memory ceiling on mono scripts and more.</nowiki></font>

[09:16] <font color=#808080><b>Kaluura (kaluura.boa)</b><nowiki>: (Lot of good things in there...)</nowiki></font>

[09:17] <font color=#808080><b>tehKellz (kelly.linden)</b><nowiki>: It had some bugs on aditi last week, and the release pipe may be a tad full so I'm not quite sure when it will get to an RC.</nowiki></font>

[09:18] <font color=#5a00b5><b>Leonel Iceghost</b><nowiki>: is memory ceiling going to help sim performance in any way?</nowiki></font>

[09:18] <font color=#808080><b>Kaluura (kaluura.boa)</b><nowiki>: It should...</nowiki></font>

[09:19] <font color=#808080><b>tehKellz (kelly.linden)</b><nowiki>: Right now, no.</nowiki></font>

[09:20] <font color=#808080><b>Ima Mechanique (nielarcher)</b><nowiki>: does ceiling report correctly for object script memory?</nowiki></font>

[09:20] <font color=#808080><b>Ima Mechanique (nielarcher)</b><nowiki>: or is it still 64KB?</nowiki></font>

[09:21] <font color=#808080><b>tehKellz (kelly.linden)</b><nowiki>: If you set a mono script to a ceiling of 10k then it will stack-heap when you go past 10k total memory used (including assembly) and it will report 10k in all memory reporting tools</nowiki></font>

[09:21] <font color=#808080><b>tehKellz (kelly.linden)</b><nowiki>: It will not report 64KB</nowiki></font>

[09:22] <font color=#808080><b>Ima Mechanique (nielarcher)</b><nowiki>: excellent</nowiki></font>

[09:22] <font color=#808080><b>Ima Mechanique (nielarcher)</b><nowiki>: a step towards getting people to be more efficient ;-)</nowiki></font>

[09:22] <font color=#5a00b5><b>Leonel Iceghost</b><nowiki>: any plans to make a script able to restart a crashed script?</nowiki></font>

[09:22] <font color=#808080><b>tehKellz (kelly.linden)</b><nowiki>: That is trickier than I would like. I have looked at it in the past.</nowiki></font>

[09:23] <font color=#5a00b5><b>Leonel Iceghost</b><nowiki>: really? how does the viewer restart it</nowiki></font>

[09:23] <font color=#808080><b>Kaluura (kaluura.boa)</b><nowiki>: Yeah... If we do it easily with the viewer... why not by script?</nowiki></font>

[09:23] <font color=#808080><b>tehKellz (kelly.linden)</b><nowiki>: magic, at least it seems that way sometimes.</nowiki></font>

[09:23] <font color=#5a00b5><b>Leonel Iceghost</b><nowiki>: lol cool</nowiki></font>

[09:24] <font color=#b5005a><b>Acheron Gloom</b><nowiki>: haha</nowiki></font>

[09:24] <font color=#808080><b>tehKellz (kelly.linden)</b><nowiki>: it has to do with the state of the scripting system when a script is running vs. when we are processing messages from viewers</nowiki></font>

[09:25] <font color=#808080><b>tehKellz (kelly.linden)</b><nowiki>: In the latter case it is easy to move things around completely and get things running, in the former it is a bit of a trick.</nowiki></font>

[09:25] <font color=#b500b5><b>Liisa Runo</b><nowiki>: scripts being able to restart crashed scripts can also become a problem, some people might just reset the crashed script instead of actually fixing the bug that cause the crash</nowiki></font>

[09:25] <font color=#808080><b>tehKellz (kelly.linden)</b><nowiki>: There is a jira for it, I'm sure I've seen it.</nowiki></font>

[09:25] <font color=#808080><b>tehKellz (kelly.linden)</b><nowiki>: We should make sure it is in the SCR project if it isn't.</nowiki></font>

[09:25] <font color=#5a00b5><b>Leonel Iceghost</b><nowiki>: Liisa, at least to recover stack head collisions</nowiki></font>

[09:26] <font color=#808080><b>Ima Mechanique (nielarcher)</b><nowiki>: Kelly, is there any docs on what's in DRTSIM-72?</nowiki></font>

[09:26] <font color=#b500b5><b>Liisa Runo</b><nowiki>: and what cause the collision if not bug?</nowiki></font>

[09:26] <font color=#808080><b>tehKellz (kelly.linden)</b><nowiki>: I wonder if a script property 'reset on stack/heap' would be more efficient.</nowiki></font>

[09:26] <font color=#808080><b>tehKellz (kelly.linden)</b><nowiki>: though then that is even worse for the case liisa mentions. possible constant crash loop</nowiki></font>

[09:27] <font color=#b5005a><b>Acheron Gloom</b><nowiki>: Somewhat off-topic, but does the llGetObjectDetails for script time return the same as the EM panel does now?</nowiki></font>

[09:27] <font color=#808080><b>Ima Mechanique (nielarcher)</b><nowiki>: thanks Kaluura</nowiki></font>

[09:27] <font color=#808080><b>tehKellz (kelly.linden)</b><nowiki>: Acheron yes.</nowiki></font>

[09:28] <font color=#808080><b>tehKellz (kelly.linden)</b><nowiki>: os Avg/frame over the last 30 minutes or life of the object, whichever is shorter.</nowiki></font>

[09:28] <font color=#5a00b5><b>Leonel Iceghost</b><nowiki>: it still triggers an error in debug channel, if the script has a bug everyone will notice it</nowiki></font>

[09:29] <font color=#808080><b>tehKellz (kelly.linden)</b><nowiki>: True.</nowiki></font>

[09:29] <font color=#b500b5><b>Liisa Runo</b><nowiki>: nope, many ppl will not notice it : because of this NON-viewer bug: </nowiki>https://jira.secondlife.com/browse/VWR-26016</font>

[09:29] <font color=#0000b5><b>flexi campfire</b><nowiki>: [#VWR-26016] Script error particle not displaying above agent when script error comes from a HUD</nowiki></font>

[09:29] <font color=#808080><b>tehKellz (kelly.linden)</b><nowiki>: Though I kinda am starting to think showing script errors for objects you don't own is not that useful most times.</nowiki></font>

[09:29] <font color=#808080><b>tehKellz (kelly.linden)</b><nowiki>: That is just for huds though?</nowiki></font>

[09:29] <font color=#808080><b>Kaluura (kaluura.boa)</b><nowiki>: Not really...</nowiki></font>

[09:30] <font color=#808080><b>tehKellz (kelly.linden)</b><nowiki>: All right.</nowiki></font>

[09:30] <font color=#b500b5><b>Liisa Runo</b><nowiki>: it is usefull in some cases, mmaybe it should have a toggle</nowiki></font>

[09:30] <font color=#808080><b>tehKellz (kelly.linden)</b><nowiki>: Yeah. probably better as a viewer side filter / option.</nowiki></font>

[09:31] <font color=#b5005a><b>Acheron Gloom</b><nowiki>: I agree to that, Kelly.</nowiki></font>

[09:31] <font color=#808080><b>tehKellz (kelly.linden)</b><nowiki>: It is open discussion day and I'm out of news. Floor is open.</nowiki></font>

[09:31] <font color=#b5005a><b>Acheron Gloom</b><nowiki>: If you don't have another point to move onto, can you give a little bit of information about any other changes to script time measurement? As I think there were some. For example I've noticed the measurement of firing guns being at least double what they used to be, and sometimes way higher than double.</nowiki></font>

[09:31] <font color=#b5005a><b>Acheron Gloom</b><nowiki>: :3</nowiki></font>

[09:32] <font color=#b5005a><b>Acheron Gloom</b><nowiki>: I was waiting to say that.</nowiki></font>

[09:32] <font color=#808080><b>tehKellz (kelly.linden)</b><nowiki>: Sure.</nowiki></font>

[09:32] <font color=#b500b5><b>Liisa Runo</b><nowiki>: but what ever path we take, we must make sure that ppl cannot ignore their own errors, we dont want bugged stuff wasting resources get more popular</nowiki></font>

[09:32] <font color=#808080><b>tehKellz (kelly.linden)</b><nowiki>: We are talking about the time reported to EMs in the region/estate debug top scripts panel?</nowiki></font>

[09:32] <font color=#808080><b>tehKellz (kelly.linden)</b><nowiki>: I agree Liisa</nowiki></font>

[09:33] <font color=#808080><b>tehKellz (kelly.linden)</b><nowiki>: So the previous times reported were broken. Flat broken. It is hard to convey how broken.</nowiki></font>

[09:34] <font color=#808080><b>tehKellz (kelly.linden)</b><nowiki>: There were many, many little bugs and some straight up faulty logic.</nowiki></font>

[09:34] <font color=#808080><b>tehKellz (kelly.linden)</b><nowiki>: We were attempting to track an average time used with a single float.</nowiki></font>

[09:34] <font color=#808080><b>Kallista Arliss (kallista.destiny)</b><nowiki>: nit just broken but BROKEN?</nowiki></font>

[09:34] <font color=#808080><b>tehKellz (kelly.linden)</b><nowiki>: The old times reported were BROKEN.</nowiki></font>

[09:35] <font color=#808080><b>tehKellz (kelly.linden)</b><nowiki>: So every time a script ran we would do: avg = avg * 0.8 + time_run * 0.2; This is a bad attempt at keeping 5 run times as average.</nowiki></font>

[09:36] <font color=#808080><b>tehKellz (kelly.linden)</b><nowiki>: Sometimes we would reset to 0, sometimes we would just do avg *= 0.8.</nowiki></font>

[09:36] <font color=#808080><b>tehKellz (kelly.linden)</b><nowiki>: And many times we would just do nothing to the number even if we should.</nowiki></font>

[09:36] <font color=#808080><b>tehKellz (kelly.linden)</b><nowiki>: The end result was a number that was only meaningful in relation to the other numbers, and even then barely due to the other bugs.</nowiki></font>

[09:37] <font color=#808080><b>Kallista Arliss (kallista.destiny)</b><nowiki>: bork bork bork</nowiki></font>

[09:37] <font color=#808080><b>tehKellz (kelly.linden)</b><nowiki>: It was possible for a script to accidentally get a really high or really low number and be poisoned for a long time</nowiki></font>

[09:37] <font color=#808080><b>tehKellz (kelly.linden)</b><nowiki>: So we ripped out that system. It is gone.</nowiki></font>

[09:40] <font color=#808080><b>Qie (qie.niangao)</b><nowiki>: (when ready for a totally ifferent topic) ... It seems wrong for Mesh to be elevating prim equivalence because an object contains a script, when in fact *every* object containing a script (mesh or not) has the same effect on the sim. Really, scripts need to be a separately metered resource, not confounded with prim count. So then, whenever scripts do get metered, the Mesh special case will need backing-out.</nowiki></font>

[09:40] <font color=#808080><b>tehKellz (kelly.linden)</b><nowiki>: Now we track # frames and total run time for ~30 mins. We do some fudging with buckets to keep a rolling average. And we filled in the gaps missing in the old system.</nowiki></font>

[09:40] <font color=#808080><b>tehKellz (kelly.linden)</b><nowiki>: In particular there was a case where the overhead of an idle script was ignored because we did a 'return' instead of a 'break' in a loop - where the only thing after the loop was time tracking.</nowiki></font>

[09:41] <font color=#808080><b>Kallista Arliss (kallista.destiny)</b><nowiki>: oO</nowiki></font>

[09:41] <font color=#808080><b>tehKellz (kelly.linden)</b><nowiki>: So now it looks like idle scripts got a spike in time. I depated this a bit since it would be easy to re-add the old bug and make idle scripts appear timeless as they had before.</nowiki></font>

[09:41] <font color=#808080><b>tehKellz (kelly.linden)</b><nowiki>: But that isn't accurate or true and never was. It was just a timing bug.</nowiki></font>

[09:42] <font color=#808080><b>tehKellz (kelly.linden)</b><nowiki>: or rather, a bug in the timing stats.</nowiki></font>

[09:42] <font color=#b5005a><b>Acheron Gloom</b><nowiki> nods</nowiki></font>

[09:42] <font color=#808080><b>tehKellz (kelly.linden)</b><nowiki>: There were other bugs as well, but that was probably the most noticed.</nowiki></font>

[09:42] <font color=#b5005a><b>Acheron Gloom</b><nowiki>: Yeah, I've definitely noticed some odd things myself. Like in something that runs an event every 0.05 seconds (timer or control, maybe), if you slept half of that time the script time would be /a lot/ lower than if you didn't sleep.</nowiki></font>

[09:43] <font color=#b5005a><b>Acheron Gloom</b><nowiki>: Even though, you would think that the sleep wouldn't make a difference either way really.</nowiki></font>

[09:43] <font color=#808080><b>Kallista Arliss (kallista.destiny)</b><nowiki>: But shouldnl ilde scripts be timeless , in an event dirven system no events should = no time</nowiki></font>

[09:43] <font color=#808080><b>tehKellz (kelly.linden)</b><nowiki>: If a script is sleeping it is using much less sim time than if it is just idle.</nowiki></font>

[09:43] <font color=#b5005a><b>Acheron Gloom</b><nowiki>: Well, even enough to drop from say 0.02 to 0.001 or something for the object?</nowiki></font>

[09:43] <font color=#5a00b5><b>Leonel Iceghost</b><nowiki>: Kelly, you need to call the scheduller after every script event, and external events.. it is insane to put it in a loop</nowiki></font>

[09:44] <font color=#808080><b>tehKellz (kelly.linden)</b><nowiki>: Kallista: while LSL is event driven, the system that runs it is not as event driven, and all scripts are considered active and checked for pending events to add to their queues based on the handlers in the script.</nowiki></font>

[09:46] <font color=#808080><b>Kallista Arliss (kallista.destiny)</b><nowiki>: Even if there are no events of the type for which it has handlers?</nowiki></font>

[09:46] <font color=#b5005a><b>Acheron Gloom</b><nowiki>: After everything else is said (just kinda raising my hand here), I also was wondering about lowering our scripts memory limit some more. I believe you said that it wouldn't increase sim-performance to do so at the moment, but I assume it will in the future then? Would it be a large difference?</nowiki></font>

[09:47] <font color=#808080><b>tehKellz (kelly.linden)</b><nowiki>: Kallista: in that case the check is as quick as comparing 2 integers with bitwise &.</nowiki></font>

[09:48] <font color=#808080><b>Kaluura (kaluura.boa)</b><nowiki>: No much room for improvement in here...</nowiki></font>

[09:48] <font color=#808080><b>Kaluura (kaluura.boa)</b><nowiki>: Not*</nowiki></font>

[09:48] <font color=#808080><b>Kallista Arliss (kallista.destiny)</b><nowiki>: Well somewheres there is 2 µsec per script of overhead</nowiki></font>

[09:48] <font color=#808080><b>tehKellz (kelly.linden)</b><nowiki>: 2usec is very small.</nowiki></font>

[09:50] <font color=#808080><b>tehKellz (kelly.linden)</b><nowiki>: Ok, lets switch topics.</nowiki></font>

[09:50] <font color=#5a00b5><b>Leonel Iceghost</b><nowiki>: if a script has a timer in the next 60 min, it should put itself in the queue and don't waste ony single cycle more.. and then you call the scheduler again when there is a collision with the object, or chat, or user imput..</nowiki></font>

[09:50] <font color=#5a00b5><b>Leonel Iceghost</b><nowiki>: that way if the script is doing nothing it will be trully there idle just using memory</nowiki></font>

[09:52] <font color=#808080><b>tehKellz (kelly.linden)</b><nowiki>: Qie: In a large sense you are correct. For now what we have is 'PrimEquivalence' which mashes all the resources into a single number. If we pull scripts out to their own resource in some way then we can remove the script effect on the simulation cost.</nowiki></font>

[09:52] <font color=#808080><b>Qie (qie.niangao)</b><nowiki>: okay, as long as you're comfortable with that. just wanted to be sure you'd been consulted.</nowiki></font>

[09:52] <font color=#808080><b>tehKellz (kelly.linden)</b><nowiki>: That would have a cost-lowering effect which is easy to do in the future, on the other hand a cost raising effect (such as adding script cost later) is much more difficult.</nowiki></font>

[09:52] <font color=#808080><b>tehKellz (kelly.linden)</b><nowiki>: I think I wrote both the equation and the code to implement it Qie.</nowiki></font>

[09:53] <font color=#808080><b>Qie (qie.niangao)</b><nowiki>: cool.</nowiki></font>

[09:53] <font color=#b5005a><b>Acheron Gloom</b><nowiki>: Haha</nowiki></font>

[09:53] <font color=#808080><b>Ima Mechanique (nielarcher)</b><nowiki>: adding it is easy, getting people to accept it is another story ;-)</nowiki></font>

[09:53] <font color=#808080><b>Kallista Arliss (kallista.destiny)</b><nowiki>: That is indeed 'In the loop'</nowiki></font>

[09:55] <font color=#808080><b>tehKellz (kelly.linden)</b><nowiki>: The benefit of lowering the memory limit on scripts is truth in reporting. Because mono scripts can use up-to their cap if we limit memory on a non-per-script scale (per parcel, per region, etc) then we have to use their ceiling.</nowiki></font>

[09:55] <font color=#b5005a><b>Acheron Gloom</b><nowiki>: Ah</nowiki></font>

[09:55] <font color=#808080><b>tehKellz (kelly.linden)</b><nowiki>: If we do that and even a door script uses 64k in mono no one will use mono.</nowiki></font>

[09:56] <font color=#b5005a><b>Acheron Gloom</b><nowiki> nods, "That makes sense."</nowiki></font>

[09:56] <font color=#b5005a><b>Acheron Gloom</b><nowiki>: this will report correctly for llGetObjectDetails, too, right?</nowiki></font>

[09:56] <font color=#808080><b>tehKellz (kelly.linden)</b><nowiki>: Yes</nowiki></font>

[09:56] <font color=#b5005a><b>Acheron Gloom</b><nowiki>: Great to hear.</nowiki></font>

[09:56] <font color=#808080><b>Ima Mechanique (nielarcher)</b><nowiki>: is there a minimum ceiling for mono scripts?</nowiki></font>

[09:56] <font color=#808080><b>Kallista Arliss (kallista.destiny)</b><nowiki>: There are regions that have script+momory counters at the entry point, the spam or even eject prople with too many sctipts/much memory</nowiki></font>

[09:56] <font color=#808080><b>tehKellz (kelly.linden)</b><nowiki>: the minimum is the size of the script at the time the function is called.</nowiki></font>

[09:57] <font color=#808080><b>tehKellz (kelly.linden)</b><nowiki>: (which is just a convenience so you don't immediately crash your own script. Use 1/0 if you need that.)</nowiki></font>

[09:57] <font color=#808080><b>Ima Mechanique (nielarcher)</b><nowiki>: hmm, let me rephrase that. CAn you request the size to the byte or is it blocks? i.e. 128 byte increments?</nowiki></font>

[09:57] <font color=#808080><b>tehKellz (kelly.linden)</b><nowiki>: The resolution is down to the byte.</nowiki></font>

[09:57] <font color=#005ab5><b>NeoBokrug Elytis</b><nowiki>: I know you're busy with other projects currently, just wanted to get this question in. Probably been asked a thousand times -- but any chances for a new type: arrays? :3</nowiki></font>

[09:57] <font color=#808080><b>Kallista Arliss (kallista.destiny)</b><nowiki>: Ima, I've heard 4K as an absoult minmum</nowiki></font>

[09:58] <font color=#808080><b>tehKellz (kelly.linden)</b><nowiki>: There is almost no chance of arrays in LSL.</nowiki></font>

[09:58] <font color=#808080><b>Ima Mechanique (nielarcher)</b><nowiki>: great. I have plenty I can shrink</nowiki></font>

[09:58] <font color=#808080><b>tehKellz (kelly.linden)</b><nowiki>: Hello World takes just under 4k.</nowiki></font>

[09:58] <font color=#808080><b>Ima Mechanique (nielarcher)</b><nowiki>: okay. good to know</nowiki></font>

[09:58] <font color=#b5005a><b>Acheron Gloom</b><nowiki>: So uh, any chance of an llRezObjectFast with a one-frame delay, and just more aggerssive throttling :3?</nowiki></font>

[09:58] <font color=#b5005a><b>Acheron Gloom</b><nowiki>: I doubt it, but *shrugs*.</nowiki></font>

[09:59] <font color=#808080><b>tehKellz (kelly.linden)</b><nowiki>: I haven't seen a jira for that suggestion yet Acheron.</nowiki></font>

[09:59] <font color=#b5005a><b>Acheron Gloom</b><nowiki>: I'll make one then.</nowiki></font>

[09:59] <font color=#b5005a><b>Acheron Gloom</b><nowiki>: I just figured it wouldn't be liked.</nowiki></font>

[10:00] <font color=#b5005a><b>Acheron Gloom</b><nowiki>: Function delays are in frames right, pretty much?</nowiki></font>

[10:01] <font color=#808080><b>tehKellz (kelly.linden)</b><nowiki>: <shrug> the idea of not sleeping scripts with function calls is liked. If we can find a throttle that would work and still allow it to be useful it is a possibility. I'd also like to strip the engergy component from it.</nowiki></font>

[10:01] <font color=#b5005a><b>Acheron Gloom</b><nowiki>: Since I assume it worsk the same as llSleep, and I believe llSleep can only sleep to the nearest frame</nowiki></font>

[10:01] <font color=#808080><b>tehKellz (kelly.linden)</b><nowiki>: function delays are in seconds.</nowiki></font>

[10:01] <font color=#808080><b>tehKellz (kelly.linden)</b><nowiki>: A sleep is at a minimum a frame</nowiki></font>

[10:01] <font color=#b5005a><b>Acheron Gloom</b><nowiki>: hmm</nowiki></font>

[10:01] <font color=#b5005a><b>Acheron Gloom</b><nowiki>: is it precise/accurate though?</nowiki></font>

[10:02] <font color=#b5005a><b>Acheron Gloom</b><nowiki>: so a 0.03 sleep would actually sleep 0.03 instead of 0.022 (1 frame) or 0.044</nowiki></font>

[10:02] <font color=#808080><b>tehKellz (kelly.linden)</b><nowiki>: This goes back to the scheduling. When your script next gets checked to run, if it is past the set time it will run.</nowiki></font>

[10:02] <font color=#808080><b>Nal (nalates.urriah)</b><nowiki>: Does that min change with low FPS?</nowiki></font>

[10:02] <font color=#b5005a><b>Acheron Gloom</b><nowiki>: Alright.</nowiki></font>

[10:02] <font color=#b5005a><b>Acheron Gloom</b><nowiki>: Thanks so much for all your answers, Kelly. :)</nowiki></font>

[10:02] <font color=#808080><b>tehKellz (kelly.linden)</b><nowiki>: (and we adjust the time to next to account for however far we missed the actual time it should have happened)</nowiki></font>

[10:02] <font color=#808080><b>tehKellz (kelly.linden)</b><nowiki>: Thanks everyone for coming!</nowiki></font>

[10:03] <font color=#808080><b>Qie (qie.niangao)</b><nowiki>: thanks Kelly</nowiki></font>

[10:03] <font color=#808080><b>Nal (nalates.urriah)</b><nowiki>: Thx Kelly</nowiki></font>

[10:03] <font color=#808080><b>Ima Mechanique (nielarcher)</b><nowiki>: thanks for having us ;-)</nowiki></font>

[10:03] <font color=#b500b5><b>Liisa Runo</b><nowiki>: thanks everybody</nowiki></font>

[10:03] <font color=#808080><b>Kallista Arliss (kallista.destiny)</b><nowiki>: thank you</nowiki></font>