Rolig Loon

It is a little confusing, I admit. Perhaps the best way to answer is to point you to some things to read. You can think of animations as something like 3D movies. They are a complex set of instructions that act directly on your avatar to make its arms, legs, torso, and everything else move. You can learn about how animations are made by reading http://wiki.secondlife.com/wiki/How_to_create_animations and watching Torley's video at http://wiki.secondlife.com/wiki/Video_Tutorial/Creating_%26_uploading_animations . Now, something needs to turn the animation on at the right time. So, if the animation is the 3D movie -- I know it's a weird analogy, but hang with me here -- the script is like the projector that you need for showing the movie. You use a script to get the avatar's permission to animate it in the first place, to position it in the right place, to rez any objects (like a book) that might need to be part of the effect, to trigger other actions (playing a sound or flashing a light, maybe), and to send or receive any messages. This part of the process is just as tricky as making the animation itself. You can read more about it here >>> http://wiki.secondlife.com/wiki/Category:LSL_Animation and in the links it offers. ETA: The "LSL Viewer" you mentioned is really the LSL Editor, the in-world system that scripters use for writing and compiling their scripts. If you want to start down that road, I'd recommend following some of the tutorials at http://wiki.secondlife.com/wiki/Category:LSL_Tutorials

I do like your solution, Ceera. Elegant simplicity. And Drongle's :smileywink: There's always more than one solution to a structural challenge.

Nice work so far. :smileyhappy: OK.... llDetectedTouch functions give you a vector as output. The X and Y components tell you relative positions on their respective axes, on a scale from 0.0 to 1.0 with the <0,0> position inthe lower left (southwest) corner of the touched face (or texture, depending on which function you used). The Z coordinate is meaningless. So, you can use that information to find exactly what spot a user clicked, or what area s/he clicked in. touch_start(integer num){ vector My_Pos = llDetectedTouchST(0); integer Face = llDetectedTouchFace(0); if (( My_Pos.x <= 0.5) && (My_Pos.y <=0.5)) { llSay(0,"You just touched somewhere in the SW corner of face #" + (string)Face); }} As for your other question.... You'll need to use a timer event. Fire the first animation in the touch_start event and set a timer for however long it takes to complete that animation. Then fire the second animation in the timer event. Don't forget to turn off the timer after it fires. The only major thing that's missing from your script is a run_time_permissions event. It's being triggered by the llRequestPermissions function in your attach event, but you need the run_time_permissions event to actually process the permission request. The wise thing would be to use that event to pass control to a second state, in which you place the touch_start event and the timer. That way, those events can't be triggered until permission is given.

You can't do that. There's no way to sit on an attachment. You can both sit on the same object and you can control the object to make it move, however. Some of those systems are very convincing.

Pretty much any instant translator uses Google's system. I know that's true of the popular free translators (Universal and Simbolic) and of the built-in translators that most viewers use. There is no substitute waiting in the wings. I'm afraid we will have no alternative but cutting and pasting through Google Translate (http://translate.google.com/?hl=en&tab=mT) or Babelfish (http://babelfish.yahoo.com/). That's slow and clumsy, unfortunately, but we're stuck.

If I'm buying furniture, I do it in world. That's really the only way to see how big it is, how many prims it has, and what it looks like from all sides. You can't get that information as easily by looking at a picture in someone's Marketplace store. I'd hate to lay out L$ for a sofa and then find out that it is way too low, has lousy sit animations built into it, and looks goofy in my living room. Go to a showroom, kick the tires, compare with other furniture, and then buy. BTW, you can see how many prims there are on a sofa in that store by selecting it with your edit tool and looking at the prim count on the General page.

If you have rebooted your router and modem as Peggy suggested in answer to your previous post (http://community.secondlife.com/t5/Technical/SL-logging-me-out/qaq-p/1164163) and are no longer using wireless, and you are still having trouble, the next thing to try is reassigning the DNS settings you have been using. I suggest using the Google public DNS servers instead of the ones that your ISP has assigned you by default. You can learn how to do this by reading here >>> http://code.google.com/speed/public-dns/docs/using.html . If that doesn't solve your problem, you'll need to look at your Statistics Bar (CTRL + Shift + 1) to see whether you have excessive packet loss (greater thn 0.1%) or a high Ping Sim rate (greater than about 100). Given the results of things we have already suggested, a high reading on either of hose may indicate either that your router is failing or that your ISP is having trouble. Incidentally, if you need to come back and add further information or ask for more help, do NOT open yet another question. Just add information to this one by clicking the Options link in its upper right corner and selecting EDIT.

It's almost impossible to guess what's wrong or how to fix it (it that's possible) without knowing more about your computer and graphics card. To help, you can add important information by (1) Logging in and going to Help >> About Phoenix (2) Highlighting and cutting (CTRL + C) the information in that window (3) Opening your question here again and selecting the Options link in its upper right corner, then selecting EDIT (4) Pasting (CTRL + V) the information that you copied in step (2). Do NOT start a new thread. Just continue with this one. When we have that information, it will be much easier to offer a solution. For now, though, the general answer is that you are indeed demanding too much out of your graphics card. Until we can offer a better solution, open Preferences (CTRL + P) >> Graphics, UNcheck shadows, and reduce your draw distance to 64. See if that helps a little.

There are many reasons for that very common problem. What works 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.

Try adjusting the CAMERA_FOCUS_LAG parameter in llSetCameraParams. If it's non-zero, I can imagine it stuttering in your application.

Certainly. It still thinks that you are its owner, unless you had the foresight to reset its script before giving it away. The cure is to make a small modification.... key gOwner;default { state_entry(){ gOwner = llGetOwner(); } changed (integer change){ if (change & CHANGED_OWNER){ gOwner = llGetOwner(); } } attach(key id) { if (id != NULL_KEY) { //check if the HUD has got attached, not detached giChan = (integer)("0x" + llGetSubString(gOwner, 0, 7)) * -1; //compute a channel number based in the key of the owner } giPressable = 1; } .... leaving the rest of the script as is. The new global variable gOwner will be set to the current owner if the script is reset or if the HUD changes ownership. You could also do this by putting llResetScript() in the changed event instead, but this is a less drastic alternative.

As viewers evolve, it's inevitable that some older machines will always be left behind. We can hardly expect anything else. What's truly unfortunate, however, is that LL doesn't keep the Minimum and Recommended standards on its web site up to date. I suspect that many (most?) prospective residents never look at those, of course . Still, a newbie who comes to SL thinking that his/her computer meets Minimum Standards may find that the modern viewers won't let them even log in, much less have a pleasant experience in SL. At least long-time residents know what to expect and can make the decision to upgrade every once in a while, albeit with some grumbling.

It's probably not your fault. Some SL residents who are just learning to build have trouble figuring out how to make poseballs work properly, so there are quite a few faulty poseballs out there. Also, poseballs are one-size-fits-all devices, so the builder has to set them up so they will work properly for the "average" person who sits on them. If you are not "average" or if the builder expects "average" people who sit to be much taller or shorter than you are, that poseball will not look right for you.

There are no Turkish documents. In fact, there are few documents in any language. Many SL residents have created tutorials and there is the LSL wiki, created and maintained by SL residents -- all written in English -- but there is no information source created by Linden Lab.

As far as I know, you can't. But you can do what a lot of people like me do..... Open the Privacy tab in Settings and set Post on your Feed to NOBODY. That way, you'll never get comments there in the first place.

Oh. That's not what you described. So ... (1) Rez a cube: X = 0.58, Y = 0.5 , Z = 0.5 (2) Taper X = 1.0 (3) Slice E = 0.3 (slices on the Z axis) This can be whatever size you want, depending on how hollow you want the final object. (4) Duplicate Prim (5) Rotate duplicate 60 degrees around Y Repeat steps (4) and (5) four more times, to create a total of six indentical pieces, each rotated 60 degrees beyond the first. Assemble into a HOLLOW hexagonal prism. ETA: Note added in step 3 for clarity.

(1) Rez a cube (2) Taper X = 1.0 (3) Slice E = 0.5 (4) Duplicate this prim (5) Rotate duplicate 180 degrees around Y (6) Move it down until its long side and the long side of the first prim are in the same place. (7) Link the two prims (8) Smile. You have a hexagonal prism.

How can you possibly get gaps? :smileysurprised: Just take your second tapered prim and flip it upside down and stick it on the bottom of the first one. Each tapered prim is a trapezohedron. All you're doing is gluing their long sides together.

Open your dashboard at secondlife.com and select Land Manager >> My Mainland from the menu on the left side of the page. It will tell you where your home is. When you find it, go there and use World >>. Set Home Here to set that spot as your Home location. Once you've done that, all you need to do to go home is type CTRL + Shift + H.

That's a very common problem and there are many solutions. See >>> http://wiki.phoenixviewer.com/doku.php?id=fs_bake_fail . Start with the easiest ideas at the top on that site and work down the list until you find the one that works for you.

We don't get the problem either. Without more information, there's no way for us to guess why you can't log in. Do you get an error message of some kind? How far through the login process can you get? What are your computer specs? What viewer are you using? What have you already tried? Do NOT start a new question. You can add important information to this question by clicking on the Options link in its upper right corner and selecting EDIT.

See http://community.secondlife.com/t5/Viewers/my-memory-pool-is-low-what-does-that-mean/qaq-p/1162575/comment-id/2962#M2962. You are not the only person with the problem, but there IS a solution.

Cool. You can do it.

Your script isn't doing that, at least not directly. If the object that your script is in has no name, then some viewers will actually say "(no name)" instead of leaving the object name blank when you put a message in chat. I have had this happen, for instance, with scripts where I have written .... string name = llGetObjectName();llSetObjectName("");llSay(0,"/me Hello, Bob!);llSetObjectName(name); Firestorm will say "(no name) Hello, Bob!" . I have been too lazy or preoccupied to find a way to beat it. I suppose one solution, though, is to give the object a name like "." that most users will never notice.

She's blowing smoke. There's no rule about using the same name for your business as another SL resident, so nobody is going to ban you for it. However, it's good business practice to avoid selecting a name that will cause confusion. It can create bad feelings with competitors, as you discovered, and more importantly, can lead to confusion for your customers. What you do in this case is up to you.