As always, please refer to the server deployment thread for the latest updates.
- On Tuesday, May 15th, the Main (SLS) channel received server maintenance package 18#18.05.07.515224, which includes two new LSL functions: llRequestUserKey and llName2Key – see below for more.
- On Wednesday, May 16th, the Release Candidate channels were currently marked as TBD at the time of writing. However, during the Simulator User Group meeting on Tuesday, May 15th, Rider Linden indicated there would be two RC deployments:
- The BlueSteel and LeTigre deployment should comprise internal fixes, together with simulator-side updates for better management of estate level ban lists – although these will require a viewer update to be visible.
- The Magnum RC update should comprise the same internal fixes, together with the simulator-side updates for abuse report categories.
llRequestUserKey and llName2Key
llRequestUserKey and llNameToKey, both of which will be across all RC channels following the Wednesday deployment, are in connection with the upcoming return of Last Names (see this blog post and this blog post for more). These functions can be summarised as:
- Requests the Agent ID for the agent identified by name from the dataserver. The name given may be either the current name of an avatar or a historical name that has been used in the past. If no agent can be found with the supplied name this function returns the value NULL_KEY.
- It returns a handle (a key) that can be used to identify the request when the dataserver event is raised.
- Note that agent being searched for with this function does not need to be signed on to Second Life.
- See the llRequestRequestUserKey wiki page for more.
- Returns a key the Agent ID for the named agent in the region. If there is no agent with the specified name currently signed onto the region, this function returns the value NULL_KEY. Names are always provided in the form “First[ Last]” or “first[.last]” (first name with an optional last name.)
- If the last name is omitted a last name of “Resident” is assumed. Case is not considered when resolving agent names.
- Uses a different mechanism to look up agent information to the older llKey2Name().
- See the llName2Key wiki page for more.
Abuse Report Category Capability
As I’ve noted in my TPV Developer meeting updates, a new capability is being introduced that will allow the viewer to call abuse report categories from the simulator, rather than having them hard-cored into the viewer itself. This will help ensure abuse reports are filed using valid AR categories, while at the same time making it easier for the Lab to maintain the AR categories.
The deployment to the Magnum RC is the first phase of this work to be made to the grid. Once the simulator changes are available grid-wide, a viewer with the new capability should be made available, with a request that TPVs adopt the updates as soon as they can in their own release cycles.
The Ouzo Maintenance viewer has updated to version 126.96.36.1995016 (dated May 7th, but the update wasn’t listed in the Alternate Viewers page until week #20).
The Animesh viewer updated to version 188.8.131.525420 on May 15th.
The rest of the viewer pipelines remain as:
- Current Release version 184.108.40.2063644, dated March 27, promoted April 13 – formerly the media update RC.
- Release channel cohorts (please see my notes on manually installing RC viewer versions if you wish to install any release candidate(s) yourself):
- Love Me Render RC viewer, version 220.127.116.114788, April 25.
- Project viewers:
- Linux Spur viewer, version 18.104.22.1689906, dated November 17, 2017 and promoted to release status 29 November – offered pending a Linux version of the Alex Ivy viewer code.
- Obsolete platform viewer, version 22.214.171.1240847, May 8, 2015 – provided for users on Windows XP and OS X versions below 10.7.
Mesh Pivot Points and the Uploader
A long-time problem with the mesh uploader is that it ignores pivot points set within tools like Blender when a model is uploaded to SL. This means, for example, that doors set with a pivot point in Blender won’t work using that pivot when uploaded to SL. A feature request to enable the uploader to recognised pre-set pivot points in mesh objects was raised in 2015 – see BUG-37617 – and more recently, Beq Janus has been looking to add further information to it.
Region Crossing Updates
Code to improve communications during region crossings went grid-wide in week #19. A further round of simulator-side updates is likely to be deployed in the next few weeks. In the meantime, Joe Magarac (animats) believes most of the minor issues relating to “partial unsits” can be handled with changes to scripting / the viewer – see BUG-214653. He’s offered to rally support to help the Lab dig more deeply into this issue, by arrange group tests, etc., if the Lab can made simulator-side changes to help improve things.
Three major issues for vehicles are No Script parcels / regions, ban lines and scripted security systems. The former can be harder to deal with, as there is no advanced warning that scripts are disabled until the boundary is crossed. Scripted security systems tend to provide some warning which can generally allow those straying into a private area time to get out (unless the delay time has been set ridiculously short). Ban lines are somewhat insidious, however, as they can physically “snag” a vehicle whilst ejecting the occupants – with the vehicle often remaining in place with no auto-return.
There has been a feature request to handle ban lines better (BUG-216276), with another request for ban-lines to “deflect” vehicles, rather than allowing vehicle to cross them and becoming snagged when the occupants are ejected. It’s not clear if the Lab will adopt these ideas.