Script Time, Memory, and Script count sensor (HUD button reports stats for nearby AVs or active objects)

This is a simple "HUD button" that reports stats for nearby AVs or active objects when clicked. Information includes script time, memory, and script count (running and total). Information is displayed as owner-only text in chat after the button is clicked (sorry, I don't like those auto-updating hovertext sensors). The values are from the sim, which reports averaged time over the last 30 minutes (or since object startup, if less than 30 minutes).

Wear this on a script-enabled parcel; it attaches to the upper-left HUD location.

Click one of the two buttons, "Scripts" and "AVs".

This results in up to 16 outputs like the following, for the 16 nearest AVs or active objects in range:

0.13142 ms, 544 KB, (33/34) : --> [TORLEY TEXTURES] v11 mini (improved by Mana Janus)

This example means the object is averaging 0.13142ms of script time per frame, 544 KB of script memory, and that 33 of its 34 scripts are currently running.

WARNINGS WARNINGS WARNINGS:

- Do not rely on times for newly-rezzed objects or AVs that have just TPed or changed attachments. It can take a while for times to settle. It's best to watch script time for a while until it's stable. A short peak in script time will still influence reported values for 30 minutes.

- Similarly, objects may have high script times from recent interactions or adjustments (like resizing) that will continue to impact reported script time for a while. Again, it's best to check later when you know the object or AV has just been doing "ordinary" things for about 30 mins.

- Your own script time will be included when you click AVs, but this time is being impacted by the sensor itself (e.g., click it many times rapidly and watch your script time increase for a while). To remove this impact, run the sensor rezzed on the ground or from another AV.

- The "Scripts" option only lists objects with currently active scripts. Some scripts are not active when nothing is triggering them to run (it depends what kind of events they handle and how they monitor their environment).