The art of Janine Portal in Second Life

A Thousand Words Coffeehouse and Gallery, March 2026: Janine Portal

In February, I received an invite from Astella Warrigal to visit her gallery, A Thousand Words Coffeehouse and Gallery. It was actually to attend the venue’s grand reopening, which was held on February 22nd, 2026. However, things being what they were for me at the time, I was unfortunately unable to attend that event; but I certainly wanted to make sure I got to see the exhibition of art by Janine Portal which formed a part of the re-opening.

I first encountered Janine’s work back in 2018, an immediately found it captivating. As I noted at that time:

Utilising animations and prims to present remarkable collage pieces with a surrealist edge that are quite captivating to see … some of the most unusual art and effects I’ve seen in Second Life for a while, each piece offering an unexpected view of what might otherwise appear to be and ordinary scene or photo or presenting a melding of ideas and / or narrative that is quite engaging.

– The artful collages of Janine Portal in Second Life

A Thousand Words Coffeehouse and Gallery, March 2026: Janine Portal

This is very much the case with the exhibition of Janine’s work at A Thousand Words Coffeehouse and Gallery, where it can be seen on the upper levels of the building. On display are some 13 collage images, all of them comprising found and manipulated (by Janine) art and photographs, including reproductions of artwork by the likes of William Blake, Hilma af Klint, Richard Diebenkorn, and Second Life photographer Ajax Ogleby.

Janine says of her work:

I’ve been making art in Second Life using a technique that involves layering transparent prims to create works with shifting collage images. In RL, long before I made an account in SL, layered transparent paint to express similar ideas, using many of the symbols you see here. 

– Janine Portal

A Thousand Words Coffeehouse and Gallery, March 2026: Janine Portal

Janine goes on to note that her art reflects ideas which have woven their way into her thinking and approach to art ever since her time at art school: ideas of the metaphysical and personal symbols of transformation. This gives her work a layered set of interpretations; whether one views them purely as visually engaging works of art or seeks to find those metaphysical ideas.  In this, Janine adds her own view on the art:

On a conceptual level they represent, to me, the endlessly shifting nature of reality, the ways in which we move through time and space and the nature of growth, change, and transformation.   

– Janine Portal

A Thousand Words Coffeehouse and Gallery, March 2026: Janine Portal

A genuinely captivating exhibition, one definitely worth the time in visiting.

SLurl Details

2026 week #10: SUG meeting summary

A view of Isola Sirena, Second Life - the main island summit village
Isola Sirena, January 2026 – blog post

The following notes were taken from the Tuesday, March 3ed, 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 deployments are planned for the week, channels will be restarted.
  • It had been planned to slot the initial deployment of WebRTC  between the 2026.02  Kiwi update (currently grid-wide), and the next formal RC release 2026.03 Loganberry. However a last-minute issue was discovered, delaying WebRTC whilst it is fixed.
  • The release to follow Loganberry will be 2026.04 Key Lime).

WebRTC Deployment

  • As noted above, the WebRTC deployment has been delayed, primarily for a couple of reasons:
    • LL is addressing some server issues that resulted in very occasional ‘drop from voice’ problems.
    • The WebRTC team is also digesting feedback from the recent Firestorm Town Hall in which firestorm users who have not moved away from a version 6.x (pre-PBR) version of Firestorm to a PBR-enabled version.
  • It is hoped the delay will not be longer than a week or so, so as to allow it to commence in March, but an update on this will be made soon.

In Brief

  • Rider Linden has just finished a tricky bit of infrastructure work and is now focusing on some the simulator aspects of the SLua project, including changes for being able to select a default script. A side effect of that is the ability for a viewer to specify a template script on create without the tricky copy stuff that the viewer was doing for that.
  • Leviathan Linden:
    • Has just finished fixing the “can’t save avatar action remap” problem with game_control but has not pushed the changes to a viewer repo as he working to clean the code up and produce documentation.
    • He regards this particular work as useful as it has reminded him of what remains to be done for game-control. In particular, remapping of controller buttons is not yet enabled in the preferences UI, although there should be work to support that already done under the hood.
    • He has not made any progress on Henri Beauchamp’s idea for solving the “perpetually cloudy avatar problem” see previously SUG summaries). It is coded on the server,  but he hadn’t been able to test it.
    • His next project is to audit how some “reliable” UDP messages are sent between viewer and server. There is a possibility he can fix some of the login/teleport/region-crossing connection failures with some work there. One of the message pairs to be looked at are CompleteAgentMovement/AgentMovementComplete. Dropping these is the source of quite a few B&W screens every day.
  • Monty Linden has been:
    • Working on meta problems, such as identifying Voice issues.
    • Talking to Brad Linden about making it easier to include logs in reports generated in the viewer.

General Discussion

Please refer to the video below as well.

  • An extensive discussion on llSetAgentRot and how it works and how it and avatar rotation / camera rotation/movement might be improved.
  • A short discussion on text-to-speech and how favourable (or not) it might be, based off of this feature request.
    • It was noted that transcription – speech to text – is already being experimented with using WebRTC.
  • Region  Crossings:
    • It is being reported that for the last week or so, region crossings – physical vehicle or teleport – have been getting worse.
    • In addition, it is being claimed that, after an extended period of time in a region, people are finding their avatars being “soft disconnected” from the simulators: they can still move around and communicate within the region, by any attempt to move out of it results in a complete disconnection – and allegedly a full disconnect can occur just by rezzing / deleting an object or changing outfits.
    • There have been no apparent changes to the simulator code that would account for a worsening of region crossings, and it’s not entirely clear how widespread the issues are.
    • However, Monty linden has requested logs from anyone encountering these issues.
    • This discussion took up the latter half of the meeting (and beyond the end of the meeting), mixed in part with the rotation discussion noted above,
  • A discussion on releasing SLua grid-wide without complete documentation, or waiting until a full set of documentation is ready for what is being released, and then updated as code updates are made.

Date of Next Meetings

  • Leviathan Linden: Tuesday, March 10th, 2026.
  • Formal SUG meeting: Tuesday, March 17th, 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 beauty of London’s China Buddha Caves in Second Life

China Buddha Caves, March 2026 – click any image for full size

Located within Gansu province in western China is the county city of Dunhaung. It sits on the old Silk Road, and forms a cultural and religious crossroads. Founded as a garrison town in 11 BCE, Dunhaung is perhaps now more famously known for its proximity to the Mogao Caves, a system of 500 temples, caves and grottoes some 25 kilometres south-east of the city.

Also known as the Thousand Buddha Grottoes or Caves of the Thousand Buddhas, the network represents, along with other cave systems in the area, some of the finest examples of Buddhist art spanning a period some 1,000 years, the earliest caves having been dug in around 366 CE, initially as places of rest, worship and meditation. However, as time passed, they became a place of pilgrimage, and further caves and grottoes were dug, with the system expanding through until the 13th century, before they were “lost” until the late 19th century.

China Buddha Caves, March 2026

I mention all of this because in his latest artistic installation, London Junker offers us a vision of the Mogao Caves and the beauty of their art, sculptures and design with his China Buddha Caves build- project was sponsored by SL Public Land Preserve and Ravenglass Rentals (La Montana Rosa) – to which he extended a personal invitation for me to visit.

Situated in the snowy uplands of south-western Sansara, the build is initially deceptive to the eye. The Landing Point sits at the head of a descending gorge through which water tumbles and falls towards the sea. A large Buddha sits behind the Landing Point, undoubtedly offering blessing to arrivals, whilst a single grotto with wall murals and three more figures of Buddha sits to one side.

China Buddha Caves, March 2026

A further Buddha can be seen lower down in the valley, together with a shrine and structures built with their backs towards the rising cliffs. A single path runs down the side of the gorge, passing over a long bridge and down stairs to reach a second bridge crossing the waters and provide access to the tall statue of Buddha and the shrine, whilst a second path rises to the lowermost of the structures build against the cliff, and which forms the entrance to the caves proper.

The art and carvings within the Mogao Caves is truly magnificent, and the site fortunately escaped the Buddhist persecutions ordered by Emperor Wuzong of Tang in the ninth century, continuing to be used through until the Yuan dynasty in the 13th century. However, it was during that era that new trade routes started to open, and the use of the Silk Road fell into decline – and with it, the use of the Mogao Caves as a place of pilgrimage. By the mid- 14th century, no new caves were being built, and the site was largely forgotten other than by locals.

China Buddha Caves, March 2026

It was not until the 19th century that the caves were re-discovered.  Interest in exploring the ancient Silk Road and uncovering its secrets was initially a goal of western explorers and historians, and this eventually led them to Dunhuang and the caves. However, it was at the start of the 20th century that the greatest work of rediscovery commenced, with the good intentions of one man in particular.

His name was Wang Yuanlu. A Chinese Taoist, he had appointed himself guardian of the caves, and in the early 1900s set about clearing the entrances to many which had become blocked over the centuries, as well to trying to renovate many of the damaged statutes.

China Buddha Caves, March 2026

Most particularly, Wang’s work led to the discovery of a vast trove of manuscripts in what had simply been called Cave 17, but which afterwards was referred to as the Library Cave. Some 1100 scrolls and 15,000 books were found in the cave, together with an estimated 50,000 texts on a range of subjects including philosophy, art, literature and medicine. This discovery brought the Mogao Caves to wider global attention, with a number of foreign expeditions to explore them being mounted – several of which simply carted off whatever they could.

Fortunately, London’s China Buddha Caves suffers none of this looting. Rising up through multiple levels, as is the case at Mogao, they instead offer a captivating interpretation of their physical world inspiration, presenting a rich mix of Buddhist art and history,  the walls bearing beautiful murals and paintings, the statuary magnificent in detail and finish. As you rises up through the caves (take your time in exploring, some of the rising tunnels are easy to miss!), you will come across an opening to a veranda located against the cliff and above the main entrance, reflecting a similar, almost pagoda-like structure found at Mogao.

China Buddha Caves, March 2026

Each level becomes more expressive and rich as one ascends, with the upper most and the landing and grotto leading up to it being particularly attention-holding. However, all of the levels capture the beauty and history to be found in the caves at Mogao, and perfectly reflect the beauty of the murals to be found in many of the caves there. In this, I would advise using a PBR viewer in order to fully appreciate this installation, or if you are still pre-PBR, that you enable ALM.

Presenting a glimpse of what is now a UNESCO World Heritage Centre (since 1988), London’s China Buddha Caves offer a superb means by which to catch a glimpse of what is a magnificent centre of Buddhist history and art in the physical world.

CChina Buddha Caves, March 2026

SLurl Details

2026 SL viewer release summaries week #9

Logos representative only and should not be seen as an endorsement / preference / recommendation

Updates from the week through to Sunday, March 1st, 2026

This summary is generally published every Monday, and is a list of SL viewer / client releases (official and TPV) 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.

Official LL Viewers

  • Default viewer 2025.08 – 7.2.3.19375695301 – maintenance update with bug fixes and quality of life improvements – December 2.
    • Notable addition: new VHACD-based convex decomposition library for mesh uploads.
  • Second Life Release Candidate viewer 2026.01 – 26.1.0.22359044520 , February 25 – NEW
    • Legacy search; WebRTC improvements; QoL improvements.
  • Second Life Project Viewers:
    • Second Life Lua Editor Alpha viewer 26.1.0.21525310258, February 3.
    • Second Life Voice Moderation viewer 26.1.0.20139269477, December 12.
      • Introduces the ability to moderate spatial voice chat in regions configured to use webRTC voice.
    • Second Life One Click Install viewer 26.1.0.21295806042, January 26, 2026 – one-click viewer installation.

LL Viewer Resources

Third-party Viewers

V7-style

  • Black Dragon for Windows –  5.6.0 March 1 – release notes.

V1-style

  • Cool VL viewer Stable: 1.32.4.22, February 28 – release notes.

Mobile / Other Clients

  • No updates.

Additional TPV Resources

Related Links

Space Sunday: major Artemis updates and a rollback

Credit: NASA

Yes, there’s been a lot in this column about Project Artemis and the US-led programme to return humans to the Moon, and while it might make Space Sunday sound a bit like a scratched record (Artemis..,Artemis…Artemis…), there is good reason for this: there’s a lot of news about the entire programme, from the anticipated launch of Artemis 2 and its crew on a trip around the Moon and back, to the focus of the main part of this article: major changes to the Artemis programme as a whole; so bear with me!

NASA’s current Administrator, Jared Isaacman, continues to surprise and impress despite concerns over his non-NASA activities and involvement with favoured space contractors. In my previous Space Sunday article, I covered Isaacman’s direct and open approach to the problems endemic to the Boeing CST-100 Starliner programme, and to the core of NASA’s management responsible for managing it (with two of the most senior resigning in the aftermath).

Following the press conference on that matter – which included the reading out of a letter to all NASA staff-  Isaacman was present at a February 27th, 2026 Project Artemis update which carried its own surprises whilst signalling a change in direction for the programme – potentially putting it on a far better footing that had previously been the case.

The update saw a number of significant announcements:

  • The much-criticised Space Launch System (SLS) is not to be cancelled as yet – something many outside NASA have called for, despite there being no currently-available launch vehicle that can match its capabilities (see: Space Sunday: of Artemis and Administrators).
  • However, SLS will be changing, with one significant element – the Exploration Upper Stage – now cancelled.
  • As a result of the Exploration Upper Stage cancellation, the Block 1B variant of SLS will no longer be part of the SLS enhancement programme, nor, potentially, will be the even more powerful Block 2 version.
  • NASA will attempt to raise the launch cadence for SLS from approximately once every 3 years to once every 10 months.
  • Artemis 3 is no longer a lunar landing mission, but will be an Earth-orbiting test flight involving at least Human Landing System vehicle.
  • The original Artemis 3 lunar landing mission is therefore redesignated Artemis 4, but the time frame remains a (optimistic) 2028.

SLS Changes

Much of the critique surrounding SLS has been on the matter of launch cost, which stands at some US $2.5 billion per vehicle. However, these costs are based on the overall development of SLS and Orion, and are not simply the physical cost of get a specific launch stack off the pad. This is something many of the louder voices raised against SLS – notably those from the SpaceX corner – tend to ignore when pointing to the “lower” cost of something like Starship, which is put at around US $100 million per launch. In this, it needs to be pointed out that this has yet to be proven, as Starship has yet to actually achieve orbit, and even then, launch costs for NASA could be as much as US 1.3 billion, when all of the required tanker launches and the launch of the (also unproven) orbital propellant station the Starship HLS will require just to get itself to the Moon.

That said, SLS is a costly launch mechanism; in 2023, the US Government Accountability Office (GAO) issued a report stating SLS was “unsustainable” at current spending levels, and suggested that launch costs could increase over time to as much as US $4 billion as a result of the technical complexity of the system, plans to try to extend its capabilities and its low launch cadence.

Exploration Upper Stage and “Near Block 1” SLS Development

Dropping the Exploration Upper Stage (EUS) from the SLS development curve should address some of these concerns over rising costs.

EUS was due to debut with the Block 1B development of SLS, providing it with a more powerful and capable upper stage than the current Interim Cryogenic Propulsion (ICPS) upper stage. As it is now cancelled, NASA is pivoting away from the Block 1B version of SLS in order to develop a “near Block 1” upgrade, which will use a new upper stage in place of both ICPS and EUS.

The original planned evolution of SLS, from the current Block 1 version for crewed launches through a cargo variant of the same vehicle to the Block 1B version utilising the EUS in both crewed and cargo versions, through the evolved Block 3 design with more powerful solid rocket boosters. Under the new plan, NASA will replace the Block 1B version with a “near Block 1” enhanced variant. Credit: NASA

Just how much this will save is open to debate: some US $3 billion has already be spent in developing EUS, and there will obviously be costs involved in developing a commercially-based replacement for it and ICPS. But there are other another compelling reasons for replacing EUS with a unit more in line (if more powerful) than the ICPS: simplicity of overall design and design and continuity of experience.

The Block 1 SLS is now a known creature, foibles and issues all taken as read. It’s a vehicle NASA is continually gaining knowledge and understanding in operating. Block 1B, with the EUS, it’s extended core stage elements (extended interstage and the enlarged universal stage adaptor) is a different beats, liable to demonstrate different flight characteristics and dynamics as well as introducing new elements which could have their own teething problems. Sticking with an only slightly modified vehicle to supersede the current Block 1 vehicle, reduces many of these factors, allowing NASA to “standardise” the SLS design and continue to gain data, knowledge and understanding on  / of its characteristics incrementally. This was pretty much how things were handled back in the Apollo era, and the approach has a lot going for it, a point acknowledged during the briefing.

After successful completion of the Artemis I flight test, the upcoming Artemis II flight test, and the new, more robust test approach to Artemis III, it is needlessly complicated to alter the configuration of the SLS and Orion stack to undertake subsequent Artemis missions. There is too much learning left on the table and too much development and production risk in front of us. Instead, we want to keep testing like we fly and have flown. We are looking back to the wisdom of the folks that designed Apollo. The entire sequence of Artemis flights needs to represent a step-by-step build-up of capability,

– NASA Associate Administrator Amit Kshatriya

Exactly who will provide the replacement for ICPS / EUS and what form it will take was now discussed at the briefing. However, it was made clear that all of NASA’s contractors and partners in Artemis were consulted through the driver to redirect the programme, and all have been supportive of the moves – even Boeing, who stand to lose the most with the EUS cancellation, whilst SpaceX and Blue Moon have both opted to “accelerate” the development of their HLS systems.

Perhaps two of the strongest potential contenders for producing a new upper stage for SLS are United Launch Alliance (ULA) and Blue Origin.

ULA already has the powerful cryogenic Centaur V upper stage. Centaur is a venerable launch vehicle stage with a lot of expertise behind it, with the Centaur 5 already forming the upper stage of ULA’s Vulcan-Centaur rocket. Blue Origin, meanwhile, has the upper stage of their New Glenn booster. Whilst a “new kid on the block”, the stage has already proven itself reliable on two high-profile flights for New Glenn, and will shortly be back in action for a third flight, thus experience is quickly being gained in its operation. Further, blue Origin are already looking to develop an enhanced version of the stage in line with their plans for an even more powerful variant of their New Glenn vehicle, thus there is potential here as well.

Neither Centaur V nor the New Glenn upper stage would be suitable for SLS straight off the shelf, but using them as either a basis for a new stage design or developing a variant off of an existing design (Blue Origin) could significantly reduce the costs and time involved in developing and testing a new SLS stage.

Launch Cadence

Another mitigating factor when it comes to reducing overall costs is the decision to try to launch SLS on a greater cadence than has thus far been seen. Isaacman would specifically like to see an SLS / Artemis launch once every 10 months, putting Artemis almost on a similar launch cadence as Apollo. Doing so will likely increase Artemis costs, but it also brings some very clear benefits:

  • Personnel expertise. Gaps measured in years between launches can result in personnel expertise loss as people become tired of waiting for the next launch and seek a career move elsewhere, taking their expertise with them. A faster launch cadence with clear mission objectives is more likely to keep more of that expertise in-house at NASA for longer.
  • It makes Artemis potentially more robust, presenting NASA with a chance to present a clear roadmap for achieving the goals of establishing a lunar base and maintaining a human presence there. Clear time frames and mission objectives also help Congress in allowing the money to flow into NASA to support the programme.

Of course, achieving such a cadence is no easy task; thus far, Artemis 1 and Artemis 2 (of which more below) have demonstrated that, like it or not, SLS and its ground support systems are extremely complex and subject to technical issues which can so easily upset launches.

Artemis 3 – No Longer Aiming for the Moon

The decision to “divert” Artemis 3 to an Earth orbital mission was perhaps the biggest surprise in the update – although “divert” is not entirely correct.

What is proposed is the insertion of an additional Artemis / SLS launch between what is currently Artemis 2 and what would have been Artemis 3, the first crewed lunar landing in the programme. That mission – presumably utilising the same crew – will now effectively become Artemis 4, with the new Earth-orbital mission taking the name Artemis 3.

An infographic outlining the revised Artemis missions (2 through 6), with the Artemis 2 crewed mission around the Moon and back (2026) at the top; the new Artemis 3 mission (2027) centre and the first three crewed lunar landing missions (Artemis 4 through 6). Credit NASA
The aims of the revised Artemis 3 mission – scheduled for a 2027 launch – so far comprise (additional mission goals may be added as the mission requirements are further assessed):

  • On-orbit rendezvous and docking with one or other (or possibly both) of the current Human Landing System vehicles in development: Blue Origin’s Blue Moon Mark 2, and the nascent SpaceX  Starship-derived HLS.
  • Perform integrated checkout of life support, communications, and propulsion systems on both HLS vehicles and assess their suitability / practically for zero gravity operations.
  • Carry out comprehensive tests of the new extended extravehicular activity (xEVA) suits to be used both with Artemis as as a replacement for the current generation of US EVA suits on the International Space Station.

This is actually a smart step on NASA’s part, and harkens back to the Apollo era and specifically, the Apollo 9 mission.

Artemis 3 will focus on earth-orbit rendezvous with either Blue Origin’s Blue Moon Mark 2 HLS or the SpaceX Starship HLS (depending on which is available at the time) or both (if both prove to be ready for testing – which right now looks unlikely in the case of the SpaceX HLS). Credit: NASA

Under the original Artemis plan, no provision was made for any on-orbit human testing of the SpaceX HLS vehicle ahead of Artemis 3. Instead, SpaceX were obliged to send and uncrewed HLS lander to the Moon and conducted an automated landing (or possibly 2) – but there were no provisions for any crewed testing of the vehicle prior to Artemis 3.

Conversely, Blue Moon Mark 2, with its longer lead time (not being required – in theory – until Artemis 5 under the previous plans, and now Artemis 6 under the revised approach) would have undergone Earth orbit crewed testing prior to being used for lunar operations.

As such, this new step offers a means by which both vehicles (assuming both are ready for a 2027 launch) can be properly tested in Earth orbit, where the risks to the crew are potentially reduced, simply because they can use Orion to make a fast return to Earth. Thus, both can be properly assessed, including any shortfalls they might exhibit in advance of any attempt at a lunar landing. This is something that is clearly much better for all concerned than otherwise sitting and crossing fingers, as would have been the case with the original Artemis 3 mission.

Other Changes

Additionally, the Artemis Update indicates further changes within NASA’s operating structure as a whole with a drive to rebuild core competences and to better oversee commercial contracts and be more hand-on with commercial partners (as indicated in the Starliner press briefing). Key to this will be the implementation of standard processes right  across the space agency, not just covering Artemis, but all commercial partnership and space projects.

Further, the space agency will embark on a process of new and more extensive involvement with Congress to keep them appraised of progress with SLS and Artemis, and has already embarked on a restructured process of negotiating with commercial partners and engaging them in NASA’s decision-making processes.

Whilst nothing should be definitively drawn from it, it is somewhat interesting that the new SLS upper stage designed to replace both ICPS and EUS (seen in the centre, above, with Orion attached) has a marked similarity to the New Glenn upper stage, seen to the right Orion and powering the Blue Moon Lander Mark 2 to orbit.

In the meantime, the NASA announcement has received a largely positive reaction from observers and stakeholders, and the approach it advocates potentially helps put Project Artemis on a much more realistic footing to achieve its goals.

Artemis 2 SLS Rolled Back to the VAB

As I reported in my previous Space Sunday update, Artemis 2 suffered another setback in plans to get a crewed Orion space vehicle on a 10-11 day free return flight to the Moon (with a day spent in a high Earth orbit beforehand) off the ground in March.

The Crawler-Transporter edges the Artemis 2 SLS stack and mobile launch platform into one of the two massive high bays of the VAB at Kennedy Space Centre near the end of an 11+ hour journey back from the launch pad. Credit: NASA livestream

The issue this time resides within the helium pressurisation system within the rocket’s Interim cryogenic Propulsion Stage (ICPS), which is required to get Orion to orbit and plays a role in meeting all of the mission’s planned goals. As I noted at the time of writing that update, NASA felt there were two potential routs to resolving the issue: by leaving SLS on the pad at Kennedy Space Centre’s Launch Complex 39B (LC-39B). Or rolling the entire stack back to the Vehicle Assembly Building (VAB), where a more comprehensive examination of the issue could be performed.

It was decided the latter was the better choice of action, and so on February 25th, 2026, the Artemis 2 launch vehicle and its Mobile Launch Platform were slowly and gently rolled back to the VAB atop one of the famous Crawler-Transporters.

A view from inside the VAB as Artemis 2 arrives. Note the curved gantries either side of the  upper parts of SLS. These can be extended outwards (as can other levels within the high bay) to encapsulate the rocket and provide ease of access to its vitals for engineers. Credit: Cameron (@nyoomtm)

The physical move of the rocket and its launch tower structure commenced at 14:38 UTC, and took over 11 hours to complete, the Crawler-Transporter inches the entire structure into one of the VAB’s massive high bays inch by inch with incredible precision given the overall size of the Crawler-Transporter and its payload. The night-time arrival also afforded some unique views of the entire stack edging up to and then entering the VAB.

Currently, the hope is to correct the helium pressure issue in time to get the rocket back to the pad so it can meet an April 1st through 6th (inclusive) launch window. However, more extensive rectifications to the helium system, if required, will be left for the next SLS vehicle which will carry the crew selected for the new Artemis 3 mission to orbit.

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

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

  • Pantera’s video (embedded at the end of this article) and my chat log of the Open-Source Developer (OSD) meeting held on Friday, February 27th, 2026, together with my chat log of that meeting.
  • Please note that this is not a full transcript of the meeting but a summary of key topics.
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.

Note: The OSD/TPV meeting has tended to occur in the same week as the content Creation User Group meeting over the last several months, resulting in a lot of repetition of information between the two meetings (and combined summaries on this blog). An attempt is being made to break this cycle by having the next OSD/TPV meeting on Friday, March 6th, 2026 before reverting to the usual every other week format (so the meeting after that will be March 20th, 2026) – thus putting the OSD/TPV meeting and the CCUG on alternate weeks.

Official Viewer Status

  • Default viewer 2025.08 – 7.2.3.19375695301 – maintenance update with bug fixes and quality of life improvements – December 2.
    • Notable addition: new VHACD-based convex decomposition library for mesh uploads.
  • Second Life Release Candidate viewer 2026.01 – 26.1.0.22359044520 , February 25 – NEW
    • Legacy search; WebRTC improvements; QoL improvements.
  • Second Life Project Viewers:
    • Second Life Lua Editor Alpha viewer 26.1.0.21525310258, February 12.
    • Second Life Voice Moderation viewer 26.1.0.20139269477, December 12.
      • Introduces the ability to moderate spatial voice chat in regions configured to use webRTC voice.
    • Second Life One Click Install viewer 26.1.0.21295806042, January 26, 2026 – one-click viewer installation.

Upcoming Viewers

Viewer 2026.01

  • Remains the current viewer development focus with the release of the beta (RC) version, although this will be shifting more to 2026.02.
  • The velopack one click installer / updater is not in the initial beta, and may now in fact slip to 2026.02.
  • 2026.01 includes a high priority fix for specific Bluetooth headset configurations which will benefit WebRTC.
  • Now available as an alpha viewer (above).
  • As the name suggests, triggers a one-click install / viewer update process.
  • Also includes improved monitoring / logging of viewer freezes and crashes, etc.

Viewer 2026.02

  • 2026.02 remains on track for the “Flat” UI and font updates.
  • It now also includes the WebRTC voice moderation capabilities (as seen in the project viewer) to help align viewer-side WebRTC updates more with the hoped-for server-side deployment (see below for more).
  • This viewer might additionally receive some backported updates to texture streaming.
  • No Alpha / Beta viewer is available as yet for this release..
Example of the upcoming flat UI. Via: Geenz Linden / Github #4681/2

Viewer 2026.03 -“SL Visual Polish” (SLVP)

  • 2026.03 had been looking to an April release, however, it might slip back to 2026.04. Part of the decision-making on this is related to upcoming server-side updates to EEP and glTF which are seen as being required prior to SLVP shipping.
  • It will likely to include:
    • The “long baking” SSR improvements that were started last year. This version of the viewer will likely have a long beta soak time to allow feedback on these changes to be gathered.
    • PBR specular for residents who are more familiar with the old Blinn-Phong workflow. This will:
      • Include another texture slot (tint of the specular reflection).
      • Work with metallics.
      • Follow the glTF specification, but will likely initially be without glTF overrides, as this requires server-side work.
    • HDR controls in EEP so residents can decide how bright or dark things should be. This work does require simulator-side updates. This will likely initially have server-side support on Aditi (the Beta grid).
  • It may additionally include:
    • Further mirrors optimisations and a new “Ultra” quality setting that will enable a system mirror for water. A caveat on this work is that while this “water mirror” might up the quality of water reflections, it will do so at a performance hit; SSR for water will always be faster and less intensive.
    • Inclusion of an emissive strength setting for PBR.
  • The Pull Request  for this work can be found here – #5385.

General Viewer Notes

  • Firestorm hosted a Townhall recently, with Lab presence, to try to determine why a percentage of Firestorm users remain reluctant to move away from a 6.x version of that viewer to a PBR-supporting version. The predominant issues appear to be concerns over performance and the degraded water visuals seen with PBR viewers.
    • One aspect of people refusing to move is hearsay: “X said PBR sucketh and has poor performance, therefore I will not even try it”, regardless as to whether this might be true for them or not; another is, potentially, people’s general unwillingness to change from what they like.
    • Exactly how to address such issues / beliefs/perceptions is no easy task.
    • A suggestion was made to have “toggle” in the viewer so users can determine which rendering system they wish to use (e.g. “legacy” or “PBR”). This is far more complicated than it sounds, requiring continued support of two rendering pipes in the viewer, potentially leading to multiple complications and the potential content breakage. As such, it is not going to happen.
  • Geenz Linden is continuing to work with texture streaming and resolutions, with some of the work possibly surfacing in 2026.02 as noted above. He further noted that:
    • Work is not stopping at texture streaming improvements; the Lab is laying plans to deal with some of the “bigger performance bullet points”.
    • It is known that PBR  has introduced performance bottlenecks, many of which have been dealt with, others of which still need work. To this end, the Lab may start running Tracy “very, very regularly” to identify bottlenecks so they can be addressed.
    • The hope is that when adding a new PBR feature / capability, at least one existing bottleneck will be corrected.
  • As noted in the 2026 week #5 OSD meeting, there are potential changes coming to the viewer build chain. These involve updates to CMake and a Pull Request relating to vcpkg. The latter is still under review, and is likely to be implemented “bite by bite”, rather than all at once. It will also be likely to go into its own branch and not emerge until after the SLua /Linux viewer work reaches release status, so as to not over-complicate things for TPVs.
  • TPV Developer Henri Beauchamp (Cool VL Viewer) suggested splitting the viewer’s main thread so that the rendering code can be separated from messaging and objects updates, thus smoothing frame rates in the viewer.
    • Geenz Linden indicated that this had been looked at by a Product Engine engineer, and that it was felt that doing so would help out massively with porting the viewer to other graphics APIs.
    • However, actual work on this has not as yet started, as there is a need to “chip away” at getting approval together with a need to avoid disrupting existing releases.
    • Such is the scale of the work, it could involve “a few quarters” of effort to implement.
    • It was noted that while some multi-threading has been introduced to the viewer, this is mostly “lighter work” more easily removed from the main thread, which still does most of the heavy lifting via a single CPU core.
  • The last point rotated into a more general discussion on the viewer, threads, the future potential for removing coroutines and fibers in favour of “actual” threads, etc. Please refer to the last 10-15 minutes of the video.

Grid-Wide WebRTC Deployment

  • This was targeting a March 2026 deployment, following the usual simulator-side deployment process (a selected RC channel or channels for the first deployment, followed by deployment to all remaining RC channels usually a week later, then a final deployment to the SLS Main channel, usually a week after that).
  • However, it now appears hat the deployment is likely to be delayed, although no specifics have been given on why or when. .

Next Meeting