Cerise Sorbet

You're getting the mandatory update mesage because that candidate is already out of date, with more bugs fixed on this round. http://wiki.secondlife.com/wiki/Linden_Lab_Official:Alternate_Viewers is a better spot for tracking pre-release viewers. At the moment, 3.7.26.299845 is the latest on the maintenance branch. Expect that to be updated within a few days too, unless it happens to graduate to the main viewer.

OK, https://greasyfork.org/en/scripts/8567-lsl-posting-tool-for-community-secondlife-com for the fix. This version is still years out of date with keywords, just wanted to get it running again. If you have your own modded copy of the script, you can fix by adding this line to the header: // @include https://community.secondlife.com/* It used to be that the SL forum always used http, whether or not you were logged in. This week, it now uses https for both cases. Whatever, maybe there was a great reason for this. A little advance mention somewhere would have been nice.

default{ state_entry() { llOwnerSay("testing 1 2 3"); }}

Is it this bear? That hair is done with particles, like eleventy bazillion particles. That approach isn't going to fly in SL.

The setting to change in this case is in the Move and View panel of the preferences. If the single-click action is set to move to target, you get the inverted mouse movement with it. Switch it off to get traditional mouse behavior.

Vivienne Schell wrote: Basically Linden Lab COULD take down whatever content they want to take down for no reason at all. They could do that, but with a loss of legal protections that would drain their bank book and put them out of business in a short time

"Avatar" content could be taken down without involving DMCA because trademarks were involved. Trademarks fall under different laws with different standards and different processes. Most notably there is nothing like "safe harbor" for trademarks. There is a fair dealing principle for trademarks, but it does not work the same way as copyright "fair use" and involves a whole different list of tests.

Bobbie Faulds wrote: It would be nice if LL actually looked at the DMCA claims. As the one filled against the Belleza mesh body shows, when Tricky went to fight it, turns out the person named as filing it didn't have and had never had an SL account and had no idea what SL was. The body was then allowed back. Just a simple fact check would have shown it was a false filing and saved everyone time and money. This is a flaw in OCILLA that was never adequately addressed by US lawmakers. Proof of identity is not one of the requirements to make a notification "effective", and bigger fish than LL (most notably Google) have been rebuffed on attempts to require it. Notifications are supposedly make under penalty of perjury, but this only comes in after the fact. This part has shown itself to have no teeth, because a takedown notification is only a statement that the filer believes an item infringes. That is a notoriously difficult thing to disprove.

Your three newest nail applier listings do have images, but Adblock Plus will hide them if you are using that. The problem is the filenames, you used moon-nails-ad.jpg, chipped-nails-ad.jpg, rainbow-ombre-nails-ad.jpg Rename the files so that words like "ad", "advert" etc. aren't in there, re-upload, and Adblock should stop bothering your listings.

Change your regular SL password, that triggers an inventory update on Aditi. That happens overnight. Send your Aditi L$ to an alt before you update, if you want to keep them, or you'll have to wait for yet another process to bump you up to the wacky high balance.

Yeah, you can look thru the messages and the LSL function and see that parcel access all works off UUIDs. Same for groups. There are some dialogs that omit the numbers, which is why for example it is not possible to mute group invites yet (mute list is all keys too), but the underlying system doesn't really rely ion the names, those are filled in at view time (which is the root cause of the infamous Loading... things we have seen over the years, the names have to be fetched and filled in).

A change to the username is a tough problem. LL has changed some on occasion and still will, for a few circumstances like Lindens who left on friendly terms, ordinary users whose names were reported as ToS violations, and a handful of people LL considered to be VIPs. The basic SL system can handle these changes fine. Land, groups and objects all reference the number, so that stuff doesn't break. There are some glaring exceptions for user-facing stuff. L$ transaction histories use the legacy names, so there are potential difficulties for merchants and their customers. Also, there is an enormous legacy of inworld scripts like security systems, tip jars and vendors, games and so on that rely on those names. Some of the ancillary SL services like JIRA, the wiki and this forum use the names. And of course, there will be numerous third party services that have relied on LL's long term policy that usernames are generally constant.

Go to Analyze>Regular interval Labels time to place first: 0, placement method: label interval, label interval: 9.9 seconds. (you can add some decimal places if you like, but keep the length a little bit under 10.0 for best results in SL), Add final label: yes, adjust label interval to fit length: no then hit OK Go to File>Export Multiple split files based on labels and that should do it to it

Lots of gift cards are rejected. LL likes to use payment info as a kind of identification, and gift cards don't always allow them to do that. You may get better results using one of the L$ resellers when you want to use that kind of payment.

Eh, that's not really enough informaton to tell how it would work, but it's a definite maybe, so load up a viewer and see what happens. It's going to depend on how old the computer's design is. Older Intel graphics offerings were absolute garbage, and would run SL at single-digit FPS when it worked at all. But with their latest efforts, SL runs pretty acceptably on mid graphics. It can even be cranked up to full fancy for photos, but will run a bit slow to leave settings that high.

It's a shader to handle objects with skeletons, originally it was only for the avatar body. The CPU functions used on low end hardware don't handle the lighting the same way. It's not a big deal for legacy avatars since each avatar only has one, but you can see that light isn't being scattered in a nice consistent way once there is more than one object attached to that skeleton. You can put on some nice mesh body, or find anyone wearing one, then wham your graphics slider all the way to the left to see how this plays out.

Yeah, if you rig all the parts consistently and keep the normals matched up, it can look great. Note that this kind of falls apart on low end systems that can't support the "hardware skinning" feature in SL, you're going to see the seams with low settings no matter what you do.

Most of these bodies are split up into sections before upload and then linked back together on the SL side, so there can be plenty more than 8 texture faces. One body in particular, the CMFF one, uses a different approach. About 100 versions of each skin are available, each with different alpha shapes cut out.

Yeah, some other places that use hippoUpdate are havng that problem too. You'll have to contact Hippo support about that one.

There may not be practical uses for these details, but here they are anyway, just because I've ended up with a few of these objects and was curious. Maybe once every few hundred sim crossings in a vehicle at speed, there is a silly kind of hiccup. The vehicle crosses without you, and sitting in the vehicle in your place is a prim. This is only supposed to be a placeholder until your avatar gets across, but this is Second Life and you don't always get across. The placeholder may be left in place if you are a driver or passenger. Even if you don't own the vehicle you were riding on, or have edit rights to the vehicle, that prim will belong to you. If you get to the vehicle before it goes back to inventory, you can unlink your prim and keep it. The prim left behind is a basic box. All textures are set to NULL_KEY so it appears gray. The object name is the same as your legacy name, but it does have a separate UUID. You are its creator. Its dimensions are the same as your llGetAgentSize() at the time you were on the vehicle. It's physical, and has its llSetStatus() set so that it only turns around the Z axis. Physics material is flesh, gravity 1.0, friction 0.6, density 1000, bounciness 0.5. Real avatars have some artificial forces added to keep them from sliding around, so the box won't behave exactly like an avatar if you push it around. It can be shoved with relative ease.

Tobacco and alcohol references are 18+ only on the marketplace and should be given an M or A rating. https://marketplace.secondlife.com/listing_guidelines (Strangely, this doesn't appear to matter at all inworld. LL's own G rated Social Island regions have liquor dispensers.)

Can you check that your LL viewer version is the laest (newer than 3.7.18)? Amazon appears to be in the process of turning off SSL3 support on some of their cloud hosts, and the older viewers can't handle that.

Default NearMeRange is 130, which will exclude a ton of avatars. Try 4112, that will cover a whole region.

There's no central database for rezzed objects. You'll either need some other object in the region to keep tabs on it, or get the object itself to respond to phone home messages, like with llEmail or to ping a web site etc.

You've made the mistake of beliving that the speculation in this thread about what the wagering policy covers has any bearing on what it actually covers.