Scripting Features

I'm posting this here since my original post as a bug was closed with an "expected behavior"-type reply. As referred to by the discussion mentioned in the LSL portal documentation for llGetLinkPrimitiveParams() ( https://community.secondlife.com/forums/topic/486118-only-set-ambiance-on-prim_projector/?_gl=11wd89ez_ga_T7G7P6DCEC*MTcwNjU2MzkwNS4xLjEuMTcwNjU2MzkwNy41OC4wLjA.#comment-2446570 ) the call with PRIM_PROJECTOR currently triggers shouting on the DEBUG_CHANNEL about an unsupported parameter. I understand that PRIM_PROJECTOR is considered, for now, as write only, but I see no valid reason why it could not be readable at all. The current situation is inconsistent in my opinion. While I understand the potential problem with texture rights, I believe the behavior of this parameter should be consistent with that of PRIM_TEXTURE: if the texture is in the prim's inventory, return its name, else if the owner has full permissions over the object return its UUID. Otherwise return NULL_KEY. This is important to be able to "copy" a user-set parameter from one object to another for example, I want to read the parameters and send them to another object. Please make PRIM_PROJECTOR behave just like PRIM_TEXTURE in this regard, as described in the discussion. Thanks!

We have many ways to Detect if an object is (left) clicked on, but no way to Detect if someone rights clicks on that same object, Why? This would be a very useful feature for the SL Racing Community and vehicle enjoyers as a whole, and I'm sure this could have many other uses for scripters in general. The reason for this request is because of the ability of a resident to effect the movement of a car (or any physical object) even if the object doesn't belong to them by right clicking on the object. I am not talking about a resident that has the person's edit rights, or estate manager of the sim they are on. But someone who has no rights to an object can still effect that object by right clicking on it, (often spamming right clicks) it will either make the object micro stutter slowing it down or out right stopping the object in place for a brief moment. Having a function that can detect a right click, much like you can with a left click, so that a script can tell you who is editing it would be very very helpful! And / Or some kind of tag that would stop physical objects from stopping when right clicked / edited would be really cool too.

I often switch back and forth between Firestorm and LL Viewer when helping customers with issues. I have found ways to be comfortable with either viewer BUT the limitation on LL viewer to not be able to derender a neighbor's way too low sky platform, a surround box that blocks my view of the water, or a random chair hanging in mid-air is very limiting. It seems a small thing but can make a huge difference when wanting to be comfortable on one's own mainland plot.

Linkset Data allows multiple scripts in the same linkset to read/create/update/delete data. We currently do not have any LSD functions with an append validation protocol. Experience KVP updating has a validation protocol w/ feedback which can address race conditions between scripts in the same linkset, different objects in the same region or different objects grid-wide. The following function satisfies the need stated above for LSD: integer llLinksetDataWriteWithValidation(string name, string value, string pass, string original_value) A new failure code constant LINKSETDATA_VALIDATION with value 6 will be needed for this function. Functionality: If name does NOT exist and value is NOT an empty string and original_value is an empty string, the entry is created and 0 is returned, else, 6 is returned. If name exists and value is NOT an empty string and original_value matches name's current value and pass matches name's current pass, the entry is updated and 0 or 5 is returned, else, 6 is returned. If name exists and value is an empty string and original_value matches name's current value and pass matches name's current pass, the entry is deleted and 0 is returned, else, 6 is returned. Other typical check failures such as empty name, name not found, pass mismatch, etc. will return the same values as they do now before validation handling is done. The server is actually already doing these checks in the background to determine what integer value to return with exiting LSD functions. There's just, currently, no validation protection. This feature offers validation protection for creates, updates and deletes which is a must in an environment where multiple scripts can potentially modify an entry at the same time creating race conditions. Since it has password input, this function becomes a defacto all-in-one append function for creates, updates and deletes, something even KVP currently doesn't offer.

## Proposal Very familiar syntax per llSetKeyframedMotion but for moving a camera through space with various options. * Client-side moves smoothly through the keyframes specified * KFM mode equivalent options available for e.g. forward, reverse, loop, ping pong * KFM command equiv to pause, resume, stop * Meant to be a single elegant function that achieves several usecases and familiar syntax llSetKeyframedCamera overrides (higher priority) but does not replace llSetCameraParams . If llSetCameraParams is set then pressing ESC should disable the keyframed camera and resume back to llSetCameraParams over KFC_EASE_OUT or CAMERA_*_LAG . llSetKeyframedCamera( list keyframes, list options ); Keyframes is a strided list of keyframe same as per llSetKeyframedMotion . KFC_* constants duplicate of KFM_* s or reuse the KFM constants. Requires PERMISSION_CONTROL_CAMERA or experience permissions. Keyframe list is uploaded to client with the options. Ping / time of function call / region time dilation should all be taken into account: Viewer skips/seeks forward to the appropriate frame between keyframes based on when function was called. Also the time delta between frames is affected by region dilation. This is so that a good attempt is made so that scripts can sync up in terms of llGetTime() . Calling llSetKeyframedCamera again should take into account the last keyframed camera position when it comes to KFC_EASE_IN . Camera should obey roll rotations on keyframes. For mouselook this is similar to sitting on a tilted object. Additionally: * An option to specify absolute/local coordinates instead of relative deltas (as client-side has no physics engine tie-in to require the deltas, default to non-delta for ease of use) * KFC_EASE_IN, float time — ease-in camera from current mode (mouselook, third person, alt-cam) over float seconds across beginning keyframes (equivalent to ZoomTime debug setting but for easing into the keyframed camera, default to ZoomTime , e.g. 0.4s) * KFC_EASE_OUT, float time — ease-out over float seconds across end keyframes (similar per above) * KFC_MOUSELOOK, integer enabled — whether user can look around in mouselook, rotation keyframes will still affect the base rotation unless decoupled * KFC_MOUSELOOK_FORCE, integer force — whether to force into mouselook (equivalent to llForceMouselook but might be from a HUD) * KFC_MOUSELOOK_DECOUPLED, integer decoupled — whether to decouple mouselook camera to prevent it from being rotated by keyframe rotations / target (usecase: if user does not enter mouselook to look around and instead uses third person camera and lets the keyframes rotate their camera; usecase #2: vehicle mouselook camera decoupling without mouslook steering) * KFC_TRACK_SIT, integer enabled — whether camera motion is coupled to sitting object, so keyframed camera moves relative to sat object (default TRUE) * KFC_TRACK_TARGET, integer enabled — similar to above but target an object/avatar by UUID to move keyframed camera relatively to * KFC_TRACK_ROTATE, integer enabled — whether keyframes should be rotated relatively to targets orientation instead of only position (default TRUE) * KFC_EASE_CUBIC, integer enabled — whether to use cubic interpolation between keyframes (default FALSE) * (and/or implement something like B-Spline Interpolation with weight/bias/tension parameters, e.g. KFC_EASE_SPLINE, float bias ) ## Usecases Smooth scripted camera movements through region coordinates Smooth camera movement relatively to object, avatar or sat object Smooth movement between static camera coordinates (via new call to llSetKeyframedCamera with KFC_LOOP & KFC_EASE_IN to ease into new static, looping camera keyframe pos) Camera that follows an object / avatar ( KFC_TRACK_TARGET ) Camera that orbits an object / avatar (keyframe list of positions around the target with rotations set to look at the center point) Camera follow/orbit an object / avatar but only in terms of position (e.g. if the object / avatar rotates it won't cause the camera to rotate, via KFC_TRACK_ROTATE, FALSE ) Vehicle mouselook repositioning ( KFC_LOOP , KFC_TRACK_SIT , KFC_MOUSELOOK ) Pausing, stopping or resuming keyframed camera similar to KFM_COMMAND — (however take into account the time of function call to ease into the frame it was supposed to pause at or resume from) Vehicle mouselook cameras that move along a scenic orbit around the vehicle for an occupant KFC_TRACK_TARGET can target an individual child prim of a linkset, or an attachment of an avatar to follow specifically Keyframed camera that follows a keyframed motion object ??? Many more usecases via creative parameter mixing Some usecases like being able to reposition vehicle mouselook cameras for occupants relatively to the vehicle is achievably by looping a position and enabling mouselook on the keyframed camera.

Suggested a method to reply to a http_request with the contents of a notecard with some simple templating options. llHTTPRespondWithNotecard(request_id, notecard_id_or_name, list_of_tokens_and_substitutions); request_id being the key of the request notecard_id_or_name being a natecard key or name of one in the objects inventory list_of_tokens_and_substitutions being a strided key value pair list of tokens to substitute in the notecards content e.g A script doing http_request( key request_id, string method, string body ) { llHTTPRespondWithNotecard( request_id, "content", [ "%%A%%", "Hello", "%%B%%", "World" ] ); } With a notecard in it's object inventory called "content" containing %%A%% %%B%%!!! %%A%% %%B%%!!! %%A%% %%B%%!!! Would serve the http content of Hello World!!! Hello World!!! Hello World!!! To the request. This sort of feature was discussed a few times a Simulator User Groups

key llGetRegionWorldMapTile(string region_name) A LSL function to return the UUID of the current world map tile for a named region, so that it might be placed on a face using PRIM_TEXTURE. This could also be added to llRequestSimulatorData Currently the only ways I know to accomplish this depend on MOAP and voodoo to get an image from slurl.com , or pulling the CDN UUID from gridsurvey.com via a HTTPRequest. Which all seems pretty hacky and unfun.

Requesting the following controls to be added for further usage of mouse input while in mouselook. CONTROL_ML_RBUTTON - Right mouse button control CONTROL_ML_MBUTTON - Mouse wheel/middle button control CONTROL_ML_MWUP - Mouse wheel up control CONTROL_ML_MWDWN - Mouse wheel down control I actually woke up this morning and realized that we didn't have an ML_RBUTTON and this hasn't been in since the launch of SL. I figured we could cover the rest of standard mice and modernize the old llTakeControls function to keep up with GameControl. Mice, as a standard, have a Left/Right button, as well as a Mouse Wheel and Middle button.

There are many animations out there which were uploaded with a low / default priority. These are fine provided other overlayed animations running at the same time don't override their actions. It would be useful to be able to change that priority when starting the animation. eg: llStartAnimationPriority("animation", 6);

Apply PBR material to the particle system. Should replace the texture if provided, only used as fallback when someone doesn't have the PBR viewer. Ex: [PSYS_SRC_PBR_MATERIAL, "MATERIAL-UUID-KEY-HERE"]