Space Sunday: Never Tell Me the Odds, Rosalind Franklin and a Health Update

Captured via a drone, NG-3’s Never Tell Me the Odds edges towards Blue Origin’s Landing Platform Vessel Jacklyn, April 19th, 2026. Credit: Blue Origin

Even as this article was being prepped, my eyes were glued to the screen watching the launch of Blue Origin’s NG-3 mission, the third flight of the company’s mighty New Glenn Heavy Lift Launch Vehicle (HLLV) and the first re-use of a New Glenn first stage – that of Never Tell Me the Odds, which was previously flown as a part of the NG-2 mission in November 2025.

NG-3 had originally been slated for the launch of Blue Origin’s Blue Moon lunar lander Pathfinder mission, which the company had originally targeted for a January / February 2026 launch. However, that mission will not now occur until mid-to-late 2026, so NG-3 was reassigned to a commercial launch, that of AST SpaceMobile’s BlueBird 7 cellular broadband satellite. Between NG-3 and the launch of Blue Moon Pathfinder, New Glenn will also serve as the launch vehicle to deliver 48 Amazon LEO (formerly Project Kuiper) to low Earth orbit as a part of Amazon’s LEO internet constellation.

An external camera on New Glenn looks down the length of the booster’s first stage towards Launch Complex SL-36, Cape Canaveral Space Force Station, 30 seconds after launch. Credit: Blue Origin

Both the NG-3 and NG-4 launches are cause of mixed emotions. In its own right, New Glenn is a remarkable vehicle, capable of delivering up to 45 tonnes to low Earth orbit with the first stage recovered – just five tonnes less than SpaceX’s Falcon Heavy with its three core elements recovered. As such, and given its recovery is  – broadly speaking – less complex than Falcon Heavy, it stands to make itself felt as a highly flexible launch platform capable of meeting both commercial and government launch requirements (as has already been demonstrated in the vehicle’s first 2 flights, including being certified for launching classified payloads).

On the negative side, NG-3 and NG-4 are both increasing the levels of satellites orbiting close to Earth together with the overall light pollution they cause for astronomers, whilst simultaneously increasing the risk of on-orbit collisions between satellites. And that’s to say nothing of the added atmospheric pollution such satellites cause when they reach the end of their (relatively short) life spans and are dumped back into the atmosphere to burn-up.

In this, AST SpaceMobile have been particularly cavalier. Whilst the likes of SpaceX (Starlink) and Amazon (Amazon LEO) have at least paid lip service to requests to reduce the amount of light pollution their satellites produce and seriously disrupts a wide range of astronomical work, AST SpaceMobile has essentially lifted a middle finger to such requests, working on generations of ever-larger and more polluting satellites. The 6-tonne BlueBird 7 for example, is not only far bigger than Amazon LEO / Starlink satellites (although its family of satellites will be far smaller than the Amazon / Starlink constellations), it and its siblings have massive solar arrays covering 223 sq metres (2,400 sq ft), which can make them brighter than any star seen in the sky.

New Glenn NG-3 captured from an airborne camera as it climbs towards first stage Main Engine Cut-Off. Credit: Blue Origin

NG-3 lifted-off from Launch Complex-36 (LC-36) at Cape Canaveral Space Force Station in Florida a little later than its target launch time of 10:45 UTC, rising into the sky at 11:25 UTC. Lift-off mark the first time the New Glenn system has lifted a fully private payload into the sky. As appears common with New Glenn Launches, the vehicle initially held on the pad for a second or so after the countdown reached zero as the seven BE-4 engine powering it all came up to full thrust, then the vehicle seemed to rise ponderously into the air, taking some 17 seconds to clear the height of the lightning towers around the pad.

Thirty seconds into the flight the 98-metre tall rocket completed its roll-over (or “pitch over”) onto to its climb trajectory to orbit. At 1 minute 29 seconds, and climbing through 10.3 kilometres altitude, New Glenn passed through “Max Q”, the period of maximum dynamic pressure, and accelerated through Mach 2 shortly after, entering the cloud base and it did so and becoming obscured from view.

A camera within the engine bay of New GlennNG-3’s upper stage captures stage separation, with the upper stage powering away from the first stage. Credit: Blue Origin

Three minutes into the flight and the rocket reached MECO – main engine cut-off – for the first stage motors at an altitude of 77.5 km. Stage separation followed quickly thereafter, together with the ignition of the two BE-3U motors on the rocket’s payload carrying upper stage, allowing it to both continue its ascent towards obit and power itself away from the first stage, jettisoning the payload fairings as it did so to expose BlueBird 7 to space.

Controlled via the fins along its side, Never Tell Me the Odds continue upwards unpowered, until it reached apogee, then became a controlled descent through the upper atmosphere, falling on a trajectory that would intersect the position of the Landing Platform Vessel Jacklyn some 600 km off the coast of Florida, so it could attempt a landing.

Never Tell Me the Odds gliding down through the lower atmosphere ahead of firing three of its motors to slow it for landing. Credit: Blue Origin
Seven minutes after launch, three of the first stage BE-4 engine ignited so 20 seconds to both bring Never Tell Me the Odds to a more upright orientation and to cushion its entry into denser atmosphere. The descent continued with the booster again “tipped” over and falling engines-first, passing through “Max Q” some 8 minutes and 20 seconds post-launch, and at T +8:53 three BE-4s again re-lit, powering the booster down over the waters close to Jacklyn, before the motors cut to just one, allowing the booster to crab sideways over the landing deck and execute a perfect touchdown.

During this time, the second stage complete its initial burn to reach orbit before shutting down for a period, prior to a final engine burn to deliver the payload to its intended orbit. This second firing of the BE-3U motors apparently failed, leaving BlueBird 7 in an off-nominal orbit following separation from the upper stage, as both Blue Origin and AST SpaceMobile looked at the issue.

Never Tell Me the Odds sits on the deck of the Landing Platform Vessel Jacklyn, auto-welded in place, post-landing. Blue Origin

SpaceX to Launch Rosalind Franklin to Mars

It has been announced that SpaceX will now launch Europe’s much-delayed Rosalind Franklin (aka the ExoMars rover) to Mars in 2028 – almost 28 years after the mission was conceived.

Originally, ExoMars (as it has been known for most of its life) was due to be a partnership mission with NASA’s MAX-C rover, only for the latter to be cancelled. As a compensatory measure, NASA offered to launch both the ExoMars rover and Europe’s Trace Gas Orbiter (TGO), which had been folded into the “ExoMars” banner, to Mars aboard two Atlas V boosters, with TGO launching in 2016 and ExoMars in 2018. However, this offer was again rescinded due to NASA budget cuts, leaving the European Space Agency looking for a new partner – and finding one in the form of Roscosmos.

A test vehicle for Rosalind Franklin seen from the rover’s front in a low angle, emphasising the drilling mechanism. Credit: ESA

This at least allowed TGO to launch in its planned year of 2016, but saw a delay in the launch of the rover, as Russia had to develop a special landing platform for it, and wanted that platform to be science-capable. Coupled with issues with the rover’s parachute system, these delays eventually hit the COVID-19 wall, and the launch was further delayed. Then Russia invaded Ukraine, and all bets were off; ESA now needed another partner to get (the now renamed) Rosalind Franklin to Mars. NASA once again stepped up – but this time, instead of offering to launch the mission, they indicated they would find a suitable launch vehicle supplier in return for ESA flying some of their own equipment on the mission.

On April 16th, 2026, this arrangement resulted in NASA and ESA announcing that SpaceX had been selected as the mission’s launch vehicle provider, and that a Falcon Heavy would be used to send the rover on its way to Mars.

An artist’s impression of Rosalind Franklin deploying from its European landing platform. Credit: Aerotime.aero

Rosalind Franklin sits between the NASA solar-powered Mars Exploration Rovers (MERs) and the current nuclear-powered Curiosity-class rovers in size, whilst retaining the former’s solar power system. Despite its boxy, almost amateurish looks, Rosalind Franklin is one of the most science-capable vehicles to be sent to Mars, carrying eight scientific instruments, all designed to aide its primary mission of seeking subsurface bio signs. It will also carry a sample-gathering drill system capable of penetrating up to 2 metres below the planet’s surface.

The landing site for the mission is Oxia Planum, a 200 km-wide clay-bearing plain in the planet’s northern hemisphere, some 18º above the equator. It is one of the largest exposed clay-bearing deposits on Mars and is believed to be some 3.6-4 billion years old. There is ample evidence for free-flowing water having once existed within the region, with the exposed rocks exhibiting different compositions, indicating a variety of deposition and wetting environments.

If the current arrangement holds, Rosalind Franklin will be launched around mid-to-late 2028, and arrive on Mars in 2029.

Cause of Medical ISS Evacuation Revealed

Back in January I covered the emergency evacuation of NASA’s International Space Station (ISS) Expedition 73/74 (aka. NASA / SpaceX Crew 11) after one of the crew experienced a medical issue. At the time, the details of the individual experiencing problems, and what those problems might be were not made public – standard NASA practice. However, all four of the crew were returned to Earth aboard their SpaceX Crew Dragon vehicle out of an “abundance of caution” – and because leaving two of them behind would have left them without a ride home in the event of a further emergency.

Astronaut Mike Fincke – NASA official portrait. Credit: NASA

The Expedition 73/74 crew comprised JAXA (Japan Aerospace Exploration Agency) astronaut and Mission Specialist Kimiya Yui, Roscosmos cosmonaut and Mission Specialist Oleg Platonov, veteran NASA astronaut Michael “Mike” Fincke – who had assumed the role of ISS mission commander not long after the crew originally arrived at the space station, and NASA astronaut Zena Cardman, who served as mission commander for the Crew 11 flight to the ISS. At the time the medical situation initially occurred, Fincke and Cardman were going through various checks of themselves and equipment in readiness for an upcoming EVA – extravehicular activity “spacewalk” to work on preparing the stations’ power system for the installation of further iROSA solar arrays to further boosts the ISS’s electrical power production.

Given this EVA prep work was underway, and NASA then called off the EVA as a whole, initial speculation was that either Fincke or Cardman had suffered some form of medical emergency. However, attention shifted to JAXA astronaut Yui after it was revealed he sought a private consultation with NASA medics on Earth at the same time the EVA preparation work was in progress.

As it turned out, the speculation about Fincke and Cardman was correct when, on February 25th, Fincke decided to go public and reveal he was the one with the issue – although at the time, he declined to indicate exactly what the issue was, and did not do so for a further month.

At the end of March 2026, 58-year-old Fincke, who had previously flown on ISS missions Soyuz TMA-4 (ISS Expedition 9), Soyuz TMA-13 (ISS Expedition 18), and STS-134, and who had been initially picked to fly a 3-person Crew Flight Test of Boeing’s Starliner before that mission was reduced to just two crew – “Butch” Wilmore and “Suni” Williams), revealed that just after the EVA prep work had ended ahead of schedule and the entire ISS crew were settling down for dinner, he suddenly lost his voice.

It was just amazingly quick. Out of the blue. My crewmates definitely saw that I was in distress. It was all hands on deck within just a matter of seconds.

– Michael Fincke, describing the episode which led to his crew being evacuated from the ISS

As several of the ISS crew sought to assist Fincke, Yui got onto a private channel with Mission Control to relay the situation to the ground-based medical team. The episode lasted some 20 minutes before Fincke recovered his voice, and throughout that time he was not in pain or suffering any other symptoms. However, the medical team on Earth could not rule out the potential that he has suffered some form of stroke or heart attack – or that contaminants in the food could have caused his issue and might do so again to himself or another crew member.

It was because of these latter aspects that the decision was made to curtail the crew’s mission to the ISS a month early and return them to Earth, where all of them were subjected to a range of tests, not of which has apparently uncovered any underlying cause for Fincke’s episode or given rise to any concerns over the health of the other three. Fincke himself, as recently as mid-April has stated he has never suffered anything like the loss of voice either before or since the episode on the ISS, and he is hoping to make a full return to flight status for future missions.

The ancient-modern beauty of Marina di Luna in Second Life

Marina di Luna, April 2026 – click any image for full size

Occupying a Homestead region, Marina di Luna is the work of Miri (SilentChloe). It is a beautiful minimalist region design which mixes a sense of history with a twist of the modern. Highly photogenic, the setting offers much to see without overloading itself or the visitor’s senses, and offers opportunities for the romantics at heart.

Marina di Luna is a breath-taking island where modern architecture meets ancient charm. Surrounded by olive trees and a carpet of flowers, the air is fragrant with herbs and the salty sea. It’s a perfect place to relax and enjoy a romantic day out.

– Marina di Luna’s Destination Guide description

Marina di Luna, April 2026

The region is split into a main island to the east and with a north-south major orientation, and two smaller isles, each home to its own structure, of which more anon.

When seen on the map, the main island carries something of a left-pointing sock look to it, the lower part of the sock – from “toe” to “heel”, forms an open meadow, curving gently upwards from the rocky coastline on three sides, and running north towards the island’s main structures.

Marina di Luna, April 2026

This gently humpbacked meadow is home to the region’s Landing Point, the lush flowering grass coating it home to toppled columns and guarded by patient red-crowns cranes.

The “toe” of this sock-like island points towards the smaller of the two other isles, while the rocks on the coast at this point offer a place to sit and a flat “table” on which an artist has set up their easel to paint the larger of the two islands  as it sits further to the north.

Marina di Luna, April 2026

The smaller isle is home to a partially-ruined stone gazebo topped by a copper (or possible iron) domed roof which shares the damage as the stone of the gazebo. With its steps dipping their toes into the water, the gazebo has been turned into a little romantic niche, complete with cosy sofa, champagne and flowers.

The larger of these own isles is home to a large circular bath house. This shares some commonality with the gazebo, hinting at their joint age and Greco-Roman heritage.

Marina di Luna, April 2026

Like the gazebo, the bath house has a copper / iron roof, this one intact but suffering signs of rusting on its iron panels. Inside, the bath house is pristine and its waters clear, the walls split between four points of access and four small alcoves. Outside, the bath house is surrounded by a small garden space on the flat-topped island, where shaded loungers await, whiles a small beach of warm sand offers its own attraction.

Both of the islands can be reached via little motorboats which can be rezzed from lifebuoys to be found on the main island, with the boat house island having its own boat rezzer to aid in a return to the main island (I didn’t see a rezzer on the gazebo island).

Marina di Luna, April 2026

Back on the main island, the northern end is given over to a modern building built in a reflection of ancient Greek designs, and with what appears to be a garden terrace of much greater age, mirroring that of the bath house and gazebo.

Places to sit can be found around this terrace, dominated as it is by a large fountain and smaller fish pond. Broad steps connect terrace and the open waters below, where one of the boat rezzers can be found, whilst to one side, a raised deck offers a place for private dining.

Marina di Luna, April 2026

The front of the main building – a museum and gallery – is guarded by an infinity pool overlooking the open waters below. The museum houses a number of exhibits and a collection of photographs by – I admittedly assume – Miri herself. The museum is also home to a little café and a wine cellar below, complete with its own secret. The For both the exhibits and the “hidden” spaces, the museum is well worth taking the time to explore and appreciate.

All of the above – I hope – draws an outline of Marina di Luna; however, to fully appreciate the naturalness of its beauty, the attractive nature present in its simplicity of design, and to fill in all of the colours it presents, it is a place deserving of a visit; just be sure to take your camera with you. Should you need props when taking photos, rezzing in the region is open – just do please be sure to pick your things up afterwards.

In all, a recommended destination.

Marina di Luna, April 2026

SLurl Details

2026 week #16: SL Open Source (TPVD) meeting summary

Hippotropolis Theatre: home of the OSD/TPVD meeting
The following notes were taken from:

  • My chat log of the Open-Source Developer (OSD) meeting held on Friday, April 17th, 2026, together with my chat log of that meeting.
  • Pantera’s video of the meeting (embedded at the end of this article) – my thanks to her for providing it.
  • Please note that this is not a full No video this week, as Pantera was absent the meeting.
Table of Contents

Meeting Purpose

  • 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.
  • Dates and times of meetings are recorded in the SL Public Calendar.

Official Viewer Status

  • Default viewer  – One-Click Installer = 26.1.1.23806384790 – April 10 – NEW.
  • Second Life Release Candidate (RC) viewer: Flat UI – 26.2.0.24254827122, April 15 -“flat” UI and font update – NEW.
  • Second Life Project Viewers:

26.2.0 – “Flat UI”

  • Now at RC status, per the Above list.
  • 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 question was asked on interpreting section 8 part of the Unauthorized Uses of Linden Lab’s Trademarks policy – a question perhaps best dealt with via a support Support Ticket.
  • 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.

Next Meeting

LL announce Mainland changes & Town Hall to discuss

Linden Lab has announced changes to the standalone Gaeta 1 continent, and the Zindra adult continent. Via the SL Wiki

On Wednesday April 15th, 2026, Linden Lab announced some significant Mainland changes involving the Gaeta 1 continent and the Adult continent of Zindra.

The Changes

Gaeta 1

  • A transitioning of all current residents from Gaeta 1 to other Mainland continents. This is to start in April 2026, with an aim to complete by the end of 2026.
  • This transitioning will be handled carefully, with personalised outreach to residents on Gaeta 1 by members of the Lab’s staff.
  • Land holders on Gaeta 1 will be offered size-for-size parcel replacements, and LL will work with them to find a comparable parcel that suits their needs and preferences.
  • No region on Gaeta will be retired without due consultation with the land holders currently based on it. Time will be given for all land holders to plan, examine options and discuss matters with the Lab as the process commences and progresses over time.
  • The transition is expected to unfold “over many months”.
  • Once complete, Gaeta 1 will go offline as a continent.

Zindra

  • Zindra will see an expansion of approximately 90 regions.
  • This expansion will be rolled-out alongside the transitioning of Gaeta 1 – but does not mean Gaeta 1 land holders “must” accept parcels within Zindra.
    • However, if moving to Zindra is seen as preferable by any Gaeta 1 land holder, they will be given priority access to the new Zindra regions.
  • These new Zindra regions will include scenic waterfront, extended road networks, coastal water passages, and additional development that helps complete and enhance the Zindra continent.

Why is this being done?

To quote from the official blog post:

Adult mainland continues to operate at very high occupancy and shows consistent demand. At the same time, some General and Moderate mainland areas, including Gaeta 1, have seen lower overall use over time. Instead of expanding the total size of mainland, we are adjusting existing capacity to better reflect where Residents are most active today.
This change applies only to the unconnected continent named Gaeta 1. IT IS NOT PART OF A BROADER MAINLAND CLOSURE, and there are no changes to content policy connected to this announcement.

– From the Lab’s official blog post on the Gaeta 1 and Zindra changes

Town Hall Meeting

As a part of the consultation process and to answer initial questions  / hear feedback on these changes, Linden Lab will be holding an in-World Town Hall meeting on Monday, April 20th, 2026, commencing at 11:00 SLT. The Town Hall meeting area can be accessed using the following SLurls:

In addition, the Lab has opened a forum discussion thread on these changes, and invited users to join that conversation.

Related Links

2026 week #16: SUG meeting summary

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.
  • Rider Linden has been working on viewer code to support the new language definition cap.
  • 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.
    • As a part of the discussion llSetLinkGLTFOverrides fails to clear alpha override was raised. No updates were given.
  • 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.

SL23B: volunteer applications now open

via Linden Lab

June 2026 will mark the 23rd anniversary of Second Life opening to public access – and as we’ve all come to expect, the month will mark the start of several weeks of events and celebrations running into July under the umbrella of the Second Life Birthday (SLB) otherwise know for this year as SL23B.

Dates and Theme

This year the SLB festivities will open on Friday, June 18th, 2026 and will run through until Sunday, July 19th, 2026. The theme for 2026 is The Golden Age of Hollywood, which the Lab describes thus:

Think classic cinema, red carpets, vintage glamour, and the magic of the silver screen. While the theme may inspire many builds and performances, exhibits are not required to follow the theme. We encourage you to share what makes your Second Life experience meaningful. Your interests. Your communities. Your creativity.

However, as has been the case over the last several birthday events, exhibitions are not confined to the theme itself, with the Lab additionally noting:

Every year, we celebrate because of the incredible Residents who bring this world to life. The birthday celebrations are an opportunity to showcase what inspires you and what keeps you coming back.

Volunteer Applications

On Tuesday, April 14th, 2026, Linden Lab announced that Volunteer applications have opened and remain so through until Monday, May 18th, 2026. As noted, exhibitor applications are now open. Key requirements for volunteers are noted below – however, for the full list of requirements, please refer the the exhibitor application form, via the link following these notes:

  • Volunteers are asked to commit to at least two hour shifts at a time, and to note that as SL23B spans 11 days, LL prioritise applicants who can participate across multiple days. Stage Crew are expected to contribute a minimum total of 8 hours.
  • Training sessions will be provided across multiple times. All volunteers are expected to complete a training session, regardless of whether they have been volunteers at previous Birthday events. Those failing to complete the required training will be removed from the Volunteer group.
  • These are volunteer positions, and as such, volunteers will not be paid. Additionally, volunteers cannot rez/wear tip jars or solicit for tips.
  • Stage Crew:
    • May not act as personal hosts for performers. You may only host if specifically scheduled as a Stage Host under the official guidelines.
    • Members should report any issues to their Stage Manager first. Stage Managers are responsible for assigning roles, tasks, and timing.
  • Greeters should report any issues in the Greeter group and a Mole or Coordinator will assist.

Volunteer Application Form.

Please note: All enquiries about hosting exhibitions, staging performances or volunteering at the event should be directed to Linden Lab, not this blog.

Related Links