Temp Rez Objects

llGetPrimitiveParams http://wiki.secondlife.com/wiki/LlGetPrimitiveParams
.

Yes, but it lets you narrow the location down to a parcel. If you really need to know and you're the landowner, you can split the parcel up and do a binary search.

Another thing you can do is use a scanner looking for changes in the UUIDs of prims at the same location.

That doesn't work for other prims than the one the script is in.

Well, looking at what Phil says it does:

1) By wearing it, you'll be able to tell if any temporary prims exist, both on a parcel and throughout the sim.

That is doable with llGetParcelPrimCount, for sure.

2) It also shows the X and Y coordinates of them, but not the Z.

This part is the curious one. This could be done with the UUID-change scan trick, but I wonder why the Z position would have been omitted, unless it was just a design decision in the output (from 2D thinking or somesuch). It reminds me a bit of a land function, though, since land functions mostly work in 2D. The UUID-change trick would seem to me to be a bit ineffectual, having to scan unfiltered, and limiting to the closest 16 objects, which means you would have to get very close to it to see it anyway.

Dunno. Anyway, I was just wondering if there was something I missed in LSL which would do this function in a rather elegant fashion.

The Z coordinate always seems to show 21 regardless of the height they are at. The temp rezzers that I'd forgotten about were thousands of meters in the sky. On the other hand, Felix found a temp rezzed object *at* 21m height.

I can't guarantee that the X anY coordinates are those of the object or of the parcel, but it does give X and Y coordinates.

Looking at the script it has scan coordiantes as 0,0,21. So 21 will always appear in the results I guess. I just got lucky to find that object that just happened to be at 21m high. I just pulled out the scanner again and it gave me coordinates for 7 items all ending in 21 for the Z position, but those are bullets because a battle is currently happening.

It works but I wonder why the last coordinate is set to 21 in the script.

**edit** Apparently it was not bullets but someone with a scanner that has 5 or 6 drones flying all over the sim.

Interesting. Phil... could I see a copy of this script?

The script is hard-coded to report 21 as the z-axis position.

It is always reporting that I have something @ 0,20,21 among some other temp-rezzed items. I am running a probe to try and find the thing @0,20 from ground level to 4096m up, so far, nothing.