Difference between revisions of "LlCollisionFilter"
m |
|||
| Line 20: | Line 20: | ||
|examples= | |examples= | ||
Stop filtering: | Stop filtering: | ||
< | <source lang="lsl2">llCollisionFilter("", NULL_KEY, TRUE);</source> | ||
Filter out all collisions: | Filter out all collisions: | ||
< | <source lang="lsl2">llCollisionFilter("", NULL_KEY, FALSE);</source> | ||
This script, placed in a wearable object, detects a collision when the person wearing it collides with an object named "Post": | This script, placed in a wearable object, detects a collision when the person wearing it collides with an object named "Post": | ||
* 1st instance : | * 1st instance : | ||
| Line 34: | Line 34: | ||
A prim named "Post" hits the scripted object or scripted prim, the collision will not be detected | A prim named "Post" hits the scripted object or scripted prim, the collision will not be detected | ||
< | <source lang="lsl2">default | ||
{ | { | ||
state_entry() | state_entry() | ||
| Line 45: | Line 45: | ||
llSay(0, "OUCH!"); | llSay(0, "OUCH!"); | ||
} | } | ||
}</ | }</source> | ||
|helpers | |helpers | ||
|also_functions= | |also_functions= | ||
Revision as of 00:28, 22 January 2015
| LSL Portal | Functions | Events | Types | Operators | Constants | Flow Control | Script Library | Categorized Library | Tutorials |
Summary
Function: llCollisionFilter( string name, key id, integer accept );| 110 | Function ID |
| 0.0 | Forced Delay |
| 10.0 | Energy |
Sets the collision filter, exclusively or inclusively.
| • string | name | – | filter for specific object name or avatar legacy name | |
| • key | id | – | filter by group, avatar or object UUID | |
| • integer | accept | – | TRUE only process collisions that match, FALSE instead excludes matches |
If accept == TRUE, only accept collisions with objects name AND id (either is optional), otherwise with objects not name AND id
If name or id are blank they are not used to filter incoming messages (or you could say they match everything).
If id is an invalid key or a null key, it is considered blank.
Caveats
- Any call of llCollisionFilter in the same event as llVolumeDetect changing (not just being called, but actually moving from FALSE to TRUE or vice versa) will be disregarded (before or after), if the event handler previously called a user-defined function. See #SVC-2490
- You can get around this by calling them in separate events, such as touch_start and touch_end.
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) |
Examples
Stop filtering:
llCollisionFilter("", NULL_KEY, TRUE);
Filter out all collisions:
llCollisionFilter("", NULL_KEY, FALSE);
This script, placed in a wearable object, detects a collision when the person wearing it collides with an object named "Post":
- 1st instance :
an object named "Post" has several child prims named "Object" . The prim named "Post" hits the scripted object or scripted prim , the collision will be detected
- 2nd instance :
an object named "Post" has several child prims named "Object" . A child prim named "Object" hits the scripted object or scripted prim, the collision will be detected
- 3rd instance :
an object named "Object" has several child prims named "Post" . A prim named "Post" hits the scripted object or scripted prim, the collision will not be detected
default
{
state_entry()
{
llCollisionFilter("Post","",TRUE);
}
collision_start(integer total_number)
{
llSay(0, "OUCH!");
}
}
See Also
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) |
Signature |
|---|
function void llCollisionFilter( string name, key id, integer accept ); |