The Open Source User Group (OSUG) meeting is an open discussion of Second Life development, including but not limited to open source contributions, third-party viewer development and policy, and current open source programmes.
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.
Seamless integration of IM histories between clients / devices.
Support for the new Group Role activity to set who can post URL links to Group chats.
This is set to allow ALL roles by default, but can be toggled for specific roles by Group Owners / Officers.
Includes a preset whitelist of LL / SL URLs which can be posted.
This whitelist may be expanded in the future.
Camera and Travel improvements.
Create an account from within the viewer.
LEAP Camera API.
Portable viewer storage.
And more.
Viewer Notes
A new 26.5.1 Maintenance viewer is in development. This will include a fix in metrics reporting that will enable LL to get a higher quality view of stability, plus numerous bug fixes.
Third-Party Viewer Policy and Directory – Potential Update and Discussions
In light of the sudden rise of various third party viewers … we’re considering a change to our TPVD policy that effectively shuts the door on closed source TPVs entering into the directory. Existing closed source viewers that are in the directory will likely get grandfathered. No final decision has been made on this policy change. To be clear this does not stop you from asking an LLM to make you a viewer, but it would require you to make said viewer open source in order for us to consider it for inclusion in the directory.
– Geenz Linden
This announcement was largely received positively by those at the meeting.
Such a change would not prevent new close-sourced viewers being used with SL, but it would deny them a voluntary listing in the Third-Party Viewer Directory.
Geenz additionally indicated that consideration is also being given to:
Potentially pruning those viewers / clients which are badly out-of-date with SL’s more recent protocol and server features.
Various measures to better inform residents about the overall safety of viewers and the like. This is unlikely to expand LL’s overall vetting process, but Geenz hopes to have more on this once internal discussions are further along.
Requests were made for LL to better define “safe” viewers and protecting user accounts, clarification on what being listed / not being listed on the Third-Party Viewer Directory (TPVD) means for the lay user, etc. In respect of the TPVD, Geenz reiterated LL’s long-standing official standpoint:
We’ve always noted that being on the TPVD is optional, and further that we don’t vouch for the security or stability of those viewers. That will still remain the case. Just that those TPVs are in some manner of “good standing” – in other words, we haven’t seen any red flags, no one’s given us any heads up about them that checked out, etc. That list is we did some basic vetting, we did some research, checked against our policies, and it checked out.
I won’t list every consideration, but some examples: Does this viewer adhere to Second Life’s permission system? Is it appropriately licensed? What kind of track record do the authors have? Is the commit history publicly available, and can we audit it? We consider many things for overall TPVD inclusion and compliance. For example, if you’re collecting user data – you’re probably not gonna get a lot of fans. We have had to pull the “shared experience” rule every now and then as well – which doesn’t mean make your viewer look exactly like the official viewer, but at least don’t break content.
– Geenz Linden
Code review on TPVs came up – but this is a matter of resources and time; viewer code is extensive, and trying to run through it all for every viewer is not practical. In response to the idea of using AI assistance, Geenz (wryly?) noted this would come down to token spend and goal.
Most of the meeting revolved around these subject and on the use and capabilities of AI tools in general, with the core of Gennz’s responses from the Lab’s point of view as give above (there were also some referrals to other user group meetings which might be better placed to answer non-viewer / open-source questions).
There were also various observations on the recent region crossing updates.
Please refer to the video below for these latter points.
The Simulator User Group meeting place at Longfellow
The following notes were taken from the Tuesday, November 10, 2026 Simulator User Group (SUG) meeting. These notes form a summary of the items discussed, and are not intended to be a full transcript. A video of the meeting by Pantera is embedded at the end of this summary – my thanks to her 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 “Leviathan Office 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
On Tuesday, November 10, the Olive simulator update was be deployed to the SLS Main channel, making it grid-wide. This update includes:
Pepper Linden’s region crossing code improvements for vehicles – feedback on experiences with the new code is requested here. He also indicated more work is to come on crossings.
The new Group Role ability to define who in a Group can post URL links to Group Chats (requires viewer support).
Support for the feature flag required by viewers to be able to safely send the GameControlData UDP message for the new Game_Control capability. Currently, the upcoming viewer 26.5, (in RC/beta at the time of writing), supports Game_Control capabilities, the sending of GameControlData currently must be enabled via Preferences. This will change as Olive moves to being grid-wide.
Wednesday November 11 should see the RC channels restarted without any updates. The Lua channel servers will also be updating – but this will not be the update with the changes that will case script breakages.
The (theoretically final) simulator update for 2026 – codenamed Plum – is currently in development.
This will include a crash fix for a rare simulator crash, and Rider Linden is hoping to get the restrictions lifted in on accept and content types for HTTP, with Rider noting there will be constants that let you indicate that the payloads (the body of the request or response in an http call) should be treated as base64 encoded so they can be brought in and out of scripts, which he hopes to include.
Leviathan Linden also indicated a number of further crash fixes lined-up for Plum, including one for a big memory leak.
General Team Updates
Leviathan Linden has been working on simulator crash fixes per above, and also “on some things to try to help game-control viewer get out”, although he also indicated he fell down a few rabbit holes on this and got side-tracked as a result.
Roxie Linden indicated there:
Are a few stability fixes going into the voice server which, once implemented, with result in fewer viewer service restarts.
Has been “good progress” in evaluating transcription technologies, and LL is now looking into what it would look like as far as where it is deployed, how it can be used, etc.
When asked why transcription isn’t simply viewer / client-side, Roxie noted that there are some security implications, and LL do not want people using their transcription mechanism for non-Second Life purposes, etc. Also, performance can be better optimised if transcription / translation is on the server.
Later in the meeting, the question of Voice instability at distances from the speaker was raised. While it is hoped the stability improvements mentioned above might fix this issue, but a bug report was requested on the issue.
Also later in the meeting, Roxie indicated she would like to add more control over attenuation (distance, drop-off, etc.) as well as effects like reverb, echo, EQ, etc; however, it is a matter of getting that work scheduled and designed.
Pepper Linden has been working to fix a grief mode related to conference chats. This is currently in QA and they are hopeful the fix will be in the Plum simulator update.
Kyle Linden reiterated his new from the week #45 CCUG that the SL Wiki update is complete, bringing a new default theme, more moderation tools and brings it one stop closer to re-opening contributor access to all registered SL accounts – those who have already volunteered to help moderate should keep an eye out for further communications about helping.
A page from the SL wiki showing the updated theme / layout
Harold Linden (Lua):
Noted that good progress is being made on the Lua front and thanked all those who have submitted bug reports and contributions.
Indicated that some of the performance analysis pieces which need to be in place before upgrading the SLua VM are in the works by other teams within LL.
The above are what is holding-up the deployment of the Lua updates liable to cause script breakages. As such, this update might surface prior to Christmas 2026 or in early 2027.
Overall, if things continue on track grid-wide deployment of Lua should be some time in the first quarter of 2027.
Documentation for Lua now forms part of the SL Wiki work.
General Discussion
A discussion on extending PRIM_POINT_LIGHT radius in llSetPrimitiveParams(), pre this Feature Request, which was seen as relatively easy to do from a simulator point-of-view but a) would require viewer work; b) is more a question for either the Content Creation User Group or the Open source Development Group meeting.
Further discussion on Lua testing (which should be more informative when the “breakage” update has been deployed), and on documentation.
It was asked when “Combat 2.1” might start as a project – whilst Rider linden would like to get back to the Combat system work as he ideas for friend fire, teams, better respawning, etc., it need time to be allocated as an actual project.
A user discussion on allowing land to be “vertically parcelled” (so to speak) to allow apartment building in which people can have their own privacy, steaming etc. Something that sounds easy to express but much harder to implement.
More mention of the emerging vibe-coded viewers starting to appear (Geenz indicated that LL is reviewing its TPV policy requirement in light of these).
A passing discussion on “void” regions: essentially temporary water region which would spin-up and allow air / water crossing between areas of SL not actually connected by any form of region bridge. Currently, there are no plans to implement this idea.
Logos representative only and should not be seen as an endorsement / preference / recommendation
Updates for the week through to Sunday, November 8, 2026
A summary, generally published every Monday, of SL viewer / client releases (official and TPV as listed in the Third-Party Viewer Directory) made during the previous week. When reading it, please note:
It is based on my Current Viewer Releases Page, a list of all Second Life viewers and clients that are in popular use (and of which I am aware), and which are recognised as adhering to the TPV Policy.
This page includes comprehensive links to download pages, blog notes, release notes, etc., as well as links to any / all reviews of specific viewers / clients made within this blog.
By its nature, this summary presented here will always be in arrears, please refer to the Current Viewer Release Page for more up-to-date information.
Outside of the Official viewer, and as a rule, alpha / beta / nightly or release candidate viewer builds are not included; although on occasions, exceptions might be made.
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, in a mix of Voice and text chat.
Seamless integration of IM histories between clients / devices.
Camera and Travel improvements.
Create an account from within the viewer.
LEAP Camera API.
Portable viewer storage.
And more.
General Viewer Notes
There are further fixes inbound for the 26.5 Chat Modernisation viewer, so a updating should be surfacing in the next week, with the focus remaining on getting this promoted up to release status ASAP.
Gneez indicated LL might try to get a Maintenance viewer out before the end of 2026.
Graphics Care Package (GCP) viewer: discussions continue on where in the queue this sits, but still looks to be no earlier than 2027 Quarter 1 (January-March time).
Specular maps are in with GCP, as is IoR; however, Geenz is still working on glTF transmission.
Geenz also indicated that in the wake of the rising number on vibe-coded / AI-assisted viewers, the Lab is reviewing its third-party viewer policy. more information on this might be available at the next Open Source User Group meeting on Friday, November 13 at 13:00 SLT.
SL Wiki News
The SL Wiki update has completed. This brings a new default theme, more moderation tools and brings it one stop closer to re-opening contributor access to all registered SL accounts.
Those who have already volunteered to help moderate please keep an eye out for further communications about helping.
While not the main reason for the update the wiki now supports SVG as well.
A page from the SL wiki showing the updated theme / layout
General Discussions
There was an aggressive exchange on the use of LLMs, vibe / Claude coding, etc., within both client-side viewer and on the back-end.
Geenz has put together the LSL definitions for scripts on the new EEP parameters. These are undergoing internal testing, and he hopes that when ready, he’ll be able to establish a test region on Aditi (the Beta grid) for broader testing.
A general to-and-fro on custom rigs (for the future) blend shapes (ideas for this, but nothing ready for showing) – all of a similar nature to discussions in past CCUG meetings. On this, Geenz noted:
We still need to figure out what needs doing on the server – of course we’d like to have blendshape parameters scriptable and such. And then there’d be mapping to the system blendshapes. So there’s a bit of a list of things we’re eyeing up.
The above drifted into recollections of the now dormant / deceased Puppetry Project and what it did / did not have – with a note from Geenz that insofar as IK (Inverse Kinematics) are concerned – these will be required for LL to get animation retargeting working with custom skeletons.
It was asked if there would ever be support for support additional/custom material shaders such as pearlescent and clearcoat. Geenz sees this being possible through the GCP viewer, through specular maps and IOR.
The above sparkled a discussion of other possible additions to PBR – or at least, “nice to haves”, e.g. iridescence and displacement maps; Geenz noted that whilst some are under consideration, every new addition adds time to the Vulkan port.
Geenz has been working “on the side” on some automatic LOD experiments for mesh uploads. He is ruminating on getting this work wired up into the mesh importer sometime in the coming releases to allow for testing.
This work has notably involved poking at existing and fit-for-purpose LOD generators in games supporting user-generated content (UGC).
The aim is to allow people to provide their own LODs if they wish, whilst also having the means to generate meaning LODs automatically more easily without having to use LL’s current “hopelessly terrible LOD generator”.
This new approach will initially be at upload, with Geenz noting,/a>:
I do want to eventually have all objects be subject to auto LOD past a certain point, but that’d need to be after we ship mesh modernization or potentially with it.
The following notes cover the key points from the Web User Group (WUG) meeting, held on Wednesday November 4, 2026. These notes form a summary of the items discussed and is not intended to be a full transcript. Pantera’s video is embedded at the end of this article, my thanks to her for providing it.
Meeting Overview
The Web User Group exists to provide an opportunity for discussion on Second Life web properties and their related functionalities / features. This includes, but is not limited to: the Marketplace, pages surfaced through the secondlife.com dashboard; the available portals (land, support, etc), and the forums.
Meetings are open to anyone with a concern / interest in the above topics, and form one of a series of regular / semi-regular User Group meetings conducted by Linden Lab.
Dates and times of all current meetings can be found on the Second Life Public Calendar, and descriptions of meetings are defined on the SL wiki.
maps.secondlife.com now supports searching by region name, and across all maturity ratings. Just enter a region name in the search bar.
The caps API issue reported in my simulator user group update is known, and it is hoped this will have a fix in place in the coming week.
This was apparently part of the fall-out from the Internet P2PShell vulnerability at the end of October.
A problem here is whilst LL own the domain and the map service, some of the API are provided by third-parties and not directly under LL’s control. Further investigations are going on to see if these APIs can be handled in a more protected manner, or whether there needs to be some form of migration away from them to an alternate solution.
A fix has gone in to hopefully resolve the issue of some snapshots failing to upload (to the SL feeds?). This is being monitored.
Continued under-the-hood (i.e. non-user-visible) refactoring and clean up of the Marketplace. This should result in:
Better visibility for the team when things fail, for fixing response / fixing.
Better performance around automated jobs (PLEs, redeliveries, etc).
Multiple security patches and cleaning-up to better deal with attempted AI generated exploits.
Once aspect of the security work LL has been implementing throughout 2026 meant that when the P2PShell vulnerability surfaced, they were well placed to deal with it, and none of the SL services had to be taken down in order to avoid exposure, etc.
Question form LL: how do creator merchants on the MP go about making images for their listings (thought processing, editing, , what is included, tools used, etc.).
General response:
Many simply use the ad image they use in their in-world vendors + supporting images.
The preferred tools were given as PhotoShop and GIMP for editing.
Requests were made for:
Actually embedding videos of products, rather than just linking to them – this appeared to be misunderstood, as a mitigating factor raised was that of “hosting” videos by LL – while what was being asked for was embedding of You Tube, etc., videos (which is still complex, but does not require storage on LL’s part).
An ability to zoom / enlarge images.
An agreed aspect ratio / format for images.
Whilst somewhat separate in terms of responsibility: a better choice of aspect ratios for Inventory thumbnails rather than just 1:1 square, as many creators use the same image for both thumbnails and MP, and so feel limited.
It was noted that support for GIF images is being looked at.
Juniper also enquired whether creators would consider having a 3D preview option for their products (e.g. as with Turbosquid or the SL mesh upload preview tool) would be useful.
This received generally favourable responses.
However, the idea of only allowing 3D previews of products was not so positively received (do HUDs benefit from a 3D preview? do texture images – such as art pieces – benefit?); what about resellers who do not have access to the original asset? What would they display?
Overall the feeling was that a 3D preview would be a powerful addition to the MP, but it should not exclude the use of 2D images, with the request being made for any 3D preview to include a wireframe view option as well, and something like a “data sheet” listing things like LOD models, Land Impact, etc., so that users who wish to can made more informed decisions on purchases.
Some of this conversation got into the weeds, technically, on how best to handle things.
Later in the meeting the request was made that – if a 3D preview option is to be provided – LL look at also providing an animation preview capability.
Juniper emphasised the idea of a 3D preview was more for feedback purposes at this point than something actively being implemented, with the internal focus at the Lab being brainstorming how to make MP listings “better”.
These topics were raised during or immediately following as a part of the above.
Variants and Styles: the ability for creators to have a single listing for all colour / size variants of the same item, rather than having to list them all individually.
The idea of “Styles” or “Variants” – both terms have been used by LL for this – has been a long-running topic, and in 2021/2 a project was initiated to provide this, and by late 2022 it was indicated it could be deployed in 2023. Since then, it has emerged that the capability is not ready for deployment, and has consistently slipped down the list of priorities at LL.
Juniper commented on the Variants situation as:
Variants is a big push we would like to do that of course, and part of our marketplace clean up is so we can work this bit by bit if we can.
The request was made to at least allow a means for creators to somehow group versions of an item together beyond just related photos.
Marketplace Categories: a further request was made for the Marketplace categories to be overhauled (e.g. “hair” being classified as an “accessory” rather than a “body part”).
It was also asked way Categories appear to the left of non-listing pages and as a drop-down selection in the page header area (where it also appears on listing pages). However, the latter is intended for searches and does not have the same granularity as the Category list in terms of sub-lists of items.
It was suggested that rather than having hierarchical/static categories, the MP should have a more filter-like approach (as seen within other on-line marketplaces), allowing returns based on multiple selections (and which can be used with search terms as well) – as with the filtering on Inventory.
Juniper noted that right now, there is an internal exercise going on to consider how categories might be improved.
“Thank You” page and links: Following a purchase, the Marketplace displays a “thank You” page, which has hints and tips for shopping which, most notably:
There is a link “How to Collect your Purchase” – which actually goes to a video covering purchasing L$, using the Marketplace, buying in-world etc., with only a small portion on how to find MP purchases in inventory. Given that people will have already gone through buying L$ and purchasing things from the MP – why not just have a clear, simple instruction directing people to look for their purchase in the Received Items area / folder of their viewer’s inventory?
Whilst there is a link to return to the MP homepage, it is buried among other links – surely it should be promoted so as to be more obvious?
More general:
Juniper noted that work is going on to make redeliveries more robust. It was noted that the ability for creators to have their own items redelivered through the listing management pages appears broken for some.
The view was again expressed that there are too many clicks required for a creator to get to their listings (currently: Creator name > My Marketplace > Merchant Home > Manage Listings – why not have Manage Listings under My Marketplace?).
Requests was made for creators to be able to:
Set an item as a Featured Item in their own Marketplace store.
Have in-world store Groups to be linked to the creator’s Marketplace, so that Group members shopping at the MP get a discount.
Various suggestions were made for LL to host “curated” limited-time sales events on the MO. For example: an invitation for creators to register for participation in periodic Marketplace Sales events (aligned with Shop and Hop?), limited to so many creators. Those who are successful have their item(s) listed a specific set of MP “Sale” pages generated by LL, with items automatically returning to their “pre-sale” price at the end of the event. Those successfully participating in one event are automatically excluded from the next.
Having a creator set their entire store as having a sale was seen as a potentially easier option to provide than this particular idea.
A request for a store’s banner logo to appear on all associated listing pages, not just the store page, rather than the small square logo to the right.
In Brief
[Video: 47:04-55:25] The question on what information – such as Map-related data for use in terrain maps, etc., – is permissible for collection & how it might be collected was again asked.
This is a question which has been subject to a game of pass the parcel around the various user groups.
The concern is that it is not clear as to what is / is not permissible to be collected via bot, and the potential for bot systems to be banned (a-la Bonniebots)
Ideally, having a dedicated API to furnish “allowable” region information such as terrain information (elevation, etc.), water height, region name, height of structures, etc., would be the preferred solution.
It was again noted that not all of the API LL uses are under their direct control – although this might be changing in some way. As such, Juniper offered to take the request back to the office to try to have it discussed with all relevant parties and in line with whatever is trying to be achieved with API management in general.
The Simulator User Group meeting place at Longfellow
Updated November 4: information on the cause & a fix for the maps.scondelife.com issue – see General Discussion, below (update highlighted).
The following notes were taken from the Tuesday, November 3, 2026 Leviathan Office Hour, the “off-week” sessions of the Simulator User Group (SUG) meeting. These notes form a summary of the items discussed, and are not intended to be a full transcript. A video of the meeting by Pantera is embedded at the end of this summary – my thanks to her 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 “Leviathan Office 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
The SLS Main channel was restarted on November 3, 2026 with no deployment.
On Wednesday, November 4, 2026, the RC channels should all receive the latest version of the Olive simulator update, which had a limited deployment in week #44. This update includes:
Pepper Linden’s region crossing code improvements for vehicles – these can already be tested on Blake Sea, as the majority of those regions are already a part of the Breeze RC channel, and have been used for initial code testing).
The new Group Role ability to define who in a Group can post URL links to Group Chats. However, this will not be enabled until Olive has been fully deployed grid-wide. See below for more.
Support for the feature flag required by viewers to be able to safely send the GameControlData UDP message for the new Game_Control capability. Currently, the upcoming viewer 26.5, (in RC/beta at the time of writing), support Game_Control capabilities, the sending of GameControlData currently must be enabled via Preferences. This will change as Olive moves to being grid-wide.
There are at least three crash fixes lined up for the next server release (Plum). One of them corrects a memory leak problem before it gets to a crash; it is hoped this will reduce the number of restarts required over the holiday period.
It currently looks like back-end Lua support deployment may not now take place until 2027.
General Updates
Game_Control
Game_control is available with the official viewer 26.5, currently in RC / beta.
However, the current version of game_control requires a bug fix for some 3Dconnexion devices (aka SpaceNavigator style devices). In short, any device that does not supply a “3DConnexion model-name” string on initial device detection fails to be identified. However, old devices do work.
There is a fix for this issue, but it has yet to be merged into the current 26.5 viewer code, although it will be before release.
A pull request (PR) to support per-device curvature of axis input of the gamepads has been received, and this will likely be included as well.
Leviathan is also seeking further feedback on game_control before he gives it a “final polish”, although he admits he expects far more feedback to come once popular TPVs start incorporating the code.
General Discussion
Please refer to the video, below.
Leviathan is currently working on fixes for some issues with the Interest List (the logic that figures out what is in view and send objects updates).
This work actually started earlier in 2026 but other priorities pushed it to one side.
Leviathan hopes to get these fixes into the Plum simulator update.
In relation to the above: Pepper Linden developed a simulator test harness for use with AI agents, making it easy to launch multiple simulators and to automatically exercise and debug various scenarios/content..
This approach played a key role in allowing Pepper to develop their region crossing fixes in the Olive simulator update currently being deployed.
Leviathan similarly used the harness to poke at the Interest List issues and his memory leak bugs, specifically in dissecting ana analysing core dumps.
His use of Claude has led him to believe that tracking down, assessing and fixing causes of simulator crashes should be a lot faster in future.
A question was asked on the state of map.second.life.com, which current has issues (e.g. clicking on a location on the map fails to look up the region name because the endpoint it makes a request to returns “Invalid Capability ID”) . This is a question potentially better placed with the Web Team, given map.secondlife.com is a web property.
Update, November 4: a fix for this issue should be deployed in the coming week. This issue was apparently part of the fall-out from the Internet P2PShell vulnerability at the end of October.
A problem here is whilst LL own the domain and the map service, some of the API are provided by third-parties and not directly under LL’s control. Further investigations are going on to see if these APIs can be handled in a more protected manner, or whether there needs to be some form of migration away from them to an alternate solution.
There was a user-led discussion on media and media URLs being accessible by script around the half-way point in the meeting.
The latter half of the meeting focuses on both game_control, keyboard capture, key mapping, key events in the control event and requests for scripting additions – please refer to the latter half of the video for these.