Rolig Loon

You should be fine. You're just having a bit of trouble with the Internet connection between your client viewer and SL's servers. Changes to your appearance are made on your own computer and then uploaded to SL so that others can see them. If the connection between the two spots is interrupted, you may be able to see the changes but others won't. There's a very nice and exhaustive set of suggestions for how to cure the problem HERE. It is on the Phoenix web site but it really applies to any SL viewer.

Payant a qui? Vous pouvez certainement gagner de l'argent dans SL, mais il est très difficile de gagner suffisamment pour vivre, si c'est ce que vous voulez dire. Quelques personnes ont très bien réussi dans les affaires SL, mais la plupart d'entre nous sont satisfaits de gagner une petite quantité. Il s'agit d'un loisir pour la plupart des gens, pas une carrière.

Are you using THIS SCRIPT that was posted in the old Scripting Forum archives? If not, take a look and see if it works for you. EDIT: Oh, crap. The link in that thread points to the old blogs and is dead. Sorry about that.

Well, you can avoid unnecessary messages easily enough, but you can't avoid at least some lag. It's just a question of what is creating the lag. You can try using a completely different approach from what I suggested before to see. Put a tiny script with a timer in Object 2 that checks the object's position periodically and llRegionSay(-12345, (string) llGetPos()) whenever it moves to a new spot. Then write your main script to listen for the message and if (llGetPos() != my_own_old_stored_position) { llOwnerSay("Object 2 is " + (string)llVecDist(llGetPos() - object_2_stored_position) + "m away"); my_own_stored_position = llGetPos(); } else if ( (vector)gMessage != object_2_stored_position) { llOwnerSay("Object 2 is " + (string)llVecDist(llGetPos() - (vector) gMessage) + "m away"); object_2_stored_position = (vector)gMessage; } The timer in each script will still contribute a little lag to the sim, and you will have increased the sim's script overhead slightly by running two scripts instead of one, but you won't have a sensor firing all the time. Frankly, I don't know which option is friendlier to the sim but I can't imagine that either is much to worry about.

When that happens it's usually a connection issue of some kind. Changes to your avatar's appearance always take place on your client viewer and then are uploaded to SL's servers so that other people can see them. It's a process called "baking." If the connection between your client and SL is wonky, you can have incomplete baking. Depending on when the transmission error happens, changes might be visible only to you or only to other people. Visit THIS SITE to see a rather exhaustive set of options for curing the problem. It's written for Phoenix users but really has nothing to do with Phoenix itself. These are solutions that should work for any viewer.

SLT/PST is the standard for anything that is generated by LL, but individual people or groups may decide to post times in GMT or whatever zone is handy for most of their members and friends. As a rule, any time that is displayed in a regular heading on your screen should be SLT/PST. Any time reported in the body of a message or in a message heading that is created by a person (like the heading in a group message) could be in any time zone.

When you write your script, use llSensorRepeat to drive a sensor that looks for the second object. Then in your sensor event all you need to write is llOwnerSay("Object 2 is " + (string) llVecDist(llGetPos() - llDetectedPos(0)) + "m away."); If you only want the message when the distance between the objects changes, then store the result each time the sensor fires and compare it with the new result the next time it fires. Incidentally, this will only work if the objects are within 96m of each other, but there are other ways of getting the position of a more distant object.

Maybe I'm not seeing some obvious complexity, but couldn't you just script an object with llWater to detect whether it is above or below the sim's water table? Trigger a fast timer event when you sit on the object, then if (llWater(ZERO_VECTOR) < 0.0) {llStartAnumation("I'm_swimming");} else {llStartAnimation("I'm flying");} Use a control event to handle movement of the object. If you're trying to swim in a pool or if you want to swim under water, you'll need to feed it an offset vector, but that shouldn't be all that hard. Or am I missing something?

If you get a message saying that it can't resolve the host name, it's probably not your system at fault. That's a connection issue. It may be a problem with your own router or modem. Reboot them by unplugging both of them and going out for a cup of coffee. Then come back, plug them in, and let them re-establish an IP address. If that's not th problem, then it's either your ISP with server issues or it's LL's servers (or something in between). Usually all you can do is wait and try again later.

The Second Life installer executes automatically as soon as you download it, the same way most programs do these days. It's just a matter of clicking a couple of dialog buttons. You do need to be sure that your system meets LL's minimum standards. If it does not, you may be able to install the viewer but you will almost certainly have lower performance than you might hope for. Now, if you have a system that meets the standards, and you have downloaded the viewer and clicked the dialogs and it doesn't install, what IS it doing? ============== Your computer must meet these REQUIREMENTS, or you may not be able to successfully participate in Second Life. Mac OS X Minimum Requirements RecommendedInternet Connection*:Cable or DSLCable or DSLOperating System:Mac OS X 10.5 or betterMac OS X 10.5.4 or betterComputer Processor:1.5 GHz Intel based Mac2 GHz Intel Core 2 Duo or aboveComputer Memory:512 MB or more1 GB or moreScreen Resolution:1024x768 pixels1024x768 pixels or higherGraphics Card**:ATI Radeon 9200 and above OR NVIDIA GeForce 2, GeForce 4 ATI: 4850, 4870 OR NVIDIA: 9800

You'll need to be sure that it's not just the viewer that's on your removeable drive. SL stores a mess of XML files that contain information about your avatar, your chat history, your preference settings, and many other things, as well as your cache. If it can't find those files, it will be dead in the water.

It all depends on what you want your skirt to look like, so there's no formula to follow. Watch THIS VIDEO by the amazing Torley Linden to see how to make a flexi prim if you have never done it. Most of the time, you'll want to start with a cylinder. I have used cubes too, for pleated skirts. I tend to start without being very careful about the length or proportions of the prim, because I always change my mind as I work anyway. A flexi prim is always attached at its -Z (that is, DOWN) end and it's flexible at the other end, so whatever shape you choose will be upside down from the way you want to use it in a skirt. Give the prim a negative taper in both X and Y, so that it is pointy end down. How much taper? You choose. You'll want to bury the pointy end inside the avatar body when you make the skirt, so the amount of taper is partly a matter of how deep you need to bury it. It's also a matter of how many prim panels you're using and how flared your skirt will be. You may want to cut the prim, or not. Again, it all depends on what sort of skirt you're making. Uncut prims make nice, full petticoats, especially if you overlap them a lot. Prims that are cut about halfway around are great for more wispy skirts, or for miniskirts that need a big flare. The real trick is choosing the flexi parameters, and that's really a matter of practice and experimentation. Personally, I avoid using a wind setting higher than 0.5, and I only use that on light, gauze-like fabrics for things like overskirts. Otherwise, a skirt tends to have a mind of its own. I also like to use a gravity setting of about 4.0, again to keep the skirt from flying away too much as I move. The rest is really a matter of deciding how you want the skirt to bounce or flow. The same flexi settings will look very different on a short skirt than a long one, or on a skirt with 20 panels instead of 12. I recommend that you make a pile of practice skirts and just start playing with flexi to see what happens. Even after 4 years of doing this, I still discover neat combinations that do fascinating things with a novel skirt design.

Yay, team!

You'll need to buy or rent more land from whomever owns it. It's either that or get rid of some things that you have rezzed already to bring your prim total within the limit for your current parcel.

You'll have to give us a little more to go on. The monthly fees for what? Are you renting land or a landowner, maybe? Are you in a group that owns land? Are you in a group that has its members share financial liabilities? Are you advertising a product or service with a classified ad or a special placement in Marketplace?

The easiest way to learn a new skill in scripting is to start with a sample script that already works. Modify it a little bit at a time to see how it behaves and to understand its logic. Gradually morph it into a script that does what you want. If you get stuck, come back here and post your script (or at least the part that doesn't work right). We won't usually write a script for you, but people in this forum will be glad to help you learn how to do it.

If you want to unpack a box, you will need to be in an area where you are allowed to rez objects. Look at the center of the very top of your screen for a tiny icon that looks like a cube. It will be there if you are in a place where rezzing is permitted. Otherwise, the cube will have a red circle/slash attached, telling you that rezzing is forbidden. Use your Search function (upper right corner of the screen if you are using the V2 viewer) to look for a "sandbox" where rezzing is allowed.

Take a look at THIS SCRIPT, which reads a list of names from a notecard and puts them into a list. Also, take a look at the LSL wiki to see how llGetNotecardLine works. You'll find a couple of example scripts there that show you how to read more than one notecard.

The submit a ticket thing is at https://support.secondlife.com/contact-support/ , which you can get to from secondlife.com by clicking on Help >> Contact Support .

Did this message start with a greeting like this? Dear Sir/Madam: I am the widow of the late exalted Joseph Mbutulu, Minister of Foreign Exchange for Nigeria, who died in November 2010, leaving an estate valued at $300,000,000. My husband's will names you as a beneficiary .........

Drews Aulder wrote: And the weird thing is... The price is set to 10 but i got nine. Where did the 1 go? Taxes? ehehe Seller Sales Commissions We charge SL Marketplace merchants a Commission for each sale that the seller makes (“Commission”). Commission rates are five (5) percent of the listed price, rounded to the nearest Linden Dollar (L$). That's the way Marketplace works......... :smileyhappy:

If there are other objects in MObject's contents, then you'll want a way to ignore them as you rez each no-copy "kelp". One way to do that might be to write no_sensor() { integer Num = llGetInventoryNumber(INVENTORY_OBJECT); integer count = 0; while(Num-count) { if (llToLower(llGetSubString(llGetInventoryName(INVENTORY_OBJECT,count),0,3)) == "kelp") { llRezObject(llGetInventoryName(INVENTORY_OBJECT, count), llGetPos() + <0, 0,.5>, ZERO_VECTOR, ZERO_ROTATION, 42); return; } ++count; } }

I assume that you mean that you're trying to match colors. You'll never get it perfect, because colors change with the amount and angle of ambient light in SL. Also, despite many upgrades to SL software over the years, colors on the avatar body are never perfectly matched to colors on prim objects. Try this, though.... Use your Advanced menu (CTRL-Alt-D) and select UI >> Show Color Under Cursor. That will create (in the lower RH corner of the screen) a dynamic display of RGB color values for whatever your cursor is sitting on. Playing with that for even a few frustrating moments will show you why it is nearly impossible to get a perfect match, but it will get you as close as you will ever get. BTW, screaming won't give you a better match, but it makes you feel a lot better. I do it a lot.

Find the SL installer program on your hard drive, right click on it, and go to the Compatability tab. Select 32-bit compatability. That ought to work. I think. :smileyhappy:

You ought to be able to get to the Destination Guide from your browser at http://secondlife.com/destinations?lang=en-US.