Difference between revisions of "LlVolumeDetect"
Jump to navigation
Jump to search
All Issues ~ Search JIRA for related Bugs
| Line 8: | Line 8: | ||
|return_text | |return_text | ||
|spec= | |spec= | ||
{{{!}} {{Prettytable|style=float:left;}} | |||
{{!}}+ Events queued depending on type | |||
{{{!}} {{Prettytable}} | |||
{{!}}- | {{!}}- | ||
! | |||
! {{Hl2}} {{!}} | ! {{Hl2}} {{!}} VolumeDetect | ||
! {{Hl2}} {{!}} | ! {{Hl2}} {{!}} Phantom | ||
{{!}}- align="center" | {{!}}- align="center" | ||
! {{Hl2}} {{!}} | ! {{Hl2}} {{!}} Events<br/>Supported | ||
{{!!}} | {{!!}} [[collision_start]]<br/>[[collision]]<br/>[[collision_end]] | ||
{{!!}} | {{!!}} [[land_collision_start]]<br/>[[land_collision]]<br/>[[land_collision_end]] | ||
{{!}}- align="center" | {{!}}- align="center" | ||
{{!}}} | {{!}}} | ||
=====VolumeDetect===== | ====Differences==== | ||
There are a couple differences in how Phantom and VolumeDetect handle collisions; specifically which events are supported and how they handle the ground. | |||
<div style="clear:left;"> | |||
======VolumeDetect====== | |||
*When physical they fall through the ground with the risk of going off-world. | *When physical they fall through the ground with the risk of going off-world. | ||
=====Phantom===== | ======Phantom====== | ||
*When physical they collide with the ground but will not pass through (normal physical object behavior), land collision events are queued. | *When physical they collide with the ground but will not pass through (normal physical object behavior), land collision events are queued. | ||
</div> | |||
|caveats= | |caveats= | ||
*It cannot be enabled on attachments{{Footnote|Attachments aren't included in the avatar bounding box, so it's moot}}. | *It cannot be enabled on attachments{{Footnote|Attachments aren't included in the avatar bounding box, so it's moot}}. | ||
Revision as of 17:07, 17 October 2009
| LSL Portal | Functions | Events | Types | Operators | Constants | Flow Control | Script Library | Categorized Library | Tutorials |
Summary
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. 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.
| • integer | detect | – | TRUE enables, FALSE disables |
Specification
| VolumeDetect | Phantom | |
|---|---|---|
| Events Supported |
collision_start collision 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.
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 cannot be enabled on attachments[1].
- 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 will not register collision events when the avatar collides with a VolumeDetect object.
Examples
<lsl>default {
state_entry()
{
llVolumeDetect(TRUE); // Starts llVolumeDetect
}
collision_start(integer total_number)
{
llSay(0, "Detected!"); // Tells you when something penetrates the prim
}
}</lsl>
See Also
Deep Notes
All Issues
~ Search JIRA for related Issues
|
|
SVC-2996 | A | llDetectedLinkNumber returns 0 with llVolumeDetect(TRUE) |
Footnotes
- ^ Attachments aren't included in the avatar bounding box, so it's moot
Signature |
|---|
function void llVolumeDetect( integer detect ); |