Difference between revisions of "Talk:Stopwatch(float precision time)"
(comment feasability of the idea, and needs a jira request not a wiki page) |
(→Wouldn't work.: new section) |
||
| Line 8: | Line 8: | ||
--[[User:Stickman Ingmann|Stickman]] 15:55, 5 July 2008 (PDT) | --[[User:Stickman Ingmann|Stickman]] 15:55, 5 July 2008 (PDT) | ||
== Wouldn't work. == | |||
No aspects of LSL scripts are executed on the client. Since llSetTimerEvent is (roughly) accurate to 1/45ths of a second, which is the maximum granularity of script execution, that is all you're going to get. [[User:Nelson Jenkins|Nelson Jenkins]] 19:57, 9 July 2014 (PDT) | |||
Latest revision as of 19:57, 9 July 2014
I do not see a JIRA on this. The wiki is probably not the best place to make feature requests. I suggest submitting an official one on JIRA.
If the script was partway moved onto the client, then you would lose the precision you seek as the server needs to transmit data (1-500ms+) telling the client it's time to trigger it. If it was wholly moved, then different clients would have different starting times and it wouldn't sync up (not to mention that a lot of what a script does can't be handled purely client side, as the server needs to be the final say on how many things behave). So I'm not sure how this could be done.
Also, scripts are one of the few things that are relatively well protected. Animations, textures, objects, and sounds all get downloaded to the client. But scripts are "safely" on the server. I rather like it that way, and would be against the ability to move all or part of the script execution to the client.
If you're still interested, submit a JIRA request and see what Linden Lab and The Community has to say about it.
--Stickman 15:55, 5 July 2008 (PDT)
Wouldn't work.
No aspects of LSL scripts are executed on the client. Since llSetTimerEvent is (roughly) accurate to 1/45ths of a second, which is the maximum granularity of script execution, that is all you're going to get. Nelson Jenkins 19:57, 9 July 2014 (PDT)