Difference between revisions of "Talk:LlSensorRepeat"

From Second Life Wiki
Jump to navigation Jump to search
Line 5: Line 5:
It seems to me that if you use 0 as your 'type', it never runs sensor() or no_sensor(). Why is this? How can I make it detect everything?
It seems to me that if you use 0 as your 'type', it never runs sensor() or no_sensor(). Why is this? How can I make it detect everything?
:Try <code>ACTIVE | PASSIVE | AGENT</code> -- [[User:Strife Onizuka|Strife Onizuka]] 10:10, 17 May 2008 (PDT)
:Try <code>ACTIVE | PASSIVE | AGENT</code> -- [[User:Strife Onizuka|Strife Onizuka]] 10:10, 17 May 2008 (PDT)
The initial description is misleading: "Performs a single scan [..] and repeats every '''rate''' seconds." In fact, it lies dormant for '''rate''' seconds after the call, and then fires the first scan. [[User:Tali Rosca|Tali Rosca]] 10:31, 15 October 2008 (PDT)

Revision as of 10:31, 15 October 2008

Scanning adjacent regions

If I remember correctly using llSensorRepeat you can get sensor data from adjacent regions every (I think) 5 seconds. Should we include this information in the article? This does not affect llSensor. I am not sure if this has been fixed in previous updates. --TxMasterG Ping 15:06, 10 April 2007 (PDT)

I've not heard of this restriction before but if it can be verified then it belongs in the caveats section. I have not done worked with llSensorRepeat in a long time. -- Strife Onizuka 20:18, 10 April 2007 (PDT)

It seems to me that if you use 0 as your 'type', it never runs sensor() or no_sensor(). Why is this? How can I make it detect everything?

Try ACTIVE | PASSIVE | AGENT -- Strife Onizuka 10:10, 17 May 2008 (PDT)

The initial description is misleading: "Performs a single scan [..] and repeats every rate seconds." In fact, it lies dormant for rate seconds after the call, and then fires the first scan. Tali Rosca 10:31, 15 October 2008 (PDT)