Rolig Loon

This is a known issue, the recurrence of an old bug. Fortunately, most people are able to get around it with a fairly simple process. As explained by Marigold Devin, our queen of the ghosts, " Not guaranteed, but has worked for me (again) today. Bring up log in screen and change the start login location to Furball or Chalvez or Quarrel or Itress (these are not magic sims, just nice empty ones). And try to log in, and try and try and try and try and try. It does often take MANY attempts, but it is possible (if you believe in yourself) to log back in this way. However, the stuck presence will remain in the sim/server it is stuck on until you teleport across to within range of it. Then you should be ok again" Give it a try, and do be patient. You are not alone. ETA: As an alternative, if you are a Premium member, just call Live Chat and explain your problem. They'll fix you up right away.

Joshewa Daniels wrote: Use llRemoveInventory(llGetScriptName()); to remove a script from the object without effecting anything else just removing the script @ Royalbank: That's not a complete script, so it won't actually do anything. That's a good thing, actually, because it's not necessarily true that it won't affect anything else. After all, it will stop whatever the script was meant to do. Since you didn't tell us what your object is or what the script is for, I would be very cautious about recommending that you remove it. A vehicle or a radio without its script, for example, is pretty worthless. Also, some prim properties are set by a script and can only be unset or removed by a script. Hover text and particles fall into that category, for example. If you remove the script that controls them, the effects will still be in your object -- and uncontrollable except with another script. The proper way to remove them (if you want to) is to use a scrubber script that deletes not only the script in your object but all the script-dependent properties as well. Again, however, you wouldn't want to take that step without knowing what the script in your object is meant to do. The bottom line and the answer to your original question is that it might be possible to remove the script from your object -- whatever it is -- without harming it, but you would be unwise to do it unless you either had a backup copy of the object to play with or understood exactly what the script was there for. THEN you could either use a scrubber script of some kind or simply reach into the object's contents and delete it manually.

Tell us what the object is and what the script does. We might be able to help. You can add information to this question by clicking on the Options link in its upper right corner and selecting EDIT. Please do NOT start a new thread.

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, a white egg, or a quirky circle. 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.

"System" clothes that are essentially painted on your body (like blouses, for example) fit directly to your body, whatever its size or shape. Prim clothes, like most skirts, do NOT adjust to fit you. Some have a resizer script built in, but most do not. You need to learn how to do some gentle, judicious resizing yourself. It's good practice and MUCH easier than altering RL clothing. Just be sure you make a backup copy before you practice. Sculpty clothes (some skirts and many attachments) behave like prim clothes but are usually easier to resize because they have fewer pieces. Mesh clothes cannot be resized (at least for now), so you're stuck with whatever size and shape you bought.

Preferences >> Audio & Video >> Streaming Preferences >> Settings ... Highlight a URL in the "Blocked" list and click REMOVE. In the future, please do NOT add your question to the bottom of someone else's unrelated question .... especially one that is several months old. Start your own new question.

I have never dared to cancel a TP in progress myself, since I am all too aware of the problems that people have as they move from one server to another. You are most vulnerable to crashes during those transfers, and you are most likely then to develop inventory loss problems. As far as I am aware, there is not Debug setting that does what you want, but I wouldn't use it if there were.

Unlike Lindal, I am way out in the sticks in the U.S.. Well, sort of way out, anyway. I can get 5Mbps service for a very reasonable price, and could upgrade to 10Mbps if I really wanted to. As has already been pointed out, though, the quality of your graphics card makes a lot more difference than the speed of your connection, assuming that you aren't on a dialup or using two tin cans and a piece of string. A direct cable connection will almost always give you better service (i.e., less crashing and fewer rezzing issues) than wireless, simply because it is less prone to interferences from every RF source in the area. Laptops with graphics chips rather than removeable graphics cards are often problematic, which is why gaming quality laptops typically have high-end cards and are at least as expensive as a comparable quality desktop. All in all, then, it's most important to put your money (or future investment) into a good graphics card, assuming that your computer can handle it.

This is very crazy software. Direct responses to your question are easy to see because they are displayed right under your original post. Your question http://community.secondlife.com/t5/Technical/Help-with-Graphics-Cards-for-SL/qaq-p/1356039/comment-id/18985#M18985 has two of these. Sometimes other people may comment on one of the displayed responses. If so, their comments are hidden in the link labelled Permalink in the post that they commented on. In the case of your question, Innula Zenovka commented on LoveAngel Lyre's answer, so you can see it by clicking Permalink there.

SL viewers use QtWebKit for the internal browser. (Note: The Qt does NOT stand for QuickTime.) NOTE: In order to play Flash format videos (eg YouTube videos), you must have the generic Adobe Flash plugin installed. If you use IE as your web browser and already have Flash, you will need to get the generic Flash plugin; see here. linux users need to have gstreamer installed, with the “bad” plugin set. For other troubleshooting suggestions, see http://wiki.phoenixviewer.com/doku.php?id=fs_media

Go to https://support.secondlife.com/history/ to get your previous case number, then open a new case and refer back to the previous one by its case #, saying why you believe that it was not resolved.

If you are a Premium member of SL, contact Live Chat. They will be able to unghost you right away. If you are a Basic member, file a support ticket. For either option, see >> https://support.secondlife.com/contact-support/

Build something incredibly fantastic and tell 1,000 friends. I'm kidding, but not really. You can advertize like crazy, but if your sim doesn't have something pretty amazing, people who do visit will be sure to tell their friends that it's not worth seeing. Focus on quality first.

The list is a public declaration that the developers of the viewer understand and are complying voluntarily with the policy. If it comforts you to think of it this way, it's a declaration of good faith, meant to assure potential users that they know what LL expects and intend to behave well. Other developers who have not made the same voluntary declaration may also be just as trustworthy -- Henry Beauchamp and his CoolVL viewer are a good example -- but the general public is less likely to be aware. There is therefore more than a little marketing wisdom in getting your viewer's name on the TPV list, but it is not required. What IS required is compliance. That bit I quoted above says that LL will cut you off at the knees for violating the policy, whether you are on the list or not. After Emerald, I have to believe personally that they'd do just that.

The list was created in response to the Emerald affair, to mitigate against future incidents, or at least give LL a policy justification for outlawing a TPV found in violation --- whether it has voluntarily compiled with the policy or not. Under the policy now in effect, "If a Third-Party Viewer or your use or distribution of it violates this Policy or any Linden Lab policy, your permission to access Second Life using the Third-Party Viewer shall terminate automatically. ...... We may enforce this Policy in our sole discretion, including but not limited to by removing a Third-Party Viewer from the Viewer Directory and suspending or terminating the Second Life accounts of Developers or users of a Third-Party Viewer. We further reserve the right to take any and all technological measures we deem appropriate to block a Third-Party Viewer from accessing Second Life, and to pursue any and all legal and equitable remedies."

Take a look at Natalia Zelmanov's skin tutorial here >>> http://www.mermaiddiaries.com/2007/09/day-363-creating-goth-avatar-skin-part.html for a start. It's a little dated, but she goes through the basic process in simple, easy-to-follow steps, with illustrations.

Yes, of course it is safe. It is one of the most popular viewers in use in SL, with thousands of satisfied users. The Firestorm developers have voluntarily complied with Linden Lab's Third Party Viewer policy, which you ought to read in full >>> https://secondlife.com/corporate/tpv.php . It lays out specific expectations with regard to data and intellectual privacy, safeguards against viruses and other intrusive programs that may damage or circumvent your computer or LL's system, and any of the other things you might worry about. ETA: Thank you, Charolotte, for the insightful questions you raised in the Permalink to my post here.

If you're getting some sort of infamous blue circle, you may need to do more than change viewers. That's not normal behavior for any viewer, and it's not a common descrription for a failure here either. Your graphics card may be overheating. That can be expensive, especially if it takes the rest of the machine out with it.

Ther ought to b instructions with the product you bought. They are probably something like "Click on the logs to start the fire" or "Say, 'Burn, baby, burn!' in chat on channel 34 to start the fire." In any case, if you didn't receive instructions, and none were posted on the merchant's store site in Marketplace or in world, you'll have to contact the creator to find out. BTW, flames are a particle effect. Be sure that you have not accidentally set your Maximum Particle Count too low (in Preference >> Graphics -- it should default to 4096) and that you have not accidentally toggled particles OFF with CTRL + Shift + Alt + = .

Just one unlinked prim? llSetScale()

OK, I was wrong. :=X I got curious about your problem, so I tried it myself. The solution has two parts. First, the reason you are generating that error is that you need to apply a normalized rotation in the keyframed motion. We had a question here about the same thing a couple of months ago. I filed Void's verbal one line response away in my mind for "later." So this is later, and I did the math. Here's a quick function that normalizes any rotation: rotation NormRot(rotation Q){ float MagQ = llSqrt(Q.x*Q.x + Q.y*Q.y +Q.z*Q.z + Q.s*Q.s); Q.x = Q.x/MagQ; Q.y = Q.y/MagQ; Q.z = Q.z/MagQ; Q.s = Q.s/MagQ; return Q;} So, in the context of your problem, here's a follower that uses llKeyFramedMotion .... rotation NormRot(rotation Q){ float MagQ = llSqrt(Q.x*Q.x + Q.y*Q.y +Q.z*Q.z + Q.s*Q.s); Q.x = Q.x/MagQ; Q.y = Q.y/MagQ; Q.z = Q.z/MagQ; Q.s = Q.s/MagQ; return Q;} integer gON;default{ state_entry() { llSetLinkPrimitiveParamsFast(LINK_THIS, [PRIM_PHYSICS_SHAPE_TYPE, PRIM_PHYSICS_SHAPE_CONVEX]); } touch_start(integer total_number) { gON = !gON; if (gON) { llSay(0,"Switch ON!"); llSensorRepeat("","91b39b5b-13b1-2517-273a-67360b842c02",SCRIPTED,10.0,PI,0.1); //Following my scripted vehicle } else { llSensorRemove(); } } sensor(integer num) { llSetKeyframedMotion([(llDetectedPos(0) - llGetPos()) + <-1.0,0.0,0.2>*llDetectedRot(0), NormRot(llDetectedRot(0)/llGetRot()),0.11],[]); }} I am using the same general formulation that you are for setting up llKeyFramedMotion itself, except that I am calling that normalizing function to get the rotation. ( I am also using llDetectedPos and llDetectedRot instead of going the long route with llGetObjectDetails). The second part of the solution is about getting rid of the jerkiness. As it turns out, that's just a matter of setting the time in llKeyFramedMotion just slightly longer than the time step in your timer (or in my case, in llSensorRepeat). If both of them, in turn are faster than the speed of whatever you are following, the motion is smooth. For the vehicle I was following as a test, I got great results by running llSensorRepeat at 0.1 seconds and llKeyFramedMotion at 0.11.

You're probably not going to be able to get rid of the jerky movement. llSetKeyframedMotion is smooth, but you are running it within a timer event that has to trigger it at each time step, calculate a path, and set it moving again. I suspect that the root of your real problem, though, is that you are running your timer event very fast (0.04 seconds) but the keyframed motion much slower (0.1 seconds). The timer keeps trying to interrupt the keyframed motion before it has finished. You might be able to beat the problem by stopping the keyframed motion at the start of each time step, but I think you'll have better results if the two time scales are better matched. Try slowing down your timer.

Nope. I don't. :smileyhappy:

It is not possible to change the land texture on a single parcel. Land texture is applied to the entire sim. The only way to get your own parcel to have grass instead of sand is to cover it with a specially-designed scultpy or mesh surface -- like a floor that conforms to the land. You can buy systems for creating a sculpty system like that in Marketplace, but I understand that they are pricey and require some skill to use. Depending on the sim's covenant, you may be able to terraform, within limits, once the landlord gives you that permission. On the mainland, terraforming is restricted to changes of +/- 4m from the surface originally set by the Lindens when they created the sim. On private sims, there is no such restriction, but you still might not be allowed to make changes that the landowner considers "unsightly" or otherwise detrimental to other tenants on the sim.

You can change the channel from zero in each of your llSay statements to any other integer you like. That will tell the script to send its chat message on that channel instead. so, for example ... llSay(33, "The owner can say 'help' for instructions."); says its message on channel 33. Thing is, it will only be heard by an object that has a listener on that channel. Avatars can only hear chat on the public chat channel, zero. If you have further scripting questions, the best place to ask is the LSL scrfipting forum. We're always glad to help people who are learning or who have a scripting insight to share.