Difference between revisions of "LlCollisionFilter"
Jump to navigation
Jump to search
(This is a prime example of a BAD example. 1) The code has bugs, 2) Whitespace inconsistency detrimental to readability, 3) Bad grammar & spelling in comments. fix removes llCollisionFilter from code) |
m (changed OR to AND in describing the behavior of accept = FALSE. it ignore an object if name AND key match. it's not either or (what is said previously)) |
||
| Line 6: | Line 6: | ||
|p2_type=key|p2_name=id | |p2_type=key|p2_name=id | ||
|p3_type=integer|p3_name=accept | |p3_type=integer|p3_name=accept | ||
|func_footnote=if '''accept''' == {{LSLG|TRUE}}, only accept collisions with objects '''name''' | |func_footnote=if '''accept''' == {{LSLG|TRUE}}, only accept collisions with objects '''name''' AND '''id''' (either is optional), otherwise with objects not '''name''' AND '''id''' | ||
|func_desc=Sets the collision filter, exclusively or inclusively. | |func_desc=Sets the collision filter, exclusively or inclusively. | ||
|return_text | |return_text | ||
Revision as of 22:13, 25 September 2009
| 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 | |||
| • key | id | |||
| • integer | accept |
if accept == TRUE, only accept collisions with objects name AND id (either is optional), otherwise with objects not name AND id
Caveats
Examples
Stop filtering: <lsl>llCollisionFilter("", NULL_KEY, TRUE);</lsl> Filter out all collisions:
<lsl>llCollisionFilter("", NULL_KEY, FALSE);</lsl>See Also
Deep Notes
Search JIRA for related Issues
Signature |
|---|
function void llCollisionFilter( string name, key id, integer accept ); |