LlVolumeDetect

Template:Needs Translation/LSL/de Template:Needs Translation/LSL/es Template:Needs Translation/LSL/el Template:Needs Translation/LSL/he Template:Needs Translation/LSL/it Template:Needs Translation/LSL/ko Template:Needs Translation/LSL/nl Template:Needs Translation/LSL/hu Template:Needs Translation/LSL/no Template:Needs Translation/LSL/da Template:Needs Translation/LSL/sv Template:Needs Translation/LSL/tr Template:Needs Translation/LSL/pl Template:Needs Translation/LSL/pt Template:Needs Translation/LSL/ru Template:Needs Translation/LSL/th Template:Needs Translation/LSL/uk Template:Needs Translation/LSL/zh-Hans Template:Needs Translation/LSL/zh-Hant

/LSL

VolumeDetect

llVolumeDetect

Summary

2/3 Bugs

Function: llVolumeDetect( integer detect );

248	Function ID
0.0	Forced Delay
10.0	Energy

If detect is TRUE, VolumeDetect is enabled, physical object and avatars can pass through the object.

• integer

detect

–

TRUE enables, FALSE (default) disables

This works much like Phantom, but unlike Phantom, VolumeDetect objects trigger collision_start and collision_end events when interpenetrating. Collision events will trigger in any script in the object.

Specification

Events queued depending on type

	VolumeDetect	Phantom
Events Supported	collision_start collision_end	land_collision_start land_collision land_collision_end

Differences

There are a couple differences in how Phantom and VolumeDetect handle collisions; specifically which events are supported and how they handle the ground.

VolumeDetect

• When physical they fall through the ground with the risk of going off-world.
• collision events are not triggered

Phantom

• When physical they collide with the ground but will not pass through (normal physical object behavior), land collision events are queued.

Caveats

• llDetectedLinkNumber will return 0 in collision_start and collision_end events of VolumeDetect objects (SVC-2996).
• It can only be applied to the root prim (which will make the entire object VolumeDetect).
• It only detects physical objects and avatars.
• When moving via llSetPos() by a loop of stages, collision events will not trigger.

Attachments

Note: Attachments are not included in the avatar's bounding box. Collision events received by attachments are collisions the avatar is having with the world, not collisions the attachment is having. Nothing actually can collide with an attachment^[1].

• It is meaningless to enabled on attachments. Attachments cannot collide with anything.
• Attachments do not receive collision events for avatar collisions with VolumeDetect objects.
  • Attachments do receive collision events for avatar collisions with non-VolumeDetect, non-phantom objects.

Important Issues

~ All Issues ~ Search JIRA for related Bugs

		SVC-2490	A		llCollisionFilter completely ignored after call to user-defined function and then a call to llVolumeDetect(TRUE)
		SVC-8141	A		Volume Detect objects are not always allowing objects to pass through.

Examples

default
{
    state_entry()
    {
        llVolumeDetect(TRUE); // Starts llVolumeDetect
    }
    collision_start(integer total_number)
    {
        llSay(0, "Detected!"); // Tells you when something penetrates the prim
    }
}

See Also

Events

•	collision_start
•	collision
•	collision_end

Functions

•

llPassCollisions

Deep Notes

All Issues

~ Search JIRA for related Issues

		SVC-2490	A		llCollisionFilter completely ignored after call to user-defined function and then a call to llVolumeDetect(TRUE)
		SVC-8141	A		Volume Detect objects are not always allowing objects to pass through.
		SVC-2996	A		llDetectedLinkNumber returns 0 with llVolumeDetect(TRUE)

Footnotes

1. ^ Even if attachments were included in an avatars bounding box, you would not like the outcome, the avatars bounding box is not deformed by animations.

Signature
function void llVolumeDetect( integer detect );