Rolig Loon

When that happens it's usually because you have included a script, a texture, a sound, or some other component that is non-transferable.

I haven't bothered to read any of his posts in the new forums. Now that the moderators dispose of them quickly, they aren't even much of a nuisance any more. It's sort of pitiful, really, that he hasn't figured out that nobody cares about his delusional ramblings.

The parameters you have written should give you the result you wanted. You might set CAMERA_BEHINDNESS_LAG to 0.0 so that there's absolutely no delay in response as you move. Other than that, the only thing I can suggest is that the parameter list really should be in a run_time_permissions event instead of your touch_start event.. That is ... run_time_permissions(integer perm) { if (perm & PERMISSION_CONTROL_CAMERA) { //Do stuff} } In practice, it shouldn't make any difference since permission is granted automatically when you sit on or attach the scripted object. Still, it's never a good idea to assume that any requested permission has been granted.

You will never be redundant, Marigold. Out of a job, perhaps, but never redundant. :smileywink:

According to Torley, who knows everything :smileyhappy: Here's what all the abbreviations mean: B = Base - The object can never be more permissive than this. O = Owner - The permissions the owner (you) currently has. G = Group - The permissions group members currently have on the object. (The group the object is set or deeded to is shown next to Group: above.) E = Everyone - The permissions everyone else has on the object. N = Next Owner - The permissions the next person to own the object will have. F = Full/Folded - The permissions of the object as a whole, including all permissions of the object's contents. For example, a copyable object which has a no-copy item added to its contents becomes non-copyable as a whole because it's restricted by the no-copy content item. M, C, and T = Modify, Copy, and Transfer - Standard permissions. V = Velocity - This actually means "can move" permissions. For instance, if an object shows "E: V", this means everyone can move this object around inworld, which is the the same as Allow anyone to move being enabled. * = Slam bit - Explained more in the next section. You can see the extended answer at http://wiki.secondlife.com/wiki/Debug_Permissions

It can't have anything to do with the computer you used. Any time you buy something, it is stored on SL's asset servers, not your own computer. The listing you see is essentially a table of "pointers" to storage locations in the servers. Having said that, however, it is possible for the inventory listing that you see to get out of sync with the asset servers. You can cure that, if it's the problem, by clearing your cache (click the "Clear Cache" button in Preferences), logging out, and then logging back in at a really vacant sim like Smith or Pooley. When you log in, open your inventory and type anything -- the letter "A" for example) to force the asset servers to rebuild your local copy of the inventory listing. Don't do anything while it's rebuilding. Just go out for a cup of coffee. When it's done, your inventory should be properly synced. Now, if you do that and the items are still missing, then check your Transactions log to verify that you actually bought and paid for the items and then contact the seller with that information. If the items were copiable, you ought o be able o get a redelivery.

Take a good look at Marigold Devin's response to the same question in THIS THREAD. The steps she advises almost always cure ghosting. Good luck. :smileywink:

When you are setting permissions, be sure that you are always doing it on a rezzed copy, not on something in inventory. Permisssions only "stick" on rezzed items. That might account for some of what you're seeing. My guess is that a prim somewhere in your build isn't really set full-perm the way you think it is. Offhand, though, I don't know how to explain the fact that your prim names are wonky. I've found that it helps my peace of mind to activate Debug Permissions in the Advanced (CTRL-Alt-D) menu so that I can see exactly how permissions have been set for the next owner ( N: ) on any item I create.

Ishtara Rothschild wrote: (But now I had the "invalid HTML" error again. It seems that the </blockquote> tag always ends up at the wrong spot in the automatically generated HTML code. That's probably also why you see so many messages where the text under a quote is italicized and appears to be part of the quote, like in Rolig's message above). Hmmmm... That might be it, but if so it's not consistent. I haven't messed with the HTML in this post, for example, and my text is showing up as roman (not italic) despite the quote. The software got it right without intervention this time.

Check the master sound panel (upper right corner of your screen in V2, I believe) to be sure that you haven't inadvertently moved the slider all the way to the left. I have done that by mistake a couple of times and then thought that I'd gone deaf.

Ishtara Rothschild wrote: PS: I also frequently get the error message "Your post has been changed because invalid HTML was found in the message body. The invalid HTML has been removed. Please review the message and submit the message when you are satisfied." when I hit the Post button, even if I only typed one line of text with no formatting or links at all. This is very annoying. I can understand getting that message when I have messed with the HTML (as I did yesterday when removing part of a table from a post before submitting it). It's annoying to get it when I haven't touched the HTML, however. I get the same message whenever I post anything that has an accented character in it, for example, as when I'm responding in French or German. My guess is that Lithium's software isn't smart enough to recognize high-bit ASCII codes. If I go ahead and hit the submit button without making any changes at all, it's always accepted on the second pass, but it is dumb that I need to do that.

You can't. You do not have the power to remove an owner from the group. The smartest thing to do is to sell the land to yourself (or an alt), and then dissolve the group. You can do that by ejecting everyone from the group except your co-owner and then leaving the group yourself. That will leave your co-wner as the group's sole member. LL will collapse the group within 48 hours, since it will no longer meet the minimum size requirement.

Whew! I was afraid it was just me, Peewee. I was looking all over for a chrono text and a brief gantry. ;-)

SL uses a lot of bandwidth, so if you are staying in a busy hotel where every travelling businessman is on the Internet, it wouldn't be surprising to find that there's no room left in the pipeline for you. Also, Internet connections in hotels are almost always wireless these days -- not the best way to access SL. Several of my colleagues have had bad experiences accessing SL to make presentations at professional meetings in big city hotels.

What a lovely simile! You've captured the image exactly, Squashy. "Like a deceased parachute ....... " :smileytongue:

Yes, I think that change from SLT to PST/PDT was in late 2009, but most of us who were around before then continue to use the label SLT. It's hard to break a habit, I guess. I agree that the label can be confusing, especially for those who are new to SL. My personal solution (when I remember) is to write SLT/PST so I'm covering all bases. Still, regardless of what you call it, the standard time zone for SL has always been West Coast US time.

No. Not unless they tell you. This is a VERY good thing. The last thing we need to do is make it easier for stalkers.

Hehehe.... I tried that myself and couldn't find it even with his name.

Oh, good! You found it. I ran up against a dead link to the old blogs when I was searching. Nice work, Peewee.

That's wierd. When you look at the item in your inventory, does it have a little blue icon that looks like a pair of pants or does it have a pink icon that looks like a skirt? If it's the blue icon, it's supposed to be a pair of pants. Just to be clear..... Designers will usually sell a skirt with a matching pair of "glitch" pants that are meant to be worn under the skirt. It's important to do that for two reasons. First and most important, it can be more than a little embarrassing to fly around SL without glitch pants or underwear. Second, parts of your body usually poke through skirts as you move, so appropriately-textured glitch pants hide the fact that people are actually seeing your thighs. Anyway.... check to be sure that the folder that contained those pants also contains a skirt. BOTH should be there.

Nothing, unfortunately. Unless they respond to a friendly request, there's not a thing you can do. On the bright side, as long as the objects are actually on their side of the line, they won't affect your prim allowance. (If they are on your side, you can return them.)

You should be fine. You're just having a bit of trouble with the Internet connection between your client viewer and SL's servers. Changes to your appearance are made on your own computer and then uploaded to SL so that others can see them. If the connection between the two spots is interrupted, you may be able to see the changes but others won't. There's a very nice and exhaustive set of suggestions for how to cure the problem HERE. It is on the Phoenix web site but it really applies to any SL viewer.

Payant a qui? Vous pouvez certainement gagner de l'argent dans SL, mais il est très difficile de gagner suffisamment pour vivre, si c'est ce que vous voulez dire. Quelques personnes ont très bien réussi dans les affaires SL, mais la plupart d'entre nous sont satisfaits de gagner une petite quantité. Il s'agit d'un loisir pour la plupart des gens, pas une carrière.

Are you using THIS SCRIPT that was posted in the old Scripting Forum archives? If not, take a look and see if it works for you. EDIT: Oh, crap. The link in that thread points to the old blogs and is dead. Sorry about that.

Well, you can avoid unnecessary messages easily enough, but you can't avoid at least some lag. It's just a question of what is creating the lag. You can try using a completely different approach from what I suggested before to see. Put a tiny script with a timer in Object 2 that checks the object's position periodically and llRegionSay(-12345, (string) llGetPos()) whenever it moves to a new spot. Then write your main script to listen for the message and if (llGetPos() != my_own_old_stored_position) { llOwnerSay("Object 2 is " + (string)llVecDist(llGetPos() - object_2_stored_position) + "m away"); my_own_stored_position = llGetPos(); } else if ( (vector)gMessage != object_2_stored_position) { llOwnerSay("Object 2 is " + (string)llVecDist(llGetPos() - (vector) gMessage) + "m away"); object_2_stored_position = (vector)gMessage; } The timer in each script will still contribute a little lag to the sim, and you will have increased the sim's script overhead slightly by running two scripts instead of one, but you won't have a sensor firing all the time. Frankly, I don't know which option is friendlier to the sim but I can't imagine that either is much to worry about.