Rolig Loon

There are lots of good ideas to ponder. Add this one to your private list. The bottom line here is that SL is not a country with a government. It is a social/creative [platform owned by a corporation. Except for those situations that need to be regulated to protect LL's economic interest (like rules regarding Marketplace) or keep the peace (TOS violations), they have neither the incentive nor the staff to deal with regulating the behavior of residents. We regulate ourselves or (more commonly) stay out of each other's way. That doesn't stop us from debating cool ideas among ourselves, of course......

Dora Gustafson wrote: I had this message from beyond: llGetOwnerKey is only effective if the sitter is the person that owns the object being detected If someone has a first hand knowledge about this please make a note in the Wiki llGetOwnerKey() That's true, but not because it's a limitation of llGetOwnerKey. If the idea is to get the UUID of the driver, then asking for llGetOwnerKey(car'sUUID) is only going to yield the correct answer if person driving is the owner of the car. If the driver is in someone else's car. it will still tell you the owner's UUID, but that's not what you want to know. .

Try (integer)llFrand( (float) n ); and don't forget to include a sound volume in llTriggerSound. :smileywink:

This is not something that LL is likely to pay much attention to. It's a matter for work among residents, much like the railway system that runs on some mainland sims. The best models for Linden-sponsored travel networks are the highway system and the network of navigable waterways, also both on the mainland. Those work because they are on Linden-owned lands. Lindens are understandably reluctant to get involved in resident property matters, especially on private estates. The basic principle is that the landowner has virtually full control over what can happen on his land and who's allowed to be there. Other than an e-mail or a post to some Linden's RSS feed, I'm not even sure how you'd go about getting a proposal of this sort into the mix.

Yeah, you're right, and this one is right on the line. It's hard to answer one like this in the Scripting Forum without presuming a moderate level of scripting ability from the OP, so just saying "write an AO script" wouldn't be much help to a novice. I tend to avoid sending people over there when the best answer is likely to be "Here, have a free script."

You can't, unless you want one for yourself. I have set up a couple for convenience on my own sim. Until LL gets any bugs out of the new permissions system, it looks like we're stuck with a very limited function. There's been a bit of discussion in this forum and over in SLU, if you're interested.

The Scripting Forum is a place for scripters to share ideas and try to sort out problems they are having as they write scripts. It's not a place to look for a script. If you are looking for a pre-made script, you should always try the Wanted forum or Markteplace. If you want to hire a scripter, the place to go is the Inworld Employment forum. HOWEVER, having said that, I answered your original question over in the Answers forum, with a script...... It ought to do the trick, assuming that you have an animation. :smileywink:

Gestures and scripts are different beasts. If you have an animation that you want to activate at random intervals, you'll probably do best to write a small AO script, pop it into a HUD, and wear it. It doesn't need to be anything fancy. Just enough to run a timer and trigger the animation automatically. This is just off the top of my head and not tested in world, but something like this ought to work ... integer gStart;default{ on_rez(integer startup) { llRequestPermissions(llGetOwner(),PERMISSION_TRIGGER_ANIMATION); } run_time_permissions(integer perm) { if (perm & PERMISSION_TRIGGER_ANIMATION) { llSetTimerEvent(30.0); // Start off with a timer that triggers every 30 seconds.... } } timer() { if (!gStart) //This starts the animation and lets it run for a couple of seconds.... { llSetTimerEvent(2.0); gStart = TRUE; llStartAnimation(llGetInventoryName(INVENTORY_ANIMATION,0)); } else // ... and this stops it and resets the timer for a random time later. { llStopAnimation(llGetInventoryName(INVENTORY_ANIMATION,0)); float time = 3600.0 + llFrand(3600.0); // Change to a random trigger... between 1 and two hours llSetTimerEvent(time); gStart = FALSE; } }}

You don't "get" permission. You either have it or you don't. People can keep you out of their land and its airspace in two ways: (1) They can erect ban lines, which are like an electric fence that you just bounce off of or (2) they can install a scripted security system that can warn, eject, or ban you from the area if you try to enter. Ban lines are limited to a height of 768 m above the terrain mesh when you're explicitly banned from the land. If the parcel is simply not pubic access or restricted to certain Residents/groups, then the lines go up to 50 m above the terrain mesh. So ban lines are not usually a barrier to airplanes, except low-flying ones. Security systems, similarly, often have a limited range. Most will detect intruders with a simple sensor, which has a range of 96 meters. That's enough for many landowners, who simply hope to keep Peeping Toms out of their boudoirs. More sophisticated systems use a network of sensors or, nowadays, use a LSL scripting function that will detect all avatars in a single parcel or sim regardless of distance. Those sophisticated systems would discourage you from flying, even if you were 4000m above the surface. The bottom line, whether you are encountering ban lines or security systems, is that you won't know whether one is there until you encounter it. These things aren't mapped, and there's no way to buy a "free pass" that lets you fly through protected airspace. You just have to take your chances, and be polite.

If you haven't logged in for a while, chances are pretty good that it's just your locally cached copy of inventory that's borked. The real inventory is safely in Linden Lab's asset servers, so you just need to make a new copy. You could do that by simply hitting the Clear Cache button in Preferences >>. Internet & Cache, but you'll do a cleaner job if you clear cache manually from outside SL. Here are great instructions >>> http://wiki.phoenixviewer.com/fs_cache_clear

If you can't rez objects, you'll have a hard time. You need to be able to at least rez your scanner., unless you're planning on wearing it and bringing it in from the outside. If that's the case, scanning is going to be tedious, given the 16 limitation.

It works. Congratulations. :smileywink:

Have you recently put Microsoft SkyDrive on your computer? See https://jira.secondlife.com/browse/VWR-28843 for a JIRA report on this issue. Also see Latif Khalifa's solution in its comments......

You'd have to draw the texture the same way whoever created your skin did. You can fake it a little by trying to match the skin color, but you should realize that skin is not monochrome. It's shaded, like everything else in the world. Also, skin color changes with the color, intensity, and angle of the light that strikes it, so a match one second will not necessarily look right the next one. Still, it's the best you can do, and for small areas it's mildly convincing.

Be sure that whatever you downloaded is compatible with your computer's operating system. A program designed for a Mac won't do a thing on a PC, or vice versa.

Wow. I have never seen this before. Nice catch, Darren!

So it's a V1 bug? Interesting.

Claireschen's right. Your best move is to open a gmail account and use it only for Second Life. I have done that for years, and I never have to worry about SL e-mail mixing with my regular e-mail.

Didn't your Mom ever tell you not to make faces? They might get stuck some day. :smileyvery-happy: If you're lucky, it's an animation that's jammed somehow. Try using Stop Avatar Animations. In the Firestorm viewer, it's in the Avatar >> Avatar Health menu. In V3, I believe it's in the Me Menu under a similiar heading.

CTRL + Shift + R toggles wireframe ON and OFF. It's unfortunately easy to trip it by mistake because people are familiar with CTRL + Alt + R, which is a Rebake sequence. You can toggle wireframe in your Develop menu too, Look under Rendering.

Unfortunately, that's not true yet. Take a look at the latest release notes at http://community.secondlife.com/t5/Merchants/Marketplace-and-Direct-Delivery-Update/td-p/1462915 , which include this continuing comment: " Limited Quantity Support (Merchant does not have rights to copy the items for sale): This is currently being worked on. Magic Box migration will not be required until this is supported. (Note that Merchants can sell items that have next owner rights set to “No Copy”.)"

Your packet loss figure is much higher than I feel comfortable with, so you are losing a little over 1% of the data you are sending or receiving from SL's servers. When was the last time you rebooted your router? If it's been a week or two, unplug it from the power and go make a sandwich. That will give it time to clear its RAM and take a fresh look at your IP address. While you're checking things, be sure that you don't have unshielded Internet cables running over your power cords too..

Non-delivery is one of the reasons why LL is getting rid on Magic Boxes. If the sim is lagging or offline when the Magic Box is supposed to be delivering something, it can hang up. Getting a lot of requests at once will do it too. As Lindal says, wait a while. If you've received the L$, redeliver to the customer. Otherwise, ignore it.

Yes, that happens every once in a while and there's not a thing you can do except rebuild the parts with the borked perms. As you said, they should revert to be full perm once you have unlinked the no-trans items, but it doesn't always work that way. Sorry.

Why not add a llRezAtRoot on demand to create yourself a temporary sit TP object? Feed it the position of your target object on rez and then sit to TP to it. You'd have to do a little fiddling to select which detected object is your target before you rez the TP object. Instead of using llOwnerSay to give you the output, you could send it instead to a dialog and use that as your means of selecting the target object. It could be kind of interesting. BTW, your biggest limitation is going to be the 16 object limit on llSensor. If you have more than 16 objects around, you won't see them all.