2024 week #31: SL CCUG + TPVD summaries

Angel of Pain, July 2024 – blog post
The following notes were taken from:

  • My audio recording and chat log transcript of the Content Creation User Group (CCUG) meeting held on Thursday, August 1st, 2024.
  • My audio recording + the video recording by Pantera (embedded at the end of this summary) of the Third-Party Developer meeting (TPVD) held on Friday, August 2nd, 2024. My thanks to Pantera as always for providing it.

 

Table of Contents

Note that this is not intended as a full transcript of either meeting, but rather a summary of those topics discussed in terms of project LL have in progress feedback given to ideas / questions comments.

Meetings Purpose

  • The CCUG meeting is for discussion of work related to content creation in Second Life, including current and upcoming LL projects, and encompasses requests or comments from the community, together with related viewer development work. This meeting is held on alternate Thursdays at Hippotropolis.
  • The TPV Developer meeting provides an opportunity for discussion about the development of, and features for, the Second Life viewer, and for Linden Lab viewer developers and third-party viewer (TPV) / open-source code contributors to discuss general viewer development. This meeting is held once a month on a Friday, at 13:00 SLT at the Hippotropolis Theatre.
  • For both meetings: dates and times are recorded in the SL Public Calendar, and they re conducted in a mix of Voice and text chat.
  • The notes herein are a summary of topics discussed and are not intended to be a full transcript of the meeting.

Official Viewers Status

  • Release viewer: version 7.1.8.9375512768, formerly the Graphics Featurettes RC viewer dated June 5 and promoted June 10th.
  • Release channel cohorts (please see my notes on manually installing RC viewer versions if you wish to install any release candidate(s) yourself).
    • WebRTC Voice RC, version 7.1.9.10084807842, July 26.
    • Atlasaurus RC (object take options; improved MOAP URL handling), version 7.1.9.9981869229, July 22.
    • Maintenance B RC (usability updates / imposter changes) 7.1.9.9555137545, June 21.
    • Maintenance C RC (reset skeleton in all viewers), version 7.1.9.9469671545, June 14.

Upcoming Releases

  • The WebRTC RC viewer remains first in line for promotion to de facto release status.
  • It will most likely be followed by the Atlasaurus RC, although this currently has a higher then expected crash rate at present.

CCUG – Graphics / glTF

PBR Terrain Painting – Cosmic Linden

Summary
  • An in-development project. Current intent:
    • Provide a means to support the four PBR materials currently used in SL for “terrain painting”.
    • Will allow materials to be defined in their X,Y co-ordinates within a region by using a paint map, rather than having them defined by elevation defined in a height map. This will allow where grass or rock or stones or dirt, etc., appear within the region. providing much more flexibility in how terrain appears / changes.
    • Terrain painting will use the same permissions as terrain texturing (so if you have terraforming permissions, then tertian paining is possible; if you have the appropriate region permissions, you can define the PBR materials for the region.
  • Other points of note:
    • LL prefer to limit terrain painting to the four available slots at region revel, rather than allowing fully customisable swatches / slots at parcel level, as the latter presents “non-trivial issues” for terrain texture handling /loading.
    • Terrain painting will require a new entity to be introduced. Exactly what form this will take is still being discussed internally; it is unlikely to be a new asset type.
  • Much longer term options being considered for this capability might be to:
    • Allow prims to act as part of the terrain, inheriting the materials of the terrain, whilst still allowing the prim to be sized and shaped.
    • Perhaps allow the terrain within a region to be replaced by “something” else created externally to SL and then imported.
    • Neither of these ideas are currently being pursued beyond possible ideas / options.
Status
  • Cosmic has been carrying out some early internal testing on how terrain painting looks using the paint map and how it works in practice in terms of bandwidth and performance.
  • The initial results of these tests is described as “promising”.

Punctual Lights and Transmission / IOR – Geenz Linden

  • Punctual lights:
    • This a glTF extension that has recently been folded into the main specification, defining the use of lighting sources (house light, table lamps, street lights, etc.), including the potential for shadow casting from such light sources.
    • Geenz is working to implement punctual lights, but they will be tied to the node hierarchy for glTF scene imports.
    • The first iteration of the work will not include shadow casting, and will focus on point and spot lighting as defined in the glTF specification.
  • Transmission and Index of Reflection (IOR)  will provide:
    • Both refraction and “blurry” refraction suitable for things like frosted glass surfaces.
    • Dispersion, allowing chromatic aberration, allowing the RGB channels to “separate out” based on a certain factor.
    • Volume, allowing an object surface to be tinted at different surface thicknesses .
    • Geenz believes there is one significant bug left to resolve, relating to the scaling of the effect.

General Discussion

  • A request has been made for a “glTF FAQ” to be put together, based on the Lua FAQ that has been made available, and which is seen as extremely useful.
    • The request was specifically made for a glTF Scene Import FAQ, as this capability has the potential to have the biggest impact on SL in terms of content creation, as glTF scenes have the potential to cover multiple areas (e.g. object import, sounds, animations, node hierarchies, lighting, etc.).
    • However, such a FAQ / series of FAQs could allow creators to more fully understand what is being proposed / has been considered / might be excluded, etc.,  thus offering them the opportunity to make more informed suggestions / requests to hep move glTF projects forward.
    • This was seen by LL as something which should “definitely” be on the road map, but may take time to surface as much of what might be covered is still only being discussed / prototyped internally to see what is feasible, and so subject to change.
    • In the interim a set of questions posted to the Content Creation discord channel was suggested as a means to get the ball rolling in providing ideas as to what a FAQ / FAQs might address.
  • PBR individual material UUIDs accessible via llGetPrimitiveParams on non-full permission objects has been raised and is subject to being tracked and investigated.

TPVD – WebRTC Voice Update

Summary

  • Replacing the use of Vivox for Voice in SL with WebRTC communications protocol (RTC=”real-time communication”).
  • Benefits:
    • Move to a “defacto standard” for voice services, with features such as automatic echo cancellation, better noise cancellation and automatic gain control, etc., and offers much improved audio sampling rates for improved audio quality
    • WebRTC can be supplied within the viewer using a library and wrapper, ending the need for any additional third-party plug-in for Voice like SLvoice.exe, as supplied by Vivox.
    • Opens the door to adding new features and capabilities to SL Voice, some of which have been long-requested.
  • Care is being taking to address potential security issues (e.g. preventing eavesdropping, exposing users’ IP address (by using an internal proxy server), etc.).
  • Feature requests for WebRTC made via the WebRTC board on the SL Feedback Portal are being evaluated and some are being actioned, together with issues being investigated.
  • LL will be looking to Linux devs to help give feedback on how well WebRTC is working on their Linux viewers.

Status

  • The plan remains to try to promote the WebRTC RC viewer to release status ASAP, with the aim of having as many TPVs adopt it as possible prior to the back-end switch being thrown to move all simulators to only using WebRTC.
  • The work is at a point where there is just a “handful” of issues, with fixes most of them actually being tested by QA.  Some of these are transition issues related to moving between regions using Vivox and regions using WebRTC (or vice-versa).
  • LL hope to release the back-end support for WebRTC peer-to-peer and Group calls, which should remove some of the limitations with testing WebRTC.
  • Roxie Linden also noted some third party viewer users using Linux viewers have been having device/audio subsystem issues with WebRTC, and has offered to provide some assistance with these problems – with the caveat that she’ll need TPV developers to diagnose their issues and on the fixes.

In Brief (Both Meetings)

Combat 2.0

  • The updates to the SL Combat system (SLCS), otherwise known as “Combat 2.0” are now in a deployment phase.
    • After to prior attempt, the updates are now deployed to the BlueSteel simulator RC channel.
    • Providing no further issues are found, the updates (as part of the Summer Fun simulator update) will be deployed to he remaining RC channels on Wednesday, August 7th; and then to the SLS Main channel on on Tuesday August 13th.
    • In the meantime, those involved in Combat in SL and who wish to have their regions able to leverage the new capabilities can file a support ticket to have their region moved to a channel supporting Combat 2.0.
  • With Combat 2.0 becoming available, Linden Lab has announced the Combat 2.0 Promotion Partnership Programme has been launched.
    • The intention behind the Promotion Partnership Programme this is to give those actively involved in combat activities in Second Life the “opportunity to help us spread the word across the grid about Combat 2.0 in Second Life”.
    • In particular, this will see some of the LL combat regions (e.g. Concord and Lexington) a facelift and use them to showcase Combat 2.0, with participants in the Programme asked to donate free-to-use combat items for use in the regions.
    • In addition, participants will have their regions / communities included in a Combat section of the Destination Guide. There may be other benefits for participants as well.
    • Those interested can sign-up via this Google form.

2K Texture and PBR Materials Support and Bakes on Mesh

  • This is now an active project. However (and as previously indicated in these summaries), the work is more than just updating the Bake Service.
  • In particular, it will mean bringing the code for the appearance service back into the viewer codebase.  However, this will will yield two benefits:
    • It will make the code is easier to update in future.
    • Could potentially make it easier possible to add PBR materials support to Bakes on Mesh in the future (although some design work on what compositing PBR materials layers means).
  • It was noted that the priority is to get “PBR BOM” in place prior to any release of glTF scene import.

Additional Items

  • It has been reported that some auto-replies to Canny tickets do not always include any linked ticket.
    • For example: Beta grid: water “sandboxes” was raised in Canny, but closed as already tracked, but fails to publicly list the tracked issue – in this case Github archive issue #9258 (originally Jira BUG-231883).
    • It was broadly agreed that it would be useful for these replied to at least reference archived / accepted tickets from Jira – even if the tickets themselves cannot be views (e.g. as they relate to a security issue).
  • Viewer release process:
    • Brad Linden has been working on the new viewer Gitflow process and release branches.
    • As previously noted, the focus is on moving away from having multiple release candidate cohorts based on different codebases in flight, as has been the case since around 2012, and instead focus on a core Develop branch of the viewer, from which RC versions can be built – so each RC viewer is essentially a “snapshot” of the Develop Branch code, rather than being an entirely separate viewer to anything else in flight.
    • It is hoped the formal switch-over to this approach will commence with the Atlasaurus RC.
  • The Lab’s Linux viewer work currently resides within the Maintenance B RC viewer branch.
    • This is awaiting merging into the the main Development branch, and has encountered some issues with merging.
    • Once the merge has happened, and remaining issues dealt with, then packaging Linux builds for the viewer “could start happening some time after that” (so some time after the Atlasaurus viewer release).
  • The TPVD meeting included a general discussion on the future of LODs (Level of Detail):
    • As a part of glTF adoption, Linden Lab is looking at adopting the Microsoft LOD extension for glTF 2.0, one outcome of which could be the removal of the RenderVolumeLODFactor (RVLF) setting from the viewer’s Debugs.
    • It was noted that as manually setting RVLF has long been the means by which creators can hide issues with LODs (i.e. raise LOD and force the viewer into rendering the higher LOD instances of an object), removing the debug is going to the lead to a lot of poorly-made content being exposed, potentially leading to a lot of upset.
    • However, it was also noted a more standardised approach to LOD instances of objects is required, and adoption of the Microsoft glTF  extension is the means to achieve this, allowing content creators to better leverage LOD generation within tools like Blender.

Next Meetings

† 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 gathering of people every week. They are taken from my list of region visits, with a link to the post for those interested.

Visiting a further chapter of a never-ending story in Second Life

NeverendingSL: Souru Sosaeti, August 2024 – click any image for full size

Since 2021, Jayden Mercury has been creating  / writing stories involving settings he designs, sometimes on his own, sometimes with the assistance of others, and notecards which might be seen as chapter outlines or prompts, all under his Neverending banner.

While I have missed numerous segments, I did cover the start of the story when Jayden opened Adventures In Mad Wonderland in 2021 (see here for more). I then returned to it for Neverending – Sakura Tales (more here) and again for The Dark Tower (more here), after which I kind-of lost touch with things. I was therefore pleased to be recently able to visit the 13th chapter in the series NeverendingSL: Souru Sosaeti.

NeverendingSL: Souru Sosaeti, August 2024

Jayden’s settings often have a suggestion of pulling on the threads of literature and storytelling from times past in order to create a tale of its own. With Adventures In Mad Wonderland, for example, there was the obvious element of Dodgson’s stories as written under his pen name; with The Dark Tower there seemed to be multiple potential intertwining references: Stephen King, Robert Browning, Tolkien, and so on.

Here, the name of the setting appears to be taken from the Japanese term for Soul Society (aka “dead spirit world” or “spirit world”, Souru Sosaeti), where souls are said to reside whilst awaiting reincarnation.

NeverendingSL: Souru Sosaeti, August 2024

Whether the reference is meant literally or simply as a means of unfolding this chapter of Jayden’s story (or even as an oblique reference to the Japanime series BLEACH), I’ve no idea. Certainly, the introductory notecard gives the impression that there is a common thread linking this Soul Society with its namesake:

Souru Sosaeti, once bustling and lively, now lay shrouded in fog and surrounded by an eerie silence. The artist arrived in the harbour aboard his small boat, guided by his constant companion, the majestic phoenix. The bird of rebirth was more than just a symbol; it seemed to have a connection to this mysterious city, whose fate threatened to disappear into the mist.

– Introductory notecard for NeverendingSL: Souru Sosaeti

NeverendingSL: Souru Sosaeti, August 2024

Stranded, the artist has set-up home on the edge of the city, and among the tower of stacked trailer homes similar in nature (if on a smaller scale) to the one popularised by a certain E. Cline in his debut novel. And it is at his little retreat that the story opens, with an invite to sit and then explore the setting. As with previous iterations of the story, the setting is interactive, and visitors are encouraged to explore, take photos, discover – and to try to find the artist’s pen and paper in order to read on to see what happens next.

The story itself carries the sub-title The Artist and the Cards of Destiny. This appears to be a reference to a game within the setting which can be triggered by locating the local Experience and receiving the game HUD. The Experience trigger might take a little finding; all I’ll say is look for alley with the red lanterns and the gate at its far end. Locate it, and the Joker may have a challenge for you!

NeverendingSL: Souru Sosaeti, August 2024
Suddenly, the Joker appeared, emerging from nowhere with a diabolical grin and a theatrical voice that echoed through the deserted streets. ‘Ah, finally a curious wanderer,’ chuckled the Joker as he faced the artist. ‘Are you here to unravel the secrets of this city? 
The artist stepped back, startled by the Joker’s sudden appearance. Gathering his composure, he met the Joker’s gaze. ‘Who are you? What do you know about the disappearances?’ he demanded …
The Joker smiled mysteriously and replied, ‘Ah, that is a question for those who seek the truth. The city has many faces, each with its own stories to tell. Perhaps you will find the answers you seek if you find the four king cards. Are you ready for the challenge?

I’ll say no more on the game here – you can discover it for yourself when you find the “Joker’s gate”, as it were. So why not pay a visit to NeverendingSL: Souru Sosaeti and see what you might find on the ground  (and elsewhere!), both on foot and by way of theJoker’s challenge?

Slurl Details

En vacances à la Petite Provence d’Annisss in Second Life

Petite Provence d’Annisss, July 2024 – click any image for full size

In leafing through the Destination Guide recently, I happened across an entry for Petite Provence d’Annisss, a full private region setting leveraging the Land Capacity bonus, designed by Annisss Mathịṣ (annisss). Offering a mix of public spaces and rental properties (so some caution might be in order during wanderings to avoid invading someone’s privacy), it offers a good deal to see and appreciate and some pleasing opportunities for photography.

Visit a village in the south-east of France, have lunch at a restaurant with a sea view or enjoy its beaches and small isolated coves, visit its superb caves or come and enjoy the evenings at the Club.

– Petite Provence d’Annisss About Land description

Petite Provence d’Annisss, July 2024

A visit commences towards the west side of the region where a tall clock tower keeps watch over a channel cutting its way into the landscape. Perhaps this watery cutting and the bay at its eastern end may once have been a natural inlet, but where the banks may have once stood has been built up with walls and topped out with paving to provide space for local businesses, the town church, with the inlet becoming something of a small harbour, offering a safe haven to various craft which appear to enter via a separate channel.

Gathered behind the clock tower, the part of the town adjacent to the landing point carries hints of multiple locations – some of the buildings having a lean towards Tuscany; others seemingly plucked from rural France. It’s a mix that is pleasing to the eyes with cobblestones an paving run around and between the buildings, inviting feet to follow, while to the south a road sweeps down from the heights before performing a u-turn and ending as abruptly as it started have served its intent and brought visitors down to the golden sands of a beach whilst cupping one of the region’s restaurants in its arms as it does so.

Petite Provence d’Annisss, July 2024

The beach offers plenty of places and space to catch the sun, whilst a makeshift bar might allow sunbathers to quench their thirst when it is stocked and operating. For those who prefer, steps to one side of the clock tower offer a quicker way down from the landing point to the beach, and both the the steps and the road will direct wanderers to where a horse rezzer is also available should clip-clopping around the town appeal.

Across the channel, and linked to the clock tower by way of a bridge, the north side of town has fairly packed itself into a small island, the buildings shuffling together shoulder-to-shoulder is if in mutual protection. Between them might be found narrow streets and alleys that – as is so often the way with old towns – suddenly burst forth into a square or walk raised above a beach, offering places to sit and pace the time and / or steps down to the sands.

Petite Provence d’Annisss, July 2024

Follow the raised water front here down to where it overlooks the moorings for boats, and you cannot fail to find The Blue Note, the club mentioned in the About Land description. Sitting within the remnants and façades of a number of buildings and with its very roof the sky above, this a a place ready to host both DJs and live musicians alike, its dancefloor sitting above a tropical isle in miniature.

Reached by walking through the town and passing by the church and another restaurant, visitors can make their way to the region’s art gallery. Sitting with cliffs on three of its four sides, the gallery was hosting a exhibition of photography by Ludi Tarus at the time of my visit, with its courtyard area sporting various 3D pieces. Just to the south of the gallery are two blocky promontories, a narrow cove cutting between them. One of these promontories is home to a public baths, and those seeking it out might also notice there’s a path edging its way around the cliffs below it, offering access to the cove.

Petite Provence d’Annisss, July 2024

The second promontory is the location to one of the setting’s rental homes. Overlooking another cove-like beach sheltering between the rocky bluffs, this house looks across the sands to another headland marked by more rentals, and with another path running through it connecting the two baches along its shoreline. To be honest, I’ve not sure if this aspect of the island is intended to be open to the public; while it links directly to the the gallery and its courtyard, the only means to reach the footpath and the beached appears to be by taking a walk through the gardens of the rental houses. I wasn’t keen on doing this in case I was trapsing across private property, so I simply cammed  over and looked around.

Some of the cliffs dropping away to the harbour from the rentals and the gallery have waterfalls bursting out of them, suggesting the presence of a rocky aquifer. More to the point, for those who find it, there’s a stairway leading down to the base of some of these falls, where a bag of gifts awaits, together with the entrance to the cave mentioned in the About Land description.

Petite Provence d’Annisss, July 2024

Charming, quiet and with plenty of opportunities for photography, Petite Provence d’Annisss makes from a pleasing visit with plenty to seen and photograph.

SLurl Details

2024 SL SUG meetings week #31 summary

The Magic Hour, July 2024 – blog post

The following notes were taken from the Tuesday,  July 30th, 2024 Simulator User Group (SUG) meeting. They form a summary of the items discussed, and are not intended to be a full transcript, and were taken from my chat log. Pantera videoed the meeting, and the recording is embedded at the end of this piece – my thanks, as always, for her work.

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.
  • These meetings are conducted (as a rule):
  • 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.

Simulator Deployments

  • The SLS Main channel was restarted on Tuesday, July 30th 2024.
  • On Wednesday, July 24th:
    • The BlueSteel RC is due to (again) receive Summer Fun simulator update, which includes the initial Combat 2 updates from Rider Linden. Hopefully this third attempt will see it stick.
    • The remaining RC channels will be restarted.

SL Viewer Updates

  • Release viewer: version 7.1.8.9375512768, formerly the Graphics Featurettes RC viewer dated June 5 and promoted June 10th.
  • Release channel cohorts (please see my notes on manually installing RC viewer versions if you wish to install any release candidate(s) yourself).
    • WebRTC Voice RC, version 7.1.9.10084807842, July 26.
    • Atlasaurus RC (object take options; improved MOAP URL handling), version 7.1.9.9981869229, July 22.
    • Maintenance B RC (usability updates / imposter changes) 7.1.9.9555137545, June 21.
    • Maintenance C RC (reset skeleton in all viewers), version 7.1.9.9469671545, June 14.

WebRTC Voice Update

Summary

  • Replacing the use of Vivox for Voice in SL with WebRTC communications protocol (RTC=”real-time communication”).
  • Benefits:
    • WebRTC is something of a “defacto standard”, with features such as automatic echo cancellation, better noise cancellation and automatic gain control, etc., and offers much improved audio sampling rates for improved audio quality
    • WebRTC will be supplied within the viewer using a library and wrapper. This will mean no requirement to run a third-party voice plugin (SLvoice.exe, as supplied by Vivox) going forward.
    • The switch to WebRTC also opens the door to adding new features and capabilities to SL Voice, some of which have been long-requested.
    • Care is being taking to address potential security issues (e.g. preventing eavesdropping, exposing users’ IP address (by using an internal proxy server), etc.).
  • Feature requests for WebRTC made via the WebRTC board on the SL Feedback Portal are being evaluated and some are being actioned, together with issues being investigated.
  • LL will be looking to Linux devs to help give feedback on how well WebRTC is working on their Linux viewers.

Status

  • The plan remains to potentially make a switch-over to WebRTC on the back-end in August.
  • This is dependent upon third-party viewers picking up the WebRTC updates from LL and incorporating them.
  • During the transition period, viewers will connect to either Vivox or WebRTC voice, depending on the service available to them. As such most voice services should be uninterrupted.
  • HOWEVER, during the transitional period, there will be some short-term issues around peer-to-peer, Group and ad-hoc voice connections between those on regions running the two different voice services (Vivox and WebRTC).

In Brief

  • A further conversation on Lua(u), including supported data types and whether an integer type will be added to LL’s implementation. The answer may be no, going on the Lua FAQ.
  • There is a reported uptick in vehicle region crossing issues in the Blake Sea regions, but more than anecdotal reports are required (e.g. information such as timestamps, agents, and regions need to be properly reported which incidents occur.
  • Changes related to avatar teleports are due to be included in the Picnic simulator update, which should start deployment as Summer Fun reached the Main SLS channel (or shortly thereafter).
  • Monty Linden has some event-queue fixes to bring to life, and would like to get them up on Aditi as a pilot test for various viewers.
This is a re-writing of a fundamental service between viewer and server.  *Not* the LSL scripting event queue – communications event queue between viewers and simulators (we have lots of things called ‘event queue’).  [The] discussion is deep inside this [forum] topic for the interested.

– Monty Linden

  • Concern was raised over recent changes to llSensor doubling the number of objects returned, causing some scripts to receive more data than they are designed to manage, resulting in increased stack heap collisions.
    • It was requested that when fundamental changes are made to a function like this, they are used within a new function, rather than changing the existing function. This sparked a conversation on what a new llSensor function (“llSensorPlus” or whatever) might include / work.
    • It was further equested that if llSensor is being updated, news flags / filters are added (e.g. HAS_SIT_TARGET, TOUCH_EVENT, SOUND_EMITTER).
    • A Canny feature request on the latter was requested, with examples of how the flags might be used.

† 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.

2024 SL viewer release summaries week #30

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

Updates from the week through to Sunday, July 28th, 2024

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.
  • Note that for purposes of length, TPV test viewers, preview / beta viewers / nightly builds are generally not recorded in these summaries.

Official LL Viewers

  • Release viewer: version 7.1.8.9375512768, formerly the Graphics Featurettes RC viewer dated June 5 and promoted June 10th.
  • Release channel cohorts:

LL Viewer Resources

Third-party Viewers

V6-style

  • No Updates.

V1-style

  • Cool VL Viewer Stable branch updated to version: 1.32.2.7 (PBR) on July 27 – release notes.

Mobile / Other Clients

  • Mobile Grid Client version 1.25.1298, July 25 – release notes.

Additional TPV Resources

Related Links

Space Sunday: observatories, rockets and capsules

An artist’s impression of the Chandra X-Ray Observatory orbiting Earth. Credit: NASA

Twenty-five years ago, on July 23rd, 1999, the Chandra X-Ray Observatory was launched aboard the Space Shuttle Columbia as a part of STS-93. At the time of its launch, it was the third of NASA’s four Great Observatories, the other three being the Hubble space Telescope (HST), launched in 1990; the Compton Gamma Ray Observatory (1991–2000) and the Spitzer Space Telescope launched after Chandra, in 2003 and operating through until 2020.

Originally called the Advanced X-ray Astrophysics Facility (AXAF), Chandra can trace its history back to the mid-1970s. Originally intended for operations in an orbit similar to that of Hubble, thus making its servicing and upgrade possible using the space shuttle, the observatory went through various design changes during the 1980s and 1990s, with its overall mission being redefined in 1992. This saw Chandra have four of it planned 12 mirrors eliminated from the telescope, together with two of the six planned science payloads. To compensate for this, the telescope’s mission was revised so that it could be placed in an orbit well above Earth and well clear of the planet’s radiation belts, allowing it to have a clearer view of deep space.

The Chandra X-ray observatory, wrapped it its thermal protection blanket, attached to its IUS space launcher, images from the space shuttle Columbia shortly after the latter had deployed them from its payload bay, July 23rd, 1999. Credit: NASA

Renamed in 1998 in honour of Nobel Prize-winning astrophysicist Subrahmanyan Chandrasekhar, Chandra was deployed from Columbia’s payload the same day as it launched, attached to a 2-stage Boeing  Inertial upper Stage (IUS) space launch system. Together, they represented the heaviest payload ever carried to orbit by the shuttle system, massing 22.75 tonnes.

Once the shuttle had moved to a safe distance, the IUS first stage fired for 125 seconds, boosting Chandra away from Earth (and beyond any capacity for it to be upgraded or serviced), followed by a 117-second burn of the IUS upper stage motor. The later placed Chandra into a geocentric orbit with a perigee some 14,307.9 km from Earth and an apogee of 134,527.6 km, roughly one-third of the way to the Moon.

Following a short period of commissioning, Chandra started returning data to Earth within a month of launch, and has continued to do so almost without interruption through to 2024 – although its primary mission period was placed at a conservative 5 years. Through this time, only one system on board has suffered significant damage, but it is still operational alongside the other science instruments, and only one significant glitch – lasting three days in October 2018 – when the observatory entered a safe mode as a result of a short-term issue with one of the gyroscopes used for pointing it at targets and holding it steady during observations. All science functions were fully restored once the issue had been resolved.

Chandra X-Ray Observatory diagram. Credit: NASA Chandra Space Centre

Over the years, Chandra’s import and discoveries have tended to be overshadowed by Hubble and, more recently, the James Webb Space Telescope (JWST). These have included the first observations of a “mid-sized” black hole, claimed to be the “missing link” between stellar-sized black holes and the super massive black holes found at the centres of galaxies; making one of the most accurate measurements of the Hubble constant; observing the most massive X-ray flare yet recorded from the super massive black hole Sagittarius A* (pronounced “Sagittarius A star”) at the centre of our galaxy; and making possibly the first observation of an object (possibly an asteroid) crossing the black hole’s event horizon; and also making potentially the first indirect observations of an exoplanet in another galaxy.

In additional to all of this, Chandra has supported Hubble in making significant observations of the planet and dwarf planets and moons in our own solar system, and also like Hubble, has benefitted the work of early career researchers, helping them to become established in the fields of astronomy, astrophysics and space science.

To mark Chandra’s 25th anniversary, NASA has issued a wallpaper featuring 25 of Chandra’s most stunning images captured in the X-ray wavelengths. The official announcement of the images can be found on the Chandra website, and the images are previewed in the video below, as well as being available for download as a wallpaper mosaic for computers.

Sadly, the celebration is a potentially bitter-sweet affair. Currently, Chandra has the ability to remain operational for at least another decade – possibly long enough to see the European Space Agency launch what might be seen as its successor, the Advanced Telescope for High-ENergy Astrophysics (Athena), which is due to be launched sometime in the early-to-mid 2030s. Unfortunately, this is may not now be the case; Chandra could cease operations within the next 12 months.

The reason for this is that NASA’s space science budget is being tightly squeezed, largely as a result of the rising costs associated with Project Artemis and returning humans to the surface of the Moon. In 2024, the space science budget had been due to get a US $500 million boost. Instead, Congress actually cut it by that amount. For 2025, Congress is looking to cut NASA’s space science directorate’s budget by almost US $1 billion.

Cassiopeia A, a supernova remnant 11,000 light-years away, imaged in X-ray & Infrared light, with the x-ray image produced by Chandra. Credit: NASA / ESA / CXC

As a result NASA has been looking at programmes to cut – and Chandra has been one to top the lists, with NASA management suggesting its US $67 million budget could be cut by 40%. The reaction to this was swift, with those managing Chandra both from within and without NASA pointing out that a cut that large would effectively end Chandra’s science mission forthwith. Thus, in an attempt to find some middle ground that would allow both Chandra and Hubble to continued to be operated, various ideas were put forward as to how Chandra’s costs could be reduced and / or how both the Chandra and Hubble science missions could be redefined, in order to allow both to continue for the next few years.

In response to this efforts, NASA authorised an Operations Paradigm Change Review (OPCR) to look at all of the suggested options and make a determination on their viability to reduce costs. The findings of this review were presented on the very day of the 25th anniversary of Chandra’s launch, during a meeting of the Astrophysics Advisory Committee, or APAC, the body, chartered to provide advice to NASA’s astrophysics programme. And the news was not good.

Having reviewed all the options weighted the costs and saving, the OPCR has essentially concluded that while they believe Chandra could be operated a a budget smaller than its present allocation, it would still require funding beyond what the new science directorate budget can afford – at least not without putting programmes and missions outside of it and Hubble at risk. Therefore, it may not be feasible for Chandra to continue from 2025 onwards.

When a massive star exploded in the Large Magellanic Cloud LMC), a satellite galaxy to the Milky Way, it left behind an expanding shell of debris called SNR 0519-69.0. This image shows a composite of the debris gas field using Chandra to reveal the multimillion degree gas cloud (blue) and Hubble to reveal the expanding edge of the explosion (red) and the stars of the The outer edge of the explosion (red) and stars of the LMC. Credit: NASA / STScl / CXC

The OPCR findings drew some frustration from APAC members, in part because APAC was itself excluded from any involvement in the OPCR process and was not given the opportunity to review the report ahead of the announcement. In response, OPCR members stated the review had to be handled on a short-term turn-around so that if a way forward could be identified and which offered a reasonable compromise on costs, it had to be published rapidly, so as to allow NASA and the agencies responsible for both Chandra and Hubble (the Chandra X-Ray Centre and Space Telescope Science Institute) to assess the overall feasibility ahead of staff layoffs across both programmes that are due to commence in September 2024.

The report does not automatically seal Shandra’s fate, options may yet arise where it is allowed to continue – such as through the support of one or both of the houses in Congress – but right now, it does make Chandra’s future appear to be grim.

SpaceX Resumes Starlink Flights with Falcon 9; Announces Dragon Splashdowns to Move back to US West Coast

In my previous Space Sunday article, I noted that SpaceX Falcon 9 flights were suspended pending the results of a Federal Aviation Administration (FAA) Mishap Investigation relating to the loss of a Falcon 9 upper stage and its Starlink payload during a July 11th/12th launch.

On July 25th, SpaceX announced the root cause of the loss had been traced to fatigue causing a a crack in a redundant “sense line” in the upper stage, resulting in “excessive cooling” of engine components, causing the rocket motor to fail. A near-term fix – removing the redundant line – has been identified pending a more in-depth fix, and this has been enough for the FAA to clear Falcon 9 to resume commercial launches. As a result, on July 27th, a Falcon 9 lifted-off from Kennedy Space Centre’s Launch Complex 39A, carrying 23 of the company’s own Starlink satellites.

One Falcon 9 stands on the pad at Space Launch Complex 40 while another lifts off from nearly by Launch Complex 39A early July 27th, 2024, marking the resumption of non-NASA related Falcon 9 launches. Credit: SpaceX

Whilst successful, the flight does not mean Falcon 9 flights to the International Space Station will necessarily immediately resume. NASA still plans for a “rigorous certification” of Falcon 9 and the software associated with the sensor to which the sense line had been connected, once SpaceX has completed all modifications to the upper stage of the vehicle. As such, the agency is not committing to going ahead with the launch of the 4-person Crew 9 mission to the ISS, due to lift-off on August 18th, 2024. However, whether this also means the planned launch of an automated Cygnus resupply vehicle to the station due on August 3rd remains on hold, is unclear; NASA’s had previously indicated all Falcon 9 flights to the ISS would be suspended pending re-certification, but following the July 27th launch, the agency specifically only mentioned the Crew 9 flight.

In a separate press release, SpaceX has indicated it will be switching Dragon splashdowns to off the west coast of the United States from 2025 onwards, rather than bringing them down off the Florida coast.

The decision is in the wake of significant pieces of debris from the Dragon vehicle’s trunk (effectively the power and propulsion “service module”) surviving re-entry into the denser atmosphere to fall to ground in places as wide apart as Australia, North Carolina and Saskatchewan. The change means that from 2025, instead of being used in the initial de-orbit burn and and then jettisoned from the Dragon capsule, which then performs its own final de-orbit burn, leaving the trunk to decay in its orbit and later re-enter the atmosphere a burn up, dragon vehicles will remain attached to the trunk throughout both de-orbit burns, with the trunk being jettisoned just before both reach the re-enter interface.

This means the the capsule and trunk will come down over the Pacific Ocean, rather than passing over the North American continent, with any trunk debris surviving its re-entry hitting the water somewhat up-range from where the capsule will splash down under parachutes.

Boeing Starliner Remains at ISS Amidst More Media Alarmism

The past week saw NASA provide an update on the Boeing Starliner situation, in which the CST-100 Calypso remains docked at the International Space Station, where it has been for some 50 days, despite the first planned crewed flight of the vehicle only being intended to last some 6 days in total following its launch in early June 2024.

As noted previously in these pages, issues occurred during the vehicle flight to the ISS, when it suffered a series of thruster failures – an issue that has been dogging the Starliner programme for some time. While the vehicle, carrying astronauts Barry “Butch” Wilmore and Sunita “Suni” Williams managed to safely docked with the ISS, its return has been repeatedly delayed leading to highly inaccurate references in the media and on social media to the idea that Wilmore and Williams are somehow “stranded” in space.

A time-lapse photograph of the CST-100 Starliner Calypso docked at the International Space Station as both orbit the Earth. Credit: NASA

This is far from the case, again as I noted as recently as June 30th (see: Space Sunday: of samples and sheltering); the delays have been purely to allow Boeing and NASA to conduct further comparative tests between systems on the ground and those aboard the Starliner docked at the ISS to better understand precisely where the issue lies. These tests are necessary inasmuch as the service module of the vehicle – which is home to the problematic thruster systems –will not be returning to Earth, but will burn-up in the atmosphere when Calypso does eventually make its return. Ergo, keeping it in space and carrying out these tests is the only means of verifying the findings of on-going Earthside investigations.

With further tests taking place over the weekend of July 27th/28th, both NASA and Boeing believe they are honing into on the root cause. Starliner has four clusters of thrusters gathered around the outside of the service module. These clusters, comprising a mix of four larger orbital manoeuvring and attitude control (OMAC) thrusters and smaller reaction control system (RCS) thrusters (28 in total, of which only one has completely failed) are housed in protective units call “doghouses”. Both the OMACs and RCS units are required during flight operations, often firing in sequence.

What appears to be happening is that under orbital conditions, pulse-firing the RCS thrusters (a rapid series of short, sharp burst of firing) immediately following the use of the OMACs thrusters in a doghouse can cause the temperatures inside the unit to rise well above anticipated levels. This causes the helium purge valves to leak, causing problems.

Boeing’s Starliner capsule is seen docked to the International Space Station in this zoomed-in and slightly pixelated view of an image captured by Maxar Technologies’ WorldView-3 satellite on June 7th, 2024. Credit: Maxar Technologies

Because of this, engineers, together with Wilmore and Williams, have been looking to make operational changes to how the OMCS and RCS system are used – such as by reducing the number of pulses the RCS makes when fired, or by reducing the number of times OMACs and RCS need to be fired either individually or in sequence, thus preventing the temperature spikes within the doghouse units.

During the update, NASA clearly stated that if the July 27th/28th tests yield good results, then an agency-level review on clearing Starliner for a return to Earth could take place within a week of the test results being confirmed. However, this still didn’t stop some media continuing to report Wilmore and Williams as continuing to be “stuck” or “stranded” in orbit, because drama maketh the headline.