Lucia Nightfire

Max rez distance = 10.0 + (triagonal of the rezzing link's size * 0.5); To get triagonal, simply use llVecDist(ZERO_VECTOR,rezzing link's size). So, a 1x1x1 rezzer prim can rez up to 10.866 meters away. Trying to rez 10.866 meters away will succeed. Trying to rez 10.867 meters away will fail. This is why 1024 meter long laser megaprim can rez a payload at "hit" location 100+ or 200+ meters away across a sim. Worn megaprims also facilitate this mechanic even in HUDs.

The Sugarcult Xolo dog avatar comes in BoM form factor. The dog looks good enough to also use as an Animesh companion, but I'm not finding any raw textures for it, only wearables, which Animesh does not yet support. If anyone knows of any skins offered in applier format or as raw textures, please let me know. Thanks.

INB4 one of SL's prominent user base asks, "Where's the 'Blender After Dark' version?".

So now it's metaverses we all need and not a metaverse? Got it. Capitalism, patents and brand/IP rights/protection won't allow for a true metaverse anyway. All this metaverse slanging that tech companies are doing now is to gage interest and to signal to those with less money to throw around that, "We got this. Don't even try it.". All the while, no one is going to come up with anything remotely like the pie in the sky everyone is dreaming of. Until the day full-dive is actually a thing, it's all an absolute waste of time. P.S. Full-dive without RW-to-IW observed time ratioing will be a bummer to. I want to overclock my brain and live pseudo forever while acquiring the knowledge of a god and all the time to do it in. IDC if I lose my humanity/identity/compassion in the process. Yeah...

There is no "broadcasting". Scripts that contain experience permissions (0x62000) automatically monitor when the perms holder either blocks the experience or enters land that does not have a land scope experience allowed and removes all perms. FYI, llAgentInExperience() can return false negatives while the target is over land that does not have the land scope experience allowed.

Unanswered experience permission requests remain active in the background for any one agent up to 5 minutes. You need to tailor your work flow to only handle one user at a time and ignore denied events from anyone other than the person of interest. What you encountered is the opposite of someone granting permissions after someone else steps in and has a request made and granted. https://jira.secondlife.com/browse/BUG-228162 In that scenario, we really need a dedicated error code.

When is https://jira.secondlife.com/browse/BUG-231144 going to be fixed?

More like https://jira.secondlife.com/browse/BUG-231218 Notice the report date? They've allowed this annoying(IMO, critical) bug to exist for over week now. Why didn't they roll the MP code change back?

Why we really need a placeholder for current diffuse, normal and specular texture with llSLPP* https://jira.secondlife.com/browse/BUG-227223

first, check an attachment with llGetAttachedList() + llGetObjectDetails () + OBJECT_GROUP (alternatively, make sure object isn't temp attached if NULL_KEY is returned) then, check the wearer with llGetObjectDetails () + OBJECT_GROUP_TAG (make sure all group role titles are unique and no one else can/will change them) http://wiki.secondlife.com/wiki/LlGetObjectDetails http://wiki.secondlife.com/wiki/LlGetAttachedList

Yet, another dated bug LL won't prioritize fixing. https://jira.secondlife.com/browse/BUG-37601 The parcel privacy ceiling no longer works on full region estates, too. https://jira.secondlife.com/browse/BUG-230749

*Windows 10 and up

What's with all the regions restarting ATM? OK, not "all", but I indirectly monitor thousands of regions and I'm seeing dozens restarting ATM, plus many of them are "stuck" showing "starting" via dataserver events. OK, got word it is "minor grid maintenance" and won't result in an incident report...

SL is the last thing I would waste BTC on. I wouldn't be spending BTC on anything ATM. Hold on to it until the next rocket to the moon.

Not to be a downer, but you discovered something that some people have been using for years. 😉 *1000 (you made me check that again to see if LL changed anything recently, but they didn't)

"We'll add it in a follow-up!" is also part their tao now which, at this point, has been either one broken promise after another or just straight up lies.

Would have helped explaining all the region rolls happening ATM with a separate post.

I simply do not want to add the overhead to each rezzer, one for rezzing characters, furniture, bits, animation preloaders, adjusting helpers. I'm already splitting scripts big time with everything as it is. To check who is sitting on something and where, I would have to use a dedicated llGetAgentList() script per rezzer or involve back and forth to a central service. I can't depend on an unsit magically causing a vehicle to die especially if the owner selects it or might have it already selected. Vehicles sometimes enter regions without a sitter as they've already crashed to desktop or got unsat in an adjacent region. I simply have a dedicated central single-scripted host that, at the bare minimum, checks for changes in llGetParcelPrimCount() that, upon change, checks where the land impact is coming from and if it is not owned by me, moves to the parcel, executes a prim return then moves back to its origin. I simply do not want to add overhead anywhere to accommodate vehicles. If vehicles weren't able to override the no-object entry flag, 99.9% of vehicle user's ire would be on just banlines and not security orbs.

That still depends on the land owner's needs/reasoning. For me, I've had idiots stop on my land with their 500+ land impact (once it turned physical) car doing who knows what, maybe take a selfie or to look at the surroundings. My land has a specific use case and that is to rez one or more high land impact animesh "playmates" on demand per clientele, anywhere from 75 to over 400 land impact each. I also offer private rooms at various altitudes on individual privacy parcels. So when I get people entering private parcels or when I get an influx of land impact that I do not own, people get sent home and objects get returned.

There are two pools that are being used, the parcel pool (parcel owner available prims grid-wide) and the region pool (ignoring region object bonus). Driving off the parcel, just means someone else is now eating the land impact, that is, if you entered a different land owner's parcel. Also, as long as the land impact doesn't go over their available prims, else, others are eating that overage in a distributed ratio region wide.

Fillers and overfillers have been a thing in "Combat HUDs" for years. It's why I even added it to my NPV from the days(over 5 years ago) I use to hang out in the weapons testing sandbox to block idiots from filling it with spam or attacks. I've filed this feature request and this feature request to deter that behavior, but LL hasn't bothered implementing any protocol.

I got something wrong in that previous list. It's 10% region overflow of non-temp legacy prims or mesh that blocks non-temp legacy prim and mesh rezzing in the reigon. It's 10% region temp prim overflow that blocks temp legacy prim or mesh rezzing, but not non-temp legacy prim rezzing. Also, this rate might also apply to the grid-wide parcel owner level as well.

Well, I don't want to show off too much, so I'll just "drive" there from the nearest rez parcel. 😉

I can come to your parcel, rez and sit on my NPV and block all rezzing on your land or in the region if you want. Send me a tp lure. 😉

Only if the vehicle is temp on rez, contains 0 mesh and the land impact does not go over 10% of the region's max prims. Mesh, even when set to temp, does not use temp prim accounting. Mesh "Prim" physics shapes can balloon land impact when a linkset is turned physical. The presence of sitters or selectors prevents autoreturn or overflow return. Non-temp land impact that exceeds a parcel's maximum prim allowance begins to "take away" available prims from other parcels at a proportion based on % of parcel size versus region max prims. Temp prim land impact that overflows a region's max prim allowance by 10% will block rezzing of temp, non-temp or mesh content anywhere in the region. Region-wide temp prim overflow can instantly cause all temp non-mesh objects in the region to die. And, yes, when a region's max prims have been overflowed, no vehicles or objects can enter. TL;DR - If a vehicle contains mesh or is non-temp, a parcel owner is eating the land impact.