Update, May 29th: the BlueSteel RC updated to server maintenance package #19 19.05.24.527547. Magnum and LeTigre appear to have remained on #19 19.05.17.527341.
Server Deployments
At the time of writing, a deployment thread had yet to be posted however:
- On Tuesday, May 28th, the SLS (Main) channel updated to server maintenance package #19 19.05.17.527341, previously deployed to all three RC channels.
- It does not appear that the three main RC channels will be updated on Wednesday, May 29th. Commenting on releases, Simon Linden said:
For server news, we updated the main channel of regions this morning, so the grid is pretty much all on the same version, except for one small RC channel. That’ll get updated tomorrow, I believe.
This “small” update might include an initial deployment of the updated region crossing code that has been subject to testing in the last couple of weeks, as per my last couple of Simulator User Group updates.
SL Viewer
There have been no LL viewer updates at the start of the week, leaving the pipelines as follows:
- Current Release version 6.2.2.527338, formerly the Teranino RC viewer, promoted May 22nd.
- Release channel cohorts:
- Bakes on Mesh RC viewer, version 6.2.3.527418, dated May 23rd.
- EPP RC viewer, version 6.2.3.527250, dated May 16th.
- Love Me Render viewer, version 6.2.2.527021, dated May 13th.
- Project viewers:
- 360 snapshot viewer, version 5.1.6.515934, dated June 6th, 2018 (see my hands-on update).
- Linux Spur viewer, version 5.0.9.329906, dated November 17th, 2017 and promoted to release status November 29th, 2017 – offered pending a Linux version of the Alex Ivy viewer code.
- Obsolete platform viewer, version 3.7.28.300847, May 8th, 2015 – provided for users on Windows XP and OS X versions below 10.7.
In Brief
Script Processing Issues
As I’ve recently report, there have been numerous reports of script run time issues, with some reporting that problems only started occurring following the roll-back on April 18th, 2019. BUG-226851 outlines some of the problems. Some regions experiencing the issue have been cloned to Aditi (the beta grid) where they are running fine, and the Lab is currently looking at script scheduling on Agni (the Main grid).
It has been suggested that multi-thread LSL might offer advantages, prompting Simon Linden to comment:
Again it’s a tougher job retrofitting multiple threads since it wasn’t part of the original design … it would have to be an update queue … but that adds some problems too, as if you call one function and it changes something in-world, then one to get the info … we’d have to suspend until we apply the first. I’m not saying it’s a bad idea or anything … just that it would turn into a monster project.
Rider Linden added:
Threading is one of those things that really needs to be considered up front in the design. Trying to retrofit it into an existing project can lead to madness.
Voice Griefing
Voice griefing can be a problem on voice-enabled regions. It can take several forms (e.g. someone hacks voice system so they can connect to a region without being in it or even logged in). Detailing with these types of hacks is exceptionally difficult. However, Oz commented in the SUG meeting that LL are working to address this problem – how wasn’t specified, but one possible way of doing so would be for Support to be able to remove an offending user from voice.
Inara Pey: Living in a Modemworld 