Rolig Loon

Yes, any of the chat-type functions will work. Some make a better choice than others, though. Distance is obviously the biggest factor. You can't llWhisper to something that's halfway across the sim, and there's no point in llShout-ing if you know that you will always be within 20m of whoever you're talking to, where llSay is the best choice. llRegionSay is a good fallback choice for communicating between objects, because it can be heard anywhere on the sim. llRegionSayTo, on the other hand, can talk to other objects or to people. In your case, I'd use llRegionSayTo for talking to an attachment, because you simply send your communication to the person who is wearing the attachment --- no need to know the attachment's UUID. If the object won't always be attached, though, llRegionSay is the better choice. You never need to know the object's UUID to make llRegionSay work.

The way to check on "known issues" is always to look at the Grid Status Reports. I just did. There are no "known issues" with the billing system right now.

It sounds like you are trying to wear an item that is stored in one of your outfits. The things there are stored as links to the actual items, which are in folders elsewhere in inventory. If those links are broken, you won't be able to werar the items that way. Try just going to the items themselves. I assume that they are in your Animations forder or maybe your Objects folder, unless you have put them somewhere else.

It's not impossible at all. What you want is llSetKeyframedMotion.

This may be one that you need to sort out with the Linden Lab billing office. If you have a non-technical issue related to billing concerns, you can call the Linden Lab billing team at the following toll-free numbers: US/Canada: 800-294-1067 France: 0805-101-490 Germany: 0800-664-5510 Japan: 0066-33-132-830 Portugal: 800-814-450 Spain: 800-300-560 UK: 0800-048-4646 Brazil: 0800-762-1132 Long distance ( not free, but you can use Skype to save some cost ) : 703-286-6277 **Note: Support is offered only in English BTW, I understood you to say that you were having trouble buying Lindens. If that's not the case, but you are receiving an error message when attempting to use your credit card or PayPal to make a Marketplace purchase, please attempt to make the purchase using Linden dollars (L$) as the payment method. To purchase additional Linden dollars to complete your purchase: On the upper-right of the page, click Buy L$ In the Linden Dollars (L$) box, enter the amount of Linden Dollars necessary to complete your purchase Click Place Order Return to the Marketplace and check out using Linden dollars as your method of payment.

Visually challenged?

Maybe the sim where you have set as Home is off line. If you can log in at other places, explore for a while ..... go shopping ..... dance....... whatever .... and try TPing to your home later in the evening.

Here are some common reasons for credit card failure: You entered the credit card number incorrectly. You did not enter the billing address or entered it incorrectly. It should be the same address that appears on your bill. You did not enter the name on the card or entered differently from how it appears on the card. The credit card is not in the list of accepted payment methods (see http://community.secondlife.com/t5/English-Knowledge-Base/Billing/ta-p/700037#Section_.3) You did not enter the CVV (3 digits on the back, or 4 digits on the front for AmEx) or entered it incorrectly. The card is expired, or the expiration date was entered incorrectly. There are no funds available on the credit card to validate it. We send a US$1.00 authorization to ensure that a credit card is valid. This is not a billing, but the card must have at least US$1.00 available on it to pass validation. Your monthly payment limit is reached, and/or your bank is not authorizing any more transactions. The issuing bank has not pre-approved transactions with Linden Research, Inc. Contact the issuing bank to resolve the problem. If you are outside the US, your card may not be set up for international/overseas transactions (this is very common with Visa Electron). A common cause of payment method failure is the use of unsupported card types. At this time, the majority of prepaid cards are not compatible with our system, even if they bear the VISA/AMEX/Mastercard logo. This includes cards purchased at retail stores, rechargeable credit cards, and bank-issued check cards. If none of the above applies, contact your credit card provider to determine the cause. You may also contact Linden Lab Billing Support. Often the initial agreement can't be set up due to an unverified PayPal account. To use your PayPal account with Linden Lab, it must be verified and have a credit card on file as a backup funding source. Linden Lab does not accept e-check (bank account) payments through PayPal because they cannot be processed quickly enough to match the instant delivery of virtual goods and services. Therefore, we require that you have a credit card on file with PayPal as a backup payment source.

To downgrade your premium or Concierge account to basic, follow these steps: Log into the Second Life website. On the lef side of the screen, select Premium Membership. The Change Membership Plan screen opens, displaying a chart of Membership plans and prices. Select Basic Account. Click Save Changes. Your new plan becomes effective at your next billing date. Warning: If you downgrade to a basic account, you will lose all the land you own on the Mainland, and you will no longer have access to your weekly Linden dollar stipend or live chat support. You may continue to own land in private etstates. Make sure to sell all your land before you downgrade! Check the Land Manager menu in the left sidebar of your dashboard at secondlife.com. You may also wish to check your group land contributions and make arrangements to keep your group's land holdings in good standing.

WooHoo.

That's interesting. You actually get an error message that says slvoice crashed? It's not uncommon for voice to fail. It's a flaky feature at best, but it usually fails silently. One common reason for failure is having your Maximum Bandwidth set too high (in Preferences >> Network) . Ideally, it should be no higher than 75% to 80% of your connection's measured download speed (see http://www.speedtest.net/ ). For most people, that's about 1200 to 1500 Kbps (half that if you're on DSL or wireless). If you set Maxuimum Bandwidth higher than that, your viewer will be using all available bandwidth for its basic functions. You'll have less lag, but there won't be any bandwidth left over for voice or streaming media.

Yup.

It depends in a way on how fast the lights are supposed to blink and how perfect you want the synchronization to be. The faster they blink, the harder the problem will be to solve. You might tell your master script to do llSetTimerEvent(0.1);....timer(){ if (~(llGetUnixTime() - (gTime + 1))) { llSetLinkPrimitiveParamsFast(LINK_THIS,[PRIM_FULLBRIGHT, ALL_SIDES,TRUE]); gTime = llGetUnixTime(); llRegionSay(gChan,(string)gTime); } else { llSetLinkPrimitiveParamsFast(LINK_THIS,[PRIM_FULLBRIGHT, ALL_SIDES,FALSE]); }} EDIT: Ooops.. Got this master script backward at first.. Fixed now. Then tell your slave lights to do this llListen(gChan,"","","");llSetTimerEvent(0.1);....listen(integer channel, string name, key id, string msg){ gTime = (integer msg); gBlink = TRUE;}timer(){ if (gBlink && (~(llGetUnixTime() - (gTime + 1))) { llSetLinkPrimitiveParamsFast(LINK_THIS,[PRIM_FULLBRIGHT, ALL_SIDES,TRUE]); gBlink = FALSE; } else { llSetLinkPrimitiveParamsFast(LINK_THIS,[PRIM_FULLBRIGHT,ALL_SIDES,FALSE]); }} That should make the master and the slaves blink at exactly the same llGetUnixTime, with no more than a 0.1 second error.

That sounds very frustrating. I'd be annoyed too. Here are a few things to check .... 1. Look at the prim allowance on your land (in About Land >> Objects). If your house + furnishings + outdoor stuff are close to the maximum you are allowed, it should be impossible to rez anything else. However, there are circumstances under which rezzing too many things will force something else that was already rezzed to vanish. For example, if a griefer dumped a self-replicator object somewhere else on the sim, it could easily overload the entire sim's prim allowance and cause your things to disappear. 2. Look at the Options tab in About Land too. For maximum peace of mind, your parcel should be set to allow only you (or maybe group members) to rez things, and should only allow you or group members to bring object into the parcel. Setting those two options will prevent visitors from, say, rezzing a skybox at 3000m or lobbing grenades across the border. 3. On that same tab, check to be sure that you don't have the Autoreturn box checked or, if you do, check your objects to be sure that you were wearing the proper group tag when you rezzed them. (I can't believe how many times I have made that mistake. :smileyembarrassed: ) Incidentally, Firestorm has an option in Preferences that will force newly rezzed objects to take the correct tag for the parcel, even if you forget. It's GREAT. 3. If you are using Firestorm or Phoenix, which let you maintain an asset blacklist, check the blacklist to be sure that you haven't accidentally derendered your house. The other way to check is to ask a friend or your alt if they can see your house when you can't. 4. If you are using Firestorm or any other viewer that has an Area Search feature, use it to look for your missing objects. They may still be on the sim but not where they belong. That begs the question of how they might have moved, but at least you'd be able to find them. I'm sure there are other possibilities too, but these are the first ones that pop to my mind.

Actually, even the corrected sensor event that I just gave you contains a flaw. If the detected name is more than 24 characters long, it is truncated before it's stored in sensl. If the same name is encountered a second time, the long version is compared against the truncated version. The two obviously won't match, so the truncated name will be added again .... and again... and again.... What you really want is sensor(integer num_detected) { integer i; string name; for(i=0;i<num_detected;i++) { name = llDetectedName(i); if(llStringLength(name) >24)//if name characters are greater that 24 { name = llGetSubString(name,0,23); } if (!~llListFindList(sensl,[name])) { sensl += [name]; } } } BTW, I assume you know that the sensor event will only detect the 16 closest avatars that are within its range. .

Exactly. But your sensl list is never being loaded correctly because your sensor event is all messed up. When you have a problem like this, the best way to see what's going on is to pepper your script with strategically placed llOwnerSay commands. Try asking llOwnerSay(llList2CSV(sensl)) at the end of the sensor event and then again in the listen event.

LOL... The OP knew that in the beginning. He said... "Now as far as i can see you could only do this by checking the persons ip address which i think would be in breach of terms of use so i dont think il bother with it. Any ways i thought i would ask on here if there was any other way like get data ...."

Well, that's what you told the script to do. Your listen event says ... 1. If the message is "Add", create a new Dialog 2. If the message is anything else (like "Remove"), check to see if it is already on the list called sensl. 3. If the message is not on the list called sensl, add it to the list called accessl, and let me know. So that explains why the word "Remove" is added to the list. So why aren't any of the detected names added? Look back at the sensor event. The entire for loop is being ignored because there are no curly brackets around its scope. The sensor event should be written sensor(integer num_detected) { integer i; string name; for(i=0;i<num_detected;i++) { if (!~llListFindList(sensl,[llDetectedName(i)])) { name = llDetectedName(i); if(llStringLength(name) >24)//if name characters are greater that 24 { name = llGetSubString(name,0,23); } sensl += [name]; } } } The way it's written now, no names are being added to the sensl list at all. EDIT: It would help if I could write something without making typos. Sheesh. Fixed.

That's a very good question. It doesn't have just one answer. Part of the problem is that Second Life is a world created by amateurs. Almost everything you see was created by someone like me, a person with marginal talent and a fair amount of imagination. We don't know the rules for making great designs work efficiently, so we make good designs that get in each other's way. Being able to creat your own surroundings is a great strength of SL, but we create our own lag. Sometimes the problem is the Internet. Being far from SL's servers means that signals are more easily lost, or just take too long to get to your computer. Being on wirelesss doesn't help either. There are loads of ways that your information flow can be disrupted. Most of the time, though, lag is your own problem. You have an old computer, or one that's inadequate for SL's demanding graphics. You Are wearing way too much stuff as you wander around in SL. You are trying to see soo much from too far away. You are trying to see shadows and use other high-resolution features that will always take more compouting power than simple images. Read more about lag here >>> http://wiki.phoenixviewer.com/fs_very_laggy . This is probably the most common topic of conversation in SL.

@ Viper -- OK. Now I feel like the other half of Good cop, Bad cop. You learned a lesson. Second Life is not a game. It's as real as RL is and we're all real people. Every bit of land in SL is owned by somebody. If it's not owned by Linden Lab, it's owned by someone who shells out hundreds of dollars in land fees to Linden Lab every month. Occasionally you'll find a landowner who is pretty laid back (or who isn't paying attention) and will let you squat on his land for a while. Maybe you'll find a friend who will let you stay with her. Most of the time, though, landowners get very upset when they find you using their land to build on. You've just had a mild taste of the kind of reaction you might get. So ..... don't do it.

Go to Preferences → Graphics -> General; if you cannot see that tab full of options, click the Advanced button. Then enable, in order: Basic Shaders Hardware Skinning If either of those remain greyed out, then increase the level of Render Quality until they become enabled and can be checked. In some cases, worn mesh attachments will not render properly still. Go to Preferences → Graphics -> Rendering and disable both of the Alpha Mask Rendering options. If none of the above work - and make sure you try all of them first! - then in the top menu bar, open Advanced → Debug Settings, find MeshMaxConcurrentRequests and gradually increase the value. It is recommended that you not go over 64; try to keep it less.

For the simplest face lights, you don't need a script at all. Just do this.... 1. Rez a sphere and make it about 0.2m in diameter. 2. While you have the Edit panel open, go to the Features tab and select the box WAY at the bottom that makes it a light source. 3. Adjust the light Radius to 1.0m. You may want to use an Intensity that is lower than the default value too. 4. Name your sphere "Face Light" and take it to your inventory. 5. Find the Face Light in invenory and Attach it to your nose. 6. Use the Edit tool to move the Fac Light so that it hovers about 0.5m in front of your face (You may want to stand on a pose stand while you do this.) 7. Go to the Textures tab and set the Transparency to 100%. All Done. :smileywink: To turn the face light OFF, just detach it to your inventory again. BTW, if you really want to use your script, don't do steps 2 and 3. Just put the script in the sphere you create with the other steps. It ought to work.

Try an e-mail to support@payments.secondlife.com . It will be slower than a voice conversation, but should be as satisfactory in the end, and you'll have a printed record of what was said.

What she said ^^ . Rent a parcel somewhere and rez your home permanently. It's less pain for you and its definitely a more honest use of space.

Do be patient. Not everyone logs in to SL every day or checks their e-mail. If you still haven't heard in another day or two, follow it up with a second polite note and finally, if you STILL haven't heard, file a support ticket at https://support.secondlife.com/create-case/ , selecting Marketplace from the pulldown menu.