OsVolumeDetect

Home

Download

News

Support

Admin

Dev

Screen Shots

Grid List

Bugs

Languages:

English

osVolumeDetect(integer detect)
If script is on root prim, it is like llVolumeDetect(). On child prims, it will turn just that prim a detector.
Threat Level	This function does not do a threat level check
Permissions	Use of this function is always allowed by default
Extra Delay	0 seconds
Example(s)
// Example of osVolumeDetect default { state_entry() { llSay(0, "Script running"); osVolumeDetect(TRUE); } on_rez(integer hh) { osVolumeDetect(TRUE); } collision_start(integer uu) { llOwnerSay("s"); } collision_end(integer uu) { llOwnerSay("e"); } }
Notes
This function was added in 0.9.0.1 Since version 0.9.2.0, llDetectedLinkNumber will return the DETECTOR prim link number even on collision events and not 0 as spec. Our llVolumeDetect does the same now At current time, this is not persistent (so the on_rez on example) This is also lost on child prims if physics state changes or on link/unlink. Script must set it again after such changes Note that like with llVolumeDetect, the name Volume is misleading. Detection will only be by volume on some basic shapes like pure spheres or pure boxes. On other shapes it will only be by surface collisions. What prims will do by volume or surface, depends on the physics engine The name of function llDetectedLinkNumber is also misleading, it returns the detector prim link number, not the detected.