Difference between revisions of "Talk:ACTIVE"

From Second Life Wiki
Jump to navigation Jump to search
(why does ACTIVE 's behaviour vary between functions?)
 
m
Line 1: Line 1:
I honestly don't understand why this is implemented to return BOTH scripted and physical objects in sensor calls. It would make a tiny amount of sense if it behaved the same way in llDetectedType, indicating there is some sort of technical hurdle in separating scripted from physical, but it's not. It would be super helpful to grid health if this could be changed so ACTIVE represents only physical objects when used in sensor calls, or even to implement PHYS. Having a sensor return all physical AND all scripted, especially with a return limit (16, isn't it?) hamstrings the ability to check an area for physical objects, triggering the sensor event full of junk that has to be filtered out with DetectedType or GetObjectDetails checks, and even then will not work properly.  - Icra Nosferatu
I honestly don't understand why this is implemented to return BOTH scripted and physical objects in sensor ([[llSensor]] and [[llSensorRepeat]]) calls. It would make a tiny amount of sense if it behaved the same way in [[llDetectedType]], indicating there is some sort of technical hurdle in separating scripted from physical, but it's not. It would be super helpful to grid health if this could be changed so [[ACTIVE]] represents only physical objects when used in sensor calls, or even to implement PHYS. Having a sensor return all physical AND all scripted, especially with a return limit (16, isn't it?) hamstrings the ability to check an area for physical objects, triggering the sensor event full of junk that has to be filtered out with [[llDetectedType]] or [[llGetObjectDetails]] checks, and even then will not work properly.  {{Unsigned|Icra Nosferatu}}
 
:You could use [[llGetAgentSize]] instead for the filter checks against scripted items. If you're checking for agents though, maybe try [[llGetAgentList]]? -- [[User:Kireji Haiku|Kireji Haiku]] 12:03, 12 December 2013 (PST)

Revision as of 13:03, 12 December 2013

I honestly don't understand why this is implemented to return BOTH scripted and physical objects in sensor (llSensor and llSensorRepeat) calls. It would make a tiny amount of sense if it behaved the same way in llDetectedType, indicating there is some sort of technical hurdle in separating scripted from physical, but it's not. It would be super helpful to grid health if this could be changed so ACTIVE represents only physical objects when used in sensor calls, or even to implement PHYS. Having a sensor return all physical AND all scripted, especially with a return limit (16, isn't it?) hamstrings the ability to check an area for physical objects, triggering the sensor event full of junk that has to be filtered out with llDetectedType or llGetObjectDetails checks, and even then will not work properly. —The preceding unsigned comment was added by Icra Nosferatu

You could use llGetAgentSize instead for the filter checks against scripted items. If you're checking for agents though, maybe try llGetAgentList? -- Kireji Haiku 12:03, 12 December 2013 (PST)