SL project updates 16 18/1: server, viewer

Airship Pirates Town; Inara Pey, May 2016, on Flickr Airship Pirates Townblog post

Server Deployments Week 18

On Tuesday, May 3rd, the Main (SLS) channel received the same server maintenance package originally deployed to the three RC channels in week #17, comprising a crash fix and minor internal improvements.

There will be no deployment to the RC channels on Wednesday, May 4th, and no scheduled restart of simulators on that channel.

SL Viewer Updates

The two release candidate viewers currently in the release channel were updated at the end of week #17:

  • The current Maintenance release candidate updated to version, dated April 28th
  • The Quick Graphics release candidate updated to version, dated April 26th.

This means there has been no promotion of an RC to de facto release status, while the project viewers have not been updated, leaving the complete list of remaining official viewers as follows:

  • Current Release version:, dated March 23rd and promoted on April 1st,  formerly the HTTP / Vixox RC viewer
  • Project viewers:
    • Project Bento (avatar skeleton extensions), version, dated April 15th
    • Oculus Rift project viewer, version, dated October 13, 2014
  • Obsolete platform viewer version dated May 8, 2015 – provided for users on Windows XP and OS X versions below 10.7.

Avatar Complexity

There are still some issues yet to be resolved with Avatar Complexity which is why this viewer is currently not progressing towards a release status at present. One of these is avatars which should render as solid colours (or “Jelly Dolls” as the popular term for them is now) or imposters are invisible.

This has been a long-standing issue (see BUG-10330), which has proven hard to reliably reproduce, and has had a number of theories attached to it. Recent testing has suggested one of the causes is a possible conflict between the viewer trying to render avatars as Jelly Dolls whilst trying also to account for any alpha mask applied to the avatar with all the layer check boxes ticked.  This is possibly because ticking the alpha mask check boxes result in a “special” UUID being applied. Currently, the precise cause of the issue has yet to reach a consensus opinion, and investigations and tests continue.