Rolig Loon

It does sound like an Internet issue, so I would suspect the new ISP. When you get that message about region capabilities, it's telling you that it's taking way too long to download basic startup files from the SL servers (now AWS). That means your avatar appearance files, inventory, group information, and a lot of other things that need to be refreshed as you log in are stuck somewhere in the pipeline. If the block was on LL's end, we would see a huge wave of residents complaining about logins and there would probably be a message on the Grid Status Blog. Since those things are not happening, the slowdown has to be elsewhere ... your ISP or your own computer and its connection.

I was learning at a fantastic pace during my first three or four years in SL. Everything was new to me. I had to pick up building and texturing skills that I never knew even existed, and I had to learn LSL ( a very different sort of scripting environment than I had ever known). I had some highly talented mentors like Void Singer, but most of the people I learned from were barely more experienced than I was. It was all very heady. As time has gone on, much of what I learned back then has become "old hat" or has become obsolete knowledge. LL has added new features and tools at an accelerating rate, so it's still an exciting race to keep up with everything. At the same time, though, I find myself in a paradoxical spot. I am now one of the "old hands" who mentors newcomers but I have also hit my own limits so I don't understand some of the new features and probably never will. In an odd way, my SL has developed some gray, fuzzy "unknown" territories; years ago, the unknown territories were all hazy but well-lighted and welcoming. All of this says much more about me than about SL, of course. After all, I can say exactly the same things about RL.

To save yourself a LOT of trouble, always build with the root prim's +Z axis pointing UP and its +X axis facing FORWARD. When you set the object to ZERO_ROTATION, it will be standing up and facing East.

As always, the Knowledge Base is a good place to start reviewing basic information. Look for articles about Buying and Selling in SL, possibly beginning with this one:

Oh, that's pretty much a given. We may be crazy but we're not stupid enough to hang around on a glowing cinder. And we're ornery enough to find someplace else to carry on our greedy whining.

And to cap off an eclectic playlist for the evening.... Vertigo : Béla Fleck (feat. Sam Bush, Bryan Sutton, Edgar Meyer & Stuart Duncan) I'm not a fan of bluegrass, but I do make an exception for Bela Fleck.

You're probably right. That's the problem with posing a response off the cuff too close to bedtime, without taking the time to go in world to see if physics agrees with your brain. Your solution does look more plausible. Still, the magic is in llRotBetween. That's where the OP has to do his own experiments.

Unpopular Opinion: Customers are self-entitled whiners that don't deserve nice things. Unpopular Opinion: The human race is doomed. Unpopular opinion: Greedy creators and whiny customers are in near-perfect balance. If creators were less greedy, customers would have less to whine about. If customers were whinier, creators would be less sympathetic and more likely to think only of themselves. Thus (the ultimate unpopular opinion), creators and customers are feeding off each other, each getting exactly what they expect. The human race is likely to survive until the sun turns dark. 🙃

And something for those who are trying to keep their CPR skills current ..... Stayin' Alive : Luca Stricagnoli

So, ... Step 1: You rez the object, setting it to ZERO_ROTATION on rez (using llRezAtRoot, that's the rotation parameter) Step 2: On Rez, you quickly locate the object's owner. One fast way to do that is to ask vector OwnerPos = llList2Vector(llGetObjectDetails( llGetOwner(),[OBJECT_POS]), 0); Step 3: Adjust the Z value of OwnerPos to be the same as the Z value of llGetPos() (that is, the object's own position on rez). This will make the object keep its Z-axis vertical as it rotates. Step 4: Rotate the rezzed object to face the owner with llSetLinkPrimitiveParamsFast(LINK_THIS, [PRIM_ROTATION,llRotBetween( llGetPos(), CorrectedOwnerPos)]);

Here's an unexpected find .... Take Five - Public Piano Performance at a Castle Gate in Okinawa, Japan : Jacob Koller

Heather : Jessica Williams

This one I somehow missed. (Weird!) Wierd? Nah. That's just basic matrix algebra. vector A = < A1, A2, A3> vector B = < B1, B2, B3 > in which each of the elements in A and B are floats, then vector A * vector B = A1*B1 + A2*B2 + A3*B3 <---- a float If any of the elements are integers, I think LSL does implicit typecasting to convert them to floats before multiplying.

Minha : Bill Evans & Eddie Gomez

Love and Hate : Jessica J Williams, pianist and composer

All generalizations are flawed, for that matter. Including this one.

Indeed. I remember first hearing the Chopin #15 nocturne when I was about 14 and feeling overwhelmed by the melodic line and the cascading harmony. I had an LP recording of the nocturnes by Svaitoslav Richter for many years -- loaned to my sister who, sadly, misplaced it -- but this Horowitz performance is much more emotional than I remember Richter's being.

Vladimir Horowitz: Chopin - Nocturne No. 15 In F Minor, Op. 55 No. 1 This recording of the Nocturne #15 is one of the best I have heard, by one of the best pianists of the 20th century.

Ah, OK. Then you'll never hear anything directly from LL, and if you just submitted the AR they probably won't even see it until Monday. As helpful as a photo might seem, it's too easy to fake one, so the Lab won't make a decision based on your submission alone. They will do a full investigation, gathering their own evidence. That's likely to take time, so be patient. Meanwhile, I'd suggest not taking any action against the neighbors yourself. After all, they could submit their own ARs, which could complicate the investigation.

If you submitted a Support ticket, you did it wrong. File an Abuse Report instead. Support tickets go to the tech team for triage or repair. Abuse reports go to the Governance Team.

I used to feel inadequate and morally lax for not having a tidy, well-organized inventory. I'd lurk in forum threads about how to sort things into logical folders and I'd imagine intricate tree structures with a perfect spot for each of my belongings. I have just a touch of OCD, so I was embarrassed to admit that my inventory is a total mess. NO MORE! My inventory may be a mess but it's my mess and I am proud of it. After almost 17 years in SL, I still have only 46,000+ items in inventory and I rarely have trouble finding things when I need them. Things are jammed into folders with names that point me in the right direction ( "Landscaping Stuff", "Dresses (mostly)", ... ) and many that refer to specific projects ( by a code name and date, usually), but the folders are wherever I thought they made sense at the time. There's no consistent logic to them. I run barefoot through inventory to find specific things, trusting my memory and enjoying a touch of serendipity when I discover something I wasn't really looking for along the way. It's all gleefully chaotic, quite like the random stacks of things around me in RL. I couldn't explain to anyone else how I find my way through the mess, but who cares?

Cambridge Buskers Concert This is an unorthodox but very entertaining selection of classical and semi-classical favorites. I remember seeing the two of them perform sometime in the early 80s. This video in this recording (in Japan) is not very good but the music is fun.

J.S. Bach: Brandenburg Concerto No. 4 / Cappella Gabetta, Maurice Steger, Andrés Gabetta This is one animated performance!

Unlikely, although you should probably contact the scripter directly to see if s/he has any suggestions (or has perhaps been working on an update). It's more likely that you are accidentally overloading it somehow. Trying to feed it too much data? Feeding it data in the wrong format? Unfortunately, since you can't see the script itself there's no way you can do the sort of debugging that would give you clues about why it's overloading.

If that's not your script, you probably don't have permission to view it or modify it, so the short answer is that you can't "fix" it. Frionil is right. Your script has run out of memory, probably because it has been saving information in internal lists and it has saved so much information that it is choking on it. I doubt that you will be able to reset the script by the methods Frionil suggests, but go ahead and try anyway. If you don't have permission, the reset options should not be available for you. You will need to rez a fresh copy of the script.