Belleck House, Oct 2015 (Flickr) – blog post
The following notes are primarily taken from the TPV Developer (TPVD) meeting held on Friday, October 23rd, 2015. A video of the meeting is included at the end of this report, and time stamps to it are provided. My thanks as always to North for the video recording and providing it for embedding.
Deploys for Week #43 – Recap
There was no deployment to the Main (SLS) channel on Tuesday, October 20th. On Wednesday, October 21st, all three RCs should receive the same new server maintenance package, which include server-side improvements for delivering group notice attachments, together with some simulator crash fixes and code to prevent the uploading of “hacked” mesh content (e.g. mesh items which show a LI of 1 no matter what their actual complexity, or which spoof a creator’s name).
[00:00] There have been no further updates to the SL viewer currently at RC or project status since the update to the Quick Graphics RC, which I covered in part 1 of this week’s report.
It still appears as if the next RC that will be promoted to a de facto release status will be the Notifications RC viewer (currently version 184.108.40.2065981), although this won’t be confirmed until the start of week #44.
[00:37] As previously noted, the Quick Graphics and HTTP viewers still have some problems which need to be addressed before either one can proceed forward to release status. So except to see further RC updates to both of these in due course.
[00:54] The Chromium Embedded Framework project viewer is getting some good public testing, and is expected to get some “fairly frequent” updates.
[01:05] The Oculus Rift viewer currently isn’t being worked on, as attention is focused on the other viewers in the various pipelines. However, it is hoped work will resume “pretty soon”.
[01:20] There are further bug fixes and updates in progress, including some fixes for some minor regressions in the current release viewer, and these are getting fast-tracked and will be appearing in a further Maintenance RC in due course.
[15:00] It is likely that when the next release viewer promotion takes place (Notifications viewer), the Lab will block a series of much older versions of their viewer, but not the Obsolete Platforms viewer, version 220.127.116.110847, which they still plan to have available until such time as it simply stops working – although it should be remembered this viewer is already regarded as unsupported by the Lab.
Grid Status Page RSS Feed
[01:58] In week #31 I reported that the Lab are working to update the Grid Status page RSS feed from RSS version 1 to RSS version 2. As existing web pages, etc., using the feed may need to be adjusted to accept the updated feed format, a proxy URL (http://beta.status.secondlifegrid.net/feed) has been available for testing purposes. It now appears that the switch will be thrown very soon to make the new version 2 RSS feed the default.
[02:15] As per the Lab’s recent SL improvements blog post, the first set of viewer-side updates aimed at improving inventory reliability are being queued up ready to appear in the project viewer. however, these are unlikely to appear before the HTTP updates currently in RC reach a release status. Once the viewer-side changes appear, the Lab will start work on deprecating the outdated inventory messages which are no longer required on the simulator side.
Server-side Upload Checks for Assets
[02:50] As a part of their overall work in trying to improve reliability within second Life, the Lab is looking to add further server-side checks to ensure viewers aren’t attempting to do anything the simulators aren’t equipped to handle, or which may cause unintended issues or outcomes, etc., for users.
This work will see the introduction of further validation checking on various asset types at upload. An example of this might be checks to ensure animations are what they say they are, further checking of mesh uploads to ensure they can be rendered correctly, etc.
[08:00] In particular with mesh, a simulator check is to be introduced to prevent the upload of mesh items weighted to all attachment points. There has been a viewer-side check designed to prevent such mesh items from being uploaded, which will in future be enforced simulator side. Existing content weighted in this way should not be “broken”, appearance-wise; but the simulator check will ensure such meshes cannot be uploaded (see FIRE-17144 for further details).
Attachment Point Validation
[04:20] Alongside the above, the Lab will be looking to introduce simulator-side attachment point validation checks. Right now, it is possible to have the viewer attach items to an avatar using points with are not correctly defined on the avatar skeleton. This can result in other viewers showing the item randomly attached to the avatar (or possibly floating nearby – for those with long memories, think of the Emerald “attachment tail” which multiple attachments were introduced on that viewer without adequate simulator support).
To prevent this, the Lab are looking to enforce the recognised attachment points simulator-side, so that any attachments using an incorrect attach point will be mapped to a defined attachment point, and moved there. This work will be carried out incrementally, and will initially offer the changes to Aditi to allow for testing.
Firestorm is now in Feature Freeze in preparation for the next release, which is now undergoing testing. Assuming no major blockers are uncovered, the next release should be available in November. This will be up-to-date with the Lab’s current release viewer (18.104.22.1685531 – Maintenance release), and may included some additional items cherry-picked from upstream of that release. However, it is unlikely to have the new notifications updates, HTTP, Quick Graphics, etc.