Update, April 10th: as per Bugsly Linden’s forum comment, the RC regions are receiving a maintenance update – 19#19.04.09.526122, which contains additional logging to help capture data on the region crossing issues.
As always, please refer to the server deployment thread for updates and news.
- On Tuesday, April 9th the SLS (Main) channel was updated to server maintenance package 19#19.03.28.525781, comprising the simulator operating system update and EEP.
- RC deployments – at the time of writing, there was a degree of conflict here:
- The deployment thread states there is no planned deployment to the three main RC channels, and all three should remain on server maintenance package 19#19.03.28.525781.
- At the Simulator User Group meeting, Simon Linden indicated there will likely be two deployments, stating:
We’re doing last-minute discussions but will likely have updates out tomorrow in the RC channels. One won’t have any visible changes, but has some logging that might help sort out the region change issue [teleport disconnect?].
The other is a maintenance release, the most interesting thing there is some additions to llGetObjectDetails() that give Animesh information.
- I’ll update should the deployment thread be refreshed with new information.
UDP Asset Messaging Deprecation
It was indicated in the week #14 deployment notes that 19#19.03.28.525781 would contain the removal of UDP Asset message handling from the simulator code, meaning that anyone using very old viewers still reliant on UDP messaging for assets will not be able to receive any updates for the following: animations, body parts, clothing, gestures, landmarks, meshes and sounds.
However, testing after the deployment of this package suggests that UDP messaging is still being handled through older viewers (notably the SL Linux Spur and Obsolete Platforms viewers) and on regions on any of the RC channels or the SLS (Main) channel. Whether this is due to a back-end issue (a stale cache?) or something else, is unclear. Commenting on the situation, Simon Linden noted:
I’m not sure what’s going on … it was _supposed_ to be disabled with the update that went to the full grid today.
There have been no updates to the current SL viewer pipelines, leaving things as follows:
- Current Release version 184.108.40.2065446, formerly the Love Me Render RC viewer, dated March 26th, promoted April 2nd.
- Release channel cohorts (please see my notes on manually installing RC viewer versions if you wish to install any release candidate(s) yourself):
- Project viewers:
- Linux Spur viewer, version 220.127.116.119906, dated November 17th, 2017 and promoted to release status 29th November, 2017 – offered pending a Linux version of the Alex Ivy viewer code.
- Obsolete platform viewer, version 18.104.22.1680847, May 8th, 2015 – provided for users on Windows XP and OS X versions below 10.7. This viewer will remain available for as long as reasonable, but will not be updated with new features or bug fixes.
Teleport disconnects continue to be a problem, and the Lab is continuing to investigate, having issued a blog post on the matter on April 8th. Commenting on the situation at the Simulator User Group meeting, Simon Linden said:
Currently we know that the 2nd region and the viewer aren’t communicating as they should when it fails … it seems like you get transferred to the 2nd region OK, but the viewer just doesn’t get connected properly … The first region thinks all is well and it’s done, the 2nd gets the TP data but never starts talking right with the viewer.
Following the Simulator User Group meeting, a stress test was attempted, with groups of people teleporting between a group of three regions, with mixed results (some reported disconnects, others had no issues).
Older viewers have additionally been suffering with “regular” disconnects roughly every 15-minutes, which may be related to the deployment of the latest simulator operating system updates, and might be getting conflated with the teleport disconnects to some degree. However, for Singularity users, there are fixes in the works, and the suggestion is that, if possible, people try installing one of the more recent nightly builds.