Rolig Loon

Some people who have ATI graphics cards are having this problem with the most recent V3 upgrade. If you had done a very simple search of this forum with the keyword PINK, you would have seen dozens and dozens of posts on exactly the same question during the past two months. :smileywink: 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

As Val says, that error message means that you are using a very old computer that does not have a central processor that supports SSE2, which has been a standard in virtually all computers manufactured since about 2004. If your computer does not have that capability, you will not be able to run any of the current viewers for Second Life. The only way to get around the problem is to buy a new computer. :smileysad:

You can do some asymmetrical designs as long as you don't use sleeves. The problem is that your av really only has one arm. The other arm is a mirror image of it, so anything you do to one arm shows up on both. Of course, you can always make prim or sculpty attachments for one shoulder and upper arm, or you can make a custom mesh avatar that does have two arms, but that's more work.

Almost everything you want to know is right here >>> http://community.secondlife.com/t5/English-Knowledge-Base/Selling-in-the-Marketplace/ta-p/700193 or in the links in that article.

The limit is really the size limit to a linkset. To place an object off sim, its root prim has to be ON the sim. It doesn't have to be very big -- a 0.5m cube is enough -- but it needs to be somewhere on the sim, even if all the rest of the linkset is off sim. So, how far? Well, as far as you can make the distance between prims and still have them linked. I think it's still true that he linkability rule can be written as: LINKABLE = D < 54 AND N ≤ 256 where D = diameter of the smallest bounding sphere of the collection of prim centers and N = number of prims in the collection

When you are standing in your rented parcel, check the World >> About Land >> Objects menu to see how many prims you are allowed ro rez there. Then check to see how many of those prims you are using by just rezzing the skybox. You can click on the skybox itself and use the Edit tool to tell you its prim count, or you can take another look at the About Land display to see how many prims you have left. The point of this is that you cannot rez any more prims than your parcel allows. If you try -- say, by rezzing a primmy couch -- the item will either not rez at all (the normal behavior) or be bounced back to your inventory. If you are too close to the limit before you even rez a few things, your skybox is too much for the land. You'll have to rent a larger parcel somewhere.

There's not much you can do about that. "Collision" in this context just means that something or someone is making contact wih the deck. That's pretty inevitable if you are walking or dancing on it. A large prim like that will often be listed in the Estate/Region tools list of Top Colliders, basically because it's large enough that things naturally keep bumping into it all the time. The only time to worry about collisions is when a scripter has added a script to the floor to make it light up or trigger a message whenever someone steps on it. If the script isn't written carefully, it can keep firing continuously and drive everyone nuts. The only way to cure that sort of behavior is to go in and mess with the script.

Your laptop might meet the minimum requirements listed here >>> https://secondlife.com/my/support/system-requirements/index.php?lang=en-US but still be inadequate for a satisfactory experience in Second Life. If you are having severe lag problems, you may have a weak Internet connection (high packet loss or a very large ping time -- very often a problem for SL residents who are outside the U.S.) or your graphics card may not be able to handle the heavy rendering load that SL presents. You should try reducing your draw distance (to 64m or less), reducing your Quality slider (in Preferences >> Graphics) to Low, and cnsidering other solutions here>>> http://wiki.phoenixviewer.com/fs_very_laggy

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

If you have mod permssion on the furniture, you can just open it with your Build/Edit tool (Right click on it and select "Edit") and then click the Contents tab. You'll see everything that is listed in the contents of the furniture, which should include the animations and the script that creates the menu. You can select and delete them from there (or drag/drop backup copes to your own inventory first and THEN delete them). If you do not want to delete the menu, that's fine. The menu buttons for the missing poses may still remain in the menu, however, and may generate an error message or cause the script to freeze if you click those dead buttons. If you have permission to modify the script (highly unlikely) you can remove those choices. Otherwise, just avoid them. If the poses are not in the furniture itself but in linked poseballs, you can select a poseball (again, right click to select the furniture, then check the "Edit Selected Link" box and then click to select the poseball itself), and then click UNlink or type CTRL + Shift + L. That will unlink the poseball from the furniture, thus making it possible to delete it alone. If you do not permission to modify the furniture, then neither of these will work. Also, please remember tht if you have not had much experience with this sort of thing -- or even if you have -- it's smart to make a backup copy before you modify anything (assuming that you have copy perms).

It's impossible to answer a question like that without any information at all except that you can't log in. You have to give us something to work with. What kind of computer? What graphics card? What sort of Internet connection (Please, not wireless)? Exactly what error messages are you getting? How far does it get through the log-in process? What have you tried already? What have you changed recently in your computer? To add important information, click on the Options link in the upper right corner of your question and select EDIT. Please do NOT start a new thread. Meanwhile, take a look at http://blog.nalates.net/2011/09/11/cant-login-second-life/

When you are seeing persistent grey textures, it's because your viewer is either not getting the data or, more likely, is being overwhelmed by having to process too much texture data at once. The problem is likely to be greater for some people than others, depending on the quality of their Internet connection (bandwidth, packet loss....) and the efficiency of their graphics cards. Much of that is under the control of the individual user, who can reduce draw distance, manipulate maximum bandiwdth, or use strategies like the progressive draw distance stepping that is built into Phoenix and Firestorm. There are things that builders can do to help too. Reducing the size and total number of different textures are the big ones. It is rarely necessary to use textures larger than 512 x 512 pixels. It takes four times as much memory to handle a 1024 x 1024 pixel image, and it doesn't take many of those to swamp a uiser's graphics card. Simple images, especially on small objects or ones that most people will never see close-up or for very long, are much better as 256 x 256 or smaller textures. Also, since multiple copies of the same texture are rendered at the same time, you can save users a lot of trouble by cutting down on one-time images. You can also help users by placing visual barriers (walls, trees, ...) that reduce the number of textures that they have to process at the same time. It won't make any difference whether you create textures as TGA, PNG, JPG, or BMP files on your computer, by the way, since all images are converted to JPEG2000 when they are uploaded to SL's servers.

Of course. Premium members are not an elite club. They are just people who have decided to pay for Mainland. It's OK to be friends, even visit. The only possible exception that I'm aware of is with Premium sandboxes. Not being a Premium member myself, I have never visited one, so I don't know exactly what would happen if I tried.

The SLURL (wherever it is) is just another line of text. Highlight it the way you would highlight any other text, and copy it with CTRL + C. Then start your IM to another person and just type CTRL + V to paste the SLURL wherever your cursor is at the moment. Just like any word processor you ever used.

Well..... you could separate the touch_start event and the control event in different states. Use the touch_start event to determine where the person is and then check in the control event to be sure that the person is no more than, say, 5m from that spot when he fires the crossbow. Let the script return to state default only when the crossbow has been fired.

An alt is a new account. You open it the same way you opened your current one. It's separate from your current account .... different name, different inventory, .... You can use the same e-mail and payment information. I use my alt as a "third hand" when I am testing scripts or checking the permissions on something I am about to sell. For many people, an alt is a way to get some privacy or to experiment with a different personality or develop a new set of friends. You may have up to 5 alts, according to LL.

Awwww.... I haven't had any trouble buying or selling anything on Marketplace in ages. All my Magic Box sales used to go through, and my Direct Delivery ones do now too. I think people just have to be careful not to overload the system. I really suspect that most of the ones who have problems are just stuffing the shopping cart full.

You can clearly make up your own mind, but I would walk away from someone like that myself. You may want to consider making an alt and not telling anyone who you are. Anyway.... as someone explained in response to you in a different thread, he is probably tracking you by getting a signal from some scripted object that you are wearing --- probably something he gave you as a gift at some point (jewelry?....) . Open your Inventory's WORN tab and start taking off unfamiliar objects. Certainly take off anything that he may have given you.

The web profile? Try using a different web browser. For some reason, Firefox works much better than IE on SL's web site.

It can sometimes take anywhere from a few minutes to a day or more for your items to be delivered, so don't panic yet. 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. Better yet, avoid the Shopping Cart altogether and just use the Buy Now button. That's what I do. (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.

Ah... I misunderstood what you are trying to do. Yes, that will only work on an object. You cannot move an avatar with a script (well, except with llPushObject which is a very rough, uncontrolled sort of movement). The only way to move an avatar to another spot is to have the avatar seated on somehing that you move. I assumed that's what you were doing. That's also what Peter was referring to, somewhat obliquely. :smileytongue: See http://community.secondlife.com/t5/LSL-Library/Walking-through-walls/td-p/1390043

No. You can certainly send an object to any spot on the same sim. We have a lovely new LSL function for doing that. However, " llSetRegionPos Returns FALSE and does not move the object if........ the object can not move to position due to parcel/region restrictions (object entry rules, prim limits, bans, etc). " So, if you have set the proper restrictions on your parcel, there's no way to send a "bomb" there remotely.

Yes, they can. Even if you have No Object Entry checked for your parcel, a fast-moving object can travel fairly far into the parcel before it dies or is returned. Bullets often do that. If you can actually capature and identify such an object, you can file an AR on its owner. It's possible, of course, that your neighbor has no idea that his projectiles are ending up on your land. So, if that's what you think might be happening, you could ask innocently and see what he says. To the general question ..... A beacon is a handy tool for locating a sound source, but not if the source doesn't stick around for long. Locating a short-lived source is a really hard challenge. If it were my own parcel, I might write a script to detect newly-rezzed objects by name and location, but that's a lot of trouble to go to.

I had the same problem last weekend when I was trying to locate items that a tenant had left behind on a neighboring parcel. It's frustrating, and I cannot explain why they can't be highlighted or selected. They CAN be returned, however. If they are scripted objects, for example, you can select them from the Top Scripts list and return them that way. I wish I had a better answer. If I can think of one, I will let you know. You may also want to ask Ceera Murikaml, who is one of the most talented builders I know in SL. She may know a way that I do not. If so, please let ME know.

You need to rotate the target avatar to face you before you can move him/her. Because the av is seated on your scripted object, that means making its +X axis face you. If my_position is the position vector of the object and other_position is the location ot the avatar you want to turn toward, you can write......... llSetRot(llRotBetween(<1.0,0.0,0.0>, llVecNorm(my_position - other_position));