The majority of the following notes are taken from the TPV Developer meeting held on Friday, June 15th 2018. A video of the meeting is embedded below, my thanks as always to North for recording and providing it.
- The Pálinka Maintenance RC updated to version 126.96.36.1996459 on Friday, June 15th.
- The Bakes on Mesh project viewer updated to version 188.8.131.526270 on Thursday, June 14th.
The rest of the current SL viewer pipelines remain as follows:
- Current Release version 184.108.40.2065811, dated May 31, promoted June 1 – formerly the Love Me Render Release Candidate – No Change.
- 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 17, 2017 and promoted to release status 29 November – offered pending a Linux version of the Alex Ivy viewer code.
- Obsolete platform viewer, version 18.104.22.1680847, May 8, 2015 – provided for users on Windows XP and OS X versions below 10.7.
[13:07-13:30] The 360 snapshot viewer has been stalled pending other work (such as support for uploading 360 images to Second life Place Pages) and for resources to work on it – but it has not been forgotten.
- [4:15-4:36] Voice update: there should be a new Voice RC viewer arriving, hopefully in the next two weeks. This will contain a new SL voice updated from Vivox.
- [5:56-6:26] Texture caching: a project viewer re-working texturing caching should be appearing soonTM. This viewer (and the work related to it) is currently on hold pending the Environment Enhancement Project (EEP). When it does appear, the Lab is confident it will make a noticeable improvement to viewer performance.
Please refer to my CCUG meeting summary for more on the status of Animesh.
[0:24-2:46] The Lab is aiming to try to get Animesh deployed to a release candidate channel on Agni (the Man grid) during week #25 (week commencing Monday, June 18th, 2018). It is not 100% certain there will be a deployment but, according to Oz, if it does go ahead, it will likely be a part of the RC deployment to the BlueSteel channel. Region holders wishing to test Animesh can request their region be moved to the required RC via a support ticket.
Note that the viewer supporting Animesh will remain at project release status for the time being.
[38:28-42:40] discussion – voice and chat of the Animesh 90-degree rotation issue. Again, all see my CCUG meeting notes, linked to above.
[4:42-5:50] Work on trying to improve region crossings on the simulator side of the equation is continuing. The messaging changes as a result of this work are being ported to the SL viewer, and should appear in a future Maintenance branch of the viewer, although the messaging updates themselves are not expected to have any real effect on improving region crossings from a viewer perspective.
The simulator changes are being handled one at a time, and will be appearing in simulator RC updates over the course of the next few months.
In the meantime, and as reported in my Simulator User Group updates (see here for an example), user Joe Magarac (animats) has developed a viewer-side update to help correct some of the region crossing issues within the viewer, particularly in relation to “partial unsits”. His work is likely to be featured in the upcoming Firestorm release, and I’ll have more on that in my review of that release. It’s not clear if these changes have been contributed to the Lab (or if they would be accepted if they have).
[14:58-17:45] There have been concerns that the roll-out of grid-wide experiences will mean automatic opt-in to such activities, rather than consented opt-in. This will not be the case: grid-wide will function the same as current region / parcel experiences – consent will need to be granted via a dialogue box. Only experiences developed by Linden Lab may have automatic opt-in, although none of the Lab’s experiences to date use this, and there are currently no plans to deploy any that do.
The only difference with grid-wide experiences and current experiences is that the land owner doesn’t have to explicitly allow grid-wide experiences (it will – I understand – instead be a case of land owners opting out of grid-wide experiences if they don’t want them on their land).
There has also been a request to make experience dialogues when requesting the ability to take control to be friendlier / more informative on the grounds that people are scared of them.
[23:30-37:00] There is an extended discussion (mostly text) over unintended consequences of experiences when combined with tools such as avSitter (and / or RLV), and the potential for abuse. This includes a discussion on how to make it easier for users to discover what is acting on their avatar through the viewer UI (and the problems in trying to do so).
- [3:28-3:58] https move – work is progressing on moving all of the SL web services to https: – however, this work has been more of a background task of late while the web services team work on other projects. So, not time frames on when the various services still to be moved will do so.
- [8:44-9:58] SL wiki edit rights / JIRA comments rights: because of issues with spam bots, etc., both the SL wiki and the SL JIRA has been locked from casual editing (wiki) / making comments on reports (JIRA).
- If you have a valid need to edit SL wiki pages, submit a support ticket with a request for edit rights. All requests are reviewed and access granted on the outcome of said review.
- If you have a valid reason to want to comment on SL JIRA reports, you should e-mail a request with your SL user name and why you are requesting access to letmein-at-lindenlab.com.
- Note that the JIRA lock does not prevent people from raising JIRA bug reports and feature requests.
- [22:48-23:28] The Read Off-Line Messages Capability: there have been a couple of issues in handling Friend and Group requests received while off-line. These are being addressed server-side, and it is hoped the code will be with QA in week #25 (commencing Monday, June 18th, 2018), and will hopefully be deployed shortly thereafter.