2020 SL project updates week #36: TPVD summary

Pony Box, July 2020 – blog post

The following notes are taken from the TPV Developer meeting held on Friday, September 4th, 2020. These meetings are generally held every other week, unless otherwise noted in any given summary. The embedded video is provided to Pantera – my thanks to her for recording and providing it. Time stamps are included with the notes will open the video at the point(s) where a specific topic is discussed.

Two length text conversations dominated the meeting. The first focused on mesh heads and brains, the second on graphics and users and system updates.

SL Viewer News


  • Current release viewer version, dated August 11, promoted August 17, formerly the Arrack Maintenance RC viewer – No Change.
  • Release channel cohorts:
    • Bormotukha Maintenance RC viewer, version, issued August 28.
    • Love Me Render RC viewer, version,August 21.
    • Mesh uploader RC viewer, version, July 27.
  • Project viewers:
    • Project Jelly project viewer (Jellydoll updates), version, issued August 26.
    • Custom Key Mappings project viewer, version, June 30.
    • Copy / Paste viewer, version, December 9, 2019.
    • Project Muscadine (Animesh follow-on) project viewer, version, November 22, 2019.
    • Legacy Profiles viewer, version, September 17, 2019. Covers the re-integration of Viewer Profiles.
    • 360 Snapshot project viewer, version, July 16, 2019.

General Viewer Notes

  • All three RC viewers have updates that are being queued for issue.
  • It is possible the Bormotukha Maintenance RC viewer will be promoted to release status at the start of week #37 (commencing Monday, September 7th).
  • As  noted in my previous CCUG summary, a new Love Me Render (LMR) RC viewer should be available soon (it is currently in QA, so could potentially appear in week #37). This viewer will have further EEP fixes, although not all of them may be in the initial RC release.
  • The Legacy Profiles viewer is awaiting a back-end update to the feeds, which may be being worked on.

In  Brief

  • [4:09-7:00] there is an intermittent problem of people viewing the Lab’s own web pages via the viewer’s built-in viewer finding at time that the website doesn’t see them as logged-in (although it should pick this up from the viewer).
    • This appears to be the result of a validation issue with the token generated at log-in and which should be passed to LL’s websites to allow the viewer to access them without the need for a further log-in.
    • LL are hesitant to fix the issue at the moment, as the back-end service handling the tokens is in the process of being moved to the cloud. Once the service has been transitioned, then the matter will be investigated and rectified.
    • This issue may have been triggered by changes make to the way server certificates are validated, which may have had an unintended knock-on impact.
  • [9:07-15:20]  a general discussion on performance issues that are most often tied to Linden Water, and suggestions on how it might be dealt with.  This largely matches the discussion summarised in my previous CCUG summary. These again included the idea of an update to prevent the viewer attempting to draw the Linden Water plane when above a certain altitude (and the majority of users cannot see it when at that altitude or above), or f having a UUID that can be set via the environment controls that effectively stops Linden Water Rendering when applied. Again, these are just *suggestions*, not things that have / are / will be implemented.
  • [21:12-23:12] OpenGL replacement: LL are not considering “seriously starting” on any OpenGL replacement work within the viewer until they have reasonable confidence the worst of the EEP bugs have been dealt with, simply because this is consuming the majority of the rendering team’s bandwidth.
    • Currently efforts are focused on gathering data on people’s systems – how they are running in terms of graphics options, what they are capable of running allowing for their GPU., etc., in order to hep the Lab better define parameters they need to consider. The code for this is in the current release viewer, and is propagating to TPVs as they merge and release that code.
    • One problem is that there are users who have hardware capable of running Vulkan, but they’ve not updated their Windows OS to a version that can support it.
  • [32:08-33:03] Viewer stats: by log-in session, the official viewer currently has a average of around 76% of sessions using Windows 10 64-bit; 15% using OS X, and the rest split between other Windows + Linux flavours. In terms of average users, Firestorm believe that have around 6% of users on OS X, perhaps 2% using various Linux flavours and the rest on various versions of Windows (32-bit and 64-bit).