Rolig Loon

To quote the LSL wiki (which is only as infallible as we make it), the catch is that "scripts may hold permissions for only one agent at a time. To hold permissions for multiple agents you must use more than one script." If that were not so, this nice little discovery would help make some really great couples dance machines.

See the long-running thread on this topic at http://www.sluniverse.com/php/vb/scripting/32062-script-read-song-information-stream.html

My guess is that LL will treat this as yet another "disagreement between residents" and will ignore it..... until it blows up and they can't. It all depends on how many AR's they get and who's watching.

The reason for turning off your translator, as Cinn and Chelsea have suggested, is that the built-in translators no longer work unless you have paid for an account with Google for their translation service, or have a free Bing translation account. Google pulled the plug on their free Tranalation API in December, so that service is no longer available. If you have an account number for one of those two subscription services, you can enter it in Preferences >> Chat. Also, there are still some translators available in world that do not rely on Google.

When you are shopping in Marketplace, it's probably wise to avoid the shopping cart and just buy items individually. Aside from occasional problems with the shopping cart itself, you may run into problems getting your purchases delivered if you buy too many things at once. Items that you buy are actually delivered from each Merchant's Magic Box, a scripted device that sits on land that the merchant owns somewhere in SL. If a Magic Box gets to many requests at once, it can easily lose track of what it's doing, so it may report that it sent some items that were not, in fact, delivered at all. The two ways around that problem are (1) buy Marketplace items one at a time or (2) shop in world.

Interesting. As I said, I was pretty sure that other people had discovered this behavior before me. Like most people, I stopped paying any attention to that ancient wiki two or three years ago when it stopped being updated. It does have some chatty tidbits like that one that never made it into the current wiki, though. Thanks, Clarke. Now, all we need to do is get the note into the current wiki ........... EDIT: Done, in both llSitTarget and llLinkSitTarget.

Quoting LoveAngel Lyre...... "Hello SpinWeaver and welcome to SL Forums. If you use the last version of Viewer 3 (3.2.4) is a known issue. Several other residents reported this here. You can roll back to the previous version (3.2.1) In this case set your software updates not to be installed automatically (preferences --> setup). Alternatively download the beta (3.2.5)." You might also try turning off OpenGL Vertex Buffer Objects (VBO) in Preferences >> Graphics >> Hardware settings and see if that helps.

I suppose others have made this discovery, but I just realized that the llLinkSitTarget function that was added late last year makes it very easy to seat several avs on the same object, in a way that I hadn't expected. I have a simple park bench made of two sculpties (the seat is the root prim and the legs are prim 2). I put this script in it.... default { state_entry() { llSetMemoryLimit(0x4000); llLinkSitTarget(1,<-0.5,0.32,0.1>,llEuler2Rot(<0.0,0.0,PI/2>)); // Sit on the "seat" prim llLinkSitTarget(2,<0.2,0.35,0.4>,llEuler2Rot(<0.0,0.0,PI/2>)); //Sit on the "leg" prim } }and two avs can sit on the seat. If both avs click on the same prim, the first one to sit down is always assigned to the target on that prim, and the second av is seated on the other prim. So, if both avs click only on the "seat" prim, the first av always gets link sit target #1 and the second always gets target #2. If both click only on the "leg" prim, then the first one is assigned to link sit target #2, and the second av gets target #1. The thing that surprises me is that the second av is always seated on the "other" prim without having clicked that prim to sit, and that the system knows that the second av should default to the prim with the empty sit target. As I say, others have probably already made this discovery, but I just found it and I think it's cool. It adds a new dimension to multiple seating, not yet documented in the LSL wiki. :smileyhappy:

ALL of your cache is on your computer. That's the whole idea. A cache is a local storage location (local = on your computer) where your viewer saves copies of things that it has downloaded. Having downloaded and stored them once, it doesn't have to go to the trouble of doing it again, over and over and over, every time you want to use the same information. Your texture cache, for example, saves copies of every texture that you see on screen in SL. If it didn't do that, you would have incredible texture lag. You would see every object as gray while your computer downloads its texture again. Angel and Cinn have told you where to find it

Well, since it is getting baseRot from that prim's local rotation, just add an extra rotation to it. You want to rotate the local X axis vertical, so (....doing this in my head .... ) this ought to work...... baseRot = llEuler2Rot(<0.0,PI/2,0.0>*llGetLocalRot(); Thing is, you are using an overkill door script for a job that really doesn't need all of its baggage. It would be much better to write yourself a short script that handles the movement instead of modifying this monster. It's easy to get lost in this thicket of code.

Good! I mean, good that you meant "above 10." You had me worried there. Lag is a tricky problem to solve. There are many sources, and the ones that are most important for most people are on their own computers. That makes lag difficult to diagnose from a distance. Take a look at the suggestions at http://wiki.phoenixviewer.com/doku.php?id=fs_very_laggy . I already suggested some of the more obvious ones, and you have apparently tried them. There are others, though, so give them a try till you find what works best for your system.

I wondered where they were coming from. There's a small knot of newbies who like to stand in the unoccupied parcel next to mine and chatter while they try on every blessed thing in their wardrobe, and they all have that sort of chunky-body, puffy lipped look. I agree, it's not a very flattering shape. /me makes a note not to visit IMVU.

It can sometimes take anywhere from a few minutes to a day or more for your items to be delivered, especially if the merchant's Magic Box is temporarily out of service or the sim it's on is offline. (We had a grid-wide system failure today, so that messed up a lot of things, including Magic Boxes.) Unfortunately, the system will sometimes mark the item as "delivered" once the Magic Box gets the order to send it out, whether it actually gets sent or not. It's definitely the weak point in the system, which is why LL is changing it sometime this Spring. Not that it helps now, but to remember for the future: (1) Don't overuse the shopping cart. It is easily confused if you put more than a couple of things in it. (2) Don't buy things from Marketplace (especially LOTS of things) unless you are in world to receive them at the time. We each have an "in box" that holds IMs, notecards, group notices, group invitations, and anything that is delivered to us if we aren't in world at the time. That "in box" can only hold 25 things, total. If anything else comes in, it isn't saved. It is gone ... poof .... forever. If you have a mess of things delivered from Marketplace and half your friends send you notecards, that in box will be capped and you will never know what happened. So, what do you do now? ....... To get a record of the individual items in your order, open Marketplace and click the My Marketplace menu at the top of the page. Select My Account >> Order History from the pulldown menu. If you do not receive items within about 24 hours, you should cut and paste the information about a missing item from that Order History and send it in a IM or notecard to the merchant, along with a polite message requesting redelivery. Most merchants are very kind and willing to redeliver. This happens all the time and they are aware of it. Do be patient, though. 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.

You probably ought to call Linden Lab's billing office to figure out what's messed up in your acccount. The billing team is available 24 hours a day, seven days a week. Toll-Free (US/Canada) 800.294.1067 Long-Distance 703.286.6277 Local Toll-Free numbers * 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 * Support is in English Only

At the risk of repeating myself yet again ..... You are not the only one. Look down the list of questions before yours and you'll see several others. Some people who have ATI graphics cards are having this problem with the most recent V3 upgrade. 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

That's fascinating, Lucinda. I can't find any logic to the way it behaves, but you are right. You can easily rez an object well beyond 10m from the center of the rezzer. The odd thing is that I can rezz up to 31m away if I have a 30x 30 x 1m rezzer, but up to 20m away if I have a 15 x 15 x 1m rezzer. Neither one makes sense to me. Your note led me to believe that I might be able to rez as far away as the rezzer's maximum dimension -- surprising in itself -- but apparently you can rez up to some random distance beyond even that. This is not what I would have expected at all. I'll do some more experiments to see if there is a rule of some kind that would predict the maximum rez distance. If you or anyone else knows what it is, though, I'd love to know. And again, the wiki ought to be updated once we know what's going on. This is cool. :smileyhappy:

As we have explained in your previous threads on the same topic, we are all SL residents like you. We can't put your inventory back together. All we can do is give you advice about how to do it yourself. If nothing that we have suggested works for you, the only choice you have left is to either call Live Chat (if you are a Premium member) or file a support ticket.

I don't know what your avatar is trying to charge, but the "white egg"problem is very common and easily fixed. 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 file. Either way, your av's appearance defaults to a fluffy cloud or a "white egg." 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 possibilitites 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. The plug it back in and let it get a fresh hold on an IP address.

I suggest that you re-read all of the answers to the other times you have asked versions of this same question here during the past week or two. The bottom line is that it is extremely hard to earn "real money" in SL. For the same amount of time and effort, you can earn a LOT more by getting a job in RL. The only people who make a fair amount of money in SL are creators who have a special talent, and some very lucky entrepreneurs who have managed to invest in land at the right time and are getting a good return on real estate rental and sales. If you want to work, do it because you enjoy it. If you are coming to SL in order to make a lot of money, you will almost certainly be disappointed.

Interesting. I wonder if that behavior is new since LL changed the limits on prim size last year? If so, the caveat in the wiki page fo llRezAtRoot should probably be updated.

Get the information about the sale from her Transaction History, so that you have the seller's name and the details about the purchase. Also, copy the record of the L$20,000 transfer, with all of its details. Then have her file an Abuse Report that includes both sets of information. She must do this. You cannot. Also, copy the sam information into a support ticket and file it at https://support.secondlife.com/create-case/ . The Abuse Report will put LL on the track of the person who recived the L$, and the support ticket will alert the Markeplace team to a problem on the site. BTW, please note that your girlfriend did not buy anything on SLX, which has not existed for well over a year. She bought on Marketplace.

We cannot do anything for you here, because we are all SL residents like you. There are no Lindens here. You should probably try calling the LL Billing Office to explain your problem. The billing team is available 24 hours a day, seven days a week. Toll-Free (US/Canada) 800.294.1067 Long-Distance 703.286.6277 Local Toll-Free numbers * 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 * Support is in English Only

See Billing and Trading Limits to check your limits and ensure that your difficulties are actually related to your billing and trading limits. Your level will be highlighted if you're logged in. If this does appear to be the difficulty, you may request a review of your account to increase your limits by submitting a ticket. Premium account holders select: Billing and L$ ticket type LindeX Tier Review billing type Basic account holders select: Special Questions - Basic account or Guest Login ticket type LindeX Tier Review We'll review your request and get back to you within five business days.

No. The solution is not to turn off the indicator. It's to take steps to increase your frame rate. ( Putting black tape over the "Check Engine" light on your car's dashboard doesn't make a problem go away. It just hides it. ) Try reducing your Quality slider by one step (from Ultra to High or High to Medium), or reducing your draw distance, or turning off anti-aliasing or anisotropic filtering. You will see a slightly lower quailty, but your FPS will improve because the viewer is matched better to what your computer can handle.

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. Be sure you updated your card's expiration date in the Second Life Billing Information page. The credit card is not in the list of accepted payment methods (see above) 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). If none of the above applies, contact your credit card provider to determine the cause. You may also contact Linden Lab Billing Support.