Rolig Loon

I know how you feel. People move on and communities that were once vibrant drift apart. At the same time, thoiugh, there are always new people moving in and, like you, they are looking for communities that seem welcoming. Find friends the same way you do in RL. Hang out in places that look interesting, and are probably interesting to other people like you. Take a look in your in world Search, under the Events tab, for activites that sound interesting. There are always musical events, classes, exhibits, and celebrations going on somewhere in SL. Since you have been in SL for a while, you have an advantage over many newcomers who are struggling to learn how SL works. You may be able to turn that asset into an opener in conversations, especially as you start to meet people in your explorations.

Check to be sure that you don't have a firewall set to block access. Therre are some guidelines HERE on how to configure common software firewalls, and you may also want to check your router's hardware settings as well.

Getting Blender set up properly so you can make sculpties for SL is complicated. You have to have just the right version of Python to match the version of Blender you've installed, and you need a few extras to make it easy to create UV maps for sculpties. Like everyone else who has tried, I wasted a lot of time swearing and tearing at my hair. However ...... The easy way out is to download JASS-2 (which is free) or Jass-2 PRO (which is worth the L$). JASS-2 includes Blender, Python, and the Primstar extras, and it installs itself beautifully. Also, Gaia Cleary's tutorials on the Jass-2 website are incredibly well done. It's the best way to learn how to make sculpties.

I'm not keen on limiting the number of posts per day. I have seen quite a few people in the Content forums who ask complicated questions that require a lot of back and forth before everyone understands the problem and can home in on a resonable set of solutions. Limiting the number of posts in that environment could get frustrating for people who have those tricky questions. When you add the fact that some of us may reply to a dozen or more content questions or threads in SL Answers every day, limiting the number of posts we're allowed could really cut into the effectiveness of the forums.

I considered that, but the OP can't measure the height of his follower on the appearance sliders. Unless he means "character" == "avatar" ....???? If so, 21 is an arbitrary slider value, not his av's height. You can't use it in this context. More to the point, the spinning that he was describing sounded to me like what happens when a physical object gets knocked off axis. That's why I suggested letting it go non-physical every once in a while, set itself upright, and go back to physical status again. I'm not sure how changing it's vertical position will change that, except to keep it from bumping into the ground as often, perhaps.

This isn;t exactly a function library, but it acts like one sort of. Script A doesn't ever know that happens in script B. It simply passes a value to the Description field and gets one back when it senses that the field has changed again. You could swap out different versions of script B without ever having to mess with script A. This could be handy if, for example, you wanted to make script A no mod but let your end user create custom versions of script B.

SelItami wrote: My character is only 21 height, so maybe I have it set too high initially. 21m tall? Or 0.21m? I'm not sure that I understand now. My own av is 2.1m tall. If I get its position with llGetPos, that will return a Z component that is 1.05m above the ground (well, close to it). If I want to rez an object one meter behind me that is 1.0m tall and has its feet on the ground, I should rez it at llGetPos() + <-1.0,0.0,-0.55>*llGetRot() . If I rezzed your 0.21m tall follower behind me, I'd do it at llGetPos() + <-1.0,0.0,-0.945>*llGetRot() .

It doesn't bother me much that you can't see who a reply might be directed at, since I never found much use for the threaded view of the old forums anyway. I can see that it could be confusing in some marathon threads, however. Limiting the number of new threads (not posts) that a person might create in a day seems like a decent idea, though. Aside from cutting down on the Easy L$ spammers, it might help even the most creative and prolific forum dwellers to focus a bit more. After all, how much attention can you devote to more than three or four good, completely new ideas in a day?

Yup. My silly mistake. Fixed. :smileysurprised:

Of course, one might also make the obvious observation that this is a scripting forum, not a software development forum. Side discussions about other things are interesting, perhaps, but it doesn't make much sense to waste energy yelling about them with someone who isn't paricularly interested in scripting.

It isn't much easier to get a job that pays well in SL than it is to get one in RL. You need to have a skill of some kind, like scripting, or building, or being a DJ. If you don't have some background in a related area in RL, it takes a while to learn a skill in SL well enough to make it pay. After all, there are lot of other people who already have a head start on you. Don't get discouraged, though. Just take time to learn. Meanwhile, there are so many good quality free things in SL that you really don't need much L$ to enjoy yourself.

I rarely change my shape any more. After four years, I think I finally have it right. I do swap skins sometimes, maybe three or four times a month, depending on what I'm doing. Outfits are different, though, I can sometimes change clothes and hair four or five times a day. I like to mix items, just the way I do in RL, so I almost never save a whole outfit -- just change one blouse or skirt or pair of shoes for another.

It compiles in the LSLEditor, so it will run in world on the main grid. There may be runtime errors at that point, of course, but you aren't that far yet.

Make a backup copy of your object first. Then stand on a pose stand, so that you are immobilized, and then select the object in Edit. Click the "Edit Linked Parts" box and select just one prim to adjust (usually the largest one or one that is an obvious "anchor" like a waistband or the main prim in a belt). Unclick the "Stretch both sides" box and then select the stretch option and make your adjustments very gently, moving your camera around so that you can check your work from all angles. Rinse and repeat until done. It's good practice and really the only way to guarantee that you have the best fit to your own shape. No resizer script knows what your body looks like, after all.

Those look like compilation error emssages, but it compiles for me with no problems at all. As others have said, though, those are not standard error messages, so you are evidently doing something out of the ordinary.

I was trying to do this same thing last month. I managed to make a pretty nice seat that looks like it has a hydraulic lift under it, using llVolumeDetect and physics to get it to move smoothly up and down. My goal, like yours, was actually to force the seat underground, but I couldn't find a way to do it with the av on the seat. I suspect that it can't be done. Av's just don't like to be under sod.

This script will let you make a shadow that follows the movement of the sun and adjusts its length to the sun's elevation. It could be handy if you want to create a realistic shadow around something like a fence post. The length of the shadow is limited by the maximum dimension allowed for prims (no megaprims, since you cannot change their dimensions), so it is only realistic for reasonably short objects (no flagpoles). Still, there are plenty of short objects that deserve a dynamic shadow. To use, rez a box prim, flatten it along its Z axis and make its Y dimension approximately the width of the target object that it will be a shadow for. Place the name of your target object in the gName variable in this script and drop the script into your prim. Touch the prim to reset the script. Your prim will position itself at the base of the target object and adjust its rotation and length according to the position of the sun. Thereafter, it will track the sun, disappearing at dusk and reappearing at dawn. // Shadow -- Rolig Loon -- March 2011 // This script controls a shadow that tracks the sun's position (azimuth) and adjusts its length to the sun's elevation // Rez a prim that is flattened on Z and is as wide (Y axis) as the target object you want to shadow. // Set the gNAME parameter (below) to the name of the target object being shadowed. // Set your shadow prim within 10m of the target object and touch it to reset this script. // The shadow prim will position itself at the base of the target object and will adjust its own length (X) and texture. string gNAME = "Pole"; // The name of your target (shadowed) object goes here. float gHeight; // The target object's height (will be measured by this script). GoSun() { vector Sun = llGetSunDirection(); if (Sun.z > 0.0) //It's daytime....... { llSetAlpha(0.5,ALL_SIDES); // Track the sun's azimuth llSetLocalRot(llGetLocalRot() * llRotBetween( <-1.0,0.0,0.0> *llGetLocalRot(), <Sun.x,Sun.y,0.0> )); //Calculate the length of the shadow float SunAngle = llRot2Angle(llRotBetween(<-1.0,0.0,0.0>*llGetLocalRot(), <Sun.x,0.0,Sun.z> )); vector MySize = llGetScale(); //And set its length llSetScale(<2*gHeight/llSin(SunAngle),MySize.y,MySize.z>); } else //It's night ..... { llSetAlpha(0.0,ALL_SIDES); } } default { state_entry() { llSetTexture("5c50e129-0b07-3834-0748-f1df74234a65",ALL_SIDES); //All transparent llSetPrimitiveParams([PRIM_TEXTURE,0,"21b98d3c-617c-c1b7-8165-d1bb67ec9dfb",<0.5,0.8,0.0>,ZERO_VECTOR,0.0]); //Shadow on face 0 llSetPrimitiveParams([PRIM_TYPE,PRIM_TYPE_BOX,PRIM_HOLE_DEFAULT,<0.125,0.625,0.0>,0.0,ZERO_VECTOR,<1.0,1.0,0.0>,ZERO_VECTOR]); llSensor(gNAME,"",PASSIVE,10.0,PI); llSetTimerEvent(120.0); //Check sun every 2 minutes } touch_start(integer num) { if(llDetectedKey(0) == llGetOwner()) { llResetScript(); } } timer() { GoSun(); } sensor(integer num) { //How tall is the target object? list Box = llGetBoundingBox(llDetectedKey(0)); vector Low = llList2Vector(Box,0); vector High = llList2Vector(Box,1); gHeight = High.z - Low.z; //Move shadow to the base of the target object vector Pos = llDetectedPos(0); llSetPos(<Pos.x,Pos.y,Pos.z-0.5*gHeight>); GoSun(); } no_sensor() { llOwnerSay("I can't find the object named " + gNAME + ". Check to be sure that its name is entered properly in this script and that it is within 10m."); } }

We're all a little jittery at times. It's the coffee. There are tradeoffs in any script. You could reduce the jitteriness a bit by putting that llSetRot business in the sensor event, but that would really add a lot of work for the sim's servers to do, and add to overall lag. In the end, you have to ask yourself how much it's worth to you. Yes, followers are usually made physical because that's a reliable way to get smooth motion.

That's because the follower is physical and the script is allowing rotation on the Z axis. If it bumps into anything (like the ground), it will start spinning. You could set STATUS_ROTATE_Z to FALSE, or you could add a bit of code to force the follower to match your own rotation periodically. Off the top of my head, you might try putting llSetTimerEvent(3.0); in the setup function at the top of the script and then adding a timer event that looks something like this in the body of the script: timer() { if(llGetAgentInfo(llGetOwner()) != AGENT_WALKING) { llSetStatus(STATUS_PHYSICS,FALSE); llSetRot(gAgent_Rot); llSetStatus(STATUS_PHYSICS,TRUE); } } To make this work, you will also have to add a line that says rotation gAgent_Rot; at the very top of your script, so that it's a global variable, and then also add a line that says gAgent_Rot = llDetectedRot(0); in the sensor event. The net effect should be that the script checks every 3 seconds to see if you are walking. If not, it makes the follower temporarily nonphysical and matches its rotation to yours, then makes it physical again.

When you have Inventory open, you can also select the "Recent" tab to see any items that have been added to your inventory since you logged in. When you are just beginning in SL, this list will not look much diferent from what you see when you list your entire inventory. As you start to accumulate things, though, it can be very handy to isolate the things that you just added. Then, before you log off again, rename those items or move them to folders that seem more logical in your own filing system.

My best guess is that something has changed locally. If you're on wireless, maybe someone is eating a lot of your bandwidth. Or maybe you are running something in the background that's eating system resources (an antivirus scan or a routine Microsoft update). Maybe you just need to defrag your hard drive. If it's not that sort of thing, the next place to look is on your av. Check to see what your current script count is. If you are carrying around more than 50 scripts, you can be generating lag for yourself and others around you, especially if many of them are compiled in Mono. It's not likely that the lag you're seeing has anything to do with LL's servers or everyone else would be experiencing it too.

It looks as if this script is already designed to do what you want. It can be triggered in either a touch_start event or by commands received through a linked mesage. I think all you need to do is remove the touch_start event and then write a second script to control the pet's movement. When it starts to move, send a llMessageLinked to this script to start the animation. Send a second one to stop the animation when the pet stops moving.

It all depends on your sales volume. If you are making dozens of sales an hour, a flood of e-mails will be very annoying. A database is a much better choice. However, if you get a couple of sales a day like Dora and me, a private database is overkill. Your transaction history with LL is more than adequate for record-keeping. A nice heads-up e-mail is just enough to remind you to look in the transaction log. Or, as Dora says, you can easily do without notification at all and be pleasantly surprised when you see your balance increase. :smileyhappy:

Il y a aussi quelques lieus dans SL ou l'un peut trouver ces informations. Essayez, par example, le College of Scripting, Music and Science.

I'm finding the Knowledge Base almost impossible to navigate. Its Search function doesn't seem to be able to find things that were easily accessible before. For example, I had a request this morning for a tutorial or other information about how to use the in-world Search function. I tried typing in keywords "Search", "Using Search", ""Search in world", "How to Search" and several other variants. None of the suggestions I got pointed to anything remotely relevant. I expected it to point to Torley's videos and to KB pages that I know were there before. What's up?