Rolig Loon

Without knowing more about your setup or the error message you may be getting, it's hard to know exactly what to recommend. In general, that sort of behavior is typical of a flaky Internet connection -- usually one that's flaky right at home. The generic advice, which works in a surprising number of cases, is to reboot your router and let it get a fresh hold on an IP address. Just unplug it from the power for a few minutes while you go for coffee. The other bit of generic advice is to avoid wireless, which can be problematic even on a good day for a lot of SL residents. Beyond those two standards, it is smart to check your firewall and antivirus programs to be sure that they haven't decided to block SL. An upgrade to either of them could suddenly make them misbehave. Take a good look at Nalates's blog for more in-depth suggestions about diagnosing and repairing your connection >>> http://blog.nalates.net/2011/10/26/troubleshoot-your-sl-connection/ If you have more specific details to add, or if you simply want to let us know whether anything we have suggested worked, click on the Options link in the upper right corner of your question and select EDIT. Please do NOT start a new thread.

I haven't seen a viewer do this or the transparent Moire trick in your other post for a long time -- maybe three years. It used to happen for me in the old 1.23 viewer a lot. As I recall, it stopped when I updated my graphics drivers. I can't swear that's the solution, but you might give it a try. Nvidia Video Driver Latest driver Last checked Feb 6th- Windows: 285.62 (Oct 24) beta: 295.51 (Jan 31) - Linux: 290.1 (Nov 22)ATI Video Driver Latest driver Last checked Feb 6th- Windows and Linux: 12.1 (Jan 25)Intel Video Driver Intel driver download page Intel does not have a universal driver set. Please go to Intel's site and select the appropriate download.

Yes, there is. You and many other people -- do a quick search of this forum to see loads of questions like yours -- are dealing with a bug that Linden Lab technicians are trying to fix >>> Problem of not being able to rez on my land continues Essentially what's hapening is that the servers can't tell where the edges of your parcel are, so they assume that you are trying to rez beyond them, on your neighbor's land. The workaround is to rez as close to the middle of your parcel as possible. Try rezzing a cube near the center of your parcel, and do it again and again and again until it works. When you find that spot, you will be able to rez other things there and then drag them to where you want them.

The only way to tell whether something is overheating is to measure it. It's not good enough to just say that nothing seems to be overheating. What you are describing is a classic symptom of a computer that is trying to avoid self-destruction. Go on the Internet and Google "computer temperature software." There are some good, inexpensive programs -- and some free ones -- that will monitor temperature and will adjust your fan speeds to try and keep the machine cool. Before you even get the software, though, open the case of the computer now and use a can of air to blow out all the dust bunnies and cat hair. I do that regularly once every month or two. It's amazing how much gets in there. Overheating is serious business, and SL puts a heavy load on your system. If you don't do something about this now, you will fry your graphics card or worse.

That's not the way you do it in LSL. If you want to change multiple prims, put your SLPPF command in a loop and change each child prim individually. Here's one way .... integer i = 10;while (i < 15){ llSetLinkPrimitiveParamsFast(++i, [PRIM_GLOW, ALL_SIDES, 0.9]);} A better way is to name your target prims something like "Glow" and then do this... integer i = llGetNumberOfPrims();while ( i ){ if (llGetLinkName(i) == "Glow") { llSetLinkPrimitiveParamsFast(i, [PRIM_GLOW, ALL_SIDES, 0.9]); } --i;}

If you are the current owner, you can return anything that is on your land. It doesn't make any difference what the status of their owner is. You're just clearing the stuff from your area. If you have trouble, see if the sim owner can do it. If you're on the Mainland, submit a support ticket and let LL clean it up.

Terceros los cambios de divisa utilizar la API de Linden Lab de riesgo para determinar si es seguro para ellos que le permite utilizar su servicio. Cuando la API de riesgo les dice que usted es un riesgo de crédito, se le puede decir que se niegan a aceptar su pedido. La API de riesgos puede haber estimado que tiene un mal historial de crédito, o puede haber un error. La mejor solución para usted es probablemente usar la Lindex en lugar de un intercambio de terceros. La oficina de Linden Lab, la facturación podría ser capaz de darle más información. Si usted tiene un problema de carácter no técnico relacionado con las preocupaciones de facturación, puede llamar al equipo de Linden Lab de facturación en los siguientes números gratuitos: 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 De larga distancia (no es gratuito, pero se puede usar Skype para ahorrar un poco de costo): 703-286-6277 Nota **: El apoyo se ofrece sólo en Inglés

I'm assuming that yours is http://my.secondlife.com/Gwendoline.Philbin . That worked for me when I looked at your profile just now.

Yes. If you have full perms on any texture, including a snapshot, you just have to double click on it in inventory to open it, and then click Save Image to download it to your computer. (The words vary from one viewer to another, but the command is still the same and it's pretty obvious.) If you don't have full perms, though, you cannot download the image to your computer legally.

The problem is that you haven't created a Received Items folder in your own viewer yet. Go to Marketplace and order a free item --- https://marketplace.secondlife.com/p/Direct-Delivery-Linden-Bear/3290638 or https://marketplace.secondlife.com/p/MAGIC-WAND-Stops-Animations/3475671 maybe. When you receive the item, your viewer will automatically create the Received Items folder. Then log out of SL and log back in again. You should be able to use the Merchant Outbox then. Review the instructions for setting up Direct Delivery at http://community.secondlife.com/t5/English-Knowledge-Base/Marketplace-Direct-Delivery-migration-guide/ta-p/1293139

Can't TP to it, or can't find it? If you can't find it, just go to your dashboard at secondlife.com and follow the links to Land Manager >> My Mainland, where you will find a SLURL to your Linden Home. If you can't TP, try going to another sim first -- like Smith or Aqua --- and then teleporting. Or, try flying up to a high elevation first --- maybe 2000m -- and then teleporting. There are other suggestions at >>> http://community.secondlife.com/t5/English-Knowledge-Base/Landmarks-teleporting-and-SLurls/ta-p/700123#Section_.1a If you have already set your home location with World >> Set Home Here, then you ought to be able to teleport directly by clicking on the Home button in your viewer or typing CTRL + Shift + H.

Check to be sure that you are downloading the Mac version and then see whether you have a firewall or an antivirus routine that is blocking it.

Take a look at http://community.secondlife.com/t5/LSL-Library/Linkable-Multiprim-Sliding-Door/td-p/722649

From the very clever support staff at Firestorm ... If you find yourself suddenly starting to wear your entire inventory, here are some suggestions for how to fix the problem. Please do them one at a time; the initial methods are similar than later ones, and will often work. If a method fails, then move on to the next one. Please also follow the instructions as exactly as possible. Method 1 Right click the Current Outfit folder and select Remove from Current Outfit or Take Off. Method 2 Open the Current Outfit folder (no, don't click on the Worn tab; find the Current Outfit folder), and delete everything inside it, then relog. Method 3 If the above doesn't solve the problem, the fix below usually works - though it may need to be repeated a couple of times: Go to Hippo Hollow Make a temporary folder in your inventory; in that, put a *copy* of your skin, shape, hair base and eyes - and if you like, a base layer garment like jeans or a dress. NO PRIMS Right click the folder you just made, and select Replace Outfit. No Add, not wear, but REPLACE Once that has done, relog to last location - ie, back to Hippo Hollow. Make sure you are still wearing only the things from the temporary folder you made At this point, you can put your normal avatar back on.

Use the bake fail suggestions that Val and Nalates have both given you. They work. From what you have said, however, those solutions may not fix things for you permanently. If you have chronic bake fail problems, then all that the solutions on those web sites will do is help you cure the symptoms -- not the issue behind them. That's fundamentally a weak or flaky Internet connection. Unlike web browsing, e-mail, or on-line games, Second Life puts a very high demand on having a continuous, high-quality connection between your computer and LL's servers. If you have competiton for your bandwidth, or if your signal is losing information or taking too long to travel between computers, you will start to have chronic bake fail problems and may have severe lag and crashing. The best steps you can take are (1) avoid using a wireless connection -- a common source of problems for many residents and (2) reboot your router by unplugging it from the power for a few minutes. For more serious connection issues, consult Nalates's blog here >>> http://blog.nalates.net/2011/10/26/troubleshoot-your-sl-connection/

If you are getting that message, you are trying to enter the hard way --- at least hard for a newcomer. The "normal" way to enter is by clicking on the Second Life viewer's shortcut on your computer's desktop. That's assuming that you have downloaded and installed a viewer >>> https://secondlife.com/support/downloads/?lang=en-US . Once you have used SL for a while, then you can teach your web browser how to find the viewer, so that it will let you enter SL by the back door -- with a SLURL >>> http://community.secondlife.com/t5/English-Knowledge-Base/Landmarks-teleporting-and-SLurls/ta-p/700123#Section_.2. That's the method you're trying now, but you aren't set up to do it yet.

If you are simply using the 64 boxes as tiuch-sensitive swtiches, to tell when a person have selected that particular box, use llDetectedTouchST. Divide a face of a single prim into 64 areas, and identify each one by its boundary coordinates. That will save you 63 prims. However, if you want each box to change its appearance when someone touches it -- maybe by displaying the person's photo -- then you need to use 64 separate prims. That is a very tedious challenge. I do not recommend it unless you believe that it is absolutely necessary, and unless you have the extra prims to burn. If you want to make the clicked box turn red temporarily, try rezzing a temporary red cube at the coordinates of the box. It will highlight the selection for a little less than a minute and will then disappear.

Talia Davidov wrote: [...] Is there a reason why using owners UUID instead of objects UUID? If I use the object UUID instead of the owner, then each device has its own random channel? That way if I rez two devices that are exactly the same I won't get cross talk? Or am I missing something . ..just curious. Thanks It depends on the application. I'll use the owner's UUID if I want several scripted devices owned by the same person to be able to communicate on a common channel. I don't need to go to all the trouble of passing a new random channel to each device, since they all know the owner's UUID and can generate the unique channel automatically. However, if I'm dealing with a situation in which a person may have several devices that shouldn't talk to each other, I'll use an object's UUID. It's easy enough for an object to create a channel based on its own UUID, and there are several simple ways for other objects to get its UUID and do the same thing.

It's kind of a waste to read a notecard for just one value. If you want the owner to be able to pass a private chat channel number to the script, just tell her to type it in the object's Description field and read it at run time with integer Chan = (integer) (llGetObjectDesc() ); In general, though, Innula's answer is a straightforward, commonly-used one. My own shortened version is integer Chan = (integer) ("0xF" + llGetSubString(llGetOwner(),0,6)) + offset; where offset can be provided in the object Description field as described above.

Your viewer and SL's servers have temporarily lost the ability to talk to each other. Unless there's a problem with the servers (Always check http://status.secondlifegrid.net/ first), it's probably something on your end. So.... (1) Try shutting off your computer, unplugging the router and modem for a couple of minutes, and then plugging them back in and restarting. That simple step may clear up everything (2) Change your DNS settings from whatever your ISP assigns you as a default. Use Google's free public DNS servers instead. Here's how >>> http://code.google.com/speed/public-dns/ (3) If things are STILL messed up, contact your ISP. Maybe they are working on their Internet connections. Mine go down for about 20 minutes once a month or so while they are vacuuming dust out of their servers, or whatever they do.

Emmett --- I think it's about time for you to visit your closest good-sized bookstore and buy a Photoshop manual. There are dozens out there, so thumb though all of them until you find one that matches your style. Nobody ever learns all of the fancy options in Photoshop, but you truly need to learn the basics. Asking here -- in question at a time as you run up aginst a new problem -- is terribly inefficient and a crummy way to learn.

I truly do not understand what you are asking, but if it involves getting an avatar's key from its Display Name, you will not be able to do it. Display Names are not unique. There could be 50 avatars with the same Display Name. Even getting a UUID from a username is difficult. There is no LSL function that can do that, so you need to search an external database, like this one >>> http://wiki.secondlife.com/wiki/Name2Key . I'm not sure why you need to do any of that, of course. As I said, I cannot understand what you are trying to do, but if you expect someone to touch an object in order to pay it, you will automatically know the person's UUID from the touch* or money event.

It's unlikely that anyone is going to bother to work through a script in that format. It's impossible to read. That said, the answer is to either put the rotation in a timer and simply reverse its direction every time the timer triggers or .. better ... write yourself a new script that uses llSetKeyframedMotion, with which you can execute a smooth rotation in a looped or pong-pong fashion. You can do the whole thing in a few lines of code.

Gift purchases are problematic. You'll find several longstanding JIRAs on this topic. The surest way to give a gift is to send your friend the L$ and indicate tell her what you'd like her to buy with it. That takes the surprise and magic out of it, but it lets her know what you think she might really like, gives her a chance to get something that she really wants, and is more likely to result in a successful delivery. If you don't want to go that route, the next best cure is to be sure that your friend has previously received an item from Marketplace. Somehow the servers have a hard time delivering gifts to people who don't have a delivery record on file. So, ask her to buy a free item from Marketplace -- like this >>> https://marketplace.secondlife.com/p/Direct-Delivery-Linden-Bear/3290638 or this >>> https://marketplace.secondlife.com/p/MAGIC-WAND-Stops-Animations/3475671 . Once she has received her free item -- be sure that she checks her Received folder --- then try sending her your gift.

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. Your av's appearance may default to a fluffy cloud or you mayend up wearing several parts of yesterday's clothes, so that you look like a patchwork quilt. 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.