llGetSim() Please!!

hello! I want to request something that could make life alot eiasier for ppl like me. I would really like a:
string llGetSim() function implimented into LSL. Speak up anyone who agrees!

(and if your a scripter whos written a function for this already please contact me any way possible, I desperately need something to do this for me).

Seconded

I definately third this and was going to post a similar request... beat me to it Christopher.

Well, as I tried to explain to Chris on two separate occasions, this is already possible and not too hard. A variant of this problem -- finding the "grid coordinates" of the simulator -- is described below, and will work for all time. The actual problem, that is getting the name of the simulator itself, is simply a matter of matching up grid coordinates to simulator names; unfortunately, this function will need to be expanded every time a new simulator is brought online. It's still possible, though, and actually quite easy.

As I've pointed out before, it would be ideal to have global coordinates instead of Sim + x, y coordinates as we have now; that would go a long way towards eliminating script-based navigation problems. Certainly Sim + x, y works well for presentation to the user, and maybe for internal representation, but abstracting out positions into global coordinates would be most helpful for scripters.

Anyway, here's how to find out where you are. Basically, the idea is to put a landmark for a location on a known simulator into the navigator object, and have the script (through llGetInventoryData) request the location of the landmark. If the returned coordinates are on the current simulator (i.e. the x, y values are "valid" then you're on the same simulator as the landmark's location. If not, then you can use the vector to the known location to calculate what simulator you're on. That's just a matter of dividing each element of the vector by the size of the simulator on that axis, and taking that as the grid coordinate offset from the known simulator.

Actually implementing this is on my (ever-growing) to do list. I'll make sure to make the script available freely when/if I get around to writing it. Of course, anyone is free to implement the method described above.

A fairly simple script/object way to do this, expanding on Bobs ideas:

Make an object with a landmark for each sim. It reads through each landmark until it finds the right one and reports that. If done correctly everytime a new sim is added, just drop a new landmark on the object. It is not the fastest method but is the most scalable (that I can think of).

That being said, I think a llGetSim() call would still be great instead of using this work around, especially considering how many sims it seems likely the Lindens will expand to.

Thanks for posting that Ama, I will probobally use that method of finding the current sim, however I am currently in the process of building a large complex system of objects, and that method would be quite difficult to maintain. I would still like an llGetSim function...

I know you are dealing with objects across sim boundries (otherwise what would be the point eh?) but....

If you know the keys of the objects you can use llGiveInventory to help distribute updates. Then you may only have to update one per sim, if you have an llGiveInventory inside an changed event....

It all depends on the setup of the rest of the project how much extra work or feasable that would be.

And again, I'm all for llGetSim(). Just offering what ideas I can think of to ease suffering.