2026 week #5: SL CCUG and Open Source (TPVD) meetings summary

Hippotropolis Campsite: venue for CCUG meetings
The following notes were taken from:

  • My chat log of the Content Creation User Group (CCUG) meeting of Thursday, January 29th, 2026 and my chat log of that meeting
  • Pantera’s video (embedded at the end of this article) and my chat log of the Open-Source Developer (OSD) meeting held on Friday, January 30th, 2026.
Table of Contents

Please note that this is not a full transcript of either meeting but a summary of key topics.

Meeting Purpose

  • The CCUG meeting is for discussion of work related to content creation in Second Life, including current and upcoming LL projects, and encompasses requests or comments from the community, together with related viewer development work.
    • This meeting is generally held on alternate Thursdays at Hippotropolis and is held in a mix of Voice and text chat.
  • The OSD meeting is a combining of the former Third Party Viewer Developer meeting and the Open Source Development meetings. It is open discussion of Second Life development, including but not limited to open source contributions, third-party viewer development and policy, and current open source programs.
    • This meeting is generally held twice a month on a Friday, at 13:00 SLT at the Hippotropolis Theatre and is generally text chat only.
  • Dates and times of meetings are recorded in the SL Public Calendar.

Official Viewer Status

  • Default viewer 2025.08 – 7.2.3.19375695301 – maintenance update with bug fixes and quality of life improvements – December 2 – No Change.
    • Notable addition: new VHACD-based convex decomposition library for mesh uploads.
  • Second Life Project Lua Editor Alpha version 7.2.3.19911032641, December 5 –  No Change.
  • Second Life Project Voice Moderation viewer 26.1.0.20139269477, December 12 – No Change.
    • Introduces the ability to moderate spatial voice chat in regions configured to use WebRTC voice.
  • Second Life Project One Click Install viewer 26.1.0.21295806042, January 26, 2026 – one-click viewer installation.

Upcoming Viewers

Viewer 2026.01 – One-click Installer / Updater

  • Now available as an alpha viewer (above).
  • As the name suggests, triggers a one-click install / viewer update process.
  • Is still being worked on, with a focus on ironing out some kinks in the one click install, including an uninstaller for old non-velopack viewers that can be triggered when required, the usual registry stuff for Windows, and so on.
  • Also includes improved monitoring / logging of viewer freezes and crashes, etc.

Viewer 2026.02 – “Flat” UI, Font Changes

Example of the upcoming flat UI. Via: Geenz Linden / Github #4681/2
  • This viewer is to be part of the Lab’s “first impressions” push to make SL resonate more with incoming new users and hopefully encourage them to keep logging in.
  • Will include a new “flat” UI (as seen in the Project Zero (viewer in a browser) version) which comprises things like a font change, a colour scheme change,  and generally giving the viewer a more “modern” look and feel. This is not a major UI overhaul in terms of overall look and feel, more an aesthetic one.
  • Font changes within this viewer are currently described as “experimental”.
  • Also looking like it will include a log-in landing refresh.
Example of the upcoming flat UI. Via: Geenz Linden / Github #4681/2

General Viewer Notes

  • Work on clearing viewer bugs and implementing smaller feature requests into the viewer is continuing, so users can expect more of this, allowing for other priorities in viewer work.
  • On the viewer development side:
    • There should be some vcpkg movement in the near future. A Pull Request for this work via a third-party developer is apparently in progress, but will not be shipped immediately on approval. Rather, it will be allowed “soak time” so other developers can assess impact on their build pipelines downstream and the like.
    • There will also be some CMake project changes, although these appear to be more of a “modernization” push, to bring CMake in the viewer into line current CMake project norms.
  • LL is contemplating bringing back viewer maintenance releases to try to encourage some TPVs to pick-up bug fixes and incorporate them faster into their viewers (rather than waiting for a major viewer update which includes bug fixes to get to release status and then merging them).
    • If this is done, the maintenance releases will be “much smaller in scope” than past maintenance updates (so a kind of taking bug fixes that are flowing into upcoming major viewer releases, cherry picking them and then QA’ing and releasing them as a small update to the viewer.
    • Those TPVs at the meeting indicated this could either add to their workload or that they would not alter their existing workflow due to overheads, but instead will continue to cherry-pick upstream fixes as a part of their own release cycles.
  • In response to questions on whether Kitty Barnett’s RLVa code contributions will be included in the official viewer (and which are currently pending fixes she has submitted for RLVa avatar appearance fixes anyway), Geenz Linden stated:
If we did, it’d likely be a very progressive and targeted thing that we do. And hopefully not in a way that significantly makes downstream more difficult to maintain. It’s a longer discussion that needs to be had basically. 
    • This led to concerns that LL could end up implementing a variant of  RLVa that is at odds with the current RLV/RLVa API, and effectively end up being ignored for being incompatible. In response, Geenz further noted:
I’d prefer one that everyone can participate in if we do go that route so we can be more targeted with others helping to guide that. Last thing we want to do is make it take 7 months to ship a TPV just because we made a change to RLVa. We also have to consider overall content compatibility and such.
  • Also as per the last meeting, official Linux support is aligned with the in-progress SLua viewer .

“First Impressions” Context

  • This work is focused on trying to ease that first experience for a lot of new residents to try and drive up retention numbers.
  • The work is seen more-or-less as experimentation at this point in time, but the goal is to drive up first day engagement among incoming new users to encourage them to continue to log-in to SL.
  • Work on this is on multiple fronts, and more will be shared on it in due course.

Grid-Wide WebRTC Deployment

  • The Lab is currently looking at a March deployment of WebRTC voice across the grid, but this is subject to possible change.
  • The viewer server is currently in a beta soak test (see: WebRTC Voice Open Beta is Expanding).
  • The last major server crash has been fixed, and there have been none since that fix went in.
  • There is an upcoming fix – see Pull Request #5322  (included in viewer 2026.01) – to address some of the issues with voice dropping. The recommendation is for TPVs to get this into their viewers for a good user experience.
  • An upcoming server-side update will hopefully address some of the issues with WebRTC spatialisation (e.g. voice volume varying greatly with even small camera position movements on the part of a listener).
  • Additional connection tweaks for WebRTC have been made to the 2026.01 viewer to help improve voice performance (e.g. to improve auto-reconnect).
  • Feedback on people’s experiences with WebRTC is still being sought (notably via the beta testing).

SLua Update

  • An update to the SLua project viewer is forthcoming.
  • As noted above, this will bring with it support for Linux
  • Still no confirmation as to when SLua will go live across SL

General Discussion

OSD Meeting

  • SSR and PBR water real time reflections and shadows: Geenz indicated that work is progressing on this and that when available, it will be given “a proper” alpha/beta/Release Candidate process.

  • The was noted that whilst improvements on SSR and PBR water reflections are being made, they will never 100% match pre-PBR views without a lot of work being put into optimisation, what would likely still result in mixed feedback without any significant win.
  • This led to a general discussion on addressing water reflections and shadows.

CCUG Meeting

  • PBR lighting: still on the list of potential updates, but requires “quite a few” server-side changes in order for it to happen.
    • The existing SL lighting system has a range of constraints dating back 20+ years, and so would require significant modification in order to enable PBR lighting support.
    • As such, this is currently viewed as being on the back burner for the foreseeable future, while other things are worked on.
  • A question was asked on whether it would be possible for an Animesh using only ten bones in total to have a lower Land Impact / rendering cost than one rigged to 10 out of the 110 bones of the default skeleton. Short answer: no, not without custom rigs.
  • Custom rigs themselves are acknowledged as something SL should have, but the work involved in enabling them is extensive and touches on multiple areas (e.g. re-targeting bones for clothing fits; re-targeting animations – and even a couple overhaul of the animation system -, etc.). There is also work to be carried out elsewhere that would yield benefits for things like quality of life which are of a higher priority. As such, custom rigs are not something currently on the roadmap.
  • In-world mesh creation tools: unlikely to be a thing, as the implementation would be costly in time and effort, and likely would not measure up to the capabilities of external tools like Blender.
  • It was asked if the import route for rigged meshes could be “streamlined” without the need for AvatarStar / MayaStar. Neither of these tool are actually a requirement for rigged mesh import / export, rather they are tools that can help with the process of rigging from within SL. Meshes that have been correctly rigged and weighted using external tools should import correctly through the current import mechanisms (COLLADA or glTF).
  • Overhauling the mesh import file format  / process through the support of something like OpenUSD is an idea that is being mulled over within the Lab. However, a) this is not something that is likely to be prioritised in the next 12 months; b) it is something that would require a lot more in the way of discussion before moving towards it; c) there is still work to be done in improving the import / export of currently supported formats before trying to add to them / replace them.
  • Materials import for meshes: this is something the Lab wanted to implement for glTF mesh import (rather than having to import materials separately).
    • However, due to the way in which asset uploads to SL work, it proved to be more a complex issue than first thought.
    • The hope is that the work can be returned to in the future, possibly using a new import flow that is more in line with other platforms and tools, but this is not something on the current roadmap.
  • PBR specular support: this is still something Geenz would personally like to get done, but it is currently sitting behind various other items which need to be completed / implemented in order to clear time for working on it. Also, this work does have impacts on things like the glTF upload validator, scripting, simulator support, managing glTF overrides (which are currently not well handled) etc., all of which would have to be factored into the work and which are outside of Geenz’s immediate responsibilities.
  • In terms of extending glTF support in general (PBR specular, IoR, etc.), the preference at the moment is to fix more of the existing issues / bugs within the existing PBR capabilities before adding further options.
  • The meeting was somewhat sidetracked by talk on the use of bots, ToS bot violations, Tiny Empires, etc., the majority of which are more of a Governance issue.

Next Meetings

2026 week #3: SL CCUG and Open Source (TPVD) meetings summary

Hippotropolis Campsite: venue for CCUG meetings
The following notes were taken from:

  • My chat log of the Content Creation User Group (CCUG) meeting of Thursday, January 15th, 2026 and my chat log of that meeting
  • Pantera’s video (embedded at the end of this article) and my chat log of the Open-Source Developer meeting held on Friday, January 16th, 2026.
Table of Contents

Please note that this is not a full transcript of either meeting but a summary of key topics.

Meeting Purpose

  • The CCUG meeting is for discussion of work related to content creation in Second Life, including current and upcoming LL projects, and encompasses requests or comments from the community, together with related viewer development work.
    • This meeting is generally held on alternate Thursdays at Hippotropolis and is held in a mix of Voice and text chat.
  • The OSUG meeting is a combining of the former Third Party Viewer Developer meeting and the Open Source Development meetings. It is open discussion of Second Life development, including but not limited to open source contributions, third-party viewer development and policy, and current open source programs.
    • This meeting is generally held twice a month on a Friday, at 13:00 SLT at the Hippotropolis Theatre and is generally text chat only.
  • Dates and times of meetings are recorded in the SL Public Calendar.

Official Viewer Status

  • Default viewer 2025.08 – 7.2.3.19375695301 – maintenance update with bug fixes and quality of life improvements – December 2 – No Change.
    • Notable addition: new VHACD-based convex decomposition library for mesh uploads.
  • Second Life Project Lua Editor Alpha version 7.2.3.19911032641, December 5 –  No Change.
  • Second Life Project Voice Moderation viewer 26.1.0.20139269477, December 12 – No Change.
    • Introduces the ability to moderate spatial voice chat in regions configured to use webRTC voice.

Upcoming Viewers

Viewer 2026.01 – One-click Installer / Updater

Viewer 2026.01 is in progress. This will include:

  • Improved bugsplat support (we want better reporting for freezes, and just generally better crash reporting). This work builds on the successes of 2025 in detailing with viewer crashes and reducing overall causes for crashes.
  • A new one-click installer, which in brief:
    • Will be powered by a new dependency called velopack, and will allow a single-click installation of the viewer (with a brief pop-up message), with the viewer launching once the install process is complete.
    • Will default to installing under Apps/Local on windows; will remain as a drag-and-drop process on Mac OS, while Linux is currently TBD. It will still be possible to install the viewer to a custom location, initially via a command line argument.
    • Will not change the install location of config files, or anything that counts as user data.
  • Development work on this did hit a delay, which has now been cleared, the hope remaining to get an Alpha (previously known as Project) viewer out with the update code in place sooner rather than later.
  • As an added benefit to the switch to velopack for TPVs, LL will be providing a solution to add auto-update functionality to TPV projects, if TPVs wish to leverage it. More information on this is due to be made available in the next week or so.

Viewer 2026.02 – “Flat” UI, Font Changes

  • This viewer is to be part of the Lab’s “first impressions” push to make SL resonate more with incoming new users and hopefully encourage them to keep logging in.
  • This first impression work is on multiple fronts, and for the 2026.02 viewer will be a switch to the “flat” UI seen in the Project Zero (viewer in a browser) version which comprises things like a font change, a colour scheme change,  and generally giving the viewer a more “modern” look and feel.
  • The font update:
      • Should not impact people’s use of unicode.
    • Will require XUI updates which will likely require updates for TPVs using their own custom XUI – TPVs are advised to keep an eye on Discord and Github for more information on these changes as they develop, and to particularly track this github issue.

General Viewer Notes

  • Linux support will likely ship as a part of the in-progress SLua beta viewer.
  • The viewer development roadmap is still being worked on in terms of fixes and updates and actioning feature requests, the focus being to work these into the viewer without disrupting major initiatives the Lab is looking to develop (such as the “first impressions” drive).
  • 2026.02 might include some screen space reflections (SSR) updates to help improve the appearance of Linden Water under PDR/HDR.
  • The avatar appearance fixes contributed by Kitty Barnett and intended to make the current outfit folder more reliable when changing outfits, messing with outfits, etc., may get to see the light of day in viewer 2026.03 – but this had yet to be confirmed.

Grid-Wide WebRTC Deployment – Initial Announcement (OSD Meeting)

  • The Lab is currently looking at a March deployment of WebRTC voice across the grid.
  • The schedule is not firmly set as yet, but will follow the usual server-side deployment routine: first to one (or more) simulator RC channels, then to all simulator RC channels (if not all rolled at once), and then a week after this, deployment to the Main simulator channel.
  • The important point in this is that once grid-wide, WebRTC will completely supplant Vivox Voice, and those who use Voice by who are not running a WebRTC voice capable viewer (which generally means anyone not on a non-PBR supporting viewer) will be unable to use Voice.
    • This does not mean that the Vivox service will be immediately shut-down. It will remain an option for the Lab to re-enable until such time as LL is confident in the WebRTC service and no surprises have come to light.
  • There is one remaining WebRTC critical issue in the viewer that makes the experience not great for a small body of users:
    • People with certain network characteristics may see a dropout because the WebRTC provider is not properly handling renegotiation.
    • LL has a fix which should be deployed with viewer 2026.01. However, TPVs wishing to merge it now can do so via Pull Request 5126.
  • In the meantime, the beta for WebRTC has expanded – see this official blog post for details.
  • Roxie Linden also indicated that LL is experimenting with speech-to-text using WebRTC, but does not as yet have anything available for public demonstrations.
  • The issue of Linux builds not using Pulseaudio but with the WebRTC code crashing on start-up was reiterated at the meeting. Whilst this might not be a widespread issue, the feeling was that it should be looked at; however, if the pool of impacted users is liable to be very small, it will not be seen as a reason to block / delay WebRTC deployment as a whole and any fix is liable to be prioritised in terms of resources / impact of the issue, post-deployment.

General Discussion – Both Meetings

  • Avatar support related:
    • Shape key support and / or custom bone hierarchies – seen as complex area of work, and not being looked at.
    • While the current avatar does technically use shape keys, it is very different to how modern blend shapes are used.
    • SL’s internal format also doesn’t store bones.
  • Questions were raised on the status of game_control. This is more a subject for the Simulator User Group meetings, where Leviathan Linden indicated he was trying to resume work on the code. However, it was also indicated during this meeting that Leviathan had again been “borrowed” to work on other code.
  • Despite rumour to the contrary, Puppetry is not currently set for revival or on the current 2026 roadmap.
  • Geenz noted that while work on things like new tools, updates to the GLTF uploader, etc., are not “done”, the focus for the time being in more on dealing with technical debt together with the aforementioned “first impressions” initiative, etc.
  • Questions were asked on auto / planar-aligning PBR materials  – see: Aligning Faces when using PBR and Planar face alignment with PBR GLTF materials. This is something the Lab has yet to resolve, and has offered a contribution bounty for any developer who is able to provide a solution. Geenz also indicated he would try to get bugs like this better prioritised.
  • A general discussion on ideas for improvements to chat, including: ability to have a “last unread” indicator in chat when logging-on; having the chat rings on the mini-Map on by default, some idea about a special chat tab that would allow region-wide chat (presumably at the region owner’s discretion to enable), ability to correct text in chat / IM after sending(!), etc.
  • The You Tube embedding issues was again raised (see here for more), with a possible (if hacky) workaround. LL are looking to You tube to address the problem, as they created it.
  • There was a general discussion on the complexities of Land Impact, particularly – but not restricted to – mesh objects. In short, LI is a complicated subject, and not easily addressed; hence why the Lab backed away from the subject recently. This also strayed into the equally complicated realm of LOD generation.
    • On the subject of LOD generation, it was suggested that the Lab should look to implement a LOD generator and then inform creators LODs have to be generated  to fit a defined set of criteria – or defaults will be forced.
  • A discussion on the choice of VHACD over HACD as a replacement for Havok in mesh decomposition. The latter is seen as more mature, but LL opted for VHACD is a “middle ground” solution as it is more regularly maintained, it is also apparently more reliable when dealing with the “weirder meshes” some SL creators produce, when compared to something like CoACD. However, Geenz indicated it would be “nice” to have “swappable”  convex decomposition solutions at runtime.
  • A further request for Error creating thumbnail” message on SL wiki, breaking images  to be addressed.

Next Meetings