- Forums
- :
- Creation Forum
- :
- LSL Scripting
- :
- Re: best way to monitor sensor-script lag?
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic to the Top
- Bookmark
- Subscribe
- Printer Friendly Page
best way to monitor sensor-scr ipt lag?
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Email to a Friend
- Report Inappropriate Content
11-15-2012 06:19 PM
I recently put 16 sensors carpets (size 50m x 50m) with the function of record who entered the site and are working perfectly.
My question is:
what is the best way to monitor whether these sensors are causing slowness in my region?
Thanks
Re: best way to monitor sensor-scr ipt lag?
[ Edited ]
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Email to a Friend
- Report Inappropriate Content
Reply to helsen - view message
11-15-2012 07:58 PM - edited 11-15-2012 08:54 PM
nowadays , nobody scripts a sim-monitor with sensors to record who enters and who leaves
Either we use a phantom invisible mega prim at the size of your parcel with a collision_start and collision_end event ( if there are no rez and no object entry in the parcel) , either we use the function llGetAgentList inside a timer
You may call too llGetRegionAgentCount to detect some changes in the sim and reduce the number of calls to llGetAgentList.
And don t call some functions if you may call them later once time when you generate the report .
For instance , if you want the names of the people , don t call some function to collect the names and don t store the names in your script : but wait the end of day and use later llRequestUsername with your stored keys
Re: best way to monitor sensor-scr ipt lag?
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Email to a Friend
- Report Inappropriate Content
Reply to Miranda Umino - view message
11-17-2012 05:14 PM
I somewhat doubt that periodicly converting keys to names via llRequestUsername() is more efficient than immediately acquiring a name via llKey2Name(). The latter method doesn't use any resources to speak of while the former returns the result via dataserver. Besides, storing names takes less memory than storing keys as most names are shorter than 36 bytes so more could be stored.
Re: best way to monitor sensor-scr ipt lag?
[ Edited ]
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Email to a Friend
- Report Inappropriate Content
Reply to Ela Talaj - view message
11-17-2012 08:21 PM - edited 11-18-2012 06:36 AM
While I agree about grabbing the names right away, why llKey2Name rather than llGetUsername?
Re: best way to monitor sensor-scr ipt lag?
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Email to a Friend
- Report Inappropriate Content
Reply to Innula Zenovka - view message
11-18-2012 11:37 AM
Hmm... I dunno... guess just a matter of preference. I would suspect llGetUsername() is a wrapper for llKey2Name() anyways because that's how I would've implemented it with llKey2Name() already existing but who can read minds of LL programmers... ![]()

