The following notes have been taken from the Simulator User Group, held on Tuesday, May 1st, 2018.
As always, please refer to the server deployment thread for the latest updates.
- On Tuesday, May 8th, the Main (SLS) channel received server maintenance package 18#18.04.30.515008, which includes updates to simulator communication protocols aimed at improving region crossings and teleports.
- On Wednesday, May 9th, all three main RC channels should receive server maintenance package 18#18.05.07.515224, which includes two new LSL functions: llRequestUserKey and llName2Key – see below for more.
Region Crossing Updates
Commenting on the region crossing updates, Simon Linden revealed he’d be out of the office for next week, but:
After I’m back I expect to continue region crossing work … the servers are now doing a better job tracking all the attachments and objects you may be sitting on. The goal is to know when the region thinks that’s all done, and the viewer acknowledges it. If that doesn’t happen, it can do better fixing it.
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.
There have been no SL viewer updates for the start of the week, leaving the current pipeline as:
- Current Release version 220.127.116.113644, dated March 27, promoted April 13 – formerly the media update RC.
- Release channel cohorts:
- 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.
Region Restarts and Server Moves
Once upon a time, the Lab used to put effort into trying to ensure adjacent regions in the same server or nearby server. This was most notably done through server re-balancing exercises (see my notes on one of them here, for example), carried out a couple of times a year and which could take some 6 weeks to complete. These operations generally required additional restarts for the regions being moved, and were thought to bring improvements to teleports and physical region crossings.
With hardware and infrastructure improvements over the years, coupled with other sets taken to improve overall grid performance, these operations are no longer carried out – although efforts are taken to ensure multi-region events are placed on simulators all located on the same or adjacent servers. However, nowadays, for the majority of region, they are moved purely as a part of the weekly rolling restarts.
Those wishing to know which regions might be sharing a server with their own can use Tyche Shepherd’s Grid Survey (use the region search and then click the region name link in the results). However, keep in mind not all the result may be up-to-date.
As noted above, Simon Linden, who usually leads the Simulator User Group meeting will be out of the office in week #20. However, the meeting for the week will still go ahead as scheduled.