|Anonymous | Login | Signup for a new account||2020-01-23 11:26 PST|
|Main | My View | View Issues | Change Log | Roadmap | Summary | My Account|
|View Issue Details|
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0007837||opensim||[REGION] Script Functions||public||2016-03-06 16:05||2016-03-06 16:15|
|Platform||linux/mono||OS||OpenSim 0.9.0.0 or 0.8.2.1||OS Version||0.9.0.0|
|Product Version||master (dev code)|
|Target Version||Fixed in Version|
|Summary||0007837: not_at_target event is not triggered in child prims|
|Description||When you put a call to llTarget in a script in a child prim, the not_at_target event is never triggered.|
Actually, it is triggered every once in a while on very strange events, like when you add a script to the root prim, when you close the edit dialog box, perhaps other times.
|Steps To Reproduce||Make two prims and link them together. Put the following script in the child prim. It should print "tick" a gazzilion times (11 times a second).|
Close the edit dialog box and edit the build again a few times. You will see an occasional "tick.
If you move this script into the root prim it does have the correct behavior of "tick"ing very fast.
|Additional Information||default //this script fails in child prims|
|Tags||No tags attached.|
|Git Revision or version number|
|Run Mode||Grid (Multiple Regions per Sim)|
|Environment||Mono / Linux64|
Q: Does this function work in a child prim of a link set?
A: No. Either put the script in the root prim or use linked messages to relay between the child prim and root prim.
This shows that it's mot meant to fire in child prims. Current behavior appears to be the correct one.
Note: not_at_target is NOT a good way to realize high speed timers. It is heavy on sim resources, as all fast timers are. LSL provides many events that make fast timers unnecessary.
|2016-03-06 16:05||Kayaker Magic||New Issue|
|2016-03-06 16:15||melanie||Note Added: 0030070|
|Copyright © 2000 - 2012 MantisBT Group|