Rolig Loon

Are you logged out every two minutes, or do you crash? If you are being logged out, you will always get some kind of error message that can help you figure out why the servers are dropping you. If you crash, though, you won't get an error message. You'll just suddenly be out of SL with no warning, although your screen in SL may look wonky just before you crash. Angel has given you a couple of good ideas about why you might crash -- basically, your Internet connection is weak and was interrupted. There's one other serious possibility -- serious especially if you really are crashing every time within two minutes or less of logging in. You may be overheating. Your computer can be damaged critically if it gets too hot, so its built-in defense is to shut down applications that are asking it to work too hard. If you force it to keep working, you can burn out your graphics card or, worse, components on your mother board. If you are working on a desktop, open the case and use a can of compressed air to blow out all of the dust bunnies and cat hair now. You should do this every month or so normally. Also, be sure that you have adequate fans. Fans are cheap insurance against overheating, and you can download free software from the Internet that will make the fans speed up if things get too hot. If you are using a laptop, you may have to take the computer to the shop to have them open it up and clean it. Then, get yourself a ventilating lap board that will lift the computer off of your work surface -- never your lap! -- to get plenty of airflow under it. Again, it's a cheap investment compared with the cost of replacing the entire computer. Finally, if you really are being logged out -- not crashing -- tell us what error message you are getting so we can offer better help. You can add more information to your question by clicking n the Options link in its upper right corner and selecting EDIT. Please do NOT start a new thread.

Hehe ... You're right. I meant SSE2. Still, that's the problem. The OP has an old computer.

There are thousands upon thousands of freebies in world. If you really want a discussion on this, you might try posting in Favorite Destinations or General Discussion.

Tristus Patton wrote: I guess where Im getting stumped is how to setup the script to use the list, getting the information off the notecard is simple. Would I want to have one list for all the params? I dont think it would be as simple as putting all of the information from the notecard into one list called, I dont know "mainlist", then doing something like... llSetLinkPrimitiveParamsFast(linknumber, mainlist); [ ...] That's exactly what you do. One list with all of the stored parameters in it. If you need to modify a parameter before you store it, you can always do that anywhere in the script that it seems appropriate. So, your list might say list params = [PRIM_LOCAL_POS,<5.2,0.67,3.0>,PRIM_COLOR,4,<1.0,1.0,0.0>,1.0,PRIM_TEXT,"This is my prim",<1,1,1>,1.0] If you need to change the stored color, for example, one way might be to write list params = llListReplaceList(params,[<0.0,1.0,1.0>],4,4); to replace the fourth element in the params list with the new one. You could think of other ways to do it too, including not even assembling the list until you had all the values exactly the way you wanted them (That's the easiest way. Then you don;t have to mess with a list you have already made.). When you're all done and ready to apply the list, just write llSetLinkPrimitiveParamsFast(linkno,params); where linkno is the number of the link you want to apply the params to.

That specific error code means that your computer does not support SSE, which is required for almost all SL viewers except for the old 1.23 viewer and one version of Phoenix. SSE has been standard in virtually all computers manufactured since about 2004. If you want to log in to SL, I'm afraid you'll need a new computer.

Scripts don't just control minor tasks. Essentially anything other than an avatar that moves, communicates, gives items from one person (or object) to another, accepts L$, or changes appearance is controlled by a script.

As I explained in response to your previous question, you are not talking about a parcel. You are talking about a sim. A parcel is a plot of land that has property lines around int, visible only if you highlight them with CTRL+Shift+Alt + P. It may be as small as 4m x 4m A sim is 256m x 256m area, supported by a single server. There's a lot of difference. It sounds to me as if you have a firewall problem. If your firewall is blocking outbound TCP port 12043, then teleporting, viewing the World Map, crossing regions, and related activities won't work. You can reconfigure your firewall to fix the problem. See http://wiki.secondlife.com/wiki/Configure_your_software_firewall . You might also take a look at your antivirus program, which might have a similar effect. See http://wiki.phoenixviewer.com/doku.php?id=as_anti-virus_white_listing_steps

I don't see this as unusual or unexpected behavior. A KeyframedMotion object is physical, so its collision with an avatar is like any physical object's collision. I made a pair of double doors with llKeyframedMotion last week. If I stand in the way of the doors as they open, they swat me out of the way. If I make tiny doors, though, they don't have enough oomph to move me, so they stall. That's the way with any physical object I've ever worked with.

How about right where Innula has this, only put your selection of messages where she has the llRegionSayTo .... else if (~llListFindList(thank,[message])){//it's one of the messages from the "thank" list //so do whatever you want .. no need to turn the listener off, //because you did that as soon as you discovered it was a message from a sub menu llRegionSayTo(av,0,"Sending this emote to local: "+message);

Well, the llSensorRepeat functions won't work as you wrote them, so you'll have to figure out what you mistyped from the snippet I posted. You did make gAvatars a GLOBAL variable, right?

Others have had a similar problem this week. I suspect that it has something to do with maintenance that LL was doing on the Billing site. In any case, see my advice in the post I made here on Dec 10th. You can use an alternative exchange safely if it is one of those on the page that I gave a link to. There are others too, but at least we know that these ones are OK. Also, please do call the billing office at the toll-free number I listed above.

Unless, as I said, you buy the private estate yourself. :smileywink: Although it does happen that a landlord can "yank [rented land] from you at any time," that is not very common. It would be impossible to put numbers to it, but I think it's fair to say that there are way more satisfied renters on private sims than unsatisfied ones. Like many things in life, renting is a measured risk (in RL too), but it's one that a very large number of people take successfully all the time. You are right, though, that technically you can never "buy" land anywhere, regardless of your membership status. We all ultimately rent from Linden Lab. The question is simply to whom you mail the rent check.

Perhaps as in rotation newRot = llAxisAngle2Rot(<1.0,0.0,0.0>, degrees *DEG_TO_RAD) ?

That's a decent start. Here are a few things to think about ... 1. You won't be able to set the sensor for avatars and objects at the same time, so you don't actually need both AVATARS and OBJECTS. Just choose one as the default and switch to the other when you want to. integer gAvatars; // Here's your global integer variable that you use as the toggle Then in state magnetized ... state_entry(){ if (gAvatars) // That is, if you have selected to scan for avatars.... { llSensorRepeat("","",AGENT, gRadius, PI, 0.1); } else //That is, you have set gAvatars to FALSE because you are scanning for objects instead ... { llSensorRepeat("","",ACTIVE, gRadius,PI,0.1); }} 2. The touch_start events are a perfectly good way to switch states and thus turn the device on and off. The only thing you are missing is the actual OFF command, which is llSensorRemove(). That belongs in state_entry in your default state, so that switching back there automatically kills the sensor. Those are the two big things. Beyond that, there are stylistic things to consider... 3. You don't need the listener variable, because you aren't listening for anything. 4. Note that the sensor doesn't need to scan for TWO_PI radians. PI scans the entire sphere. 5. It's usually good practice to avoid naming variables in ALL CAPS, because that's the way LL names system constants. You might have the bad luck to choose a name that is already taken, and you'd be scratching your head about the error message for a while. 6. It's good to get in the habit of always putting curly brackets around the scope of an if test. In this script, you get away with omitting them because the scope in each case is a single command. Sooner or later, though, you will modify a script like this and add another command or two, forgetting that the brackets are missing. When that happens, only the first command will be affected by the if. I think it's a lot easier to just remember to always put the brackets there, whether they are strictly required or not.

Yes, there certainly is. You can buy a private estate as a Basic member. With a private estate, you can do much more ambitious terraforming that you can on the mainland, you can design your convenant to be as open or as restrictive as you wish, and you can choose your own sim name, among other things. You also pay more for the monthly fee, of course. :smileywink:

I agree. I wouldn't use this script on any avatars without their prior consent either. Turning it on and off is a simple matter, though. As you, Innula, and I have said, the OP could build a toggle into any event she wishes (touch_start, collision_start, timer, sensor, changed, listen, run_time_permission..... ), depending on how she wants to trigger it.

The first thing to do is remove those names from your message as soon as possible. Your message could be interpreted as "personal negative commentary", which is forbidden by the Community Standards on this site. Then submit Abuse Reports. You should include factual information, including avatar names, times, and specific ways in which you believe that they have violated the SL Terms of Service. Attach photographs if you can. Every time there is a problem, submit another Abuse Report, and mention each of the ones that you have already submitted.

That's really wierd, isn't it? There's one section of one wall in my house that is always the last one to rez too -- sometimes as much as 15 seconds after the rest of the house has appeared. I don't know why that one behaves that way, in particular. It just does. Cinn's right that your viewer will always prefer to render nearby objects first, but there's a degree of randomness too. Some things just take forever. In order to keep your GPU from hanging up and failing to rez some things, the Firestorm viewer prioritizes rendering deliberately when you log in. It forces your graphics card to spread the load out over 6 - 10 seconds instead of trying to do it all at once. You can slow down (or speed up) that process with a choice in Preferences >> Graphics >> Rendering >> Time to delay while pre-caching before showing world . You can also cut down the number of HTTP textures that Firestorm tries to fetch at once to see if that helps. On the same page in Preferences that I just point to, see Max number of concurrent HTTP GET requests .

Ariel and Angel have done a great job of answering most of your questions, so I won't repeat what they have said. You'll get many opinions about whether to buy or rent, and where to do it, so you'll have to make up your own mind. My personal choice has been to rent a parcel on a private estate. Ariel is right in saying that a private landlord might decide to pull up stakes at any point, leaving you stranded. We hear from people with that experience, and I wince. Frankly, I think they are a small minority, however. I have had shops on four different sims, two of which no longer exist. Both of those landlords let me know well in advance and were kind enough to refund a portion of my last month's rent. The landlords on each of the sims were helpful and responsive, and so is the landlady for the sim where I have rented my home for the past couple of years (she's a very good friend, too). As I talk with people who have been in SL as long as I have -- about 5 years -- I hear much the same thing from almost all of them. When you rent in SL, follow some of the common sense rules that you know well from RL: (1) Research the neighborhood. Look at how the other parcels are kept, visit at different times of the day and see what the traffic is like, read the covenant carefully to see what's allowed, and talk with current residents if you can. (2) Have a clear idea about how you want to use the land. Do you value privacy or do you want do entertain a lot? Do you plan to spend a lot of time indoors or will you prefer gardens? Do you want space to use as a private sandbox? Do you want to be able to terraform the land? Do you want "beachfront" property? Do you want to be able to open a shop? (3) Get referrals from people that you trust. Talk to friends about places where they rent or places that they would avoid. (4) Know your budget before you shop -- not just what you want to spend but where that money is going to come from. I decided a long time ago never to rent more land than I could expect to pay for with my average monthly earnings in world. That was a personal decision. You may decide that you will never buy more than L$6,000 each month with RL dollars, so that's your cap. (BTW, I know of at least one private estate where you can rent a decent-sized parcel for L$600/week, which is about your $10 USD limit.) (4) Remember that unlike RL, you can leave a rented parcel at any time if you find a better place or decide that you made crummy choice. You might forfeit a little rent, but you can pack up your entire house and all your stuff and be gone in 10 minutes if you have to. No land decision is irreversible.

Yes, I agree with you, Suzan. This ought to be a standard feature in the LL viewer too. It's an excellent idea. My only point was that SL residents do have this option already, if they choose to use it. ALL viewers are official, since Linden Lab was wise enough to make the viewer code open source. BTW... I voted

Or just use Firestorm, where this is a standard feature. :smileywink:

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.It may also have a blurry appearance, or be wearing a strange collection of textures. 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.

touch_start (and touch_end and touch) are events, not functions. They are simply blocks of code that respond to a left mouse click. What you do in an event determines the response. If you want a simple toggle switch .. integer gON;default{ touch_start(integer num) { if (!gON) { // Do something (or don't) } else { // Don't do something (or do it) } gON = !gON; }}

That's usually what happens. That's why you have to contact the merchant or file a support ticket. The Magic Box system is odd. Marketplace receives your order and sends a message to the merchant's Magic Box, telling it to deliver the item you ordered. If it receives a reply from the Magic Box, it assumes that the item WAS delivered, so it takes your money and marks the delivery as complete. If the Magic Box screws up and DOESN'T deliver, though, Marketplace has no idea. The items is marked as Delivered, but you are out the L$ and you don't have what you ordered. The merchant gets a bad reputation for non-delivery too, when it was really the fault of an unreliable Magic Box.

If you cancelled an account 3 years ago, the chances that it is still there are very dim indeed. If the account can be resurrected, I would be very surprised to see that its inventory was still there. You can pay the $9.95 to find out, but you may be better off just opening a new account.