Increasing Detection Range (By Meter)

[joniveehernandez]

Hi Guys sorry not sure if this is duplicate post where it's detecting agent topic also:

http://community.secondlife.com/t5/LSL-Scripting/Detect-All-Agents-In-Multiple-Parcels/m-p/1776211/highlight/false#M14841

I look for some Security Orb System in Marketplace I saw that there's a certain feature using meter range. how other Security Orb System do the detection range expand higher where the sensor can only reach a limit of 96.0 meters? I'm thinking are rezzing child objects to extend the sensor range? or there's other way of maximizing the detection range?

[Cerise Sorbet]

Yes, that was the traditional way, to use either a moving object or multiple stationary ones to increase the range.

For most applications it would now be easier to use llGetAgentList. That function has only been around for a few months, so most offerings on the market are probably still using sensors.

[joniveehernandez]

Yes I use 4 modes of detection: Region, Parcel, Sim-Wide and optionally they can set range by meter, if they only want to protect a certain part of the parcel.

[Miranda Umino]

It s useless to use a range detection for an Orb Security :

let s guess the orb is on the ground at Z = 20 m . 

One avatar come on the parcel exactly at the same position X,Y but at the altitude Z = 4000m, so the distance is 3980 meters

To limit the range  won t detect him ...

 

If your customers use the NO-FLY tag on their parcel , and have for instance several skyboxes at different altitudes , and request you to detect which skybox has traffic ,  it will be better to check the altitudes of the avatars and not the distances.

If your customers don t use the NO-FLY tag , it makes no sense to check the altitude of avatars.

In the first case , for every elements of the result list from llGetAgentList , you call llGetObjectDetails(OBJECT_POS) and you check the Z altitude from the vector 

 

 Give up this awful laggy  idea to rez several sensors on the parcel .To rez objects is more laggy than to do some list operations ; to move object to the spot after the rez is more laggy than to do some list operations . It s by far the worst solution. And generally , people are closed to be able to chat , so with a big sensor  , you will need several operations to detect if there are are more than 16 avatars in your sensor range . Awful .

 

 

[joniveehernandez]

Can you tell me guys how the SWA Security Orb and other orbs increase the range of there detection to 4096? if these orbs used sensor how can they manage to extend the range from maximum of 96.0 range to 4096? if not using range, how they do it?

[Innula Zenovka]

If they have any sense they are now doing it with llGetAgentList, which will list everyone on the parcel or sim.

If you want then to filter the results by range, you simply loop through the keys it returns, checking llGetObjectDetails(id,[OBJECT_POS]) and seeing how far away the avatar is in each case.

 

[joniveehernandez]

Thank you Innula you got it. That makes sense now to me by checking the distance of the object and the agent.

[joniveehernandez]

Innula I follow your suggestions checking distance, what is the x position is match in the range but the y position is not? what i mean is how to check it diagonally?

[Innula Zenovka]

If you are simply trying to discover how far away someone is, then llVecDist is all you need.

[joniveehernandez]

Oh my I guess I need to reveiw more functions in wiki I never thought there's a function like this. I made up multiple lines just to achieve this but it's easy like 1 2 3 using llVectDist. ~Thanks appreciated.