Difference between revisions of "User:Hidenori Glushenko/Sandbox"

From Second Life Wiki
Jump to: navigation, search
(Removing all content from page)
Line 1: Line 1:
 +
Transcript of [[User:_Linden| Linden]]'s office hours:
  
 +
{|
 +
<span id="chat1"></span>
 +
|- style="vertical-align:top;color:#FF9900;background-color:#FCFCFC;"
 +
| [[#chat1|[8:01]]] 
 +
| Babbage&nbsp;Linden:
 +
| style="white-space:normal;"|hi nick
 +
<span id="chat2"></span>
 +
|- style="vertical-align:top;color:#FF9900;background-color:#FCFCFC;"
 +
| [8:01] 
 +
| Babbage&nbsp;Linden:
 +
| style="white-space:normal;"|hi becky
 +
<span id="chat3"></span>
 +
|- style="vertical-align:top;color:#66FF33;background-color:#F0F0F0;"
 +
| [8:01] 
 +
| Nock&nbsp;Forager:
 +
| style="white-space:normal;"|Hi Babbaage
 +
<span id="chat4"></span>
 +
|- style="vertical-align:top;color:#FF9900;background-color:#FCFCFC;"
 +
| [8:01] 
 +
| Babbage&nbsp;Linden:
 +
| style="white-space:normal;"|nock, sorry
 +
<span id="chat5"></span>
 +
|- style="vertical-align:top;color:#66FF33;background-color:#F0F0F0;"
 +
| [8:01] 
 +
| Nock&nbsp;Forager:
 +
| style="white-space:normal;"|NP, everybody misspelled at first. :)
 +
<span id="chat6"></span>
 +
|- style="vertical-align:top;color:#FF9900;background-color:#FCFCFC;"
 +
| [8:02] 
 +
| Babbage&nbsp;Linden:
 +
| style="white-space:normal;"|thanks for coming
 +
<span id="chat7"></span>
 +
|- style="vertical-align:top;color:#66FF33;background-color:#F0F0F0;"
 +
| [8:02] 
 +
| Nock&nbsp;Forager:
 +
| style="white-space:normal;"|hmm, acctually I'm not a good scripter. Here to listen some update infor about Mono...
 +
<span id="chat8"></span>
 +
|- style="vertical-align:top;color:#FF9900;background-color:#FCFCFC;"
 +
| [8:03] 
 +
| Babbage&nbsp;Linden:
 +
| style="white-space:normal;"|that's fine
 +
<span id="chat9"></span>
 +
|- style="vertical-align:top;color:#66FF33;background-color:#F0F0F0;"
 +
| [8:03] 
 +
| Nock&nbsp;Forager:
 +
| style="white-space:normal;"|Bugs differences bitween LSL2 and Mono.
 +
<span id="chat10"></span>
 +
|- style="vertical-align:top;color:#FF9900;background-color:#FCFCFC;"
 +
| [8:03] 
 +
| Babbage&nbsp;Linden:
 +
| style="white-space:normal;"|i'll wait a few minutes for people to turn up, then give an overview of where we are
 +
<span id="chat11"></span>
 +
|- style="vertical-align:top;color:#33CC00;background-color:#F0F0F0;"
 +
| [8:04] 
 +
| Fake&nbsp;Fitzgerald:
 +
| style="white-space:normal;"|hi
 +
<span id="chat12"></span>
 +
|- style="vertical-align:top;color:#FF9900;background-color:#FCFCFC;"
 +
| [8:04] 
 +
| Babbage&nbsp;Linden:
 +
| style="white-space:normal;"|hi fake
 +
<span id="chat13"></span>
 +
|- style="vertical-align:top;color:#66FF33;background-color:#F0F0F0;"
 +
| [8:04] 
 +
| Nock&nbsp;Forager:
 +
| style="white-space:normal;"|lol everybody fall
 +
<span id="chat14"></span>
 +
|- style="vertical-align:top;color:#66CC66;background-color:#FCFCFC;"
 +
| [8:04] 
 +
| Becky&nbsp;Pippen:
 +
| style="white-space:normal;"|wheeee
 +
<span id="chat15"></span>
 +
|- style="vertical-align:top;color:#FF9900;background-color:#F0F0F0;"
 +
| [8:04] 
 +
| Babbage&nbsp;Linden:
 +
| style="white-space:normal;"|it's possible to make it across if you're lucky
 +
<span id="chat16"></span>
 +
|- style="vertical-align:top;color:#33CC00;background-color:#FCFCFC;"
 +
| [8:04] 
 +
| Fake&nbsp;Fitzgerald:
 +
| style="white-space:normal;"|I didn't fall
 +
<span id="chat17"></span>
 +
|- style="vertical-align:top;color:#FF9900;background-color:#F0F0F0;"
 +
| [8:05] 
 +
| Babbage&nbsp;Linden:
 +
| style="white-space:normal;"|hi miya
 +
<span id="chat18"></span>
 +
|- style="vertical-align:top;color:#336633;background-color:#FCFCFC;"
 +
| [8:05] 
 +
| Creem&nbsp;Pye:
 +
| style="white-space:normal;"|thanks
 +
<span id="chat19"></span>
 +
|- style="vertical-align:top;color:#00CC33;background-color:#F0F0F0;"
 +
| [8:05] 
 +
| Miya&nbsp;Watanabe:
 +
| style="white-space:normal;"|hello
 +
<span id="chat20"></span>
 +
|- style="vertical-align:top;color:#336633;background-color:#FCFCFC;"
 +
| [8:05] 
 +
| Creem&nbsp;Pye:
 +
| style="white-space:normal;"|howdy
 +
<span id="chat21"></span>
 +
|- style="vertical-align:top;color:#FF9900;background-color:#F0F0F0;"
 +
| [8:06] 
 +
| Babbage&nbsp;Linden:
 +
| style="white-space:normal;"|hi creem
 +
<span id="chat22"></span>
 +
|- style="vertical-align:top;color:#66FF33;background-color:#FCFCFC;"
 +
| [8:06] 
 +
| Nock&nbsp;Forager:
 +
| style="white-space:normal;"|Hi
 +
<span id="chat23"></span>
 +
|- style="vertical-align:top;color:#33CC00;background-color:#F0F0F0;"
 +
| [8:06] 
 +
| Fake&nbsp;Fitzgerald:
 +
| style="white-space:normal;"|hi
 +
<span id="chat24"></span>
 +
|- style="vertical-align:top;color:#FF9900;background-color:#FCFCFC;"
 +
| [8:06] 
 +
| Babbage&nbsp;Linden:
 +
| style="white-space:normal;"|let's give people a couple more minutes, then i'll start
 +
<span id="chat25"></span>
 +
|- style="vertical-align:top;color:#FF9900;background-color:#FCFCFC;"
 +
| [8:06] 
 +
| Babbage&nbsp;Linden:
 +
| style="white-space:normal;"|i'll ping the Mono groups too
 +
<span id="chat26"></span>
 +
|- style="vertical-align:top;color:#FF9900;background-color:#FCFCFC;"
 +
| [8:08] 
 +
| Babbage&nbsp;Linden:
 +
| style="white-space:normal;"|so, here's where we are with 1.24
 +
<span id="chat27"></span>
 +
|- style="vertical-align:top;color:#FF9900;background-color:#FCFCFC;"
 +
| [8:09] 
 +
| Babbage&nbsp;Linden:
 +
| style="white-space:normal;"|we had some problems initially with a debug server build, which was causing problems with 1.24.1
 +
<span id="chat28"></span>
 +
|- style="vertical-align:top;color:#FF9900;background-color:#FCFCFC;"
 +
| [8:09] 
 +
| Babbage&nbsp;Linden:
 +
| style="white-space:normal;"|then 1.24.2 fixed a number of crash bugs with features other than mono
 +
<span id="chat29"></span>
 +
|- style="vertical-align:top;color:#FF9900;background-color:#FCFCFC;"
 +
| [8:09] 
 +
| Babbage&nbsp;Linden:
 +
| style="white-space:normal;"|and 1.24.3
 +
<span id="chat30"></span>
 +
|- style="vertical-align:top;color:#FF9900;background-color:#FCFCFC;"
 +
| [8:10] 
 +
| Babbage&nbsp;Linden:
 +
| style="white-space:normal;"|after looking at the crash bugs, the next priority was issues that affect both LSL and Mono scripts
 +
<span id="chat31"></span>
 +
|- style="vertical-align:top;color:#FF9900;background-color:#FCFCFC;"
 +
| [8:10] 
 +
| Babbage&nbsp;Linden:
 +
| style="white-space:normal;"|as these affect existing content
 +
<span id="chat32"></span>
 +
|- style="vertical-align:top;color:#FF9900;background-color:#FCFCFC;"
 +
| [8:11] 
 +
| Babbage&nbsp;Linden:
 +
| style="white-space:normal;"|1.24.4 which we're rolling out now fixed a problem with LSL script scheduling that was causing state_exit events to run slowly
 +
<span id="chat33"></span>
 +
|- style="vertical-align:top;color:#FF9900;background-color:#FCFCFC;"
 +
| [8:11] 
 +
| Babbage&nbsp;Linden:
 +
| style="white-space:normal;"|as well as state changes
 +
<span id="chat34"></span>
 +
|- style="vertical-align:top;color:#FF9900;background-color:#FCFCFC;"
 +
| [8:11] 
 +
| Babbage&nbsp;Linden:
 +
| style="white-space:normal;"|with scripting running on the original scripting engine
 +
<span id="chat35"></span>
 +
|- style="vertical-align:top;color:#336633;background-color:#F0F0F0;"
 +
| [8:11] 
 +
| Creem&nbsp;Pye:
 +
| style="white-space:normal;"|ah, so there will no longer be a 22ms delay for state changes?
 +
<span id="chat36"></span>
 +
|- style="vertical-align:top;color:#FF9900;background-color:#FCFCFC;"
 +
| [8:11] 
 +
| Babbage&nbsp;Linden:
 +
| style="white-space:normal;"|as well as in some cases the order of timer events vs state_exit and state_entry events
 +
<span id="chat37"></span>
 +
|- style="vertical-align:top;color:#FF9900;background-color:#FCFCFC;"
 +
| [8:11] 
 +
| Babbage&nbsp;Linden:
 +
| style="white-space:normal;"|correct creem
 +
<span id="chat38"></span>
 +
|- style="vertical-align:top;color:#FF9900;background-color:#FCFCFC;"
 +
| [8:12] 
 +
| Babbage&nbsp;Linden:
 +
| style="white-space:normal;"|what was happening in 1.24.1-3 is that scripts were yielding when a state change was pending
 +
<span id="chat39"></span>
 +
|- style="vertical-align:top;color:#FF9900;background-color:#FCFCFC;"
 +
| [8:12] 
 +
| Babbage&nbsp;Linden:
 +
| style="white-space:normal;"|so, you could only do 1 state change per time slice and so per frame
 +
<span id="chat40"></span>
 +
|- style="vertical-align:top;color:#FF9900;background-color:#FCFCFC;"
 +
| [8:13] 
 +
| Babbage&nbsp;Linden:
 +
| style="white-space:normal;"|also, because scripts were yielding all the time when state changes were pending, that slowed down state entry a lot
 +
<span id="chat41"></span>
 +
|- style="vertical-align:top;color:#FF9900;background-color:#FCFCFC;"
 +
| [8:13] 
 +
| Babbage&nbsp;Linden:
 +
| style="white-space:normal;"|as a sim running at 45 hz has a frame time of 22ms, that made it look like state changes were taking longer
 +
<span id="chat42"></span>
 +
|- style="vertical-align:top;color:#FF9900;background-color:#FCFCFC;"
 +
| [8:13] 
 +
| Babbage&nbsp;Linden:
 +
| style="white-space:normal;"|they weren't, they were just being gated by the frame rate
 +
<span id="chat43"></span>
 +
|- style="vertical-align:top;color:#336633;background-color:#F0F0F0;"
 +
| [8:13] 
 +
| colspan="2"|Creem&nbsp;Pye nods
 +
<span id="chat44"></span>
 +
|- style="vertical-align:top;color:#FF9900;background-color:#FCFCFC;"
 +
| [8:14] 
 +
| Babbage&nbsp;Linden:
 +
| style="white-space:normal;"|also, the event ordering was changing as previously state_exit and state_entry events were being run immediately
 +
<span id="chat45"></span>
 +
|- style="vertical-align:top;color:#FF9900;background-color:#FCFCFC;"
 +
| [8:14] 
 +
| Babbage&nbsp;Linden:
 +
| style="white-space:normal;"|in 1.23 and before
 +
<span id="chat46"></span>
 +
|- style="vertical-align:top;color:#FF9900;background-color:#FCFCFC;"
 +
| [8:14] 
 +
| Babbage&nbsp;Linden:
 +
| style="white-space:normal;"|when the script was yielding on state change pending, it gave a timer event the chance to sneak in before the state_entry/exit event
 +
<span id="chat47"></span>
 +
|- style="vertical-align:top;color:#FF9900;background-color:#FCFCFC;"
 +
| [8:15] 
 +
| Babbage&nbsp;Linden:
 +
| style="white-space:normal;"|1.24.4 also fixes a problem with llEmail
 +
<span id="chat48"></span>
 +
|- style="vertical-align:top;color:#FF9900;background-color:#FCFCFC;"
 +
| [8:15] 
 +
| Babbage&nbsp;Linden:
 +
| style="white-space:normal;"|that caused email to not be delivered to a script under some circumstances
 +
<span id="chat49"></span>
 +
|- style="vertical-align:top;color:#FF9900;background-color:#FCFCFC;"
 +
| [8:16] 
 +
| Babbage&nbsp;Linden:
 +
| style="white-space:normal;"|and fixed a problem with prepending to a list having side effects
 +
<span id="chat50"></span>
 +
|- style="vertical-align:top;color:#FF9900;background-color:#FCFCFC;"
 +
| [8:16] 
 +
| Babbage&nbsp;Linden:
 +
| style="white-space:normal;"|we're now moving on to looking at problems which only affect Mono scripts
 +
<span id="chat51"></span>
 +
|- style="vertical-align:top;color:#336633;background-color:#F0F0F0;"
 +
| [8:16] 
 +
| Creem&nbsp;Pye:
 +
| style="white-space:normal;"|will scripts need to be reset to take advantage of these fixes?
 +
<span id="chat52"></span>
 +
|- style="vertical-align:top;color:#FF9900;background-color:#FCFCFC;"
 +
| [8:17] 
 +
| Babbage&nbsp;Linden:
 +
| style="white-space:normal;"|we'd really like to be able to get a good repro for http://jira.secondlife.com/browse/SVC-2908
 +
<span id="chat53"></span>
 +
|- style="vertical-align:top;color:#FF9900;background-color:#FCFCFC;"
 +
| [8:17] 
 +
| Babbage&nbsp;Linden:
 +
| style="white-space:normal;"|which i think is actually a number of separate issues
 +
<span id="chat54"></span>
 +
|- style="vertical-align:top;color:#FF9900;background-color:#FCFCFC;"
 +
| [8:17] 
 +
| Babbage&nbsp;Linden:
 +
| style="white-space:normal;"|but we haven't been able to repro any of them yet
 +
<span id="chat55"></span>
 +
|- style="vertical-align:top;color:#FF9900;background-color:#FCFCFC;"
 +
| [8:18] 
 +
| Babbage&nbsp;Linden:
 +
| style="white-space:normal;"|we're currentlly looking at http://jira.secondlife.com/browse/SVC-2751
 +
<span id="chat56"></span>
 +
|- style="vertical-align:top;color:#FF9900;background-color:#FCFCFC;"
 +
| [8:18] 
 +
| Babbage&nbsp;Linden:
 +
| style="white-space:normal;"|which has a good repro
 +
<span id="chat57"></span>
 +
|- style="vertical-align:top;color:#FF9900;background-color:#FCFCFC;"
 +
| [8:18] 
 +
| Babbage&nbsp;Linden:
 +
| style="white-space:normal;"|and then will probably tackle the other Mono specific bugs in http://jira.secondlife.com/browse/SVC-1276
 +
<span id="chat58"></span>
 +
|- style="vertical-align:top;color:#FF9900;background-color:#FCFCFC;"
 +
| [8:18] 
 +
| Babbage&nbsp;Linden:
 +
| style="white-space:normal;"|if nothing else comes up in the meantime
 +
<span id="chat59"></span>
 +
|- style="vertical-align:top;color:#FF9900;background-color:#FCFCFC;"
 +
| [8:18] 
 +
| Babbage&nbsp;Linden:
 +
| style="white-space:normal;"|creem, no you don't need to reset scripts to see the fixes to the scheduler
 +
<span id="chat60"></span>
 +
|- style="vertical-align:top;color:#FF9900;background-color:#FCFCFC;"
 +
| [8:19] 
 +
| Babbage&nbsp;Linden:
 +
| style="white-space:normal;"|the changes are in the simulator code
 +
<span id="chat61"></span>
 +
|- style="vertical-align:top;color:#FF9900;background-color:#FCFCFC;"
 +
| [8:19] 
 +
| Babbage&nbsp;Linden:
 +
| style="white-space:normal;"|and will take effect on running scripts
 +
<span id="chat62"></span>
 +
|- style="vertical-align:top;color:#336633;background-color:#F0F0F0;"
 +
| [8:19] 
 +
| Creem&nbsp;Pye:
 +
| style="white-space:normal;"|hm the svc-2751 repro could use some llSleeop functions I think
 +
<span id="chat63"></span>
 +
|- style="vertical-align:top;color:#336633;background-color:#F0F0F0;"
 +
| [8:20] 
 +
| Creem&nbsp;Pye:
 +
| style="white-space:normal;"|sometimes chat arrives out of order, even within the same event
 +
<span id="chat64"></span>
 +
|- style="vertical-align:top;color:#FF9900;background-color:#FCFCFC;"
 +
| [8:20] 
 +
| Babbage&nbsp;Linden:
 +
| style="white-space:normal;"|yes, agreed
 +
<span id="chat65"></span>
 +
|- style="vertical-align:top;color:#336633;background-color:#F0F0F0;"
 +
| [8:20] 
 +
| Creem&nbsp;Pye:
 +
| style="white-space:normal;"|(but I guess if you had another object in the same sim listening, it should always receive messages in the correct order)
 +
<span id="chat66"></span>
 +
|- style="vertical-align:top;color:#FF9900;background-color:#FCFCFC;"
 +
| [8:20] 
 +
| Babbage&nbsp;Linden:
 +
| style="white-space:normal;"|moon metty tried it with llSleep(3) calls and still saw the problem
 +
<span id="chat67"></span>
 +
|- style="vertical-align:top;color:#FF9900;background-color:#FCFCFC;"
 +
| [8:21] 
 +
| Babbage&nbsp;Linden:
 +
| style="white-space:normal;"|and http://jira.secondlife.com/browse/SVC-2365 suggests there are other problems with scripts being reset
 +
<span id="chat68"></span>
 +
|- style="vertical-align:top;color:#FF9900;background-color:#FCFCFC;"
 +
| [8:21] 
 +
| Babbage&nbsp;Linden:
 +
| style="white-space:normal;"|so that's where we are now
 +
<span id="chat69"></span>
 +
|- style="vertical-align:top;color:#FF9900;background-color:#FCFCFC;"
 +
| [8:22] 
 +
| Babbage&nbsp;Linden:
 +
| style="white-space:normal;"|new crash bugs seem to have been fixed
 +
<span id="chat70"></span>
 +
|- style="vertical-align:top;color:#FF9900;background-color:#FCFCFC;"
 +
| [8:22] 
 +
| Babbage&nbsp;Linden:
 +
| style="white-space:normal;"|LSL2 is mostly working as it was
 +
<span id="chat71"></span>
 +
|- style="vertical-align:top;color:#FF9900;background-color:#FCFCFC;"
 +
| [8:22] 
 +
| Babbage&nbsp;Linden:
 +
| style="white-space:normal;"|and we're going to look at the Mono only issues next
 +
<span id="chat72"></span>
 +
|- style="vertical-align:top;color:#FF9900;background-color:#FCFCFC;"
 +
| [8:22] 
 +
| Babbage&nbsp;Linden:
 +
| style="white-space:normal;"|sound reasonable?
 +
<span id="chat73"></span>
 +
|- style="vertical-align:top;color:#336633;background-color:#F0F0F0;"
 +
| [8:22] 
 +
| Creem&nbsp;Pye:
 +
| style="white-space:normal;"|sure
 +
<span id="chat74"></span>
 +
|- style="vertical-align:top;color:#336633;background-color:#F0F0F0;"
 +
| [8:23] 
 +
| Creem&nbsp;Pye:
 +
| style="white-space:normal;"|I have a question - will the state change fixes in 1.24 affect the execution speed of on_rez at all?
 +
<span id="chat75"></span>
 +
|- style="vertical-align:top;color:#336633;background-color:#F0F0F0;"
 +
| [8:23] 
 +
| Creem&nbsp;Pye:
 +
| style="white-space:normal;"|oops 1.24.4
 +
<span id="chat76"></span>
 +
|- style="vertical-align:top;color:#FF9900;background-color:#FCFCFC;"
 +
| [8:23] 
 +
| Babbage&nbsp;Linden:
 +
| style="white-space:normal;"|no
 +
<span id="chat77"></span>
 +
|- style="vertical-align:top;color:#66CC66;background-color:#F0F0F0;"
 +
| [8:23] 
 +
| Becky&nbsp;Pippen:
 +
| style="white-space:normal;"|sounds like you've accomplished a lot of fixes already! Those reset issues are nasty.... hope they are easy to find and fix.
 +
<span id="chat78"></span>
 +
|- style="vertical-align:top;color:#FF9900;background-color:#FCFCFC;"
 +
| [8:23] 
 +
| Babbage&nbsp;Linden:
 +
| style="white-space:normal;"|are you seeing rez behave more slowly for scripts running on the original scripting engine creem?
 +
<span id="chat79"></span>
 +
|- style="vertical-align:top;color:#FF9900;background-color:#FCFCFC;"
 +
| [8:24] 
 +
| Babbage&nbsp;Linden:
 +
| style="white-space:normal;"|(Mono scripts rez more slowly as they do more work)
 +
<span id="chat80"></span>
 +
|- style="vertical-align:top;color:#336633;background-color:#F0F0F0;"
 +
| [8:24] 
 +
| Creem&nbsp;Pye:
 +
| style="white-space:normal;"|yeah, running slightly more slowly (~1 frame), and also using up slightly more script time than LSL2
 +
<span id="chat81"></span>
 +
|- style="vertical-align:top;color:#FF9900;background-color:#FCFCFC;"
 +
| [8:25] 
 +
| Babbage&nbsp;Linden:
 +
| style="white-space:normal;"|hi zena
 +
<span id="chat82"></span>
 +
|- style="vertical-align:top;color:#336633;background-color:#F0F0F0;"
 +
| [8:25] 
 +
| Creem&nbsp;Pye:
 +
| style="white-space:normal;"|the application I was looking at was scripted bullets, and they "initialize" on rez to become enabled. And with their speed, the execution speed of on_rez affects the minimum range
 +
<span id="chat83"></span>
 +
|- style="vertical-align:top;color:#33FF66;background-color:#FCFCFC;"
 +
| [8:25] 
 +
| Zena&nbsp;Juran:
 +
| style="white-space:normal;"|hiyas everyone :-)
 +
<span id="chat84"></span>
 +
|- style="vertical-align:top;color:#FF9900;background-color:#F0F0F0;"
 +
| [8:25] 
 +
| Babbage&nbsp;Linden:
 +
| style="white-space:normal;"|the on_rez handler should run fine
 +
<span id="chat85"></span>
 +
|- style="vertical-align:top;color:#336633;background-color:#FCFCFC;"
 +
| [8:26] 
 +
| Creem&nbsp;Pye:
 +
| style="white-space:normal;"|I'm using llSetName() in that function, so maybe the UTF16 being used in Mon ois causing the slight slowdown
 +
<span id="chat86"></span>
 +
|- style="vertical-align:top;color:#FF9900;background-color:#F0F0F0;"
 +
| [8:26] 
 +
| Babbage&nbsp;Linden:
 +
| style="white-space:normal;"|but Mono has to check a digital signature when it first rezes an assembly which takes longer
 +
<span id="chat87"></span>
 +
|- style="vertical-align:top;color:#336633;background-color:#FCFCFC;"
 +
| [8:26] 
 +
| Creem&nbsp;Pye:
 +
| style="white-space:normal;"|er llSetObjectName
 +
<span id="chat88"></span>
 +
|- style="vertical-align:top;color:#FF9900;background-color:#F0F0F0;"
 +
| [8:26] 
 +
| Babbage&nbsp;Linden:
 +
| style="white-space:normal;"|but with bullets you are probably rezzing the same script repeatedly, so should only see that hit the first time
 +
<span id="chat89"></span>
 +
|- style="vertical-align:top;color:#FF9900;background-color:#F0F0F0;"
 +
| [8:26] 
 +
| Babbage&nbsp;Linden:
 +
| style="white-space:normal;"|Mono also has to do more set up of objects than LSL
 +
<span id="chat90"></span>
 +
|- style="vertical-align:top;color:#336633;background-color:#FCFCFC;"
 +
| [8:27] 
 +
| Creem&nbsp;Pye:
 +
| style="white-space:normal;"|ah I see
 +
<span id="chat91"></span>
 +
|- style="vertical-align:top;color:#FF9900;background-color:#F0F0F0;"
 +
| [8:27] 
 +
| Babbage&nbsp;Linden:
 +
| style="white-space:normal;"|so rezzing can take slightly longer
 +
<span id="chat92"></span>
 +
|- style="vertical-align:top;color:#66CC66;background-color:#FCFCFC;"
 +
| [8:27] 
 +
| Becky&nbsp;Pippen:
 +
| style="white-space:normal;"|are there any tricks to minimize that setup time?
 +
<span id="chat93"></span>
 +
|- style="vertical-align:top;color:#FF9900;background-color:#F0F0F0;"
 +
| [8:27] 
 +
| Babbage&nbsp;Linden:
 +
| style="white-space:normal;"|make sure you do as much script sharing as possible
 +
<span id="chat94"></span>
 +
|- style="vertical-align:top;color:#FF9900;background-color:#F0F0F0;"
 +
| [8:28] 
 +
| Babbage&nbsp;Linden:
 +
| style="white-space:normal;"|it minimises the time the simulator spends checking signatures
 +
<span id="chat95"></span>
 +
|- style="vertical-align:top;color:#FF9900;background-color:#F0F0F0;"
 +
| [8:28] 
 +
| Babbage&nbsp;Linden:
 +
| style="white-space:normal;"|and saves memory too
 +
<span id="chat96"></span>
 +
|- style="vertical-align:top;color:#FF9900;background-color:#F0F0F0;"
 +
| [8:28] 
 +
| Babbage&nbsp;Linden:
 +
| style="white-space:normal;"|so, if you have a display with lots of XYText scripts for example
 +
<span id="chat97"></span>
 +
|- style="vertical-align:top;color:#FF9900;background-color:#F0F0F0;"
 +
| [8:28] 
 +
| Babbage&nbsp;Linden:
 +
| style="white-space:normal;"|copy the same compiled script in to the object many times
 +
<span id="chat98"></span>
 +
|- style="vertical-align:top;color:#FF9900;background-color:#F0F0F0;"
 +
| [8:29] 
 +
| Babbage&nbsp;Linden:
 +
| style="white-space:normal;"|instead of using recompile scripts in selection
 +
<span id="chat99"></span>
 +
|- style="vertical-align:top;color:#336633;background-color:#FCFCFC;"
 +
| [8:29] 
 +
| Creem&nbsp;Pye:
 +
| style="white-space:normal;"|in terestsing
 +
<span id="chat100"></span>
 +
|- style="vertical-align:top;color:#FF9900;background-color:#F0F0F0;"
 +
| [8:29] 
 +
| Babbage&nbsp;Linden:
 +
| style="white-space:normal;"|which will create a new XYText assembly for each script
 +
<span id="chat101"></span>
 +
|- style="vertical-align:top;color:#66FF33;background-color:#FCFCFC;"
 +
| [8:29] 
 +
| Nock&nbsp;Forager:
 +
| style="white-space:normal;"|hmhm
 +
<span id="chat102"></span>
 +
|- style="vertical-align:top;color:#FF9900;background-color:#F0F0F0;"
 +
| [8:29] 
 +
| Babbage&nbsp;Linden:
 +
| style="white-space:normal;"|if everyone takes copies of the same script when they use popular scripts
 +
<span id="chat103"></span>
 +
|- style="vertical-align:top;color:#FF9900;background-color:#F0F0F0;"
 +
| [8:30] 
 +
| Babbage&nbsp;Linden:
 +
| style="white-space:normal;"|sharing will happen between objects too
 +
<span id="chat104"></span>
 +
|- style="vertical-align:top;color:#FF9900;background-color:#F0F0F0;"
 +
| [8:30] 
 +
| colspan="2"|Babbage&nbsp;Linden wants to see only one XYText assembly per simulator
 +
<span id="chat105"></span>
 +
|- style="vertical-align:top;color:#336633;background-color:#FCFCFC;"
 +
| [8:30] 
 +
| Creem&nbsp;Pye:
 +
| style="white-space:normal;"|btw since it seems that scripts in an avatar's inventory remember if they were compiled as LSL2 or Mono, it might be nice to have a UI option in the script editor, when the script is in avatar inventory
 +
<span id="chat106"></span>
 +
|- style="vertical-align:top;color:#336633;background-color:#FCFCFC;"
 +
| [8:30] 
 +
| Creem&nbsp;Pye:
 +
| style="white-space:normal;"|(the same "Mono" checkbox, I guess)
 +
<span id="chat107"></span>
 +
|- style="vertical-align:top;color:#FF9900;background-color:#F0F0F0;"
 +
| [8:31] 
 +
| Babbage&nbsp;Linden:
 +
| style="white-space:normal;"|that's tricky, as the simulator populates the checkbox by examining the bytecode
 +
<span id="chat108"></span>
 +
|- style="vertical-align:top;color:#FF9900;background-color:#F0F0F0;"
 +
| [8:31] 
 +
| Babbage&nbsp;Linden:
 +
| style="white-space:normal;"|the dataserver doesn't know if a script in your inventory is mono or lsl
 +
<span id="chat109"></span>
 +
|- style="vertical-align:top;color:#FF9900;background-color:#F0F0F0;"
 +
| [8:32] 
 +
| Babbage&nbsp;Linden:
 +
| style="white-space:normal;"|we could extend the database to store that information
 +
<span id="chat110"></span>
 +
|- style="vertical-align:top;color:#336633;background-color:#FCFCFC;"
 +
| [8:32] 
 +
| Creem&nbsp;Pye:
 +
| style="white-space:normal;"|but the script in your inventory has its bytecode attached?
 +
<span id="chat111"></span>
 +
|- style="vertical-align:top;color:#FF9900;background-color:#F0F0F0;"
 +
| [8:32] 
 +
| Babbage&nbsp;Linden:
 +
| style="white-space:normal;"|but it would be considerably more work
 +
<span id="chat112"></span>
 +
|- style="vertical-align:top;color:#FF9900;background-color:#F0F0F0;"
 +
| [8:33] 
 +
| Babbage&nbsp;Linden:
 +
| style="white-space:normal;"|also, knowing whether nested objects contain mono scripts is even harder
 +
<span id="chat113"></span>
 +
|- style="vertical-align:top;color:#FF9900;background-color:#F0F0F0;"
 +
| [8:33] 
 +
| Babbage&nbsp;Linden:
 +
| style="white-space:normal;"|so showing a mono checkbox for objects is really hard
 +
<span id="chat114"></span>
 +
|- style="vertical-align:top;color:#FF9900;background-color:#F0F0F0;"
 +
| [8:33] 
 +
| Babbage&nbsp;Linden:
 +
| style="white-space:normal;"|you would have to recurse through the object checking the information for all scripts
 +
<span id="chat115"></span>
 +
|- style="vertical-align:top;color:#66CC66;background-color:#FCFCFC;"
 +
| [8:34] 
 +
| Becky&nbsp;Pippen:
 +
| style="white-space:normal;"|makes sense
 +
<span id="chat116"></span>
 +
|- style="vertical-align:top;color:#FF9900;background-color:#F0F0F0;"
 +
| [8:34] 
 +
| Babbage&nbsp;Linden:
 +
| style="white-space:normal;"|so, it would be nice to have
 +
<span id="chat117"></span>
 +
|- style="vertical-align:top;color:#336633;background-color:#FCFCFC;"
 +
| [8:34] 
 +
| Creem&nbsp;Pye:
 +
| style="white-space:normal;"|hm yeah, nested objects also often don't reflect the true permissions
 +
<span id="chat118"></span>
 +
|- style="vertical-align:top;color:#FF9900;background-color:#F0F0F0;"
 +
| [8:34] 
 +
| Babbage&nbsp;Linden:
 +
| style="white-space:normal;"|but a lot of work
 +
<span id="chat119"></span>
 +
|- style="vertical-align:top;color:#FF9900;background-color:#F0F0F0;"
 +
| [8:34] 
 +
| Babbage&nbsp;Linden:
 +
| style="white-space:normal;"|hi tegg
 +
<span id="chat120"></span>
 +
|- style="vertical-align:top;color:#66FF99;background-color:#FCFCFC;"
 +
| [8:34] 
 +
| Tegg&nbsp;Bode:
 +
| style="white-space:normal;"|Hi All
 +
<span id="chat121"></span>
 +
|- style="vertical-align:top;color:#336633;background-color:#F0F0F0;"
 +
| [8:35] 
 +
| Creem&nbsp;Pye:
 +
| style="white-space:normal;"|hello
 +
<span id="chat122"></span>
 +
|- style="vertical-align:top;color:#FF9900;background-color:#FCFCFC;"
 +
| [8:35] 
 +
| Babbage&nbsp;Linden:
 +
| style="white-space:normal;"|any other questions?
 +
<span id="chat123"></span>
 +
|- style="vertical-align:top;color:#66FF33;background-color:#F0F0F0;"
 +
| [8:35] 
 +
| Nock&nbsp;Forager:
 +
| style="white-space:normal;"|Hi Tegg, Imaze, Keimar
 +
<span id="chat124"></span>
 +
|- style="vertical-align:top;color:#FF9900;background-color:#FCFCFC;"
 +
| [8:35] 
 +
| Babbage&nbsp;Linden:
 +
| style="white-space:normal;"|how have peoples experiences with mono been?
 +
<span id="chat125"></span>
 +
|- style="vertical-align:top;color:#FF9900;background-color:#FCFCFC;"
 +
| [8:35] 
 +
| Babbage&nbsp;Linden:
 +
| style="white-space:normal;"|hi imaze
 +
<span id="chat126"></span>
 +
|- style="vertical-align:top;color:#66FFCC;background-color:#F0F0F0;"
 +
| [8:35] 
 +
| Keimar&nbsp;Kuhn:
 +
| style="white-space:normal;"|Hi
 +
<span id="chat127"></span>
 +
|- style="vertical-align:top;color:#33FFCC;background-color:#FCFCFC;"
 +
| [8:35] 
 +
| Imaze&nbsp;Rhiano:
 +
| style="white-space:normal;"|hi
 +
<span id="chat128"></span>
 +
|- style="vertical-align:top;color:#336633;background-color:#F0F0F0;"
 +
| [8:35] 
 +
| Creem&nbsp;Pye:
 +
| style="white-space:normal;"|very smooth sailing so far. my only annoyance was that batch-converting scripts would enable scripts that were disabled
 +
<span id="chat129"></span>
 +
|- style="vertical-align:top;color:#FF9900;background-color:#FCFCFC;"
 +
| [8:36] 
 +
| Babbage&nbsp;Linden:
 +
| style="white-space:normal;"|ah, interesting
 +
<span id="chat130"></span>
 +
|- style="vertical-align:top;color:#FF9900;background-color:#FCFCFC;"
 +
| [8:36] 
 +
| Babbage&nbsp;Linden:
 +
| style="white-space:normal;"|could you file that as a bug please?
 +
<span id="chat131"></span>
 +
|- style="vertical-align:top;color:#336633;background-color:#F0F0F0;"
 +
| [8:36] 
 +
| Creem&nbsp;Pye:
 +
| style="white-space:normal;"|sure
 +
<span id="chat132"></span>
 +
|- style="vertical-align:top;color:#FF9900;background-color:#FCFCFC;"
 +
| [8:36] 
 +
| Babbage&nbsp;Linden:
 +
| style="white-space:normal;"|if it's not already in jira
 +
<span id="chat133"></span>
 +
|- style="vertical-align:top;color:#FF9900;background-color:#FCFCFC;"
 +
| [8:36] 
 +
| Babbage&nbsp;Linden:
 +
| style="white-space:normal;"|i haven't seen that yet
 +
<span id="chat134"></span>
 +
|- style="vertical-align:top;color:#336633;background-color:#F0F0F0;"
 +
| [8:37] 
 +
| Creem&nbsp;Pye:
 +
| style="white-space:normal;"|sure thing
 +
<span id="chat135"></span>
 +
|- style="vertical-align:top;color:#FF9900;background-color:#FCFCFC;"
 +
| [8:37] 
 +
| Babbage&nbsp;Linden:
 +
| style="white-space:normal;"|hi gabriel
 +
<span id="chat136"></span>
 +
|- style="vertical-align:top;color:#0099CC;background-color:#F0F0F0;"
 +
| [8:37] 
 +
| Gabriel&nbsp;Linden:
 +
| style="white-space:normal;"|hiya
 +
<span id="chat137"></span>
 +
|- style="vertical-align:top;color:#0099CC;background-color:#F0F0F0;"
 +
| [8:37] 
 +
| Gabriel&nbsp;Linden:
 +
| style="white-space:normal;"|hows it going?
 +
<span id="chat138"></span>
 +
|- style="vertical-align:top;color:#33FFCC;background-color:#FCFCFC;"
 +
| [8:38] 
 +
| Imaze&nbsp;Rhiano:
 +
| style="white-space:normal;"|there has been also some negetive noise about Mono in scripter groups
 +
<span id="chat139"></span>
 +
|- style="vertical-align:top;color:#33FFCC;background-color:#FCFCFC;"
 +
| [8:38] 
 +
| Imaze&nbsp;Rhiano:
 +
| style="white-space:normal;"|saying that mono is crashing sim, consuming more processor time, etc...
 +
<span id="chat140"></span>
 +
|- style="vertical-align:top;color:#FF9900;background-color:#F0F0F0;"
 +
| [8:39] 
 +
| Babbage&nbsp;Linden:
 +
| style="white-space:normal;"|i'm not aware of any mono crash bugs at this point
 +
<span id="chat141"></span>
 +
|- style="vertical-align:top;color:#FF9900;background-color:#F0F0F0;"
 +
| [8:39] 
 +
| Babbage&nbsp;Linden:
 +
| style="white-space:normal;"|i'd be interested in seeing mono using more processor time too
 +
<span id="chat142"></span>
 +
|- style="vertical-align:top;color:#0099CC;background-color:#FCFCFC;"
 +
| [8:39] 
 +
| Gabriel&nbsp;Linden:
 +
| style="white-space:normal;"|yeah
 +
<span id="chat143"></span>
 +
|- style="vertical-align:top;color:#FF9900;background-color:#F0F0F0;"
 +
| [8:39] 
 +
| Babbage&nbsp;Linden:
 +
| style="white-space:normal;"|it may use slightly more when scripts are doing nothing
 +
<span id="chat144"></span>
 +
|- style="vertical-align:top;color:#FF9900;background-color:#F0F0F0;"
 +
| [8:39] 
 +
| Babbage&nbsp;Linden:
 +
| style="white-space:normal;"|as mono scripts check whether they need to migrate when they're run
 +
<span id="chat145"></span>
 +
|- style="vertical-align:top;color:#33FFCC;background-color:#FCFCFC;"
 +
| [8:40] 
 +
| Imaze&nbsp;Rhiano:
 +
| style="white-space:normal;"|I tried to ask from them what they are talking about - but no one didn't provide list of crash bugs or examples
 +
<span id="chat146"></span>
 +
|- style="vertical-align:top;color:#66FF99;background-color:#F0F0F0;"
 +
| [8:40] 
 +
| Tegg&nbsp;Bode:
 +
| style="white-space:normal;"|I am getting a lot more crashing this week on both RC and 1.20, and not using mono scripts yet :)
 +
<span id="chat147"></span>
 +
|- style="vertical-align:top;color:#FF9900;background-color:#FCFCFC;"
 +
| [8:40] 
 +
| Babbage&nbsp;Linden:
 +
| style="white-space:normal;"|there have been problems with the web services this week
 +
<span id="chat148"></span>
 +
|- style="vertical-align:top;color:#FF9900;background-color:#FCFCFC;"
 +
| [8:40] 
 +
| Babbage&nbsp;Linden:
 +
| style="white-space:normal;"|that have caused concurrency drops
 +
<span id="chat149"></span>
 +
|- style="vertical-align:top;color:#336633;background-color:#F0F0F0;"
 +
| [8:40] 
 +
| Creem&nbsp;Pye:
 +
| style="white-space:normal;"|heavy text processing could be slower with mono, right?
 +
<span id="chat150"></span>
 +
|- style="vertical-align:top;color:#FF9900;background-color:#FCFCFC;"
 +
| [8:41] 
 +
| Babbage&nbsp;Linden:
 +
| style="white-space:normal;"|but we're seeing a pretty low crash rate with 1.24.4.95600
 +
<span id="chat151"></span>
 +
|- style="vertical-align:top;color:#336633;background-color:#F0F0F0;"
 +
| [8:41] 
 +
| Creem&nbsp;Pye:
 +
| style="white-space:normal;"|like llList2CSV(llCSV2List()) of something really long
 +
<span id="chat152"></span>
 +
|- style="vertical-align:top;color:#0099CC;background-color:#FCFCFC;"
 +
| [8:41] 
 +
| Gabriel&nbsp;Linden:
 +
| style="white-space:normal;"|so these might be coincidence, as many people are thinking about mono atm
 +
<span id="chat153"></span>
 +
|- style="vertical-align:top;color:#FF9900;background-color:#F0F0F0;"
 +
| [8:41] 
 +
| Babbage&nbsp;Linden:
 +
| style="white-space:normal;"|mono has to convert strings to utf-8 when passing them to library calls implemented in C++
 +
<span id="chat154"></span>
 +
|- style="vertical-align:top;color:#FF9900;background-color:#F0F0F0;"
 +
| [8:42] 
 +
| Babbage&nbsp;Linden:
 +
| style="white-space:normal;"|that could take longer
 +
<span id="chat155"></span>
 +
|- style="vertical-align:top;color:#FF9900;background-color:#F0F0F0;"
 +
| [8:42] 
 +
| Babbage&nbsp;Linden:
 +
| style="white-space:normal;"|which is the common case
 +
<span id="chat156"></span>
 +
|- style="vertical-align:top;color:#FF9900;background-color:#F0F0F0;"
 +
| [8:42] 
 +
| Babbage&nbsp;Linden:
 +
| style="white-space:normal;"|but in generally Marshalling data from Mono to C++ is very fast
 +
<span id="chat157"></span>
 +
|- style="vertical-align:top;color:#33FFCC;background-color:#FCFCFC;"
 +
| [8:42] 
 +
| Imaze&nbsp;Rhiano:
 +
| style="white-space:normal;"|what about those reports about using more cpu time? could it be that all SIM monitor tools are not yet optimized for Mono?
 +
<span id="chat158"></span>
 +
|- style="vertical-align:top;color:#FF9900;background-color:#F0F0F0;"
 +
| [8:43] 
 +
| Babbage&nbsp;Linden:
 +
| style="white-space:normal;"|some of the library calls have been reimplemented in managed code and should run much faster there
 +
<span id="chat159"></span>
 +
|- style="vertical-align:top;color:#FF9900;background-color:#F0F0F0;"
 +
| [8:43] 
 +
| Babbage&nbsp;Linden:
 +
| style="white-space:normal;"|lists are now implemented as ArrayLists for Mono scripts
 +
<span id="chat160"></span>
 +
|- style="vertical-align:top;color:#FF9900;background-color:#F0F0F0;"
 +
| [8:43] 
 +
| Babbage&nbsp;Linden:
 +
| style="white-space:normal;"|so indexing in to them should be constant time instead of requiring a search
 +
<span id="chat161"></span>
 +
|- style="vertical-align:top;color:#FF9900;background-color:#F0F0F0;"
 +
| [8:43] 
 +
| Babbage&nbsp;Linden:
 +
| style="white-space:normal;"|for example
 +
<span id="chat162"></span>
 +
|- style="vertical-align:top;color:#FF9900;background-color:#F0F0F0;"
 +
| [8:44] 
 +
| Babbage&nbsp;Linden:
 +
| style="white-space:normal;"|i'd like to see examples where running Mono scripts use more time than LSL"
 +
<span id="chat163"></span>
 +
|- style="vertical-align:top;color:#FF9900;background-color:#F0F0F0;"
 +
| [8:44] 
 +
| Babbage&nbsp;Linden:
 +
| style="white-space:normal;"|i haven't seen any examples yet
 +
<span id="chat164"></span>
 +
|- style="vertical-align:top;color:#0099CC;background-color:#FCFCFC;"
 +
| [8:44] 
 +
| Gabriel&nbsp;Linden:
 +
| style="white-space:normal;"|its very unlikely you'd see a huge jump in cpu time imho
 +
<span id="chat165"></span>
 +
|- style="vertical-align:top;color:#FF9900;background-color:#F0F0F0;"
 +
| [8:44] 
 +
| Babbage&nbsp;Linden:
 +
| style="white-space:normal;"|just idle scripts using up slightly more time
 +
<span id="chat166"></span>
 +
|- style="vertical-align:top;color:#336633;background-color:#FCFCFC;"
 +
| [8:45] 
 +
| Creem&nbsp;Pye:
 +
| style="white-space:normal;"|maybe the performance hit adds up if there are thousands of idle scripts in a sim
 +
<span id="chat167"></span>
 +
|- style="vertical-align:top;color:#FF6600;background-color:#F0F0F0;"
 +
| [8:45] 
 +
| Christos&nbsp;Atlantis:
 +
| style="white-space:normal;"|does that idle time affect the sim, if there are alot of idle scripts , like in a furniture store that has poseballs in almost every piece
 +
<span id="chat168"></span>
 +
|- style="vertical-align:top;color:#333300;background-color:#FCFCFC;"
 +
| [8:45] 
 +
| Bartlee&nbsp;Arai:
 +
| style="white-space:normal;"|It would be nice if you had a suite where you could do compartive analysis of mono to lsl and track local maxima
 +
<span id="chat169"></span>
 +
|- style="vertical-align:top;color:#FF9900;background-color:#F0F0F0;"
 +
| [8:46] 
 +
| Babbage&nbsp;Linden:
 +
| style="white-space:normal;"|imaze, most of those are now fixed in 1.24.4
 +
<span id="chat170"></span>
 +
|- style="vertical-align:top;color:#FF9900;background-color:#F0F0F0;"
 +
| [8:46] 
 +
| Babbage&nbsp;Linden:
 +
| style="white-space:normal;"|see the mono meta issue in jira for the status
 +
<span id="chat171"></span>
 +
|- style="vertical-align:top;color:#333300;background-color:#FCFCFC;"
 +
| [8:46] 
 +
| Bartlee&nbsp;Arai:
 +
| style="white-space:normal;"|comparative*
 +
<span id="chat172"></span>
 +
|- style="vertical-align:top;color:#33FFCC;background-color:#F0F0F0;"
 +
| [8:46] 
 +
| Imaze&nbsp;Rhiano:
 +
| style="white-space:normal;"|ok - that was list I received last night
 +
<span id="chat173"></span>
 +
|- style="vertical-align:top;color:#33FFCC;background-color:#F0F0F0;"
 +
| [8:46] 
 +
| Imaze&nbsp;Rhiano:
 +
| style="white-space:normal;"|so - it was bit outdated info then
 +
<span id="chat174"></span>
 +
|- style="vertical-align:top;color:#FF9900;background-color:#FCFCFC;"
 +
| [8:46] 
 +
| Babbage&nbsp;Linden:
 +
| style="white-space:normal;"|creem, long term, idle scripts shouldn't consume any CPU time
 +
<span id="chat175"></span>
 +
|- style="vertical-align:top;color:#99CC33;background-color:#F0F0F0;"
 +
| [8:47] 
 +
| Jam&nbsp;Meili:
 +
| style="white-space:normal;"|do thousand idle scripts contribute then more to sim lag then before?
 +
<span id="chat176"></span>
 +
|- style="vertical-align:top;color:#FF9900;background-color:#FCFCFC;"
 +
| [8:47] 
 +
| Babbage&nbsp;Linden:
 +
| style="white-space:normal;"|they should be moved to a non-running scripts list
 +
<span id="chat177"></span>
 +
|- style="vertical-align:top;color:#FF9900;background-color:#FCFCFC;"
 +
| [8:47] 
 +
| Babbage&nbsp;Linden:
 +
| style="white-space:normal;"|and only become runnable when they have pending events
 +
<span id="chat178"></span>
 +
|- style="vertical-align:top;color:#FF9900;background-color:#FCFCFC;"
 +
| [8:47] 
 +
| Babbage&nbsp;Linden:
 +
| style="white-space:normal;"|we have plans to address that
 +
<span id="chat179"></span>
 +
|- style="vertical-align:top;color:#FF9900;background-color:#FCFCFC;"
 +
| [8:47] 
 +
| Babbage&nbsp;Linden:
 +
| style="white-space:normal;"|but it may not be for a while
 +
<span id="chat180"></span>
 +
|- style="vertical-align:top;color:#FF9900;background-color:#FCFCFC;"
 +
| [8:48] 
 +
| Babbage&nbsp;Linden:
 +
| style="white-space:normal;"|in the meantime, i doubt the extra work mono scripts do would have a noticable effect
 +
<span id="chat181"></span>
 +
|- style="vertical-align:top;color:#FF9900;background-color:#FCFCFC;"
 +
| [8:48] 
 +
| Babbage&nbsp;Linden:
 +
| style="white-space:normal;"|even with 1000s of them in a sim
 +
<span id="chat182"></span>
 +
|- style="vertical-align:top;color:#FF6600;background-color:#F0F0F0;"
 +
| [8:49] 
 +
| Christos&nbsp;Atlantis:
 +
| style="white-space:normal;"|I heard mono scripts taste like chicken
 +
<span id="chat183"></span>
 +
|- style="vertical-align:top;color:#FF6600;background-color:#F0F0F0;"
 +
| [8:49] 
 +
| Christos&nbsp;Atlantis:
 +
| style="white-space:normal;"|to many rumours
 +
<span id="chat184"></span>
 +
|- style="vertical-align:top;color:#FF9900;background-color:#FCFCFC;"
 +
| [8:49] 
 +
| Babbage&nbsp;Linden:
 +
| style="white-space:normal;"|yes, agreed
 +
<span id="chat185"></span>
 +
|- style="vertical-align:top;color:#FF9900;background-color:#FCFCFC;"
 +
| [8:50] 
 +
| Babbage&nbsp;Linden:
 +
| style="white-space:normal;"|mono was the biggest change in 1.24
 +
<span id="chat186"></span>
 +
|- style="vertical-align:top;color:#66FF33;background-color:#F0F0F0;"
 +
| [8:50] 
 +
| Nock&nbsp;Forager:
 +
| style="white-space:normal;"|yes, many rumours :)
 +
<span id="chat187"></span>
 +
|- style="vertical-align:top;color:#FF6600;background-color:#FCFCFC;"
 +
| [8:50] 
 +
| Christos&nbsp;Atlantis:
 +
| style="white-space:normal;"|most are saying we should not recomplie
 +
<span id="chat188"></span>
 +
|- style="vertical-align:top;color:#FF9900;background-color:#F0F0F0;"
 +
| [8:50] 
 +
| Babbage&nbsp;Linden:
 +
| style="white-space:normal;"|so is being cited as the cause of many things
 +
<span id="chat189"></span>
 +
|- style="vertical-align:top;color:#333300;background-color:#FCFCFC;"
 +
| [8:50] 
 +
| Bartlee&nbsp;Arai:
 +
| style="white-space:normal;"|How long before Mono is where you think it needs to be, ball park?
 +
<span id="chat190"></span>
 +
|- style="vertical-align:top;color:#FF9900;background-color:#F0F0F0;"
 +
| [8:50] 
 +
| Babbage&nbsp;Linden:
 +
| style="white-space:normal;"|but mostly, if you're not running mono scripts, your problem is unlikely to be mono
 +
<span id="chat191"></span>
 +
|- style="vertical-align:top;color:#FF9900;background-color:#F0F0F0;"
 +
| [8:50] 
 +
| Babbage&nbsp;Linden:
 +
| style="white-space:normal;"|and for most people, most of the time, mono scripts will work fine
 +
<span id="chat192"></span>
 +
|- style="vertical-align:top;color:#333300;background-color:#FCFCFC;"
 +
| [8:51] 
 +
| Bartlee&nbsp;Arai:
 +
| style="white-space:normal;"|the good old 90 10
 +
<span id="chat193"></span>
 +
|- style="vertical-align:top;color:#99CC33;background-color:#F0F0F0;"
 +
| [8:51] 
 +
| Jam&nbsp;Meili:
 +
| style="white-space:normal;"|why it seems mono affects also old scripts? is that mono-related or just bugs that happened in modified servercode?
 +
<span id="chat194"></span>
 +
|- style="vertical-align:top;color:#FF6600;background-color:#FCFCFC;"
 +
| [8:51] 
 +
| Christos&nbsp;Atlantis:
 +
| style="white-space:normal;"|one small thing I did notice, is that the speed of the scripts is a bit faster when running a swarm script, it made the pet move faster
 +
<span id="chat195"></span>
 +
|- style="vertical-align:top;color:#0099CC;background-color:#F0F0F0;"
 +
| [8:51] 
 +
| Gabriel&nbsp;Linden:
 +
| style="white-space:normal;"|we need good reproducable cases if issues are found, if everyone avoids recompilation we wont get them
 +
<span id="chat196"></span>
 +
|- style="vertical-align:top;color:#FF9900;background-color:#FCFCFC;"
 +
| [8:52] 
 +
| Babbage&nbsp;Linden:
 +
| style="white-space:normal;"|we left the original scripting engine alone as much as possible
 +
<span id="chat197"></span>
 +
|- style="vertical-align:top;color:#FF9900;background-color:#FCFCFC;"
 +
| [8:52] 
 +
| Babbage&nbsp;Linden:
 +
| style="white-space:normal;"|but we needed to make a few changes to allow mono to run alongside it
 +
<span id="chat198"></span>
 +
|- style="vertical-align:top;color:#FF9900;background-color:#FCFCFC;"
 +
| [8:52] 
 +
| Babbage&nbsp;Linden:
 +
| style="white-space:normal;"|the state change problems are a good example
 +
<span id="chat199"></span>
 +
|- style="vertical-align:top;color:#FF9900;background-color:#FCFCFC;"
 +
| [8:52] 
 +
| Babbage&nbsp;Linden:
 +
| style="white-space:normal;"|the old scripting engine interpretted 1 instruction at a time
 +
<span id="chat200"></span>
 +
|- style="vertical-align:top;color:#FF9900;background-color:#FCFCFC;"
 +
| [8:53] 
 +
| Babbage&nbsp;Linden:
 +
| style="white-space:normal;"|Mono executes small pieces of code at once
 +
<span id="chat201"></span>
 +
|- style="vertical-align:top;color:#FF9900;background-color:#FCFCFC;"
 +
| [8:53] 
 +
| Babbage&nbsp;Linden:
 +
| style="white-space:normal;"|so we had to change the script scheduling code to cope with both engines
 +
<span id="chat202"></span>
 +
|- style="vertical-align:top;color:#FF6600;background-color:#F0F0F0;"
 +
| [8:53] 
 +
| Christos&nbsp;Atlantis:
 +
| style="white-space:normal;"|one more dumb question, if I am the owner of a script and recompile it, will all others using my script have a there items recompiled also?
 +
<span id="chat203"></span>
 +
|- style="vertical-align:top;color:#FF9900;background-color:#FCFCFC;"
 +
| [8:53] 
 +
| Babbage&nbsp;Linden:
 +
| style="white-space:normal;"|and managed to subtly change script execution behaviour in the process
 +
<span id="chat204"></span>
 +
|- style="vertical-align:top;color:#FF9900;background-color:#FCFCFC;"
 +
| [8:54] 
 +
| Babbage&nbsp;Linden:
 +
| style="white-space:normal;"|christos, no
 +
<span id="chat205"></span>
 +
|- style="vertical-align:top;color:#FF9900;background-color:#FCFCFC;"
 +
| [8:54] 
 +
| Babbage&nbsp;Linden:
 +
| style="white-space:normal;"|only the copy you recompile
 +
<span id="chat206"></span>
 +
|- style="vertical-align:top;color:#99CC33;background-color:#F0F0F0;"
 +
| [8:54] 
 +
| Jam&nbsp;Meili:
 +
| style="white-space:normal;"|ok, so that "eps" in the statistics is referred to that pieces of code that run at once? or how should we interpret that?
 +
<span id="chat207"></span>
 +
|- style="vertical-align:top;color:#FF9900;background-color:#FCFCFC;"
 +
| [8:54] 
 +
| Babbage&nbsp;Linden:
 +
| style="white-space:normal;"|it's like saving a script to produce a new script
 +
<span id="chat208"></span>
 +
|- style="vertical-align:top;color:#99CC33;background-color:#F0F0F0;"
 +
| [8:54] 
 +
| Jam&nbsp;Meili:
 +
| style="white-space:normal;"|are that library calls in c# or something?
 +
<span id="chat209"></span>
 +
|- style="vertical-align:top;color:#FF6600;background-color:#FCFCFC;"
 +
| [8:54] 
 +
| Christos&nbsp;Atlantis:
 +
| style="white-space:normal;"|so we have to recompile every single script in our stores?
 +
<span id="chat210"></span>
 +
|- style="vertical-align:top;color:#FF9900;background-color:#F0F0F0;"
 +
| [8:54] 
 +
| Babbage&nbsp;Linden:
 +
| style="white-space:normal;"|other objects still reference the old bytecode asset and so don't change
 +
<span id="chat211"></span>
 +
|- style="vertical-align:top;color:#FF9900;background-color:#F0F0F0;"
 +
| [8:55] 
 +
| Babbage&nbsp;Linden:
 +
| style="white-space:normal;"|christos, if you want to create new versions of all of them yes
 +
<span id="chat212"></span>
 +
|- style="vertical-align:top;color:#FF9900;background-color:#F0F0F0;"
 +
| [8:55] 
 +
| Babbage&nbsp;Linden:
 +
| style="white-space:normal;"|if they share scripts, the better way is to recompile 1
 +
<span id="chat213"></span>
 +
|- style="vertical-align:top;color:#FF9900;background-color:#F0F0F0;"
 +
| [8:55] 
 +
| Babbage&nbsp;Linden:
 +
| style="white-space:normal;"|then copy the new scripts in to the others
 +
<span id="chat214"></span>
 +
|- style="vertical-align:top;color:#FF9900;background-color:#F0F0F0;"
 +
| [8:55] 
 +
| Babbage&nbsp;Linden:
 +
| style="white-space:normal;"|to get more bytecode sharing
 +
<span id="chat215"></span>
 +
|- style="vertical-align:top;color:#FF9900;background-color:#F0F0F0;"
 +
| [8:55] 
 +
| Babbage&nbsp;Linden:
 +
| style="white-space:normal;"|you'll also want to test all the objects to make sure they work after conversion too
 +
<span id="chat216"></span>
 +
|- style="vertical-align:top;color:#FF6600;background-color:#FCFCFC;"
 +
| [8:56] 
 +
| Christos&nbsp;Atlantis:
 +
| style="white-space:normal;"|I have 7000 pieces of furniture in 5 stores, that is a very big task
 +
<span id="chat217"></span>
 +
|- style="vertical-align:top;color:#FF9900;background-color:#F0F0F0;"
 +
| [8:56] 
 +
| Babbage&nbsp;Linden:
 +
| style="white-space:normal;"|christos, agreed
 +
<span id="chat218"></span>
 +
|- style="vertical-align:top;color:#336633;background-color:#FCFCFC;"
 +
| [8:56] 
 +
| Creem&nbsp;Pye:
 +
| style="white-space:normal;"|ko Babbage, I've created a Jira item for the batch script conversion bug: SVC-2987
 +
<span id="chat219"></span>
 +
|- style="vertical-align:top;color:#FF9900;background-color:#F0F0F0;"
 +
| [8:56] 
 +
| Babbage&nbsp;Linden:
 +
| style="white-space:normal;"|you need to decide whether converting the scripts inside makes sense
 +
<span id="chat220"></span>
 +
|- style="vertical-align:top;color:#FF9900;background-color:#F0F0F0;"
 +
| [8:56] 
 +
| Babbage&nbsp;Linden:
 +
| style="white-space:normal;"|thanks creem
 +
<span id="chat221"></span>
 +
|- style="vertical-align:top;color:#FF9900;background-color:#F0F0F0;"
 +
| [8:57] 
 +
| Babbage&nbsp;Linden:
 +
| style="white-space:normal;"|jam, the eps change was due to Mono running small pieces of code at once
 +
<span id="chat222"></span>
 +
|- style="vertical-align:top;color:#FF9900;background-color:#F0F0F0;"
 +
| [8:57] 
 +
| Babbage&nbsp;Linden:
 +
| style="white-space:normal;"|we have no way of counting instructions with Mono easily
 +
<span id="chat223"></span>
 +
|- style="vertical-align:top;color:#FF6600;background-color:#FCFCFC;"
 +
| [8:57] 
 +
| Christos&nbsp;Atlantis:
 +
| style="white-space:normal;"|ok, so if I do not convert, will the furniture ie (pose balls) stop working
 +
<span id="chat224"></span>
 +
|- style="vertical-align:top;color:#99CC33;background-color:#F0F0F0;"
 +
| [8:57] 
 +
| Jam&nbsp;Meili:
 +
| style="white-space:normal;"|each recompile creates a new c# assembly, so i guess it uses also more memory if we compile same scripts in each prims over and over, is that right?
 +
<span id="chat225"></span>
 +
|- style="vertical-align:top;color:#FF9900;background-color:#FCFCFC;"
 +
| [8:57] 
 +
| Babbage&nbsp;Linden:
 +
| style="white-space:normal;"|so, instead we count how many events the script it executing
 +
<span id="chat226"></span>
 +
|- style="vertical-align:top;color:#FF9900;background-color:#FCFCFC;"
 +
| [8:58] 
 +
| Babbage&nbsp;Linden:
 +
| style="white-space:normal;"|which can be compared between Mono scripts and scripts running on the original scripting engine (OSE from now on)
 +
<span id="chat227"></span>
 +
|- style="vertical-align:top;color:#FF9900;background-color:#FCFCFC;"
 +
| [8:58] 
 +
| Babbage&nbsp;Linden:
 +
| style="white-space:normal;"|christos, if you don't convert your scripts they will continue to run as before
 +
<span id="chat228"></span>
 +
|- style="vertical-align:top;color:#FF6600;background-color:#F0F0F0;"
 +
| [8:59] 
 +
| Christos&nbsp;Atlantis:
 +
| style="white-space:normal;"|ok, ty those where my main concerns, I can now make logical choices
 +
<span id="chat229"></span>
 +
|- style="vertical-align:top;color:#FF9900;background-color:#FCFCFC;"
 +
| [8:59] 
 +
| Babbage&nbsp;Linden:
 +
| style="white-space:normal;"|jam, if you keep compiling scripts over and over
 +
<span id="chat230"></span>
 +
|- style="vertical-align:top;color:#FF9900;background-color:#FCFCFC;"
 +
| [8:59] 
 +
| Babbage&nbsp;Linden:
 +
| style="white-space:normal;"|eventually Mono unloads them if they're not being referenced by a script
 +
<span id="chat231"></span>
 +
|- style="vertical-align:top;color:#FF9900;background-color:#FCFCFC;"
 +
| [9:00] 
 +
| Babbage&nbsp;Linden:
 +
| style="white-space:normal;"|so, you don't need to worry about that
 +
<span id="chat232"></span>
 +
|- style="vertical-align:top;color:#FF9900;background-color:#FCFCFC;"
 +
| [9:00] 
 +
| Babbage&nbsp;Linden:
 +
| style="white-space:normal;"|but, you should try to have as many objects reference each assembly as possible
 +
<span id="chat233"></span>
 +
|- style="vertical-align:top;color:#FF9900;background-color:#FCFCFC;"
 +
| [9:00] 
 +
| Babbage&nbsp;Linden:
 +
| style="white-space:normal;"|to minimise the numbers of assemblies that mono needs to keep around
 +
<span id="chat234"></span>
 +
|- style="vertical-align:top;color:#99CC33;background-color:#F0F0F0;"
 +
| [9:00] 
 +
| Jam&nbsp;Meili:
 +
| style="white-space:normal;"|hum i said it maybe wrong. i mean if i use the same script like in hudred prims and isntead of copying one compiled in all, if i would create a script in each and recompile the source, it would use like hundred times more memory?
 +
<span id="chat235"></span>
 +
|- style="vertical-align:top;color:#FF9900;background-color:#FCFCFC;"
 +
| [9:00] 
 +
| Babbage&nbsp;Linden:
 +
| style="white-space:normal;"|it doesn't know that scripts are the same just because they have the same source
 +
<span id="chat236"></span>
 +
|- style="vertical-align:top;color:#FF9900;background-color:#FCFCFC;"
 +
| [9:01] 
 +
| Babbage&nbsp;Linden:
 +
| style="white-space:normal;"|but if you drag compiled scripts in to objects, it knows that they are sharing
 +
<span id="chat237"></span>
 +
|- style="vertical-align:top;color:#99CC33;background-color:#F0F0F0;"
 +
| [9:01] 
 +
| Jam&nbsp;Meili:
 +
| style="white-space:normal;"|so we could tune our scripts in that way, what wasnt possible in the old engine?
 +
<span id="chat238"></span>
 +
|- style="vertical-align:top;color:#FF9900;background-color:#FCFCFC;"
 +
| [9:01] 
 +
| Babbage&nbsp;Linden:
 +
| style="white-space:normal;"|and only needs to keep 1 assembly in memory
 +
<span id="chat239"></span>
 +
|- style="vertical-align:top;color:#336633;background-color:#F0F0F0;"
 +
| [9:01] 
 +
| Creem&nbsp;Pye:
 +
| style="white-space:normal;"|it would be nice if the scripts had a checksum on the bytecode to check if they're identical
 +
<span id="chat240"></span>
 +
|- style="vertical-align:top;color:#FF9900;background-color:#FCFCFC;"
 +
| [9:01] 
 +
| Babbage&nbsp;Linden:
 +
| style="white-space:normal;"|the OSE didn't do any sharing
 +
<span id="chat241"></span>
 +
|- style="vertical-align:top;color:#66CC66;background-color:#F0F0F0;"
 +
| [9:01] 
 +
| Becky&nbsp;Pippen:
 +
| style="white-space:normal;"|Is OSE the new term for the LSL VM back end? It's the term that replaces awkward names like LS2VM, or LSL-LSO, or LSL2LSOVM... ?
 +
<span id="chat242"></span>
 +
|- style="vertical-align:top;color:#FF9900;background-color:#FCFCFC;"
 +
| [9:01] 
 +
| Babbage&nbsp;Linden:
 +
| style="white-space:normal;"|so, if you had 1000 bullets flying around
 +
<span id="chat243"></span>
 +
|- style="vertical-align:top;color:#FF9900;background-color:#FCFCFC;"
 +
| [9:01] 
 +
| Babbage&nbsp;Linden:
 +
| style="white-space:normal;"|each would use 16K
 +
<span id="chat244"></span>
 +
|- style="vertical-align:top;color:#FF9900;background-color:#FCFCFC;"
 +
| [9:02] 
 +
| Babbage&nbsp;Linden:
 +
| style="white-space:normal;"|with Mono, they might use 1K shared between them
 +
<span id="chat245"></span>
 +
|- style="vertical-align:top;color:#FF9900;background-color:#FCFCFC;"
 +
| [9:02] 
 +
| Babbage&nbsp;Linden:
 +
| style="white-space:normal;"|if all the guns contained copies of the same compiled script
 +
<span id="chat246"></span>
 +
|- style="vertical-align:top;color:#FF6600;background-color:#F0F0F0;"
 +
| [9:02] 
 +
| Christos&nbsp;Atlantis:
 +
| style="white-space:normal;"|will mono allow for you to implement use of other scripting and programing choices in SL?
 +
<span id="chat247"></span>
 +
|- style="vertical-align:top;color:#336633;background-color:#FCFCFC;"
 +
| [9:02] 
 +
| Creem&nbsp;Pye:
 +
| style="white-space:normal;"|creating the UUID of a script based on its sha-160 checksum would be nice =)
 +
<span id="chat248"></span>
 +
|- style="vertical-align:top;color:#FF9900;background-color:#F0F0F0;"
 +
| [9:02] 
 +
| Babbage&nbsp;Linden:
 +
| style="white-space:normal;"|christos, yest
 +
<span id="chat249"></span>
 +
|- style="vertical-align:top;color:#FF6600;background-color:#FCFCFC;"
 +
| [9:02] 
 +
| Christos&nbsp;Atlantis:
 +
| style="white-space:normal;"|:)
 +
<span id="chat250"></span>
 +
|- style="vertical-align:top;color:#99CC33;background-color:#F0F0F0;"
 +
| [9:02] 
 +
| Jam&nbsp;Meili:
 +
| style="white-space:normal;"|ok, thats great and hopefully will make combat sims and such to work better. is there another mono-related impriovement we could use to tune the usage of resources on a sim?
 +
<span id="chat251"></span>
 +
|- style="vertical-align:top;color:#FF9900;background-color:#FCFCFC;"
 +
| [9:02] 
 +
| Babbage&nbsp;Linden:
 +
| style="white-space:normal;"|it will allow us to enable other languages to script SL in the long term
 +
<span id="chat252"></span>
 +
|- style="vertical-align:top;color:#FF9900;background-color:#FCFCFC;"
 +
| [9:03] 
 +
| Babbage&nbsp;Linden:
 +
| style="white-space:normal;"|we have been careful to keep that option open while working on LSL on Mono
 +
<span id="chat253"></span>
 +
|- style="vertical-align:top;color:#FF9900;background-color:#FCFCFC;"
 +
| [9:03] 
 +
| Babbage&nbsp;Linden:
 +
| style="white-space:normal;"|but there is still more work to be done before we get there
 +
<span id="chat254"></span>
 +
|- style="vertical-align:top;color:#FF6600;background-color:#F0F0F0;"
 +
| [9:03] 
 +
| Christos&nbsp;Atlantis:
 +
| style="white-space:normal;"|well, my dream would be if I could see a game engine running inside SL
 +
<span id="chat255"></span>
 +
|- style="vertical-align:top;color:#FF9900;background-color:#FCFCFC;"
 +
| [9:04] 
 +
| Babbage&nbsp;Linden:
 +
| style="white-space:normal;"|jam, bytecode sharing is the big thing that you can do to help Mono work effeciently
 +
<span id="chat256"></span>
 +
|- style="vertical-align:top;color:#FF6600;background-color:#F0F0F0;"
 +
| [9:04] 
 +
| Christos&nbsp;Atlantis:
 +
| style="white-space:normal;"|that would make the possibilities endless, mini games inside SL like a WoW
 +
<span id="chat257"></span>
 +
|- style="vertical-align:top;color:#FF9900;background-color:#FCFCFC;"
 +
| [9:04] 
 +
| Babbage&nbsp;Linden:
 +
| style="white-space:normal;"|Christos, SL is like a game engine in many ways
 +
<span id="chat258"></span>
 +
|- style="vertical-align:top;color:#FF9900;background-color:#FCFCFC;"
 +
| [9:05] 
 +
| Babbage&nbsp;Linden:
 +
| style="white-space:normal;"|lots of game engines have scripting engines and physics engines like SL
 +
<span id="chat259"></span>
 +
|- style="vertical-align:top;color:#FF9900;background-color:#FCFCFC;"
 +
| [9:05] 
 +
| Babbage&nbsp;Linden:
 +
| style="white-space:normal;"|games like dark life have been WoW like games in SL for a long time
 +
<span id="chat260"></span>
 +
|- style="vertical-align:top;color:#FF6600;background-color:#F0F0F0;"
 +
| [9:05] 
 +
| Christos&nbsp;Atlantis:
 +
| style="white-space:normal;"|yes, but it lacks the tools to make a good platform for developing game play
 +
<span id="chat261"></span>
 +
|- style="vertical-align:top;color:#336633;background-color:#FCFCFC;"
 +
| [9:05] 
 +
| Creem&nbsp;Pye:
 +
| style="white-space:normal;"|one thing you'd need to do is give estate managers much more control over what avatars can do
 +
<span id="chat262"></span>
 +
|- style="vertical-align:top;color:#FF9900;background-color:#F0F0F0;"
 +
| [9:05] 
 +
| Babbage&nbsp;Linden:
 +
| style="white-space:normal;"|there are some missing features, agreed
 +
<span id="chat263"></span>
 +
|- style="vertical-align:top;color:#336633;background-color:#FCFCFC;"
 +
| [9:06] 
 +
| Creem&nbsp;Pye:
 +
| style="white-space:normal;"|like forbid external attachments, and maybe force an avatar to have a certain style of appearance
 +
<span id="chat264"></span>
 +
|- style="vertical-align:top;color:#FF9900;background-color:#F0F0F0;"
 +
| [9:06] 
 +
| Babbage&nbsp;Linden:
 +
| style="white-space:normal;"|and many people are building things other than games
 +
<span id="chat265"></span>
 +
|- style="vertical-align:top;color:#FF9900;background-color:#F0F0F0;"
 +
| [9:06] 
 +
| Babbage&nbsp;Linden:
 +
| style="white-space:normal;"|so, we need to be careful to keep the platform neutral
 +
<span id="chat266"></span>
 +
|- style="vertical-align:top;color:#FF6600;background-color:#FCFCFC;"
 +
| [9:06] 
 +
| Christos&nbsp;Atlantis:
 +
| style="white-space:normal;"|like being able to control movement of props in non linear routes
 +
<span id="chat267"></span>
 +
|- style="vertical-align:top;color:#FF9900;background-color:#F0F0F0;"
 +
| [9:06] 
 +
| Babbage&nbsp;Linden:
 +
| style="white-space:normal;"|and make extensions where they are most useful to the most people
 +
<span id="chat268"></span>
 +
|- style="vertical-align:top;color:#33FFCC;background-color:#FCFCFC;"
 +
| [9:06] 
 +
| Imaze&nbsp;Rhiano:
 +
| style="white-space:normal;"|if you want game development for SL - then you need also better controls for texture usage and model/prim usage for SIM owners
 +
<span id="chat269"></span>
 +
|- style="vertical-align:top;color:#336633;background-color:#F0F0F0;"
 +
| [9:06] 
 +
| Creem&nbsp;Pye:
 +
| style="white-space:normal;"|yep
 +
<span id="chat270"></span>
 +
|- style="vertical-align:top;color:#33FFCC;background-color:#FCFCFC;"
 +
| [9:07] 
 +
| Imaze&nbsp;Rhiano:
 +
| style="white-space:normal;"|but that is bit offtopic
 +
<span id="chat271"></span>
 +
|- style="vertical-align:top;color:#FF9900;background-color:#F0F0F0;"
 +
| [9:07] 
 +
| Babbage&nbsp;Linden:
 +
| style="white-space:normal;"|we want to enable the widest array of applications possible in SL
 +
<span id="chat272"></span>
 +
|- style="vertical-align:top;color:#FF9900;background-color:#F0F0F0;"
 +
| [9:07] 
 +
| Babbage&nbsp;Linden:
 +
| style="white-space:normal;"|but we have limited resources
 +
<span id="chat273"></span>
 +
|- style="vertical-align:top;color:#FF9900;background-color:#F0F0F0;"
 +
| [9:07] 
 +
| Babbage&nbsp;Linden:
 +
| style="white-space:normal;"|so have to be smart about prioritizing improvements
 +
<span id="chat274"></span>
 +
|- style="vertical-align:top;color:#336633;background-color:#FCFCFC;"
 +
| [9:07] 
 +
| Creem&nbsp;Pye:
 +
| style="white-space:normal;"|megasims would be a nice start :D
 +
<span id="chat275"></span>
 +
|- style="vertical-align:top;color:#336633;background-color:#FCFCFC;"
 +
| [9:08] 
 +
| colspan="2"|Creem&nbsp;Pye is a vehicle creator
 +
<span id="chat276"></span>
 +
|- style="vertical-align:top;color:#FF6600;background-color:#F0F0F0;"
 +
| [9:08] 
 +
| Christos&nbsp;Atlantis:
 +
| style="white-space:normal;"|I think the number 1 with residents is stability, so I will agree with you, you need to keep it stable for a long period and understand it before adding more features
 +
<span id="chat277"></span>
 +
|- style="vertical-align:top;color:#FF9900;background-color:#FCFCFC;"
 +
| [9:09] 
 +
| Babbage&nbsp;Linden:
 +
| style="white-space:normal;"|and most of the effort at linden is working on stability
 +
<span id="chat278"></span>
 +
|- style="vertical-align:top;color:#99CC33;background-color:#F0F0F0;"
 +
| [9:09] 
 +
| Jam&nbsp;Meili:
 +
| style="white-space:normal;"|hehe megasims would require changes in alot of parts of the server- and viewercode as also to expect owners would use server resources wisely, i guess we should not expect that any time soon, it's not very realistically right now
 +
<span id="chat279"></span>
 +
|- style="vertical-align:top;color:#FF9900;background-color:#FCFCFC;"
 +
| [9:09] 
 +
| Babbage&nbsp;Linden:
 +
| style="white-space:normal;"|which is why the scripting improvements are relatively slow in coming
 +
<span id="chat280"></span>
 +
|- style="vertical-align:top;color:#FF6600;background-color:#F0F0F0;"
 +
| [9:09] 
 +
| Christos&nbsp;Atlantis:
 +
| style="white-space:normal;"|and scaleability is also something I would think will help
 +
<span id="chat281"></span>
 +
|- style="vertical-align:top;color:#FF9900;background-color:#FCFCFC;"
 +
| [9:09] 
 +
| Babbage&nbsp;Linden:
 +
| style="white-space:normal;"|Mono was mostly me working on my own until near the end of the project
 +
<span id="chat282"></span>
 +
|- style="vertical-align:top;color:#FF6600;background-color:#F0F0F0;"
 +
| [9:09] 
 +
| Christos&nbsp;Atlantis:
 +
| style="white-space:normal;"|wow
 +
<span id="chat283"></span>
 +
|- style="vertical-align:top;color:#FF6600;background-color:#F0F0F0;"
 +
| [9:09] 
 +
| Christos&nbsp;Atlantis:
 +
| style="white-space:normal;"|great job!
 +
<span id="chat284"></span>
 +
|- style="vertical-align:top;color:#333300;background-color:#FCFCFC;"
 +
| [9:09] 
 +
| Bartlee&nbsp;Arai:
 +
| style="white-space:normal;"|Nice
 +
<span id="chat285"></span>
 +
|- style="vertical-align:top;color:#66FF33;background-color:#F0F0F0;"
 +
| [9:09] 
 +
| Nock&nbsp;Forager:
 +
| style="white-space:normal;"|yup!
 +
<span id="chat286"></span>
 +
|- style="vertical-align:top;color:#FF9900;background-color:#FCFCFC;"
 +
| [9:09] 
 +
| Babbage&nbsp;Linden:
 +
| style="white-space:normal;"|help! i'm being beaten with a car
 +
<span id="chat287"></span>
 +
|- style="vertical-align:top;color:#336633;background-color:#F0F0F0;"
 +
| [9:09] 
 +
| Creem&nbsp;Pye:
 +
| style="white-space:normal;"|yep, it's working quite smoothly so far =)
 +
<span id="chat288"></span>
 +
|- style="vertical-align:top;color:#336633;background-color:#F0F0F0;"
 +
| [9:10] 
 +
| Creem&nbsp;Pye:
 +
| style="white-space:normal;"|Babbage, do you expect the script memory limit wil be raised in teh future?
 +
<span id="chat289"></span>
 +
|- style="vertical-align:top;color:#336633;background-color:#F0F0F0;"
 +
| [9:10] 
 +
| Creem&nbsp;Pye:
 +
| style="white-space:normal;"|it would be nice if objects could consolidate their functions to a single script
 +
<span id="chat290"></span>
 +
|- style="vertical-align:top;color:#FF9900;background-color:#FCFCFC;"
 +
| [9:10] 
 +
| Babbage&nbsp;Linden:
 +
| style="white-space:normal;"|gabriel, si, daveh, vektor and periapse did a lot of work over the last year too
 +
<span id="chat291"></span>
 +
|- style="vertical-align:top;color:#FF6600;background-color:#F0F0F0;"
 +
| [9:10] 
 +
| Christos&nbsp;Atlantis:
 +
| style="white-space:normal;"|I think I have skid marks on my forehead
 +
<span id="chat292"></span>
 +
|- style="vertical-align:top;color:#66FF99;background-color:#FCFCFC;"
 +
| [9:10] 
 +
| Tegg&nbsp;Bode:
 +
| style="white-space:normal;"|I think games would hae a better chance of working if we could reduce our continual downloading of textures by perhaps having a basic default texture set for walls & floors on our hard drives
 +
<span id="chat293"></span>
 +
|- style="vertical-align:top;color:#336633;background-color:#F0F0F0;"
 +
| [9:10] 
 +
| Creem&nbsp;Pye:
 +
| style="white-space:normal;"|(I imagine that without link messages etc, efficiency could be greatly improved)
 +
<span id="chat294"></span>
 +
|- style="vertical-align:top;color:#FF9900;background-color:#FCFCFC;"
 +
| [9:10] 
 +
| Babbage&nbsp;Linden:
 +
| style="white-space:normal;"|creem pye, that is also on our wish list
 +
<span id="chat295"></span>
 +
|- style="vertical-align:top;color:#FF9900;background-color:#FCFCFC;"
 +
| [9:10] 
 +
| Babbage&nbsp;Linden:
 +
| style="white-space:normal;"|proper script libraries
 +
<span id="chat296"></span>
 +
|- style="vertical-align:top;color:#FF9900;background-color:#FCFCFC;"
 +
| [9:11] 
 +
| Babbage&nbsp;Linden:
 +
| style="white-space:normal;"|so you can share code between scripts
 +
<span id="chat297"></span>
 +
|- style="vertical-align:top;color:#FF9900;background-color:#FCFCFC;"
 +
| [9:11] 
 +
| Babbage&nbsp;Linden:
 +
| style="white-space:normal;"|and develop general purpose libraries that can be used by other scripts
 +
<span id="chat298"></span>
 +
|- style="vertical-align:top;color:#FF9900;background-color:#FCFCFC;"
 +
| [9:11] 
 +
| Babbage&nbsp;Linden:
 +
| style="white-space:normal;"|instead of having to send them link messages
 +
<span id="chat299"></span>
 +
|- style="vertical-align:top;color:#FF9900;background-color:#FCFCFC;"
 +
| [9:11] 
 +
| Babbage&nbsp;Linden:
 +
| style="white-space:normal;"|or chat messages
 +
<span id="chat300"></span>
 +
|- style="vertical-align:top;color:#336633;background-color:#F0F0F0;"
 +
| [9:11] 
 +
| Creem&nbsp;Pye:
 +
| style="white-space:normal;"|even functions like llLinkParticleSystem() to set a particle system centered around a link in the object would be nice
 +
<span id="chat301"></span>
 +
|- style="vertical-align:top;color:#336633;background-color:#F0F0F0;"
 +
| [9:12] 
 +
| Creem&nbsp;Pye:
 +
| style="white-space:normal;"|instead of having to have a separate script in a child prim for particles, commanded by the main script through link messages
 +
<span id="chat302"></span>
 +
|- style="vertical-align:top;color:#FF6600;background-color:#FCFCFC;"
 +
| [9:12] 
 +
| Christos&nbsp;Atlantis:
 +
| style="white-space:normal;"|I have tried 5 times in my life to learn programing this is the closest to heaven for me, and for that I would like to thank you guys and the people that help in groups, like Jam and co
 +
<span id="chat303"></span>
 +
|- style="vertical-align:top;color:#FF9900;background-color:#F0F0F0;"
 +
| [9:12] 
 +
| Babbage&nbsp;Linden:
 +
| style="white-space:normal;"|glad to hear it christos!
 +
<span id="chat304"></span>
 +
|- style="vertical-align:top;color:#99CC33;background-color:#FCFCFC;"
 +
| [9:12] 
 +
| Jam&nbsp;Meili:
 +
| style="white-space:normal;"|uuh .. thank you :)
 +
<span id="chat305"></span>
 +
|- style="vertical-align:top;color:#FF9900;background-color:#F0F0F0;"
 +
| [9:12] 
 +
| Babbage&nbsp;Linden:
 +
| style="white-space:normal;"|:-)
 +
<span id="chat306"></span>
 +
|- style="vertical-align:top;color:#333300;background-color:#FCFCFC;"
 +
| [9:13] 
 +
| Bartlee&nbsp;Arai:
 +
| style="white-space:normal;"|will the old scripting engine be replaced eventually once transparency has been acheived?
 +
<span id="chat307"></span>
 +
|- style="vertical-align:top;color:#0099CC;background-color:#F0F0F0;"
 +
| [9:13] 
 +
| Gabriel&nbsp;Linden:
 +
| style="white-space:normal;"|teaching the world to code
 +
<span id="chat308"></span>
 +
|- style="vertical-align:top;color:#FF6600;background-color:#FCFCFC;"
 +
| [9:13] 
 +
| Christos&nbsp;Atlantis:
 +
| style="white-space:normal;"|your both welcome, its amazing to see what can be done
 +
<span id="chat309"></span>
 +
|- style="vertical-align:top;color:#99CC33;background-color:#F0F0F0;"
 +
| [9:13] 
 +
| Jam&nbsp;Meili:
 +
| style="white-space:normal;"|and yes, mono is a great improvement even it has some beginning problems (that will sure be fixed)
 +
<span id="chat310"></span>
 +
|- style="vertical-align:top;color:#FF9900;background-color:#FCFCFC;"
 +
| [9:13] 
 +
| Babbage&nbsp;Linden:
 +
| style="white-space:normal;"|ok, we should wrap up there i think
 +
<span id="chat311"></span>
 +
|- style="vertical-align:top;color:#FF9900;background-color:#FCFCFC;"
 +
| [9:13] 
 +
| Babbage&nbsp;Linden:
 +
| style="white-space:normal;"|so gabriel and i can get back to fixing bugs
 +
<span id="chat312"></span>
 +
|- style="vertical-align:top;color:#FF6600;background-color:#F0F0F0;"
 +
| [9:14] 
 +
| Christos&nbsp;Atlantis:
 +
| style="white-space:normal;"|ty for for your time
 +
<span id="chat313"></span>
 +
|- style="vertical-align:top;color:#FF9900;background-color:#FCFCFC;"
 +
| [9:14] 
 +
| Babbage&nbsp;Linden:
 +
| style="white-space:normal;"|if you find any problems, please file them in to jira
 +
<span id="chat314"></span>
 +
|- style="vertical-align:top;color:#33FFCC;background-color:#F0F0F0;"
 +
| [9:14] 
 +
| Imaze&nbsp;Rhiano:
 +
| style="white-space:normal;"|ya...and I need to go shopping new clothes... :P
 +
<span id="chat315"></span>
 +
|- style="vertical-align:top;color:#FF9900;background-color:#FCFCFC;"
 +
| [9:14] 
 +
| Babbage&nbsp;Linden:
 +
| style="white-space:normal;"|and we'll get on them as soon as possible
 +
<span id="chat316"></span>
 +
|- style="vertical-align:top;color:#66FF33;background-color:#F0F0F0;"
 +
| [9:14] 
 +
| Nock&nbsp;Forager:
 +
| style="white-space:normal;"|Thanks for very interestin meeting :)
 +
<span id="chat317"></span>
 +
|- style="vertical-align:top;color:#FF9900;background-color:#FCFCFC;"
 +
| [9:14] 
 +
| Babbage&nbsp;Linden:
 +
| style="white-space:normal;"|and if you see a repro for http://jira.secondlife.com/browse/SVC-2908
 +
<span id="chat318"></span>
 +
|- style="vertical-align:top;color:#FF9900;background-color:#FCFCFC;"
 +
| [9:14] 
 +
| Babbage&nbsp;Linden:
 +
| style="white-space:normal;"|please let us know
 +
<span id="chat319"></span>
 +
|- style="vertical-align:top;color:#FF6600;background-color:#F0F0F0;"
 +
| [9:14] 
 +
| Christos&nbsp;Atlantis:
 +
| style="white-space:normal;"|nice seeing you all here
 +
<span id="chat320"></span>
 +
|- style="vertical-align:top;color:#00CC33;background-color:#FCFCFC;"
 +
| [9:14] 
 +
| Miya&nbsp;Watanabe:
 +
| style="white-space:normal;"|thank you for the meeting
 +
<span id="chat321"></span>
 +
|- style="vertical-align:top;color:#FF9900;background-color:#F0F0F0;"
 +
| [9:14] 
 +
| Babbage&nbsp;Linden:
 +
| style="white-space:normal;"|hopefully i'll see you all here next week
 +
<span id="chat322"></span>
 +
|- style="vertical-align:top;color:#FF9900;background-color:#F0F0F0;"
 +
| [9:14] 
 +
| Babbage&nbsp;Linden:
 +
| style="white-space:normal;"|thanks for coming
 +
<span id="chat323"></span>
 +
|- style="vertical-align:top;color:#0099CC;background-color:#FCFCFC;"
 +
| [9:14] 
 +
| Gabriel&nbsp;Linden:
 +
| style="white-space:normal;"|thanks, and cya'all around
 +
<span id="chat324"></span>
 +
|- style="vertical-align:top;color:#66FF99;background-color:#F0F0F0;"
 +
| [9:15] 
 +
| Tegg&nbsp;Bode:
 +
| style="white-space:normal;"|Thanks both of you for your efforts :)
 +
<span id="chat325"></span>
 +
|- style="vertical-align:top;color:#336633;background-color:#FCFCFC;"
 +
| [9:15] 
 +
| Creem&nbsp;Pye:
 +
| style="white-space:normal;"|thanks for your help!
 +
<span id="chat326"></span>
 +
|- style="vertical-align:top;color:#33FFCC;background-color:#F0F0F0;"
 +
| [9:16] 
 +
| Imaze&nbsp;Rhiano:
 +
| style="white-space:normal;"|does Mono have metaobject in Jita?
 +
<span id="chat327"></span>
 +
|- style="vertical-align:top;color:#FF9900;background-color:#FCFCFC;"
 +
| [9:17] 
 +
| Babbage&nbsp;Linden:
 +
| style="white-space:normal;"|yes
 +
<span id="chat328"></span>
 +
|- style="vertical-align:top;color:#66FF33;background-color:#F0F0F0;"
 +
| [9:17] 
 +
| Nock&nbsp;Forager:
 +
| style="white-space:normal;"|ah Babbage, Don't you mind if I put this office hour log on your wiki profile page?
 +
<span id="chat329"></span>
 +
|- style="vertical-align:top;color:#FF9900;background-color:#FCFCFC;"
 +
| [9:17] 
 +
| Babbage&nbsp;Linden:
 +
| style="white-space:normal;"|http://jira.secondlife.com/browse/SVC-1276
 +
<span id="chat330"></span>
 +
|- style="vertical-align:top;color:#FF9900;background-color:#FCFCFC;"
 +
| [9:17] 
 +
| Babbage&nbsp;Linden:
 +
| style="white-space:normal;"|is the beta jira
 +
<span id="chat331"></span>
 +
|- style="vertical-align:top;color:#FF9900;background-color:#FCFCFC;"
 +
| [9:17] 
 +
| Babbage&nbsp;Linden:
 +
| style="white-space:normal;"|nock, that's fine
 +
<span id="chat332"></span>
 +
|- style="vertical-align:top;color:#FF9900;background-color:#FCFCFC;"
 +
| [9:17] 
 +
| Babbage&nbsp;Linden:
 +
| style="white-space:normal;"|it will save me a job :-)
 +
<span id="chat333"></span>
 +
|- style="vertical-align:top;color:#FF9900;background-color:#FCFCFC;"
 +
| [9:17] 
 +
| Babbage&nbsp;Linden:
 +
| style="white-space:normal;"|i'll leave my bear here
 +
<span id="chat334"></span>
 +
|- style="vertical-align:top;color:#66FF33;background-color:#F0F0F0;"
 +
| [9:17] 
 +
| Nock&nbsp;Forager:
 +
| style="white-space:normal;"|:)
 +
<span id="chat335"></span>
 +
|- style="vertical-align:top;color:#FF9900;background-color:#FCFCFC;"
 +
| [9:17] 
 +
| Babbage&nbsp;Linden:
 +
| style="white-space:normal;"|to auto return in 15 minutes
 +
<span id="chat336"></span>
 +
|- style="vertical-align:top;color:#FF6600;background-color:#F0F0F0;"
 +
| [9:17] 
 +
| Christos&nbsp;Atlantis:
 +
| style="white-space:normal;"|:)
 +
<span id="chat337"></span>
 +
|- style="vertical-align:top;color:#FF9900;background-color:#FCFCFC;"
 +
| [9:18] 
 +
| Babbage&nbsp;Linden:
 +
| style="white-space:normal;"|there you go
 +
<span id="chat338"></span>
 +
|- style="vertical-align:top;color:#FF9900;background-color:#FCFCFC;"
 +
| [9:18] 
 +
| Babbage&nbsp;Linden:
 +
| style="white-space:normal;"|should be copyable
 +
<span id="chat339"></span>
 +
|- style="vertical-align:top;color:#FF9900;background-color:#FCFCFC;"
 +
| [9:18] 
 +
| Babbage&nbsp;Linden:
 +
| style="white-space:normal;"|or you can buy it for 0L$
 +
<span id="chat340"></span>
 +
|- style="vertical-align:top;color:#FF6600;background-color:#F0F0F0;"
 +
| [9:18] 
 +
| Christos&nbsp;Atlantis:
 +
| style="white-space:normal;"|AWSOME
 +
<span id="chat341"></span>
 +
|- style="vertical-align:top;color:#FF6600;background-color:#F0F0F0;"
 +
| [9:18] 
 +
| Christos&nbsp;Atlantis:
 +
| style="white-space:normal;"|ty :)
 +
<span id="chat342"></span>
 +
|- style="vertical-align:top;color:#FF9900;background-color:#FCFCFC;"
 +
| [9:18] 
 +
| Babbage&nbsp;Linden:
 +
| style="white-space:normal;"|ok, see you all next week
 +
<span id="chat343"></span>
 +
|- style="vertical-align:top;color:#33FFCC;background-color:#F0F0F0;"
 +
| [9:19] 
 +
| Imaze&nbsp;Rhiano:
 +
| style="white-space:normal;"|bye
 +
<span id="chat344"></span>
 +
|- style="vertical-align:top;color:#66FFCC;background-color:#FCFCFC;"
 +
| [9:19] 
 +
| Keimar&nbsp;Kuhn:
 +
| style="white-space:normal;"|bye
 +
|}

Revision as of 02:34, 5 September 2008

Transcript of Linden's office hours:

[8:01] Babbage Linden: hi nick

[8:01] Babbage Linden: hi becky

[8:01] Nock Forager: Hi Babbaage

[8:01] Babbage Linden: nock, sorry

[8:01] Nock Forager: NP, everybody misspelled at first. :)

[8:02] Babbage Linden: thanks for coming

[8:02] Nock Forager: hmm, acctually I'm not a good scripter. Here to listen some update infor about Mono...

[8:03] Babbage Linden: that's fine

[8:03] Nock Forager: Bugs differences bitween LSL2 and Mono.

[8:03] Babbage Linden: i'll wait a few minutes for people to turn up, then give an overview of where we are

[8:04] Fake Fitzgerald: hi

[8:04] Babbage Linden: hi fake

[8:04] Nock Forager: lol everybody fall

[8:04] Becky Pippen: wheeee

[8:04] Babbage Linden: it's possible to make it across if you're lucky

[8:04] Fake Fitzgerald: I didn't fall

[8:05] Babbage Linden: hi miya

[8:05] Creem Pye: thanks

[8:05] Miya Watanabe: hello

[8:05] Creem Pye: howdy

[8:06] Babbage Linden: hi creem

[8:06] Nock Forager: Hi

[8:06] Fake Fitzgerald: hi

[8:06] Babbage Linden: let's give people a couple more minutes, then i'll start

[8:06] Babbage Linden: i'll ping the Mono groups too

[8:08] Babbage Linden: so, here's where we are with 1.24

[8:09] Babbage Linden: we had some problems initially with a debug server build, which was causing problems with 1.24.1

[8:09] Babbage Linden: then 1.24.2 fixed a number of crash bugs with features other than mono

[8:09] Babbage Linden: and 1.24.3

[8:10] Babbage Linden: after looking at the crash bugs, the next priority was issues that affect both LSL and Mono scripts

[8:10] Babbage Linden: as these affect existing content

[8:11] Babbage Linden: 1.24.4 which we're rolling out now fixed a problem with LSL script scheduling that was causing state_exit events to run slowly

[8:11] Babbage Linden: as well as state changes

[8:11] Babbage Linden: with scripting running on the original scripting engine

[8:11] Creem Pye: ah, so there will no longer be a 22ms delay for state changes?

[8:11] Babbage Linden: as well as in some cases the order of timer events vs state_exit and state_entry events

[8:11] Babbage Linden: correct creem

[8:12] Babbage Linden: what was happening in 1.24.1-3 is that scripts were yielding when a state change was pending

[8:12] Babbage Linden: so, you could only do 1 state change per time slice and so per frame

[8:13] Babbage Linden: also, because scripts were yielding all the time when state changes were pending, that slowed down state entry a lot

[8:13] Babbage Linden: as a sim running at 45 hz has a frame time of 22ms, that made it look like state changes were taking longer

[8:13] Babbage Linden: they weren't, they were just being gated by the frame rate

[8:13] Creem Pye nods

[8:14] Babbage Linden: also, the event ordering was changing as previously state_exit and state_entry events were being run immediately

[8:14] Babbage Linden: in 1.23 and before

[8:14] Babbage Linden: when the script was yielding on state change pending, it gave a timer event the chance to sneak in before the state_entry/exit event

[8:15] Babbage Linden: 1.24.4 also fixes a problem with llEmail

[8:15] Babbage Linden: that caused email to not be delivered to a script under some circumstances

[8:16] Babbage Linden: and fixed a problem with prepending to a list having side effects

[8:16] Babbage Linden: we're now moving on to looking at problems which only affect Mono scripts

[8:16] Creem Pye: will scripts need to be reset to take advantage of these fixes?

[8:17] Babbage Linden: we'd really like to be able to get a good repro for http://jira.secondlife.com/browse/SVC-2908

[8:17] Babbage Linden: which i think is actually a number of separate issues

[8:17] Babbage Linden: but we haven't been able to repro any of them yet

[8:18] Babbage Linden: we're currentlly looking at http://jira.secondlife.com/browse/SVC-2751

[8:18] Babbage Linden: which has a good repro

[8:18] Babbage Linden: and then will probably tackle the other Mono specific bugs in http://jira.secondlife.com/browse/SVC-1276

[8:18] Babbage Linden: if nothing else comes up in the meantime

[8:18] Babbage Linden: creem, no you don't need to reset scripts to see the fixes to the scheduler

[8:19] Babbage Linden: the changes are in the simulator code

[8:19] Babbage Linden: and will take effect on running scripts

[8:19] Creem Pye: hm the svc-2751 repro could use some llSleeop functions I think

[8:20] Creem Pye: sometimes chat arrives out of order, even within the same event

[8:20] Babbage Linden: yes, agreed

[8:20] Creem Pye: (but I guess if you had another object in the same sim listening, it should always receive messages in the correct order)

[8:20] Babbage Linden: moon metty tried it with llSleep(3) calls and still saw the problem

[8:21] Babbage Linden: and http://jira.secondlife.com/browse/SVC-2365 suggests there are other problems with scripts being reset

[8:21] Babbage Linden: so that's where we are now

[8:22] Babbage Linden: new crash bugs seem to have been fixed

[8:22] Babbage Linden: LSL2 is mostly working as it was

[8:22] Babbage Linden: and we're going to look at the Mono only issues next

[8:22] Babbage Linden: sound reasonable?

[8:22] Creem Pye: sure

[8:23] Creem Pye: I have a question - will the state change fixes in 1.24 affect the execution speed of on_rez at all?

[8:23] Creem Pye: oops 1.24.4

[8:23] Babbage Linden: no

[8:23] Becky Pippen: sounds like you've accomplished a lot of fixes already! Those reset issues are nasty.... hope they are easy to find and fix.

[8:23] Babbage Linden: are you seeing rez behave more slowly for scripts running on the original scripting engine creem?

[8:24] Babbage Linden: (Mono scripts rez more slowly as they do more work)

[8:24] Creem Pye: yeah, running slightly more slowly (~1 frame), and also using up slightly more script time than LSL2

[8:25] Babbage Linden: hi zena

[8:25] Creem Pye: the application I was looking at was scripted bullets, and they "initialize" on rez to become enabled. And with their speed, the execution speed of on_rez affects the minimum range

[8:25] Zena Juran: hiyas everyone :-)

[8:25] Babbage Linden: the on_rez handler should run fine

[8:26] Creem Pye: I'm using llSetName() in that function, so maybe the UTF16 being used in Mon ois causing the slight slowdown

[8:26] Babbage Linden: but Mono has to check a digital signature when it first rezes an assembly which takes longer

[8:26] Creem Pye: er llSetObjectName

[8:26] Babbage Linden: but with bullets you are probably rezzing the same script repeatedly, so should only see that hit the first time

[8:26] Babbage Linden: Mono also has to do more set up of objects than LSL

[8:27] Creem Pye: ah I see

[8:27] Babbage Linden: so rezzing can take slightly longer

[8:27] Becky Pippen: are there any tricks to minimize that setup time?

[8:27] Babbage Linden: make sure you do as much script sharing as possible

[8:28] Babbage Linden: it minimises the time the simulator spends checking signatures

[8:28] Babbage Linden: and saves memory too

[8:28] Babbage Linden: so, if you have a display with lots of XYText scripts for example

[8:28] Babbage Linden: copy the same compiled script in to the object many times

[8:29] Babbage Linden: instead of using recompile scripts in selection

[8:29] Creem Pye: in terestsing

[8:29] Babbage Linden: which will create a new XYText assembly for each script

[8:29] Nock Forager: hmhm

[8:29] Babbage Linden: if everyone takes copies of the same script when they use popular scripts

[8:30] Babbage Linden: sharing will happen between objects too

[8:30] Babbage Linden wants to see only one XYText assembly per simulator

[8:30] Creem Pye: btw since it seems that scripts in an avatar's inventory remember if they were compiled as LSL2 or Mono, it might be nice to have a UI option in the script editor, when the script is in avatar inventory

[8:30] Creem Pye: (the same "Mono" checkbox, I guess)

[8:31] Babbage Linden: that's tricky, as the simulator populates the checkbox by examining the bytecode

[8:31] Babbage Linden: the dataserver doesn't know if a script in your inventory is mono or lsl

[8:32] Babbage Linden: we could extend the database to store that information

[8:32] Creem Pye: but the script in your inventory has its bytecode attached?

[8:32] Babbage Linden: but it would be considerably more work

[8:33] Babbage Linden: also, knowing whether nested objects contain mono scripts is even harder

[8:33] Babbage Linden: so showing a mono checkbox for objects is really hard

[8:33] Babbage Linden: you would have to recurse through the object checking the information for all scripts

[8:34] Becky Pippen: makes sense

[8:34] Babbage Linden: so, it would be nice to have

[8:34] Creem Pye: hm yeah, nested objects also often don't reflect the true permissions

[8:34] Babbage Linden: but a lot of work

[8:34] Babbage Linden: hi tegg

[8:34] Tegg Bode: Hi All

[8:35] Creem Pye: hello

[8:35] Babbage Linden: any other questions?

[8:35] Nock Forager: Hi Tegg, Imaze, Keimar

[8:35] Babbage Linden: how have peoples experiences with mono been?

[8:35] Babbage Linden: hi imaze

[8:35] Keimar Kuhn: Hi

[8:35] Imaze Rhiano: hi

[8:35] Creem Pye: very smooth sailing so far. my only annoyance was that batch-converting scripts would enable scripts that were disabled

[8:36] Babbage Linden: ah, interesting

[8:36] Babbage Linden: could you file that as a bug please?

[8:36] Creem Pye: sure

[8:36] Babbage Linden: if it's not already in jira

[8:36] Babbage Linden: i haven't seen that yet

[8:37] Creem Pye: sure thing

[8:37] Babbage Linden: hi gabriel

[8:37] Gabriel Linden: hiya

[8:37] Gabriel Linden: hows it going?

[8:38] Imaze Rhiano: there has been also some negetive noise about Mono in scripter groups

[8:38] Imaze Rhiano: saying that mono is crashing sim, consuming more processor time, etc...

[8:39] Babbage Linden: i'm not aware of any mono crash bugs at this point

[8:39] Babbage Linden: i'd be interested in seeing mono using more processor time too

[8:39] Gabriel Linden: yeah

[8:39] Babbage Linden: it may use slightly more when scripts are doing nothing

[8:39] Babbage Linden: as mono scripts check whether they need to migrate when they're run

[8:40] Imaze Rhiano: I tried to ask from them what they are talking about - but no one didn't provide list of crash bugs or examples

[8:40] Tegg Bode: I am getting a lot more crashing this week on both RC and 1.20, and not using mono scripts yet :)

[8:40] Babbage Linden: there have been problems with the web services this week

[8:40] Babbage Linden: that have caused concurrency drops

[8:40] Creem Pye: heavy text processing could be slower with mono, right?

[8:41] Babbage Linden: but we're seeing a pretty low crash rate with 1.24.4.95600

[8:41] Creem Pye: like llList2CSV(llCSV2List()) of something really long

[8:41] Gabriel Linden: so these might be coincidence, as many people are thinking about mono atm

[8:41] Babbage Linden: mono has to convert strings to utf-8 when passing them to library calls implemented in C++

[8:42] Babbage Linden: that could take longer

[8:42] Babbage Linden: which is the common case

[8:42] Babbage Linden: but in generally Marshalling data from Mono to C++ is very fast

[8:42] Imaze Rhiano: what about those reports about using more cpu time? could it be that all SIM monitor tools are not yet optimized for Mono?

[8:43] Babbage Linden: some of the library calls have been reimplemented in managed code and should run much faster there

[8:43] Babbage Linden: lists are now implemented as ArrayLists for Mono scripts

[8:43] Babbage Linden: so indexing in to them should be constant time instead of requiring a search

[8:43] Babbage Linden: for example

[8:44] Babbage Linden: i'd like to see examples where running Mono scripts use more time than LSL"

[8:44] Babbage Linden: i haven't seen any examples yet

[8:44] Gabriel Linden: its very unlikely you'd see a huge jump in cpu time imho

[8:44] Babbage Linden: just idle scripts using up slightly more time

[8:45] Creem Pye: maybe the performance hit adds up if there are thousands of idle scripts in a sim

[8:45] Christos Atlantis: does that idle time affect the sim, if there are alot of idle scripts , like in a furniture store that has poseballs in almost every piece

[8:45] Bartlee Arai: It would be nice if you had a suite where you could do compartive analysis of mono to lsl and track local maxima

[8:46] Babbage Linden: imaze, most of those are now fixed in 1.24.4

[8:46] Babbage Linden: see the mono meta issue in jira for the status

[8:46] Bartlee Arai: comparative*

[8:46] Imaze Rhiano: ok - that was list I received last night

[8:46] Imaze Rhiano: so - it was bit outdated info then

[8:46] Babbage Linden: creem, long term, idle scripts shouldn't consume any CPU time

[8:47] Jam Meili: do thousand idle scripts contribute then more to sim lag then before?

[8:47] Babbage Linden: they should be moved to a non-running scripts list

[8:47] Babbage Linden: and only become runnable when they have pending events

[8:47] Babbage Linden: we have plans to address that

[8:47] Babbage Linden: but it may not be for a while

[8:48] Babbage Linden: in the meantime, i doubt the extra work mono scripts do would have a noticable effect

[8:48] Babbage Linden: even with 1000s of them in a sim

[8:49] Christos Atlantis: I heard mono scripts taste like chicken

[8:49] Christos Atlantis: to many rumours

[8:49] Babbage Linden: yes, agreed

[8:50] Babbage Linden: mono was the biggest change in 1.24

[8:50] Nock Forager: yes, many rumours :)

[8:50] Christos Atlantis: most are saying we should not recomplie

[8:50] Babbage Linden: so is being cited as the cause of many things

[8:50] Bartlee Arai: How long before Mono is where you think it needs to be, ball park?

[8:50] Babbage Linden: but mostly, if you're not running mono scripts, your problem is unlikely to be mono

[8:50] Babbage Linden: and for most people, most of the time, mono scripts will work fine

[8:51] Bartlee Arai: the good old 90 10

[8:51] Jam Meili: why it seems mono affects also old scripts? is that mono-related or just bugs that happened in modified servercode?

[8:51] Christos Atlantis: one small thing I did notice, is that the speed of the scripts is a bit faster when running a swarm script, it made the pet move faster

[8:51] Gabriel Linden: we need good reproducable cases if issues are found, if everyone avoids recompilation we wont get them

[8:52] Babbage Linden: we left the original scripting engine alone as much as possible

[8:52] Babbage Linden: but we needed to make a few changes to allow mono to run alongside it

[8:52] Babbage Linden: the state change problems are a good example

[8:52] Babbage Linden: the old scripting engine interpretted 1 instruction at a time

[8:53] Babbage Linden: Mono executes small pieces of code at once

[8:53] Babbage Linden: so we had to change the script scheduling code to cope with both engines

[8:53] Christos Atlantis: one more dumb question, if I am the owner of a script and recompile it, will all others using my script have a there items recompiled also?

[8:53] Babbage Linden: and managed to subtly change script execution behaviour in the process

[8:54] Babbage Linden: christos, no

[8:54] Babbage Linden: only the copy you recompile

[8:54] Jam Meili: ok, so that "eps" in the statistics is referred to that pieces of code that run at once? or how should we interpret that?

[8:54] Babbage Linden: it's like saving a script to produce a new script

[8:54] Jam Meili: are that library calls in c# or something?

[8:54] Christos Atlantis: so we have to recompile every single script in our stores?

[8:54] Babbage Linden: other objects still reference the old bytecode asset and so don't change

[8:55] Babbage Linden: christos, if you want to create new versions of all of them yes

[8:55] Babbage Linden: if they share scripts, the better way is to recompile 1

[8:55] Babbage Linden: then copy the new scripts in to the others

[8:55] Babbage Linden: to get more bytecode sharing

[8:55] Babbage Linden: you'll also want to test all the objects to make sure they work after conversion too

[8:56] Christos Atlantis: I have 7000 pieces of furniture in 5 stores, that is a very big task

[8:56] Babbage Linden: christos, agreed

[8:56] Creem Pye: ko Babbage, I've created a Jira item for the batch script conversion bug: SVC-2987

[8:56] Babbage Linden: you need to decide whether converting the scripts inside makes sense

[8:56] Babbage Linden: thanks creem

[8:57] Babbage Linden: jam, the eps change was due to Mono running small pieces of code at once

[8:57] Babbage Linden: we have no way of counting instructions with Mono easily

[8:57] Christos Atlantis: ok, so if I do not convert, will the furniture ie (pose balls) stop working

[8:57] Jam Meili: each recompile creates a new c# assembly, so i guess it uses also more memory if we compile same scripts in each prims over and over, is that right?

[8:57] Babbage Linden: so, instead we count how many events the script it executing

[8:58] Babbage Linden: which can be compared between Mono scripts and scripts running on the original scripting engine (OSE from now on)

[8:58] Babbage Linden: christos, if you don't convert your scripts they will continue to run as before

[8:59] Christos Atlantis: ok, ty those where my main concerns, I can now make logical choices

[8:59] Babbage Linden: jam, if you keep compiling scripts over and over

[8:59] Babbage Linden: eventually Mono unloads them if they're not being referenced by a script

[9:00] Babbage Linden: so, you don't need to worry about that

[9:00] Babbage Linden: but, you should try to have as many objects reference each assembly as possible

[9:00] Babbage Linden: to minimise the numbers of assemblies that mono needs to keep around

[9:00] Jam Meili: hum i said it maybe wrong. i mean if i use the same script like in hudred prims and isntead of copying one compiled in all, if i would create a script in each and recompile the source, it would use like hundred times more memory?

[9:00] Babbage Linden: it doesn't know that scripts are the same just because they have the same source

[9:01] Babbage Linden: but if you drag compiled scripts in to objects, it knows that they are sharing

[9:01] Jam Meili: so we could tune our scripts in that way, what wasnt possible in the old engine?

[9:01] Babbage Linden: and only needs to keep 1 assembly in memory

[9:01] Creem Pye: it would be nice if the scripts had a checksum on the bytecode to check if they're identical

[9:01] Babbage Linden: the OSE didn't do any sharing

[9:01] Becky Pippen: Is OSE the new term for the LSL VM back end? It's the term that replaces awkward names like LS2VM, or LSL-LSO, or LSL2LSOVM... ?

[9:01] Babbage Linden: so, if you had 1000 bullets flying around

[9:01] Babbage Linden: each would use 16K

[9:02] Babbage Linden: with Mono, they might use 1K shared between them

[9:02] Babbage Linden: if all the guns contained copies of the same compiled script

[9:02] Christos Atlantis: will mono allow for you to implement use of other scripting and programing choices in SL?

[9:02] Creem Pye: creating the UUID of a script based on its sha-160 checksum would be nice =)

[9:02] Babbage Linden: christos, yest

[9:02] Christos Atlantis: :)

[9:02] Jam Meili: ok, thats great and hopefully will make combat sims and such to work better. is there another mono-related impriovement we could use to tune the usage of resources on a sim?

[9:02] Babbage Linden: it will allow us to enable other languages to script SL in the long term

[9:03] Babbage Linden: we have been careful to keep that option open while working on LSL on Mono

[9:03] Babbage Linden: but there is still more work to be done before we get there

[9:03] Christos Atlantis: well, my dream would be if I could see a game engine running inside SL

[9:04] Babbage Linden: jam, bytecode sharing is the big thing that you can do to help Mono work effeciently

[9:04] Christos Atlantis: that would make the possibilities endless, mini games inside SL like a WoW

[9:04] Babbage Linden: Christos, SL is like a game engine in many ways

[9:05] Babbage Linden: lots of game engines have scripting engines and physics engines like SL

[9:05] Babbage Linden: games like dark life have been WoW like games in SL for a long time

[9:05] Christos Atlantis: yes, but it lacks the tools to make a good platform for developing game play

[9:05] Creem Pye: one thing you'd need to do is give estate managers much more control over what avatars can do

[9:05] Babbage Linden: there are some missing features, agreed

[9:06] Creem Pye: like forbid external attachments, and maybe force an avatar to have a certain style of appearance

[9:06] Babbage Linden: and many people are building things other than games

[9:06] Babbage Linden: so, we need to be careful to keep the platform neutral

[9:06] Christos Atlantis: like being able to control movement of props in non linear routes

[9:06] Babbage Linden: and make extensions where they are most useful to the most people

[9:06] Imaze Rhiano: if you want game development for SL - then you need also better controls for texture usage and model/prim usage for SIM owners

[9:06] Creem Pye: yep

[9:07] Imaze Rhiano: but that is bit offtopic

[9:07] Babbage Linden: we want to enable the widest array of applications possible in SL

[9:07] Babbage Linden: but we have limited resources

[9:07] Babbage Linden: so have to be smart about prioritizing improvements

[9:07] Creem Pye: megasims would be a nice start :D

[9:08] Creem Pye is a vehicle creator

[9:08] Christos Atlantis: I think the number 1 with residents is stability, so I will agree with you, you need to keep it stable for a long period and understand it before adding more features

[9:09] Babbage Linden: and most of the effort at linden is working on stability

[9:09] Jam Meili: hehe megasims would require changes in alot of parts of the server- and viewercode as also to expect owners would use server resources wisely, i guess we should not expect that any time soon, it's not very realistically right now

[9:09] Babbage Linden: which is why the scripting improvements are relatively slow in coming

[9:09] Christos Atlantis: and scaleability is also something I would think will help

[9:09] Babbage Linden: Mono was mostly me working on my own until near the end of the project

[9:09] Christos Atlantis: wow

[9:09] Christos Atlantis: great job!

[9:09] Bartlee Arai: Nice

[9:09] Nock Forager: yup!

[9:09] Babbage Linden: help! i'm being beaten with a car

[9:09] Creem Pye: yep, it's working quite smoothly so far =)

[9:10] Creem Pye: Babbage, do you expect the script memory limit wil be raised in teh future?

[9:10] Creem Pye: it would be nice if objects could consolidate their functions to a single script

[9:10] Babbage Linden: gabriel, si, daveh, vektor and periapse did a lot of work over the last year too

[9:10] Christos Atlantis: I think I have skid marks on my forehead

[9:10] Tegg Bode: I think games would hae a better chance of working if we could reduce our continual downloading of textures by perhaps having a basic default texture set for walls & floors on our hard drives

[9:10] Creem Pye: (I imagine that without link messages etc, efficiency could be greatly improved)

[9:10] Babbage Linden: creem pye, that is also on our wish list

[9:10] Babbage Linden: proper script libraries

[9:11] Babbage Linden: so you can share code between scripts

[9:11] Babbage Linden: and develop general purpose libraries that can be used by other scripts

[9:11] Babbage Linden: instead of having to send them link messages

[9:11] Babbage Linden: or chat messages

[9:11] Creem Pye: even functions like llLinkParticleSystem() to set a particle system centered around a link in the object would be nice

[9:12] Creem Pye: instead of having to have a separate script in a child prim for particles, commanded by the main script through link messages

[9:12] Christos Atlantis: I have tried 5 times in my life to learn programing this is the closest to heaven for me, and for that I would like to thank you guys and the people that help in groups, like Jam and co

[9:12] Babbage Linden: glad to hear it christos!

[9:12] Jam Meili: uuh .. thank you :)

[9:12] Babbage Linden: :-)

[9:13] Bartlee Arai: will the old scripting engine be replaced eventually once transparency has been acheived?

[9:13] Gabriel Linden: teaching the world to code

[9:13] Christos Atlantis: your both welcome, its amazing to see what can be done

[9:13] Jam Meili: and yes, mono is a great improvement even it has some beginning problems (that will sure be fixed)

[9:13] Babbage Linden: ok, we should wrap up there i think

[9:13] Babbage Linden: so gabriel and i can get back to fixing bugs

[9:14] Christos Atlantis: ty for for your time

[9:14] Babbage Linden: if you find any problems, please file them in to jira

[9:14] Imaze Rhiano: ya...and I need to go shopping new clothes... :P

[9:14] Babbage Linden: and we'll get on them as soon as possible

[9:14] Nock Forager: Thanks for very interestin meeting :)

[9:14] Babbage Linden: and if you see a repro for http://jira.secondlife.com/browse/SVC-2908

[9:14] Babbage Linden: please let us know

[9:14] Christos Atlantis: nice seeing you all here

[9:14] Miya Watanabe: thank you for the meeting

[9:14] Babbage Linden: hopefully i'll see you all here next week

[9:14] Babbage Linden: thanks for coming

[9:14] Gabriel Linden: thanks, and cya'all around

[9:15] Tegg Bode: Thanks both of you for your efforts :)

[9:15] Creem Pye: thanks for your help!

[9:16] Imaze Rhiano: does Mono have metaobject in Jita?

[9:17] Babbage Linden: yes

[9:17] Nock Forager: ah Babbage, Don't you mind if I put this office hour log on your wiki profile page?

[9:17] Babbage Linden: http://jira.secondlife.com/browse/SVC-1276

[9:17] Babbage Linden: is the beta jira

[9:17] Babbage Linden: nock, that's fine

[9:17] Babbage Linden: it will save me a job :-)

[9:17] Babbage Linden: i'll leave my bear here

[9:17] Nock Forager: :)

[9:17] Babbage Linden: to auto return in 15 minutes

[9:17] Christos Atlantis: :)

[9:18] Babbage Linden: there you go

[9:18] Babbage Linden: should be copyable

[9:18] Babbage Linden: or you can buy it for 0L$

[9:18] Christos Atlantis: AWSOME

[9:18] Christos Atlantis: ty :)

[9:18] Babbage Linden: ok, see you all next week

[9:19] Imaze Rhiano: bye

[9:19] Keimar Kuhn: bye