Rolig Loon

Like Innula, I know close to nothing about Macs, but your system looks to have hardware that should handle SL without trouble. That leads me to suspect that the problem is in your Internet connection, either locally or further down the pipeline. Take a good look at these two articles in Nalates's blog, each of which suggests ways to diagnose connection problems. http://blog.nalates.net/2011/10/26/troubleshoot-your-sl-connection/ http://blog.nalates.net/2011/09/11/cant-login-second-life/ We get a lot of notes here from frustrated SL residents who swear that they have excellent Internet connections. Unfortunately, SL puts very different demands on a connection than web browsing, e-mail, or even most on-line games. It is very intolerant of packet loss, for example, and it crashes quickly if it loses the connection for much more than a second.

Character test is sort of a last ditch solution, if nothing else works. See http://wiki.phoenixviewer.com/fs_bake_fail

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, ball, or "wisp". 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.

Yes. Just click the little suitcase icon at the bottom of your opened Inevntory window.

OK..... Here's a sample, offered without comments as a place to start modifying from..... vector gBaseScale;integer gChan;integer gLisn;list gSizes = ["0.5m","1.0m","1.5m","2.0m","2.5m"];default{ state_entry() { llSetMemoryLimit(0x1000); gBaseScale = llList2Vector(llGetLinkPrimitiveParams(2,[PRIM_SIZE]),0); gChan = (integer)("0xF" + llGetSubString(llGetKey(),0,6)); } touch_start(integer total_number) { gLisn = llListen(gChan,"","",""); llSetTimerEvent(10.0); llDialog(llDetectedKey(0)," /nPick a size, any size",gSizes + ["Reset"],gChan); } listen(integer channel, string name, key id, string msg) { llListenRemove(gLisn); integer i; vector newsize = <0.5,0.5,0.5>; if(msg == "Reset") { newsize = gBaseScale; } else if (~(i = llListFindList(gSizes,[msg]))) { newsize *= (i+1); } llSetLinkPrimitiveParamsFast(2,[PRIM_SIZE,newsize]); } timer() { llSetTimerEvent(0.0); llListenRemove(gLisn); }} Don't hesitate to ask questions as you play with it and make it your own. :smileywink:

You have a connection problem, and that's creating another one. 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 blob." 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. Given the other problems you are having with lag, you will probably find that the bake fail problem comes back repeatedly, even after you fix it with one of the suggestions on that wiki page. That's because 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. Those things may help, or you may have more serious issues. See Nalates's suggestions for where to go from here if the simple steps doing work >>> http://blog.nalates.net/2011/10/26/troubleshoot-your-sl-connection/

Of course you're having trouble connecting to SL, if you're trying it on a tablet. The viewer doesn't work on a tablet.

You mean the little icon under your name, here in the forums? >>> http://community.secondlife.com/t5/help/faqpage/faq-category-id/personalization#icon

There's no "UNDO" for most editing functions in SL. To a limited degree, you can use CTRL-Z to step back through changes in the position or size of an individual prim if you are really lucky and haven't closed your editor since making the change. You can't undo changes in textures, color, or other prim parameters, however. That's why we always caution people to be sure to make a backup copy of anything they want to modify, even if it's something as simple as rehemming a prim skirt. Your only choice (other than buying a new copy) is to try and "reverse engineer" what you screwed up and hope that you don't make it worse.

Yes, I cleaned that up and found a couple of other small differences between the posted version and the in-world version last night. It's working fine now.

You mean like this? default{ touch_start(integer num) { llLoadURL(llDetectedKey(0),"This is the Second Life web site.","http://secondlife.com"); }} Insert your own URL and message in the obvious spots. Drop into a prim and click on it.

It usually takes more than a day to get a response to a support ticket, so don't be too surprised by the slow response. If it's an emergency, you should be able to buy L$ on one of the safe alternate exchanges >>> https://wiki.secondlife.com/wiki/Archive/Third_Party_Linden_Dollar_Exchanges . Meanwhile, consider the possible reasons for trouble with a credit card ... 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. Note also that LL does not accept debit cards or most prepaid credit cards.

Check your Preferences (CTRL + P) >>> Network & Cache >> Maximum Bandwidth setting. It may be set too high. For most people, a setting of about 1,000 to 1,200 is about right. People occasionally push that slider all the way to the right, thinking that it will give them more bandwidth to work with, and therefore less lag. For most systems, however, once you're over about 1,500 it will not help your lag at all. That slider is telling your viewer how much bandwidth it is allowed to use for basic functions like rendering textures, moving your avatar, communicating...... If your ISP has a bad day and you don't have a lot of bandwidth to spare, the viewer will use all that you have for those basic functions unless you set the Maximum Bandwidth setting lower. If the viewer uses all your bandwidth for the basics, it will have nothing left for voice and streaming media, so they'll get choppy or disappear completely.

Please note that the person who "divorces" is charged L$25. Go to the Partners page. Check the box that says "I, (your name), would like to dissolve my partnership with (your partner's name)." Click Submit. Your partnership is dissolved and your now-ex-partner is notified.

And .... ?

You did what? It looks to me as if your entire touch_start event looks like this ... touch_start(integer s) { if (llDetectedKey(0) == Avatar) { llDialog(Avatar, "\n\nSelect a color group", main_menu, channel); }} So, change it so that it looks like this instead ... touch_start(integer s) { llDialog(Avatar, "\n\nSelect a color group", main_menu, channel);} That's ALL you have to do unless there's more lurking in the part of the script that you didn't show us.

This part that says..... touch_start(integer s) { if (llDetectedKey(0) == Avatar) { llDialog(Avatar, "\n\nSelect a color group", main_menu, channel); } } } is checking to see if the person who touched the device (that is, llDetectedKey(0) ) is the owner (defined at the top of your script as Avatar). So remove the test. That means removing the entire line that says if (llDetectedKey(0) == Avatar) { . It also means removing a } bracket farther down in the touch_start event, but I can't tell you where that is, because you didn't show us that part of the script. It should be fairly obvious, however. Each { has to be matched eventually by a }, so keep going until it's clear that the accumulated { brackets aren't balanced out by }s.

Nickel Briand wrote: [...] A game to know if the player has left, shouldn t check llrequestagentdata, but should check llGetAgentSize or llGetObjetDetails on the avatar to know it . Because these last functions return a value when the player is online AND is in the same sim of the game . And a bug majoriy of games can t work when the player is outside the sim http://wiki.secondlife.com/wiki/LlGetAgentSize They are very few use cases who are grid wide . And even for use cases who are grid wide , you shouldn t use llrequestagentdata but you should check some http/urls of prims ( for instance huds , or bdsm collars ) [....] The example I posted is exactly the sort of sim-wide application that will fail if I use your solution. Because llGetAgentSize and llGetObjectDetails will not work when the avatar is outside the sim, those functions cannot substitute for getting DATA_ONLINE. It would be significantly more awkward (and less reliable) to use http and check for a failed response. There's no point in replacing an easy-to-use function with an unnecessarily complicated workaround. That's simply "bad scripting", to use your term.

Oooo... This turns out to be really tricky if you don't use the easy way out. (The easy way is to use a cut prim and Void's simple hinge.) If you don't use a cut prim for the envelope flap, you have to calculate an offset based on the width of the flap and the angle that you will be rotating it through. Here's what works, including the code necessary to close the flap again on a second touch. Notice that I was wrong earlier. You do not need to apply any rotation at all to the position offset, once you calculate how much the offset is. [Note: The flap on my envelope is a rectangular prim, flattened on Z and oriented so that it will hinge on its Y-axis, so the offset I need to calculate is on the X-axis. It's also necessary to offset on the Z axis, because otherwise the leading edge of the envelope flap does not stay level with the envelope as it opens. This was not intuitively obvious to me until I started messing with it, but you'll see what I mean if you leave the Z correction out.] rotation adjust;vector offset;default{ state_entry() { adjust = llEuler2Rot(<0.0,-120.0,0.0>*DEG_TO_RAD); vector Size = llList2Vector(llGetLinkPrimitiveParams(2,[PRIM_SIZE]),0); offset = <-(1.0-llCos(llRot2Angle(adjust)))*0.5*Size.x,0.0,-llSin(llRot2Angle(adjust))*0.5*Size.x>; } touch_start(integer total_number) { if (llDetectedLinkNumber(0) == 2) { list temp = llGetLinkPrimitiveParams(2,[PRIM_POS_LOCAL,PRIM_ROT_LOCAL]); vector Lpos = llList2Vector(temp,0); rotation Lrot = llList2Rot(temp,1); adjust = ZERO_ROTATION/adjust; llSetLinkPrimitiveParamsFast(2,[PRIM_POS_LOCAL, Lpos + (offset = -offset), PRIM_ROT_LOCAL,adjust*Lrot]); } }}

Darkie -- The easiest way to solve the problem is to avoid it. I'll send you a demo in world that uses Void's simple hinge script. It works like a dream. (I'll still keep poking at your way of doing it, though, because it ought to work, even if it's much harder. )

In this context, it's the amount you want to move the child prim from its current position. So, if you want to move it 0.1m in the direction of its local X-axis, the offset is <0.1,0.0,0.0> . The logic of my suggestion was that you want to set the prim's position to its current local position, corrected by moving it some distance that is, itself, adjusted by rotating it by some increment (160.0 degrees) relative to its current local rotation .... if that makes sense. :smileywink:

Not at all. Click on the FORUMS link at the top of this page, then scroll down through the list of forums until you reach Wanted. It's in the Commerce forums.

Do you have a question? If so, ask it. Please create your own thread instead of burying it at the end of a necropost that someone else finished 9 months ago.

You may be having a problem with Friendlist displays users as Unknown or (loading), teleports fail, assets will not save . If so, the solution that seems to work is .... (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/

Offset from what? Your best bet is either to create a mesh or sculpty or, if you can't do that, create a track by piecing together cut sections of conical prims and straight sections. Since you can make prims up to 64m in each dimension, you ought to be able to make a decent track easily.