Rolig Loon

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.

This is very interesting. We had a similar question a couple of days ago, and that was the first time anyone has reported seeing that error message. Here's my response to the first person who asked....... That is not a message from LL. That's coming from your own computer. Basically, it is telling you that you have been asking it to do too many things and its memory is getting overloaded. I suspect that the message will go away if you reboot your computer and then don't try to do quite so many things at once when you start up again. (It also may be that some program that you are running has a memory leak that causes it to use more and more memory over time.) Someone else may have a different insight. I do find it odd that we have now had two people ask this question this week, so maybe there is some SL component causing it. You might try opening your Task Manager in Windows to see what's using a lot of CPU. In particular, look to see if there's more than one (or maybe two) copies of slplugin.exe running at the same time. That plugin is supposed to cancel when you log out of SL, but it sometimes doesn't. If so, you could end up with extra copies in memory unnecessarily. Stopp all but one.

Actually, all viewers have the Character Test option. Most people can solve a bake fail issue with simpler methods, though. Character Test is a nice one to have if nothing else works.

You are asking mostly general questions about scripting, so the smartest thing to do is (1) spend some time with the tutorials at http://wiki.secondlife.com/wiki/LSL_Tutorial to get a basic understanding of LSL and some feel for basic scripting logic (2) find some freebie scripts that are sort of like what you are aiming for and take them apart. Modify them a little bit at a time until they fit your needs. There are MANY places in world that have collections of free or low-cost scripts. Just use your Search tool and go exploring. It's hard to give you any more specific advice without seeing the script you are writing. Once you have made some progress and have questions about it, though, please come back and post your script here. That's what this forum is for. :smileywink:

That's a very common problem and it can have many diferent causes. What works for you may not be the same thing that works for someone else, or what works for you tomorrow. To see the full list of possible solutons, see http://wiki.phoenixviewer.com/doku.php?id=fs_bake_fail Start at the top of the list with the easier things (CTRL + Alt + R, change your active group, change your hair base ... ) and move down the list to more complicated things until you find what works for you today. These solutions work for ANY viewer.

I have always kept hidden files visible on any machine I have owned since the 1980s, too. I know the idea is to keep idiots from screwing around with files that might bork their entire system, but it's a real nuisance for most of us. It's Microsoft's version of LL's Basic viewer mode -- a system with training wheels.

Sparkle Mocha wrote: Rolig Loon i had done that and it still happens is what is so wild about it guess its stuck or my lap top saves my preferences i went to uninstall phoenix and i typed in my seach and delted all phoenix too and re dl new phoenix . Well, you're not removing everything, then. Your Preference settings are stored in two locations (for Local and Roaming settings). If you are still having trouble, I'd suggest posting your question in the in-world Phoenix/Firestorm users' support group. They always have support staff there who are better prepared to answer specific Phoenix questions than we are here.

If you are still seeing your old personalized settings after you re-install any viewer, then you aren't doing a clean reinstall. The user settings are all in the APPDATA folders that used to be in Documents & Settings when you were using Windows XP. You have to remove those too, not just the viewer files that are in C:\Programs. To do a proper clean re-install for Phoenix, see >> http://wiki.phoenixviewer.com/doku.php?id=clean_reinstall