Rolig Loon

Yeah. It comes down to semantics. The only place it's requested is in the logon for a V1 viewer, where it is called "Last Name", so that's what an OP is always going to ask for. I agree that it's confusing, and I wish LL had never caused this mess in the first place. My own choice when asked is to say, as I did, that your "last name" is "Resident" but you won't have to use it very much at all. It doesn't take newbies long to learn that there's only one context in which they have to even think about it.

That's a good observation. Web-based profiles are a very recent addition to SL, so if you re-activate an older account, it wouldn't have a web-based profile to activate at the same time.

Well, congratulations. It works, with a couple of minor corrections. 1. You used the variable name num_detected in the touch_start event, but then mistyped it later as numberDetected. 2. You left off the underscore in the event label no_sensor. Other than that, the script compiles and runs. Touch it and it tells you who is within 96m. You can test its remote function with a simple companion script like this integer gLisn;default{ touch_start(integer total_number) { gLisn = llListen(-4763,"","",""); llSay(7001, "getData|-4763"); } listen(integer channel, string name, key id, string msg) { llListenRemove(gLisn); llSay(0,msg); }} Now you can start modifying it to add more bells and whistles. The first modification I'd suggest is to clean up your indentations. That sounds like a very trivial step, but it is an important habit to get into. Compilers don't care about indentation, but it makes a whale of a difference in readability for anyone trying to make sense of the script (like you). It's much easier to keep track of where a block of code starts and ends if you keep it clean.

Those are tests for username, not for last name. The OP's username is haroon, but for purposes of login (the only place it makes a difference, and then only on V1 viewers), his last name is "Resident," which is what he asked.

Profiles may become "unavailable" if a SL resident was banned from SL. .... or it could just be a system failure.

Welcome to Second Life, haroon Resident. Your last name is Resident. You won't need to use it in many places, but it's yours (and about 100,000 other people's).

There's nothing wrong. PayPal needs to know where it's going to get its money from, so it asks you for either a credit card or a bank account. They won't just wait for you to mail in a personal check or an envelope full of pennies when you buy something.

Well, there are several things to work on. For starters, the big reason you're not getting any senor data is that you don't have a sensor event. The Sensor is triggered by the message that the script receives in the listen event, but you need a sensor event to receive and interpret its output. Take a look at a really basic example in the LSL wiki at http://wiki.secondlife.com/wiki/LlSensor That's only one of several things to fix, but if you get it going, you may start to see the others.

None whatsoever. You didn't tell us anything about what computer you are using or anything about its specs. What kind of Internet connection? Which SL viewer are you using? Any error messages? We need to have something to work with. Click on the Options link in the upper right corner of your question and select EDIT to tell us more. Please do NOT start a new thread.

Did you create your Received Items folder yet? Buy ANY item from Direct Delivery -- the free Linden Bear will do. That will create your Received Items folder. Then LOG OUT and back in again to activate yourMerchant In Box.

1. Go here >>> https://secondlife.com/support/downloads/?lang=en-US 2. Click the button that says DOWNLOAD 3. Click any other button that it tells you to. 4. That's it. 5. Welcome to Second Life.

This forum is for learning how to script or for sharing insights about scripting. If you have never written scripts in LSL before, it's probably a good idea to start with a few of the tutorials at https://wiki.secondlife.com/wiki/LSL_Tutorial .Peter gave you some good starting points for your own project, which is a nice starter problem. As you get working on it, post what you have done and we'll help guide you though the parts that aren't working right yet. If you don't want to write your own script, though, you are in the wrong place. Post your question in the Wanted section of the Commerce forum and see if someone either has a scrpt to sell you or wants to write a custom one for you.

Fantastic. I'm glad it worked for you. llSetKeyframedMotion is definitely one of the nicest functions we have gained in LSL recently. There's only one rather small change I'd recommend in your script. You define the variable mykey and then assign it the value of the object's UUID. It should be your own UUID, since the object is supposed to be following you, not itself. Probably the easiest way to rectify that is to get rid of mykey altogether and just write llSensorRepeat("",llGetOwner(),AGENT,15.0,PI,0.11); //Following me

Oh, my. That is NOT a great welcome to Second Life. Such things do happen, unfortunately. The best I can say is that they are not the norm. I have known many successful and happy people in business partnerships here. So, is that sort of behavior "allowed"? It's not encouraged, but there are no enforcible rules to prevent it. Linden Lab will act on Abuse Reports that involve violations of the TOS, but they leave it to residents to resolve disputes between them. It will be very hard --- no, impossible -- to recover items that were bought with your shared funds. You ought to be able to reclaim your own property if you can get close enough to take it back to inventory -- either by standing on the other side of a sim boundary or by going in world as a sleath alt to whom you have given permission to edit your objects. In the end, though, you'll probably have to just take a deep breath and walk away. My two pieces of advice: (1) Don't do anything that violates TOS as you try to pick up the pieces and (2) Don't let this leave too much of a bad taste in your mouth for SL. There are plenty of good, honest people here.

Probably because it doesn't have a good place to sit, at least not the way you're trying. Good furniture has a scripted sit target in it, so that there's no question about where you end up regardless of where you click on it. Furniture that has no scripted sit target can be chancy. If it's made of "normal" prims, you have to click from the proper angle and at a spot that is wide enough for you to sit on. Otherwise, you find yourself sitting on the arm of a chair or the back of a sofa --- or getting a message that says you can't sit there. Sculpty furniture can be even worse, because its bounding box can block you from sitting at all if the creator hasn't put a scripted sit target in it.

Take a good look at this thread >>> http://community.secondlife.com/t5/LSL-Scripting/Trying-to-make-an-object-follower/td-p/1354695 The OP was trying to solve almost exactly the same problem --- a very smooth, rideable follower that uses llSetKeyframedMotion. We managed to get it to work quite well, and I have used the solution myself a couple of times since.

SL can lose track of you sometimes when they have to pass your av from one server to another. Usually the worst that happens is that a teleport takes a little longer than usual or just fails, but occasionally the servers can lose you altogether. When that hapens, you crash but the system may still think that you are logged in. It's a rare occurrence these days, but it can happen, especially if your Maximum Bandwidth is set either much too high or too low. Try setting it to about 75% of your Internet download speed (measure it at http://www.speedtest.net/ ). For most people, that's about 1,200 to 1,500 Kbps.

Here's the long version of Ansariel's excellent answer: That's a communication problem between your computer and SL's servers. Information about your appearance has to be "baked" onto your avatar on your own computer, saved there, and then uploaded to SL before it's fully visible there. If the necessary information is messed up in transmission, you may end up with a borked file on your computer, or SL's servers may end up with a borked image. Either way, your av's appearance defaults to a fluffy cloud. What works to repair the damage for one person won't necessarily work for the next person, and it may not be the same thing that works for you tomorrow. See the full list of possibilities here >>> http://wiki.phoenixviewer.com/doku.php?id=fs_bake_fail . Start with the simple things at the top of the list and work down until you find what works for you today. You may find that the bake fail problem comes back repeatedly, even after you fix it with one of the suggestions on that wiki page. If so, you have a chronically weak Internet connection. There are many steps to take for repairing it. Perhaps the simplest ones -- ones that work best for most people -- are: (1) Don't Use WIRELESS. Wireless connections are inherently less stable than direct cable connections and are more vulnerable to interference. Then, (2) Reboot your router. Unplug it from the power for a few minutes to let it clear its RAM. Then plug it back in and let it get a fresh hold on an IP address.

1. Go to http://speedtest.net/ 2. Click "Begin Test" 3. When the test is finished, get the number for Download Speed. Multiply that number by 1,000. Your answer should be something like 2,000 Kbps. 4. Multiply THAT number by 0.75. That's your recommended Maximum Bandwidth setting for SL. Should be about 1,500 Kbps for most people.

Nalates told you exactly which one. You don't have to search for anything. ;-)

The simplest solution is to disallow building in the first place for anyone except group members. That would narrow down the list of potential miscreants if someone actually DID build there. Then just build yourself a simple device with llGetParcelPrimOwners on a timer. Trigger the timer every half hour or so and compare the current output with the previous one to see who's building and how many prims are involved.

Nope. Not unless the person you sent them to wants to give them back. Be glad that it was only L$6 -- about 2.4 cents -- instead of L$6,000. BTW, the safest way to send L$ is to open the person's profile and click the Pay button or the Send Money icon. If you try to give money by clicking on a person in a crowded room, you're likely to either hit the wrong person or some inanimate object.

Irene's got it. That's a choice, not a demand. :smileywink: PayPal also gives you a choice to use either a credit card or your bank as the guaranteed source of funds.

Not that I know of, Innula. Your solution is the most direct one, and it puts you in touch with the merchant -- probably a good outcome for both of you.

Some people who have ATI graphics cards are having this problem with the most recent V3 upgrade. If you had done a very simple search of this forum with the keyword PINK, you would have seen dozens and dozens of posts on exactly the same question during the past two months. :smileywink: See http://jira.phoenixviewer.com/browse/FIRE-4945 . For a quick but temporary solution, go to Preferences >> Graphics and disable Basic Shaders. For a more permanent solution update the 12.1 Catalyst driver from http://support.amd.com/us/gpudownload/windows/Pages/radeonmob_win7-64.aspx?type=2.4.2&product=2.4.2.... or run the AMD driver autodetect tool to update: http://support.amd.com/us/gpudownload/windows/Pages/auto_detect.aspx