Lucia Nightfire

Sounds like you're going to be needing an onion head/body as BoM can't support animated textures "adequately".

What a crock.

In applications I made that try to interpret if a return might have been truncated, I required a limit of 251 bytes. That way there is no guessing whether a 1, 2, 3 or 4 byte character got clipped or not.

I've brought up dedicated local memory and prim memory aspects for synchronous R/W. LL is scared to death of the notion. (or at least Oz Linden was) @Rider Linden Maybe you can also include this feature request if this one here gets any priority. 😉

Is this on Mainland? Is any/all encroachment return affected in the region? If memory serves, encroachment return is a console setting for estates. @Whirly Fizzle am I thinking right?

I just can imagine said forum would be filled to the brim of complaints of security orbs and dreams of being able to fly/drive/sail into people's bedrooms without fear of repercussions. 😉

To be fair, encroachment return DOES lose it's mind sometimes.

Just an FYI, but public access democratically activated moderation devices have been used in sandboxes/communities in the past and they have been abused and people wrongly ejected/banned. Said devices usually don't last for long periods of time.

Just an FYI, but public access democratically activated moderation devices have been used in sandboxes/communities in the past and they have been abused and people wrongly ejected/banned. Said devices usually don't last for long periods of time.

Just as the title says. I'm in favor of returning longer strings, but am weary of certain retoractive changes with existing functions versus offering a new function with a new limit. This discussion is in response to the filing of this feature request.

LL needs to hire a 1st string quarterback. They never have time to 'tackle' anything. 🙄

Yeah, but the bug I posted came with the changes to llUnsit() released this week.

A feature that exists in most Unity based sandbox games and we can't get it in SL, because we have to be perpetually 10+ years behind the standards. I would bring it up again at the next server or tpv meeting.

I'm not seeing the latest 360 snapshot viewer on the release notes page. The one there now is 2 years old. https://releasenotes.secondlife.com/viewer.html

In the US it's always a Dave that screws things up. Or so the job advertising commercials on the radio tell me.

We are still technologically at an infancy to have a true metaverse. Also, no true metaverse can be owned/operated by any one corporate entity.

Was another thread necessary? 🙄 Let's make 20 more threads about the same thing!

It's a shame there is still a bug with unsits. https://jira.secondlife.com/browse/BUG-231144

Someone make this meme caption: "I don't always log into a soulless husk of an MMO, but when I do, it's one that offers NFTs." 😆

vector cam_eye_offset = <3,0,4>; vector cam_at_offset = <0,0,1>; float cam_distance_tolerance = 0.01; //meters float camera_angle_tolerance = 0.5; //degrees default { state_entry() { llSetCameraEyeOffset(cam_eye_offset); //local to link, not root llSetCameraAtOffset(cam_at_offset); //local to link, not root llSetText("",ZERO_VECTOR,1.0); llSetTimerEvent(1.0); } on_rez(integer i) { llResetScript(); } timer() { if (llGetLinkKey(llGetNumberOfPrims()) == llGetOwner()) { if ((llGetPermissions() != PERMISSION_TRACK_CAMERA) || (llGetPermissionsKey() != llGetOwner())) { llRequestPermissions(llGetOwner(),PERMISSION_TRACK_CAMERA); return; } vector cp = llGetCameraPos(); rotation cr = llGetCameraRot(); vector gp = llGetPos(); rotation gr = llGetRot(); vector target_global_cam_pos = (cam_eye_offset * gr) + gp; vector vn = llVecNorm(cam_at_offset - cam_eye_offset); //local_camera_aim_vec_norm rotation target_local_cam_rot = llEuler2Rot(<0.0,llAsin(-vn.z),0.0>) * llEuler2Rot(<0.0,0.0,llAtan2(vn.y,vn.x)>); // I used this method as llRotBetween() can return '180 degrees off' scenarios on local x or z rotation target_global_cam_rot = target_local_cam_rot * gr; float dist = llVecDist(cp,target_global_cam_pos); float ang = (llAngleBetween(cr,target_global_cam_rot) * RAD_TO_DEG); if ((dist > cam_distance_tolerance) || (ang > camera_angle_tolerance)) { llSetText("Press ESC to reset camera.\n \n \n \n \n \n ",<1.0,1.0,1.0>,1.0); return; } } llSetText("",ZERO_VECTOR,1.0); } } In this example I just created out of curiosity/boredom and with "expanded" use of locals for the sole sake ease of reading, you can adjust the cam eye and at offsets and the tolerances to suit your needs and adapt the code to your application. Whenever you're sitting on the object and your camera's position or rotation exceeds tolerances, a hover text message will display telling you to press Esc to 'reset' your camera.

Secondlife already has enough facets about it that, after use, leaves one feeling empty. Why do we need to add NFTs on top of that?

Governance is already overwhelmed in handling ARs and marketplace flags. They most likely don't want the additional workload of publishing reports or even deciding which and what report can be published. I do, though, wish they could at least post a few of the most interesting cases handled per month, with "names/locations changed to protect the innocent".

I would rather have a function that can give the user the option of turning on/off what triggers the changed() event instead of turning on triggering with parameters that didn't used to trigger it before, which today could lead to a crap ton more region script eps, possibly event queues getting maxed out and content breaking. Something like: llSetChangedEventTriggeringParams(link_number, [CHANGED_NAME, FALSE, CHANGED_DESC, FALSE, CHANGED_COLOR, FALSE, CHANGED_TEXTURE, FALSE, CHANGED_INVENTORY]); I've longed for a way to not trigger changed() events from color or texture changes without first doing script state juggling.

Event then, it will be finger wagging and wrist slapping from Governance until 2025 when they may start considering bans.