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.
2026.02 remains the current Release Candidate viewer (next in line for promotion to release status).
This viewer will likely have a further RC update prior to any promotion. This update should result in much sharper text rendering within the UI.
Viewer 2026.03
LL are working on implementing “whatever performance wins that we can”.
This includes “batching” changes – that is, taking multiple objects within a scene and rendering them in a single pass, rather than multiple passes.
This work was initially undertaken for what is called the “simple draw pool”, which had batching logic added some time ago, but the work was never extended to the Blinn-Phong or PBR draw pools, and this is now being done.
The hope is that this change should help lower specification computers render scenes more comfortably.
General Viewer Notes
Work is currently stalled on the Graphics Care Package (GCP) viewer given the focus on performance improvements for 2026.03. However, work should resume on the graphic improvements and updates for this viewer soon.
Given the above, it is still anticipated that the Lua Editor viewer (which is currently available as a project viewer) will go to RC status and then release ahead of the GCP viewer.
WebRTC Deployment
The current deployment of WebRTC has hit a few bumps, but the Lab is hopefully the deployment will be completed in “the next two weeks”, and certainly before SL23B.
The lack of voice attenuation over distances less than 60 metres (allowing personal conversations to be heard over a large distance) will likely not be addressed prior to WebRTC deployment is complete, and will be looked at afterwards – although it was also noted that attenuation under WebRTC will be different to Vivox.
General Discussions
Question: will there will be further updates to Animesh, particularly with regards to having to click on them without having to put a transparent prim around them for interactions?
Short answer: the need to click is intentional, and currently, there is no work on Animesh any time soon.
Question: will the one-click installer process also be applied to alpha and beta/release candidate viewers, or will these have their own install options?
LL is looking at “future options to make opting-in to alphas and betas have a lot less friction”, but discussions a re ongoing and not ready to be announced.
Alpha and beta/release candidate viewers will retain their own cohorts within github, allowing people who opt to use them from the Alternate Viewers page to continue to be opted-in to updates to those viewers as they are made available.
The ability to select and download a viewer from the Alternate Viewers page will continue.
Aside from general text chat on matters such as Animesh (between users) and on Fantasy Faire, this was a quiet meeting, and as such was brought to a close after some 30 minutes.
On Tuesday April 21st, 2026, Linden Lab announced it is ending support for Project Zero, the viewer-in-a-browser application launched just 14 months ago, and which I was able to co-announce through this blog following a Zoom meeting between myself and Brad Oberwager and Philip Rosedale.
The project, which saw the viewer streamed to a person’s web browser from Amazon AWS servers remained in something of a beta state throughout its lifespan, initially overseen by Philip Rosedale and then (the now Lab-departed) Sntax Linden, with a dedicated User Group meeting being formed around it (although meetings ceased in the latter half of 2025). It also gained much interest among existing users, despite it being largely aimed at incoming new users, leaving access to it limited for established SL users.
The revised Avatar Picker for Project Zero saw the function moved out of the viewer window and displayed within the browser tab, leaving the viewer window unencumbered. This approach was ported to the SL Mobile App.
The project did see some interesting development – such as the updated Avatar Picker mechanism, which was also ported to the SL Mobile App, and at the time of its launch at the start of 2025 and through the initial six or so months of its development, there were plans to undertake a gradual rebuilding of the viewer UI as presented through a browser, using modern tools such as HTML5 and React. To further interest in streaming the viewer through a web browser, Linden Lab also worked with the Firestorm team to take a version of the latter’s viewer and present that as a streaming service as well – although this experiment was ultimately short-lived.
By September 2025, the Lab was indicating that between them, Project Zero (using the official viewer) and the SL Mobile App had lead to a “10x” increase in the numbers of people trying out Second Life when compared to the more traditional requirement to sign-up and then download the viewer (the latter having long been a break-point for sign-ups, with many would-be users turning away from the platform rather than downloading and installing the viewer on their computers). However, not long after this update, things began to go quiet on the Project Zero front.
As a part of the new user sign-up, those directed towards using Project Zero, rather than to having to download and install the viewer, were directed to a revised splash screen comprising a static backdrop and a “Polaroid snapshots” slide show whilst they were connected to a Project Zero streaming server
With the curtailment of the Project Zero User Group meetings and, later, the departure of Sntax Linden from Linden Lab, the Project as a whole seemed to go dark, with little in the way of direct news being given through any User Group meetings. As such, the announcement that the project is now being ended comes as both a surprise (given the enthusiasm for it evidenced by Linden Lab in 2025) and a non-surprise (lack of news / updates on the project through late 2025 and the start of 2026 suggesting it was perhaps withering on the vine).
The announcement blog post offers little in the way as to why Project Zero is being halted, other than the decision being based on both “feedback” and what the Lab has “learned” in running the project, and “insights gained from Project Zero will directly inform improvements” to both the Desktop viewer and the SL Mobile App. However, the beneficial nature of the project in circumventing the need to download and install the viewer is acknowledged.
As it stands, support for Project Zero will end on Friday, April 24th at 17:00 SLT.
Further:
If you have remaining paid time associated with Project Zero, you are encouraged to use it before the [project is shuttered – access allowing, given the potentially limited number of slots at any given time.
If you have any unused time on Project Zero after April 24th, please file a support ticket for a refund (which will be processed up to 30 days after the ticket is received).
Exactly “what’s next” isn’t actually indicated in the official blog post (despite the post’s title), other than
Note that the ending of Project Zero does not affect either the desktop viewer or the ongoing development on the SL Mobile App, which will “continue to operate as usual”.
The OSD meeting is a combining of the former Third Party Viewer Developer meeting and the Open Source Development meeting. 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.
More updates to be made to this prior to promotion.
LL is working through some font kerning problems that were seemingly made much more obvious with the new font choice.
It was also noticed that the official viewer has been rendering fonts ever so slightly different from FS – which kicked off the above investigation.
26.3.0 – Graphics Care Package
The is the viewer previously known as the SL Visual Polish (SLVP) viewer.
The performance tweak has been ported over, and the team is now looking at additional performance work.
Async inventory is being parted out into easier to review chunks.
LL is also looking at some CPU and GPU wins overall – Geenz Linden is working on getting texture batching working for the PBR and Blinn-Phong paths. There is potentially more work on these lines, and these will likely be incorporated prior to passing the viewer to QA.
Lua Viewer
The Lua Alpha update that it had been hoped would surface around the start of April is now being aimed for some time in week #17.
The current lean at the Lab is to move this viewer through to RC status and then release before the 26.3.0 GCP viewer, but no firm decision has been made.
Again, this viewer will also be the first new Linux release from LL.
As a reminder: LL have officially dropped “SLua” (“SL Lua”) and just going with “Lua”.
WebRTC Deployment
The WebRTC deployment is still underway. No firm end-date as yet, although it should now be across all simulator RC channels.
Anyone experiencing Voice issues with WebRTC is asked to file a bug report.
General Discussion
The vcpkg updates for the viewer build process will not be surfacing until “after Lua at the very least”.
Geenz estimates it will likely not emerge until late summer, due to dependencies on work being completed vis. KDU and the removal of the Havok sub-libraries from the viewer.
In terms of the latter: VHACD will replace the convex decomposition for mesh upload, and server-generated path-finding mesh will replace the Havok path-finding mesh loaded by the viewer for visualisation.
A major reason for removing the Havok sub-licences is the impact they have on TPVs, who have to go through the process of obtaining and signing sub-licence agreements via LL, which complicates the open-source environment.
In this respect, if LL had a truly open-source replacement for KDU on the graphics side, they would look to make similar moves there as well.
Physics shapes and why and what the viewer can do with them became a topic for conversation at around the half-way point in the meeting, and this continued for around 10 minutes.
During the above there was a general discussion on the mesh uploader and clarifying LOD numbers for those coming into mesh creation.
A request was made for TPVs to receive stats reports once more (use, crash rates, etc). Geenz noted in reply:
Some of that is a bit of a black box to us as far as your specific crash rates, as for viewer usage we’re bottlenecked by a single person is responsible for that so it doesn’t always get done. I’ve been hoping to get a more automatic solution for this for a while, but our metrics folks have been booked up with other things for a good bit now.
The question was asked about the possibility of viewer-side Lua for building custom UIs to replace some of the HUD systems people use, and whether work on this is still moving forward. Geenz repliedwith:
That’s been on the shelf for a while. Dunno if or when we’re gonna bring that one back – I think what we’d need to really look at bringing that back with a significant amount of interest is gonna be how people would want to use [it]. There’s a lot of criteria that goes into making product level decisions like that, and with the viewer side Lua stuff it was increasingly being looked at something for internal use than something like a content feature.
The question was asked if the puppetry project was once and for all “dead”, to which Genenz again replied:
Lots of things were learned from that project, but I wouldn’t say it’s dead necessarily. Just not a priority. There’s a lot of things that would need to happen for puppetry, and I think it’s really increasingly more of a “when we need <x> we’ll work on that part of it” sort of thing. Because like joint streaming is just generally kind of useful, but we don’t have an immediate need for it. But who knows – maybe some day. Hell, if there’s any interest in having a proper poser viewer-side that ticks all of the privacy and consent boxes that might be a potential path. But we’re nowhere near there yet.
Pususaari – Where spring feels gentle, February 2026 – blog post
The following notes were taken from the Tuesday, April 14th, 2026 Simulator User Group (SUG) meeting. These notes form a summary of the items discussed, and are not intended to be a full transcript. They were taken from the video recording by Pantera, embedded at the end of this summary – my thanks to Pantera for providing it.
Meeting Overview
The Simulator User Group (also referred to by its older name of Server User Group) exists to provide an opportunity for discussion about simulator technology, bugs, and feature ideas is held every other Tuesday at 12:00 noon, SLT (holidays, etc., allowing), per the Second Life Public Calendar.
The “SUG Leviathan Hour” meetings are held on the Tuesdays which do not have a formal SUG meeting, and are chaired by Leviathan Linden. They are more brainstorming / general discussion sessions.
Meetings are held in text in-world, at this location.
Simulator Deployments
No SLS Main channel deployments for the week, but the channel was restarted.
The WebRTC deployment will be expanded to Magnum, finally completing its deployment across all RC channels.
The next simulator update – Loganberry – will include (among other thinks) the performance improvement work Leviathan has been working on and the fix for avatars remaining a cloud Leviathan has also developed (which addresses causes of clouding on the simulator – viewer-side clouding is not touched).
In Brief
Leviathan Linden:
Has been ” removing use of Tilia (payments system) from our code.” Exactly what this means is unclear, given the use of the Tilia wallet and close ties between LL and Thunes, Tilla’s owners.
He has also spent a little bit of time trying to incorporate some suggested code changes for the game_controller code, as suggested by a user, but upon testing he found something isn’t working right, so some investigation is required.
Monty Linden has been working with the Firestorm team on some of the TeleportFinish failure modes. One set of fixes, involving viewers simply walking away from the HTTP connection, is getting improvements so one subset of viewer-side TP/RC issues will be improved.
Kyle Linden noted that the SL 26.2 Flat UI Beta (releasing soon) also has a viewer-side TP disconnect fix.
Harold Linden (SLua):
There are a number of crash fixes and minor correctness fixes out on the Aditi (the beta grid), which should be coming to the Lua region on the main grid “soonish”.
As Rider mentioned, the scripting language definitions are going to be accessible to the viewer now, so you can always pull down the correct type definitions for whatever region you’re currently on.
Harold is additionally generalising his work for making llSetPrimitiveParams less annoying to use. Essentially it’ll be a fluent API where you can batch up prim params commands as you would do currently, but you do it through function calls rather than manually adding a bunch of stuff to a list.
Kyle Linden indicated there will be a “big push” on Lua documentation in the upcoming week(s).
General Discussion
Please refer to the video below as well.
It has been again reported that large linksets of prims or meshes that have alpha scripting (LSL and / or Lua) against Blinn Phong materials (apparently PBR is reported as working as expected) for certain parts of that linkset are failing to change alpha state or are slow to change. Copies of suitable linksets / a formal bug report on this were requested.
This sparked something of a discussion on probable causes, length of time the bug has been around, means to repo, etc., running through the mid-point of the meeting through to pretty much the end.
A WebRTC question was asked: the current settings seem to be 60m range, no distance attenuation. Is that the only option available?
Response: there should be distance attenuation. The curve is different than Vivox, though. If you’re not experiencing any distance attenuation, bug fixes are required with more details so LL can try to replicate what you’re doing.
Date of Next Meetings
Leviathan Linden: Tuesday, April 21st 2026.
Formal SUG meeting: Tuesday, April 28th, 2026.
† The header images included in these summaries are not intended to represent anything discussed at the meetings; they are simply here to avoid a repeated image of a rooftop of people every week. They are taken from my list of region visits, with a link to the post for those interested.
The OSD meeting is a combining of the former Third Party Viewer Developer meeting and the Open Source Development meeting. 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.
This could be promoted as early as week #15, depending on how it performs (crash rates, etc.), over the next few days..
Other Viewers
2026.02 – “Flat” UI and Splash Screen Refresh – this is due to have an Alpha update issued on April 3rd.
The Lua Alpha viewer is also due to have an update issued on April 3rd.
Note, LL are now officially dropping “SLua” (“SL Lua”) and just going with “Lua”.
Example of the upcoming flat UI. Via: Geenz Linden / Github #4681/2
The viewer formerly known as the Second Life Visual Polish viewer (SLVP) is now known as the Second Life Second Life Graphics Care Package.
The hope is to get that into alpha soon – but only after we get the necessary server work done and get some regions up on ADITI.
WebRTC Deployment
The WebRTC deployment has hit a “hiccup”.
As a result the deployment has slowed, with WebRTC liable to remain only on the RC server channels (Le Tigre, BlueSteel, Magnum, etc.) and covering about14% of the Main grid until the problem is resolved.
Anyone experiencing Voice issues with WebRTC is asked to file a bug report.
General Discussion
There is an increasing issue of AI driven pull requests.
This appears to be a case of people trying to make claims via the bounty programme for code submissions without actually putting any effort into the work.
Commenting on the matter, Geenz Linden noted:
If you’re using LLMs to submit pull requests, that’s not an automatic no. However, blatantly vibe coded submissions, submissions that are effectively taking stuff from other viewers without any kind of attribution or permission and so on, and anything that just generally reads as super low effort just to claim a bounty is likely to be closed without comment in a worst case, or otherwise scrutinized in order to ascertain the individual’s understanding of what that code actually does vs. how much is just prompting to see if they can land something. We don’t want to shut down utilizing AI in people’s processes, but certain things are gonna get PRs shut down or scrutinized more heavily. So please keep this in mind.
This called into question the value of the bounty programme, with the fair point being made that TPV developers have spent years developing code for their viewers and submitting much of it to LL without any thought of reward other than improving people’s SL experience.
Geenz further noted the the bounty programme is due to get reviewed “sooner [rather]than later”, although it is likely “some form” of it will be kept, as it has also led to useful code contributions – such as those for getting the Linux viewer back into the frame (due to surface with the Lua viewer) and the viewer vcpkg work.
The suggestion was made that a contract programme – whereby an external coder is contracted to produce work – might be more beneficial than the current bounty programme. Again, this was pretty much the case for Linux and vcpkg.
A further suggestion was made to offer general bug / feature request bounties in L$ only – potentially making them less attractive to those trying to bend the system and earn US $ using AI LLMs.
The question was asked if Leviathan Linden’s work on server-viewer messaging would be surfacing in one (or an) Alpha viewer soon – the reply was that discussions on where and when to place this work are still ongoing, in order to ensure the viewer work and server work appear pretty much together.
Suzanna’s excellent write-up on the latest Lua release gained a further shout-out. On this (again):
This release will be deployed to Aditi (the Beta grid) first for testing.
It requires all Lua scripts to be recompiled in order to keep working.
Tis last 10 minutes of the meeting was spent discussion whether “SLua” should be retained as the name for the Lua project, or if “Lua” was better (certainly more widely recognised) given it is an implementation of Luau.
Stevie Basevi’s Sanctuary, February 2026 – blog post
The following notes were taken from the Tuesday, March 31st, 2026 Simulator User Group (SUG) meeting. These notes form a summary of the items discussed, and are not intended to be a full transcript. They were taken from the video recording by Pantera, embedded at the end of this summary – my thanks to Pantera for providing it.
Meeting Overview
The Simulator User Group (also referred to by its older name of Server User Group) exists to provide an opportunity for discussion about simulator technology, bugs, and feature ideas is held every other Tuesday at 12:00 noon, SLT (holidays, etc., allowing), per the Second Life Public Calendar.
The “SUG Leviathan Hour” meetings are held on the Tuesdays which do not have a formal SUG meeting, and are chaired by Leviathan Linden. They are more brainstorming / general discussion sessions.
Meetings are held in text in-world, at this location.
Simulator Deployments
No SLS Main channel deployments for the week, but the channel was restarted.
The WebRTC deployment will be expanded to all RC regions on Wednesday, April 1st, 2026.
The next simulator release – Loganberry (can’t we have version numbers as well, aspromised?) will be deployed to Aditi.
The new server-side Lua updates (which require all existing Lua scripts to be recompiled) has also been deployed to Aditi for testing. See this document for more on this release.
These updates might start appearing on the Agni (the Main grid) “in a week or two”, with the deployment likely be timed to coincide with the issuing of the latest SLua viewer RC, and will include some additional fixes as well.
In Brief
Leviathan Linden:
Is hoping to look into the issue where, on encountering something like a high step on stairway or a physical bench or some other form of “ledge” and stopping, the avatar will start to slide sideways rather than standing still at the foot of the offending object.
Leviathan also has work going into the loganberry release, including:
Fixes for bugs related to failed simstate saves and crashes on simulator shutdown.
The server-side workaround for mesh face count. This should fix most issues except the bug where, on connecting to a viewer the edited texture face on the mesh will revert to its previous setting.
An attempted fix for the bug where trying to rez an object on a mesh surface can result in a failure to rez message – although there are still situations where this might still fail.
A fix for the bug about multiple chat events for multiple overlapping listeners in a script.
Henri Beauchamp’s suggested ObjectUpdate data fix for avatars remaining as clouds. However, as there are multiple reasons why avatars might remain cloudy besides missing attachment ObjectUpdate data, this might not fix all avatar cloud situations.
An optimisation to make running idle scripts a little faster, which he describes as, “Probably not noticeable, but is measurable”.
In addition to all this, Leviathan has spent a small portion of his “free” time trying to figure out why the game-control viewer UI doesn’t show the device config options (inverting the axis, offset, etc), but couldn’t work out why. He hopes to take another swing at it when he has more “free” time available.
Harold Linden (SLua):
Has a number of fixes in the pipeline, including one that accidentally limited how large you could make the bytecode.
SLua *might* be deployed in time for SL23B, but no guarantees this will be the case.
Region crossings: Harold hopes to have some fixes for long-existing region crossing bugs (strictly for crashes that rendered scripts unrecoverable due to script state serialization issues) with collision handlers, since he thinks he’s found the root cause.
This is similar to a issue with sensors from “back in the day”, so he has extended that fix to cover region crossings.
This fix will not resolve other region crossing problems.
General Discussion
Please refer to the video below as well.
A further discussion on Linden Water having waves, as also raised at the CCUG meeting (and which will doubtless be raised at the upcoming OSD / TPVD meeting on April 3rd, since some people won’t accepts “not an easy thing to do” a a single meeting, and need to hear it multiple times from multiple meetings).
In this case, Leviathan Linden noted, “Simulating water waves, and transmitting the oscillating surface is tough”, with others noting it would be “super costly” in terms of rendering in the viewer.
A number of other feature requests / bug issues were raised for feedback / status updates:
Extend the 10m distance for llRezObject() and llRezAtRoot() – also seen as “easy to do”, and has garnered questions from within LL as to whether or not it is even relevant any more – but again, no time frame on possible implementation. This also sparked a discussion on object rezzing via scripts.
The last 15-20 minutes of he meeting involved a broad-ranging discussion on matters of scripted agents (bot), Tiny Empires. Please refer to the video for details.
Date of Next Meetings
Leviathan Linden: Tuesday, April 7th, 2026.
Formal SUG meeting: Tuesday, April 14th, 2026.
† The header images included in these summaries are not intended to represent anything discussed at the meetings; they are simply here to avoid a repeated image of a rooftop of people every week. They are taken from my list of region visits, with a link to the post for those interested.
