Attempt to make an inventory of items in a world and report their atttributes

[ACaterin]

Hi all, I would be really interested to keep track of how SL worlds change over time. I have a script that I think gets me close, but it does have two flaws and I can't find online how to fix them, despite searching for a couple of days. Essentially this script operates from within some small object I build and also wear. When I touch it, in the chat window it spits out a list of the first 16 objects it finds on a radius of 96m, and for each of these objects it provides the ID, the size and some other characteristics. If running this script over time, I can then compare these listings to assess what changed - if anything. However, the problems I am having are that: 1. the scanning radius apparently can't be extended beyond 96m only (with llSensor), whereas I would need a much more complete listing of the objects in a world; 2. also, it seems something is wrong with the output from llGetColor and llGetTexture, as they both spit out the exact same values for all the objects listed - which actually happen to be the colour and texture of the sensor object itself, which carries my script. I am not sure where this behaviour is coming from... Any help would be appreciated! Many thanks.

[revochen Mayne]

Like any of the existing llGet* functions, llGetColor and llGetTexture only returns the color and texture of the prim which is containing the script. Unfortunately there is no function to get prim parameters of an external object. 

[ACaterin]

Thanks for this! I had started to think my code was faulty, so that settles the issue of colour and texture with llGet functions. I find it very bizarre though - there must be a way to extract the colour of external objects, since the viewer does it in some way - with Develop -> Show info -> Show color under cursor. If I could only just get that kind of info printed in my listing, along with object ID, size and the rest... :-( As for extending the scanning range beyond 96m, would you see any way to do that? Many thanks for the help!

[ACaterin]

Kept searching and found some other method that may kind of do the job: World -> Area Search for Objects. This does seem to provide all the objects that are in a world (no 96m radius limitation) - though without providing colour or texture. But since I probably couldn't get those anyway, this is fine. If this really is the answer, I'd need to save this list, but there doesn't seem to be a way to do it - no save/export button and copying and pasting doesn't work. Any ideas about how to save/export this list would be deeply appreciated! Thanks.

[Rolig Loon]

---

ACaterin wrote:

[ .... ] As for extending the scanning range beyond 96m, would you see any way to do that? Many thanks for the help!

---

It's not particularly easy.  For many years now, I have sold a device in Marketplace that you can wear as you move around your land to take momentary "snapshots" of information about the objects around you.  I also sell another device that you can use to gather similar information about scripted objects. It sends a rotating scanner to look for all objects within 60m from ground level to 4000m, so you get vertical slices of information on your land.  We don't have a tool for objects that is comparable to llGetAgentList, so we are still stuck using moving scanners to do this sort of work. It's tedious.  You have to deal with some gaps in data and some duplications, and it's slow. Once you have gathered information, of course, you can do followup studies with llGetObjectDetails without needing to scan the same objects again.  Having found an object once, for example, you can ask where it is a week later with llGetObectDetails, to see whether it has moved (or maybe disappeared).

[Qie Niangao]

What's known to the viewer is not what's known to scripts. Generally, you'd need to program a bot to scrape that viewer list and dump it to a client-local file. It's also possible to push that information from a modified viewer (like a bot) into the world and record it using a script, but for what you'd be doing with the kind of data you'd be collecting, having it in-world is no advantage.

We don't deal with bot-programming in this forum. Using LSL, Rolig's suggestion is as good as you'll get.

[ACaterin]

Hey, thanks so much for all the help, that really clarified some things for me. I wasn't aware of llGetObjectDetails either, shall definitely keep it in mind. Also, thanks for the idea with the bot-programming, I understand that it doesn't belong here. However, unexpectedly today I came across a ready-made tool that apparently does what I want - Conover's Full-SIM Object Scanner Pro. I downloaded it and it does seem to easily deliver what I want, and without the 96m limitation. What has me a little worried is a few reviews where they say the scanner just stopped working and Thomas Conover did not offer any / adequate support. Hopefully the tool will keep working for me, as it would be terrible to miss out on scans after a while because I can't get the thing to work any more and need to take time out to write an alternative script... Hopefully this is the issue sorted (even without colour and texture, the compromise is OK), and hopefully Conover's tool will turn out to be reliable...!

[irihapeti]

ACaterin, you a pretty funny person

like you go: heres what I want to do

Rolig who is a legend scripter goes: heres what you actual can do and actual cant do

then you go: ok thanks

then you go off and buy something else which does stuff by magic seems like to you. Which isnt magic. It does it (the sim wide scan) exactly how Rolig already said

except that now you bought it ?!? it dont work seems like, and the maker is nowhere to be found

jejejeje (:

you should of just bought Roligs one. If it ever stopped working (like never. bc legend scripter) then Rolig is right here every day

you egg (:

 

eta; tpyos

 

[ACaterin]

Hi, Let's please contain the discussion to the subject matter: if you can contribute useful advice, that is very welcome and I would be grateful for this. The attitude is less welcome. I just needed some help, was honestly grateful I received it - but then unexpectedly I came across something that did what I wanted without me needing to put effort into additional scripting, which I am no pro at. That would take someone like me a lot of time, which I unfortunately do not have. I did check out Rolig's advice and understood the principle behind it without believing it is 'magic'. I also checked out Rolig's PRIM FINDER (boxed), which is similar to the script I already had - in that both scan up to 96m, but not more in one go. So I didn't see a point in purchasing it, given I had something similar already. When it works (and hopefully it will continue to do so), Conover's tool scans more automatically, without me having to put time into more scripting and repeated scans to cover more ground. So of course I wanted to give it a shot, it has absolutely nothing to do with dismissing advice I got here. In fact, it was one of Rolig's old posts ("Conover's tool works well. I can recommend it. " - 02-01-2011 01:00 PM) that actually helped me find Conover's tool, so I guess that makes me doubly grateful for Rolig's input, as that post basically helped my solve my issue.

[irihapeti]

sorry. I just started laughing when I read your post

i shouldnt laugh really but I thought was pretty funny. I am a bit weird like that

+

ps

i just add

bc you now clarify what you never said before earlier. The only way can do a sim-wide scan in LSL is not in one go. The detector prim has to traverse the whole sim doing sensors scans in bursts

[ACaterin]

Yes, in fact I had understood that since Rolig's reply. My issue was, because I am not particularly good, I'd find it a challenge to direct the repeated scans myself, through some script. I think that would take me a long time to set up correctly, then remove overlaps and who knows what other issues I might run into. So, that being the case, this tool I found does all that automatically for me, hence buying it...

[irihapeti]

yes i get what you saying

which is you came back on here after buying a product and then complained that it may not do what the sales pitch says it can do according to other purchasers reviews of the product

i dont know why you felt the need to come back on this scripters forums to say that

this is a scripters forum where people help new people to become scripters, and to help each other become better scripters

if you got a problem with a script that you are writing then post it ok and you will get help with it 

we not really interested in problems with products that you might have bought. Take that up with the person you bought it off. If you can find them

[Rolig Loon]

No worries here either.  I didn't expect you to run out and buy anybody's scanner because I thought you were interested in writing your own.  I only mentioned mine as examples, so you could look at the ad copy to see how I approached a similar problem.  My basic point was that we don't have any good tools for doing sim-wide surveys of object properties.  I wish we had something equivalent to llGetAgentList, but we're stuck with using sensor scans.  It takes an age to scan a full region with a moveable device, even at ground level, and you still have to deal with sorting through duplicate hits and gaps.  I encourage you to take a stab at writing your own script, if only get a better feel for the immensity of the challenge.

[ACaterin]

I simply thought it might help others, as it helped me to find that old thread where the tool was mentioned. Also thought it was useful to add the caveat here, so anyone reading - who wasn't aware of the tool previously - can immediately know there are apparently no guarantees if it breaks down. That's pretty much it...

[Rolig Loon]

Sounds good to me.

[ACaterin]

Yes, at first it really didn't occur to me to buy something - I really did aim to try and write something of my own when posting here for help. Then... things changed when I happened to come across that Conover thing, and reported back here so other people might know this was the way I solved it - it may help others, who knows (?). And yeah, I do want to improve my coding and I will keep trying - it's just earlier I realised it was probably going to take me ages to get something like this right... Anyway, really hope you didn't take any of this the wrong way. I sincerely appreciated all your help.:-)