2019 SL User Groups 7/1: Simulator User Group

Ponto Cabana; Inara Pey, December 2018, on Flickr
Ponto Cabanaclick any image for full size

Server Deployments

Please refer to the server deployment thread for the latest news.

  • On Tuesday, February 12th, there was no deployment to the SLS (Main) channel, leaving it on server maintenance package 19#; nor was there a restart.
    • The planned deployment was cancelled due to a last-minute bug.
  • On Wednesday, February 13th, 2019 the RCs are likely to be updated as follows:
    • BlueSteel and LeTigre should receive EEP update server maintenance package 19#
    • Magnum should receive server maintenance package 19#, comprising further internal fixes.

EEP Update

The EEP server update to be deployed to BlueSteel and LeTigre comprises:

SL Viewer

There have been no viewer updates at the time of writing, leaving the current pipelines as:

  • Current Release version, dated December 5th, promoted December 13th. Formerly the Spotykach Maintenance RC viewer – 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):
    • BugSplat RC viewer, version, January 23rd. This viewer is functionally identical to the current release viewer, but uses BugSplat for crash reporting, rather than the Lab’s own Breakpad based crash reporting tools.
    • Estate Access Management (EAM) RC viewer, version, January 23rd.
    • Love Me Render RC viewer, version, January 16th.
  • Project viewers:
  • Linux Spur viewer, version, 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, May 8th, 2015 – provided for users on Windows XP and OS X versions below 10.7.

In Brief

  • Viewer disconnects / crashes: some people on “older” hardware have been reporting what appear to be viewer disconnects / crashes of late after only being logged-on for around 15-30 minutes (see: this forum thread). This has been noted by the Lab, and a potential fix is being tested on Aditi. The problem here is that forum posts don’t always give the level of detail required for LL to really diagnose matters. Jira is always the preferred method of logging issues – and it is important to use the official viewer when doing so.
  • Name Change Issue: as reported in my last SUG meeting summary, a creator preparing for the upcoming Last Names / name changing capability encountered an unusual situation: the Lab had changed a user’s account name. However, when sending information to an external HTTP request (object UUID, object name, owner name of the object, etc.), to the creator’s customer database, a HUD used by the user was sending their original account name not their revised name. The issue is now believed to be a stale cache issues, as noted last time.

2 thoughts on “2019 SL User Groups 7/1: Simulator User Group

  1. On the JIRA issue, I have the problem that I use Linux, and the last Linden Lab release for Linux was released in November 2017. It also doesn’t use the Alex Ivy code, must be the 32-bit code, right? There maybe aren’t many of us, but how do we get around the “official viewer” thing? I know it’s a very good bet to assume Windows, but I am careful to tell people I am using Linux, and I still get asked about my Registry.

    JIRA, incidentally, is a Programmer Time Management tool, and it’s a horrible interface for bug reporting by ordinary users.

    Linden Lab have a pattern of poor communication, and they depend on people like you. Maybe you should bill them.


    1. Linux has has a rough ride in over the the last few years, but it is something LL has been trying to address, as I’ve covered in these pages. As a brief recap might help for anyone unfamiliar with the situation, given matters have continued over an extended period:

      • The Lab lost their bandwidth to maintain the Linux flavour of the viewer in 2015. At that time, they put out a request for assistance to the Linux dev community in SL for help in maintaining the viewer. This request was repeated periodically at venues such as TPV Developer meetings and Lab Chat sessions, but no assistance was forthcoming.
      • In January 2018, as you note, LL re-issued the last updated version of their Linux viewer, in the hope that it would be a stop-gap while they used the uplift to Alex Ivy code base to make decisions on how to move forward with Linux.
      • In late 2017, LL decided to simplify the Linux viewer build process: rather than try to meet the requirements of multiple flavours of Linux, they would alter their build process to produce a basic Debian flavour of the viewer, but without all the additional “flavour” libraries, so they would be able to provide a Linux viewer, and a build that TPVs could use as a base to add their own dependencies to in order to build their Linux versions of the viewer.
      • The first part of this work was completed in Q1 2018, but the Lab was still facing issues in trying to recruit Linux skill sets specifically to work on the viewer. So, again, a request was put out to open-source developers for assistance.
      • That assistance is now starting to be received, and conversations on how best to get an official flavour of Linux back on the road are continuing

      So, there is a glimmer of hope! 🙂 . Unfortunately, it’s not clear if / when an updated Linux flavour will appear. As, the project is slightly mired (depending on how you use Second Life) by the fact that the viewer will have Voice available.

      This is something beyond the Lab’s control, because Vivox, who run the Voice service and provide the Voice plug-in for the viewer ceased supporting Linux as an end-user platform in either late 2017 or 2018. Unfortunately (and as with the Windows and Mac flavours of the viewer) an older Voice .EXE cannot be used with any viewer that is released, due to assorted updates made to the Voice frame work making them incompatible with the current viewer code base.

      Also, it has yet to be determined whether or not the Lab’s version of any Linux viewer will have the mesh uploader included, due to issues around the Havok sub-licenses.

      Jira isn’t that friendly, although the Lab have been working to make the bug reporting process easier. I’ve actually been working with them for several months to produce a tutorial for those unfamiliar with raising bug reports / feature requests, and this is currently awaiting some (hopefully) final feedback from LL so it can be published.


Comments are closed.