Space Sunday: Axiom 3 and an little round-up

A mini league of nations in space: the Expedition 70 (back) and Axiom 3 (front) crews. From left to right: Michael Lopez-Alegria (AX-3); Satoshi Furukawa (JAXA/Ex 70); Loral O’Hara (NASA/Ex 70); Walter Villadei (AX-3); Konstantin Borisov (Roscosmos/Ex 70; Andreas Mogensen (ESA / EX 70, with microphone); Oleg Kononenko (Roscosmos / Ex 70 – in orange); Alper Gezeravcı (AX-3); Jasmin Moghbeli (NASA / Ex 70); Marcus Wandt (Ax-3) and Nikolai Chub (Roscosmos / EX 70). Credit: NASA TV

The first all-European crewed space mission is currently underway at the International Space Station (ISS) – albeit through the auspices of two US-based companies and NASA.

The Axiom AX-3 mission lifted-off from Launch complex 39A at Kennedy Space Centre, Florida at 21:49 UTC on January 18th, carrying a crew of four aboard the Crew Dragon Freedom. As its name suggests, the mission is the third crewed flight to the ISS undertaken on a private basis by Axiom Space, utilising the launch capabilities of the SpaceX Falcon 9 booster and Crew Dragon capsule.

Delayed by 24 hours to allow for additional pre-flight checks, the launch was perfect, carrying mission commander and former NASA astronaut Michael López-Alegría, representing Spain, his nation of birth (he holds dual Spanish and American citizenry), vehicle pilot Walter Villadei of the Italian Air Force, making his first fully orbital flight into space, having previously flown as a member of Italy’s sub-orbital flight with Virgin Galactic, and mission specialists Marcus Wandt, a reservist in the European Astronaut Corps, and Turk Alper Gezeravcı who becomes his country’s first astronaut.

The Falcon 9 booster carrying Crew Dragon Freedom and AX-3 crew, rises from Launch Complex 39A at Kennedy Space Centre, January 18th, 2024. The tall structure to the right of the Falcon launch pad is the new launch support tower for the SpaceX Starship / Super Heavy combination. Credit: Future / Josh Dinner

Following launch, the Falcon 9’s first stage made a successful landing at Cape Canaveral Space Force Base south of Kennedy Space Centre, whilst the dragon went on to a successful orbital insertion and separation from the booster’s upper stage, to start a 36-hour gentle rendezvous with the ISS, the Crew Dragon gently raising its orbital altitude to match that of the ISS before closing to dock with the station.

The latter took place at 10:42 UTC on Saturday, January 20th, 2024, when Freedom latched on to the forward docking port on the station’s Harmony module and pulled into for a hard dock. 90 minutes later, with post-flight checks completed and the AX-3 crew able to change from their pressure suits to less restrictive flight wear, the hatches between station and capsule were opened, and López-Alegría led his crew out to be greeted 7 members of ISS Expedition 70.

Freedom, complete with Axiom Space logo, contacts the docking mechanism at the forward port of the ISS Harmony module, prior to being pulled into a hard dock, January 20th, 2024. Credit: NASA TV

The mission – which is due to last some 14 days at the station – marks the sixth orbital flight for López-Alegría. He first flew in 1995 on the second mission of the US microgravity laboratory, a research module carried within the payload bay of the space shuttle prior to the development of the ISS.  He subsequently flew on STS-92 and STS-113 whilst the ISS was being constructed, prior to serving as ISS mission commander for the Expedition 14 rotation in 2006-2007. He also served as the head of NASA’s ISS Crew Operations office (1995-2000) and is also a former NASA aquanaut, serving on the first NASA Extreme Environment Mission Operations (NEEMO) crew aboard the Aquarius underwater laboratory, in October 2001. Having joined Axiom in 2017, he first flew aboard Crew Dragon in the AX-1 mission in April 2022.

The remaining three AX-3 crew are all orbital rookies making their first stay in space. However, their presence on the ISS means that the station now has its largest ever international crew, with two US citizens, three Russians, a Dane, and a Japanese astronaut making up the ISS expedition crew.

We’ve got so many nationalities represented on board, and this is really symbolic of what we’re trying to do to open it up not only to other nations, also to individuals to researchers to continue the great work that’s been going on onboard the ISS for the last two decades plus.

– Michael López-Alegría

While aboard, Ax-3 crewmembers will live and work alongside the station’s current residents, performing experiments and research started with the first two Axiom missions, with a focus on human spaceflight and habitability in microgravity environments, a goal very much in keeping with international research on the station and of particular interest to Axiom Space, which plans to operate its own orbital facilities, initially docked their own modules with the ISS prior to separating them to become a dedicated orbital facility when the ISS is decommissioned in 2030.

In addition, the AX-3 crew will conduct research into AI and human health – the mission includes an experiment from Turkey called Vokalkord, which uses AI algorithms to diagnose several dozen diseases by analysing a cough or someone’s speech -; experiments with high-strength alloys, with implications for in-space construction and assemblies as well as other biology and physics-related work.

China’s SpaceX? Sort-of, But Not Exactly

The Zhuque-3 VTVL-1 test article during it’s first lift-off / landing test at the Jiuquan spaceport, China, January 19th, 2024. Credit: Landspace

A glance at the image above might initially suggest it is one from the history books: an early flight test of the Falcon 9 reusable first stage out of SpaceX’s flight test centre at McGregor, Texas. However, the landscape isn’t entirely in keeping with that of McLennan and Coryell counties, Texas, whilst a closer look at the booster might reveal something of the truth, thanks to the large red flag painted thereon.

The craft is in fact the Zhuque-3 vertical take-off, vertical landing unit 1 (VTVL-1), a test article developed by Chinese private sector launch start-up Landspace. It is intended to pave the way for a semi-reusable launch vehicle called Zhuque-3 (“Vermillion bird-3”), which is intended to have the same overall launch capabilities as Falcon 9 (up to some 21 tonnes to low-Earth orbit (LEO) when flown fully expendable, and between 12.5 and 18.4 tonnes when the first stage is to be re-used). However, to call it an outright “Falcon 9 clone”, or a “copy” of SpaceX’s work would not be strictly accurate.

Whilst there is much about Falcon 9 which likely influenced the Zhuque-3 design, the fact is that its looks are as much about the old axiom, form follows function, as much as any “copying” of SpaceX; the overall design and appearance of the booster and its landing legs are simply the result of their form being the most logical to meet the requirements of their functionality (hence why, in aircraft design, for example, vehicles designed for a specific task by different nations can often end up appearing quite similar, even if not direct copies).

Similarly, and while SpaceX fans have pointed to Landspace also “copying “SpaceX in the use of stainless steel for the rocket and the use of methlox – liquid methane/liquid oxygen – engines (all of which are used by SpaceX in their Starship / Super Heavy combination), the fact is that the Chinese commercial space sector has been dabbling in methlox propellants since around 2015, pre-dated Starship development, whilst the use of stainless steel in the Zhuque-3 rocket is perhaps more the result of Landspace already having experience in fabricating rocket cores out of it via their operational Zheque-2 launch vehicle than any attempt to copy someone else’s work. While also is not to say that SpaceX haven’t cut a path that other companies around the world can follow.

The first (expendable) launch of Zhuque-3 is expected in 2025, and will mark a further expansion of China’s commercial space sector, in which Landspace is just one of a number of companies developing or operating launch systems and developing semi-reusable launchers. Just how much competition there is already in the market is perhaps illustrated by the fact that some news agencies reported on the Zhuque-3 test flight by using video footage of the second test carried out by China’s iSpace company of their Hyperbola-2 VTVL test vehicle, which took place in December 2023!

Such is the broad and rapid pace of reusable booter development in China’s commercial space sector, footage similar to this video showing the first VTVL test of the iSpace Hyperbola-2 booster VTVL test article (and which I covered at the time), was mistakenly used by some news outlets to report on the January 19th Zhuque-3 VTVL test. Video credit: iSpace via SciNews

Overall, the Chinese commercial market is as richly diverse as the developing commercial space sector in the US, and with China enjoying good trade relations with a number of Asian countries looking to develop space-based capabilities, there is good potentially for interest in using these vehicles to gain something of an international footprint.

Three Mini Mission Updates

Peregrine Mission One

Astrobotic’s Peregrine Mission One (aka Peregrine or Peregrine One), is now officially over. As I’ve previously reported, the NASA-funded private mission to put a lander on the surface of the Moon under the agency’s Commercial Lunar Payload Services (CLPS) programme, got off to a flying start with a January 8th, 2024 ride to TLI (trans-lunar injection) aboard the maiden flight of United Launch Alliance’s Vulcan Centaur rocket. However, some time after the separation of the lander from the rocket’s Centaur upper stage, a propellant leak occurred which resulted in the lander entering an uncontrolled tumble, shifting it away from its rendezvous with the Moon and starving it of the propellants needed to make a landing even if it could get there.

The Peregrine Lander, now lost. Credit: ULA

On January 14th, the lander crossed the orbital path of the Moon, and shortly after that, gravity took over and started pulling it back towards Earth. As a result, on January 18th, 2024, the craft re-entered the atmosphere over the South Pacific, where it proceeded to burn-up. However, analysis of data returned by the craft as it headed back to Earth revealed a possible cause of the propellant system failure, as related by Astrobotic CEO John Thornton during a press briefing on January 18th:

The valve separating the helium and oxidiser in the lander’s propulsion system did not re-seal properly. This allowed a rush of helium to enter the oxidiser tank, raising the pressure to the point where the tank ruptured.

This knowledge actually helped in securing the lander’s final demise: by characterising the nature and direction of the leak, together with the rate of loss of remaining gases, flight engineers were able to put the lander into a more controlled entry into the atmosphere, pushing itself farther over the South Pacific to avoid the risk of any components surviving re-entry from falling over land masses.

Despite the loss, Astrobotic remain upbeat about their next lunar mission – again supported by NASA – which will hopefully see the company’s Griffin lander deliver NASA’s VIPER rover to the Moon in 2024.

 Japan’s “Sniper” Achieves Lunar Landing But Not Without Issues

Meanwhile, Japan became the 5th country to successfully land a spacecraft on the Moon when their Smart Lander for Investigating Moon (SLIM)  touched-down near Shoji Crater close the Moon’s equator at 15:20 UTC on January 19th, 2024 (00:20 on January 20th, Tokyo time).

Launched in September 2023 alongside Japan’s X-Ray Imaging and Spectroscopy Mission (XRISM), SLIM – nicknamed “Moon Sniper” – took a leisurely trip to the Moon, spiralling slowly away from Earth to enter lunar orbit on Christmas Day 2023, orbiting the Moon at an altitude of just under 600 km. The orbit was then eased down to around 50 km, and than further reduced to a point just 20 km above the lunar surface, where the descent proper began, curving the lander in towards its target zone. At 5 km above the Moon, the descent became vertical, with livestream telemetry showing everything to be spot-on.

An artist’s impression of Japan’s SLIM lander descending towards the surface of the Moon. Credit: JAXA

At 50 metres above the surface, the vehicle translated in flight, moving horizontally to position itself directly over a pre-planned landing point, before descending to a successful soft-landing. It was this final manoeuvre which formed one of the key goals for the mission. Usually, landing zones for robot vehicles are planned well in advance and encompass  elliptical areas around 10 km wide and a couple of dozen in length. However, SLIM carried modified facial recognition software which allowing it to monitor its descent and adjust its position autonomously by matching surface features scanned by its cameras with high-resolution images of the landing site stored in its navigation system. At 50 metres, the craft was able to confirm its desired landing point – an area just 100 metres across by contrast to normal landing zones and then manoeuvre itself to a landing with it.

But while the landing was successful, it became clear something was wrong; there was no sign that the battery system powering the craft was receiving energy from the lander’s solar array. After investigating the issue for a number of hours, engineers at the Japan Aerospace Exploration Agency (JAXA) concluded that while SLIM had landed within the desired zone, for some reason its wasn’t correctly oriented for its solar array to receive sunlight, leaving it trapped on battery power, which would expire within hours.

Prior to completely exhausting the battery, attempts were made to put the lander in a dormant mode, the hope being that as the Moon moves in its orbit over the next few days, sunlight will fall onto the lander’s solar array, and power will start to be generated, allowing to to wake itself up and start surface operations.

A Model of the tiny LEV-2 lunar rover, called SORA-Q, in its spherical form. The 250 gram rover is equipped with camera systems (the yellow/tan elements visible inside it), and can change shape by opening its two halves to form a more cylindrical shape. It was designed to operate independently of the SLIM lander for around 2 hours after landing, but at the time of writing, it is not clear what data, if any had been received from it. Credit: JAXA / Doshisha University / Sony

While both of the mini-rovers – LEV-1 and LEV-2 are thought to have successfully reached the surface of the Moon, at the time of writing, their status is unknown.

Even if the lander cannot recover itself with the aid of sunlight, SLIM is a very successful mission: demonstrating the means to make landings on other bodies with near pinpoint accuracy will be of vital importance in unfolding efforts to explore and develop the Moon and to further explore Mars both robotically and (eventually) with human missions.

Ingenuity Suffers Communications Glitch

NASA’s Mars Helicopter Ingenuity completed its 72nd flight on January 18th, 2024, but not without incident. Lifting-off from sand dunes some 800-900 metres from the Mars 2020 rover Perseverance, the helicopter was engaged in a brief “pop-up” test flight intended to see it climb vertically to 12 metres altitude, hover, and then descend back to a landing.

Telemetry received via the rover indicated that the first elements of the flight were successful – but all contact was lost during the descent phase. For a time it was unclear if the use was a communications drop-out, or something more drastic, and with Perseverance out of direct line-of-sight with the helicopter, determining which was initially difficult.

In recent flights Ingenuity has been ranging ahead of the rover, acting as an airborne scout for possible driving routes. At the end of its 71st flight, the helicopter suffered a slight issue, causing a premature landing somewhat further than planned from the rover; as a result this flight was to confirm all flight systems and software were operating nominally, prior to resuming normal operations and allowing the helicopter to come back closer to the rover.

Following the loss of signal, telemetry was reviewed to see if it revealed any indication of a serious issue and possible vehicle loss. None was found, so engineers determined it was likely a comms problem and ordered Perseverance to change its communications parameters and lengthen the time periods it listens for Ingenuity’s transmissions.

The relative positions of Ingenuity and Perseverance, January 19th, 2024. Credit: NASA/JPL

As a result, in the early hours of January 21st (UTC), communications were once again established, allowing more data on the final phase of the flight to be relayed to Earth for study. Currently, Ingenuity remains grounded, and mission planners are considering ordering Perseverance to drive a point where it can see Ingenuity to allow for a visual inspection of the helicopter.

2024 week #3: SL CCUG and TPVD meetings summary

Blue NANA Land, December 2023 – blog post

The following notes were taken from my audio recording and chat log transcript of the Content Creators User Group (CCUG) meeting held on Thursday, January 18th, 2024, and the chat log transcript and video of the Third-Party Viewer Developer (TPVD) meeting held on Friday, January 19th, 2024. My thanks as always to Pantera for recording the TPVD meeting and providing the video, which is embedded at the end of this article.

  • 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 viewer development work.
  • 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  the third or fourth Friday, at 13:00 SLT at the Hippotropolis Theatre.
  • In regards to both meetings:
    • Dates and times are recorded in the SL Public Calendar.
    • Commence at 13:00 SLT on their respective dates.
    • Are conducted in a mix of Voice and text chat.
    • Are open to all with an interest in either content creation or viewer development.
  • The notes herein are a summary of topics discussed and are not intended to be a full transcript of either meeting.

Please note: my audio recording of the CCUG suffered a glitch in writing to disk. Whilst over an hour of audio was apparently recorded according to Audacity, only 22 minutes was actually saved to disk. As the meeting utilised voice, the loss of around half the audio means that response to questions and generally commentary from the Lab was lost. Therefore, these notes only reflect the section of the meeting which did save for playback.

Official Viewers Status

No updates through the week, leaving the current crop of official viewers as:

  • Release viewer: version 7.1.2.7215179142, formerly the glTF PBR Materials Maintenance RC, issued December 15, promoted January 8, 2024 – numerous bug fixes and improvements – NEW.
  • Release channel cohorts (please see my notes on manually installing RC viewer versions if you wish to install any release candidate(s) yourself).
    • glTF PBR Materials Maintenance-2 RC viewer, version 7.1.3.7467259489, issued January 12, 2024.
    • Maintenance-W RC viewer, version 7.1.3.7453541295, January 9, 2024 – bug and crash fixes.
    • Maintenance X RC, version 7.1.1.7088410646, December 7 – usability improvements.
    • Maintenance Y RC, version 6.6.17.6935642049, issued November 21 – My Outfits folder improvements; ability to remove entries from landmark history.
    • Emoji RC viewer, version 6.6.15.581551, August 31.
  • Project viewers:

General Viewer Notes

  • The glTF Maintenance 2 viewer includes, among other things, less blue tint to improve the general environment appearance.
  • The Emojis viewer is finally on the path towards an RC update, and it is hoped that this will be the finally update for the viewer before it gets promoted to de facto release status.
  • There is concern that the viewer crash rate has been higher than usual over the last several releases, so it appears viewer-side engineering effort is to be put towards determining underlying causes and rectifying them in order to bring the rate back down.
  • Longer-term there will be further Inventory work, with additional flags being added to the viewer which will enable future additional Inventory-related functionality – but it is too early in the process to go into specifics.

Mac OS Requirements

  • The Mac OS requirements for the viewer are changing as a result of Apple ending security updates for OSX 11 and earlier.
  • Whilst Mac OS 11 will now be the minimum requirement (up from 10.3), the recommendation to Mac users running Mac OS 11 or earlier is to “explore macOS upgrade options as soon as possible” due to the resultant security concerns (via Soft Linden).

Graphics / glTF and Future Viewer Development Overall

  • Following the glTF Maintenance 2 RC, it is likely there will be a further graphics RC viewer which will combine:
    • Geenz Linden’s work on Hero reflection probes and reflections / mirrors.
    • Cosmic Linden’s work on applying glTF materials to terrain.
    • Updates which will allow the glTF / PBR swatch boxes in the Build / Edit floater display previews of the materials being selected, rather than grey boxes.
    • Possibly, the first series of additional glTF extensions – Index of Refraction, and also potentially testing support for 2K textures.
  • The idea is to try to move development within the viewer away from huge projects (like PBR Materials), which tend to take a lot of time to develop (1 to 2 years) and suffer a lot of visible feature creep. Instead, the idea is to tackle smaller components and build them out within successive RCs which come together to enable the kind of functionality sought be large scale projects.
  • It is hoped that by focusing on “featurettes”, smaller tranches of work can be more easily validated, that workflow with development and bug fixing can become a lot more linear, and individual elements of the work can be enabled as they are ready, or hidden behind debug flags until such time as functionality they are dependent upon is also ready.
  • Should this approach work with the next iteration of glTF capabilities as listed above, the approach will likely be applied to other viewer projects.
  • BUG-234728 “[PBR] Masked alpha gradient textures change with viewing angle” has been accepted as a known PBR issue, but there is no time frame on a potential fix.

RLV / RLVa Adoption

[TPVD Video 10:16-15:40 and 25:28-28:23]

  • Per a previous TPVD meeting summary, LL is interested in the potential to adopt RLV/a functionality into the official viewer.
  • Adoption has been a popular request from many users, as RLV is seen to have a lot of beneficial uses well beyond its original scope (as is the case the RLV-driven “Wardrobe” systems which allow outfits to be visually previewed and worn in just a couple of clicks), many of which either cannot be easily achieved in viewers without RLV support, or would require Experience-based scripting, which is not seen as ideal.
  • One problem is that RLV/RLVa is for many scripters, an “all or nothing” API, as it can touch on so many areas of the viewer, so that to be of value, the entire protocol would need to be implemented – which would be a major overhaul of the viewer.
  • As such, it was noted that RLV/RLVa implementation within the official viewer could be an ideal candidate for the “featurette” approach to viewer development noted above: discrete elements of the code implemented to a point where they can be validated, but placed behind flags so that they are disabled until such time as the overall implementation has reached a point where they can be jointly enabled.
  • The option to turn it off completely – as is currently the case in the majority of viewers running the RLV/a protocol – would be retained for those not wishing to use it.

In Brief

CCUG Meeting

  • Canny Feedback glTF Materials w/Bake Layers-as-Base Colour Turn White When Editing BOM Layer caused some surprise within the Lab, as applying glTF materials in the manner hadn’t been seen as expected behaviour, as is the fact that the layers display as expected outside of the appearance editor.
    • It was noted that most PBR-related Bakes on Mesh requests have been to allow the Bake Service to composite multiple PBR materials applied to different layers (e.g. being able to apply one materials set to skin, another to (say) shirt layer and another to (say) pants layer).
    • This is something LL would like to tackle, but it is seen as a significant overhaul of the Bake Service, and so is not currently on the roadmap for implementation.
  • There is a known issue with screen space reflections (SSR) on Linden Water which can make the latter appear to “glitch”. Brad Linden is still investigating this, but the solution might be tweaking to / replacement of the SSR algorithm so it “plays nicely” with Linden Water.
  • Object unpacking: a discussion on the potential to be able to unpack the contents of objects directly from Inventory, rather than having to rez them in-world first or for creators to supply them in a scripted HUD for unpacking.
    • A feature request for the reverse – Right-Click to Box In Inventory – has been accepted (which does not indicate it will be implemented in the immediate future).
    • In terms of unpacking / previewing contents of on item directly from Inventory, this is seen as a harder issue as once items are contained within another, they are effectively in the “inventory” of the containing item, rather than the account inventory, and the container’s inventory is only loaded by the simulator when it (or a copy thereof) is rezzed (or attached as a HUD) in-world.
    • Given the above, a new Inventory behaviour would be required which would simulate the object being rezzed in-world / attached as a HUD in order to trigger the simulator to load its contents. This was noted as something worth consideration even if only as a mental exercise at the moment, in order to determine how it might be handled.
    • This is the point at which my audio recording of the meeting truncated during saving, and so ends the summary notes for the CCUG meeting.

TPVD Meeting

  • [Video: 16:02-17:40] Avatar de-clouding: There have been multiple anecdotal reports of avatars taking longer to de-cloud when logging-in. The anecdotal responses at the meeting varied between no real difference and comments that AWS may have had issues over the holiday period resulting in packet loss (and thus longer load times), but this appears to have since been resolved.
  • [Video 19:20-25:09] a discussion on TPV development, licensing, open-sourcing code, what is and is not permissible, new viewers, etc. Please refer to the video for more.
  • General notes:
    • Planar alignment being broken in the Build / Edit floater is a known issue and due to be addressed.
    • There are no plans for LL to offer various “fallbacks” for PBR to “classic” (Blinn-Phong) materials to account for users currently not running PBR enabled versions of viewers, as PBR will be a part of all viewers as they update and move forward.
    • There are no plans to make SL available through platforms such as Steam (as once was the case), due to issues around content restrictions, monetisation methods, etc.
    • A discussion on Twitch not allowing SL streaming and whether LL should try to engage with them to support it. Given that there are other avenues for streaming, and Twitch is free to stand whatever barrier to use of its platform it likes, this would seem unlikely.

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.

Morlita’s Cats and Dogs at Nitroglobus in Second Life

Nitroglobus Roof Gallery, January 2024: Morlita Quan – Cats and Dogs

It’s been over a decade since I first encountered Morlita Quan’s art in Second Life. At the time, she was one of the recipients in the Linden Endowment for the Arts 4th round of land grants to artists, and I was immediately struck by her work. Over the course of the next few years I encountered her art over and again at various festivals and collaborative art events, but it was not until 2016 that I was able to blog about it as a solo exhibition, when I visited Organic Geometry, presented at the Art Gallery the Eye under her physical world artistic name, MorlitaM. Since then, I’ve always been attracted to her exhibitions whenever presented, finding myself deeply attracted to her work, which often blends the use of geometric and organic forms in unique and captivating abstracted ways.

However, her latest exhibition – currently being hosted by Dido Haas at her Nitroglobus Roof Gallery – offers a glimpse of another side of Morlita’s life in addition to that of an artist and musician. Cats and Dogs is something of a challenge set by Dido – a long time friend of Morlita’s – to produce a themed exhibition. Dido tends to present these to folk every so often, and they are often particularly hard to fulfil, as Dido has a knack for both shining a light on a side of someone’s SL or physical life (or both) which is seldom seen, and easing them out of their established comfort zone (and I speak here from knowledge – Dido hand me such a challenge well over a year ago, and I still have yet to try and rise to it to a point where I have confidence in the results!).

Nitroglobus Roof Gallery, January 2024: Morlita Quan – Cats and Dogs

For Morlita, the challenge came in the form putting together an exhibition focused on her work in taking in and caring for abandoned and mistreated animals, notably dogs.

While this might sound easy, it’s not necessarily so. For a start, should the images be of animals taken in Morlita’s physical world life, and if so, how should they be shot? What needs to be done to eliminate too much personal information from accidentally slipping into an image? Which animals should be featured? Should these be individual or group shots? And if not images of actual animals she is caring for, that what should be offered? shots of random animals, perhaps caught on the street? or should the images be drawn from digital sources – SL and elsewhere? And so on. When you add the fact that Morlita works in the realms of the conceptual and abstract, the melding of ideas and thoughts, both in her art and in her music, then the task becomes even more of a challenge – how do such approaches mix with the practicalities of animal welfare and care?

Nitroglobus Roof Gallery, January 2024: Morlita Quan – Cats and Dogs

With Cats and Dogs the answer to that last question would appear to be quite eloquently. Cats and Dogs is at once both a collection of conceptual pieces, oft with abstractions of meaning, and of portraits and studies of cats and dogs which can be taken purely on that level, depending upon your outlook mood.

Some of the themes woven into the images will at once appear obvious to anyone what has owned a cat or a dog (perhaps most recognisably in Ego, while in others the layering of ideas might be more nuanced (as in the highlighting of the eyes in a on some, capturing the notions of intelligence and understanding within our furred friends). In others still, the potential for meaning / interpretation is even more nuanced, if one so wishes to make it so – such as GP_MorlitaM (9) – or can simply be seen as an image of an animal enjoying life (and splashing through water). These are pieces which also blend Morlita’s love of the animals with her love of geometry and organic forms, each piece bringing all of these aspects together in a unique expression of love and understanding.

Nitroglobus Roof Gallery, January 2024: Morlita Quan – Cats and Dogs

Supported by 3D elements by Adwehe, Cats and Dogs is something of a very different exhibition for Nitroglobus; one that is obviously very personal to the artist – but also one fully in keeping with Dido’s tenet of encouraging her artists to present something which engages the eye and the mind. My apologies to her and Morlita to getting to this blog post a little later than is normally the case with exhibitions at Nitroglobus – and also to Dido for the fact that I still haven’t met the challenge passed to me back in late 2022!

SLurl Details

2024 SL SUG meetings week #3 summary

Sakura Cranes, December 2023 – blog post

The following notes were taken from the Tuesday, January 16th, 2024 Simulator User Group (SUG) meeting. They form a summary of the items discussed, and are not intended to be a full transcript. A video of the meeting is embedded at the end of this summary, my thanks as always to Pantera for recording the meeting and 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.
  • These meetings are conducted (as a rule):
  • They 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

  • No SLS Main channel deployment on Tuesday, January 16th, 2024; the simhosts were all just restarted.
  • Wednesday, January 17th should see the Falls Colours simulator update once more deployed to all of the RC channels. This includes:
  • If all goes well, week #4 should see Fall Colours deployed to the SLS Main channel and the Gingerbread simulator update deployed to at least some of the RC channels.

Viewer Updates

No changes at the start of the week, leaving the list of official viewers as:

  • Release viewer: version 7.1.2.7215179142, formerly the glTF PBR Materials Maintenance RC, issued December 15, promoted January 8, 2024 – numerous bug fixes and improvements.
  • Release channel cohorts (please see my notes on manually installing RC viewer versions if you wish to install any release candidate(s) yourself).
    • glTF PBR Materials Maintenance-2 RC viewer, version 7.1.3.7467259489, issued January 12, 2024.
    • Maintenance-W RC viewer, version 7.1.3.7453541295, January 9, 2024 – bug and crash fixesz.
    • Maintenance X RC, version 7.1.1.7088410646, December 7 – usability improvements.
    • Maintenance Y RC, version 6.6.17.6935642049, issued November 21 – My Outfits folder improvements; ability to remove entries from landmark history.
    • Emoji RC viewer, version 6.6.15.581551, August 31.
  • Project viewers:

Jira End-of-Road – Reminder

  • Linden Lab is ending its use of Atlassian Jira for the filing of bug reports and feature request, and is instead moving to Github / Canny. For specifics, please refer to the following:
  • Note that this is a work-in-progress (so things like additional ticket categories are being introduced, such as the recent Server Bug category), and both the new system and Jira remain open at this time (although the latter will shutdown in February 2024).

Game Control Update

  • The game_control event for using game controllers has been removed from the Gingerbread maintenance RC to become its own branch / channel (currently on Aditi (the Beta grid), where it can be found on the regions LeviathanLove and LeviathanLost.
  • As per the previous SUG meeting summary, the game_control event signature has changed in that the button_edges parameter is no longer provided to the event and must be computed by the scripter if still needed.

In Brief

  • Further discissions on Leviathan Linden’s LSL updates for camera control, due to be deployed in the Gingerbread update (see my previous SUG summary for details)
  • A general discussion on attachment points – such as reserving some for specific uses, or providing a separate pool of attachment points for HUDs / on-screen attachments (so that they are counted separately, rather than being part of the total limit of 38 attachments).
  • Concerns were raised over the fact the PBR now makes it harder to show / hide prims/object faces (e.g. alpha cuts in mesh bodies) using LSL to set the alpha visibility, with loops now being required to achieve what could previously be done via a single function call.
    • The problem is seen as exacerbated by the fact there appears to be no way for a script to determine if PBR materials is applied, making it necessary for creators to add to their script overheads.
    • It had been thought that a bug report had been raised on this issue, as it has been discussed at the Lab and is seen as a issue which needs to be fixed – although it might not be possible to change the semantics of the current Blinn-Phong alpha setters in LSL without breaking content.
    • llSetAlpha was not expanded to handle this out of concern over mixing semantics of setting legacy and PBR alpha values correctly.
    • This led to a general discussion on possible options to manage this issue, which continued through most of the rest of the meeting.
  • Please refer to the video for these items. and on TTAORAIMWEATCP (the throwing about of random acronyms in meetings without explanation and thus confusing people).

† 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 #2

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

Updates from the week through to Sunday, January 14th, 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.2.7215179142, formerly the glTF PBR Materials Maintenance RC, issued December 15, promoted January 8th, 2024 – numerous bug fixes and improvements – NEW.
  • Release channel cohorts (please see my notes on manually installing RC viewer versions if you wish to install any release candidate(s) yourself).
    • glTF PBR Materials Maintenance-2 RC viewer, version 7.1.3.7467259489, issued January 12th, 2024.
    • Maintenance-W RC viewer, version 7.1.3.7453541295, January 9, 2024- bug and crash fixes.
  • Project viewers:
    • No updates.

LL Viewer Resources

Third-party Viewers

V6-style

  • No updates.

V1-style

  • Cool VL viewer updated to 1.32.0.5 (PBR), January 6th, 2024 – release notes.

Mobile / Other Clients

  • No updates.

Additional TPV Resources

Related Links

Space Sunday: lunar losses and delays; strings and rings

United Launch Alliance’s (ULA) Vulcan Centaur rocket lifts-off from Florida’s Cape Canaveral Space Force Station, Monday January 8th, 2024 at 07:18 UTC. Credit: CHANDAN KHANNA/AFP

On Monday January 8th, 2024 United Launch Alliance completed the maiden launch of their Vulcan Centaur rocket with complete success, silencing critics and demonstrating that the caution and most recent delays around the launch (outside of those coming from the payload side) were worth it.

Lift-off came at 07:18 UTC as the two Blue Origin BE-4 motors of the 62-metre tall vehicle’s core stage ignited together with the two solid rocket boosters strapped on either side of it, lighting up the sky at Cape Canaveral Space Force station as the rocket climbed into a pitch-black sky. At 2 minutes into the flight, their job done, the solid rocket boosters shutdown and separated, leaving the rocket’s core to continue to power it upwards for a further three minutes before its liquid propellants were expended, and it separated to fall back into the Atlantic Ocean. The Centaur upper stage coasted for some 15 seconds before igniting it own pair of RL-10 motors in the first of three burns to place the vehicle and its payload into a trans-lunar injection (TLI) orbit and the first phase of what was hoped would be a looping trip to the lunar surface.

Lighting up the sky: a dramatic time-lapse image of the Vulcan Centaur rocket’s climb to orbit from Cape Canaveral Space Force Station. Credit: CHANDAN KHANNA/AFP

As I’ve previously noted, Vulcan Centaur is slated to replace ULA’s Atlas and Delta workhorses as a highly-capable, multi-mission mode payload launch vehicle in both the medium and heavy lift market places. Initially fully expendable, the vehicle may evolve into a semi-reusable form in the future, ULA having designed it such that the engine module of the core stage could in theory be recovered. It is also intended to become a human-rated launch vehicle. The Centaur upper stage is also designed with enhancement in mind, with ULA indicating that future variants might be capable of orbiting on an automated basis as space tugs or similar, once in orbit.

Whilst the vehicle carried a critical payload, the flight was actually regarded as a certification flight rather than an operational launch; one designed to gather critical performance and other data on the rocket which can be feed back into any improvements which might be required to make the vehicle even more efficient, etc.

A second certification flight is due to take place in April 2024, again with a critical payload – this one in the form of Sierra Space’s Dream Chaser cargo vehicle Tenacity, the first in a number of these fully reusable spacecraft which will help to keep the International Space Station (ISS) supplied with consumables and equipment, as well as helping in the removal of garbage from the station and the return of instruments and experiments to Earth.

Three incredible shots of the BE-4 engines and two strap-on boosters of ULA’s Vulcan Centaur, as the start to lift the vehicle away from the launch pad. Credit: Josh Dinner

While the launch of the Vulcan Centaur was a complete success – doing much too potentially boost ULA’s position as it seeks a buyer – the same cannot be said for its primary payload, which now looks set to make an unwanted return to Earth.

Peregrine Mission One (or simply Peregrine One), was to have been America’s first mission to land on the surface of the Moon since Apollo 17 in 1972. Financed in a large part via NASA’s Commercial Lunar Payload Services (CLPS) programme, this mission is nevertheless regarded as a private lunar mission, carrying some 20 experiments and instruments allowing it to operate in support of NASA’s broader lunar goals.

At first everything seemed to be going well with the mission. The lander rode the Vulcan Centaur to orbit before it powered-up its own flight systems and ‘phoned home to say it was in good shape. Then, some 50 minutes after launch, and the Centaur upper stage having completed its final burn to set the lander on its looping course to the Moon, Peregrine One separated from its carrier.

All appeared to go well in the hours immediately following separation, but following an attitude adjustment, telemetry started being received suggesting the craft was in difficulties and was unable to correctly orient itself. It was not initially clear what was wrong with the lander, and in an attempt to find out, Astrobotic – the company responsible for designing and building it – ordered camera mounted on the lander’s exterior to image its outer surfaces for signs of damage. The very first image returned showed an area of the craft’s insulation around the propulsion system – required to make the descent and soft-landing on the Moon – had suffered extensive damage, with propellants leaking into space from around it.

The first image returned from cameras on the Peregrine One lander revealed extensive damage to insulation material on the craft’s exterior and propellants venting into space. Credit: Astrobotic

This, coupled with the telemetry gathered from the lander caused Astrobotic to determine that one of the vehicle’s attitude control system (ACS) thrusters was still firing well beyond expected limits, most likely due to a failed / stuck valve, placing the vehicle in an uncontrollable tumble.

If the thrusters can continue to operate, we believe the spacecraft could continue in a stable sun-pointing state for approximately 40 hours, based on current fuel consumption. At this time, the goal is to get Peregrine as close to lunar distance as we can before it loses the ability to maintain its sun-pointing position and subsequently loses power.

– Astrobotic statement, Monday, January 8th

Initially, it had been hoped that the craft would still reach the Moon and make what is euphemistically called a “hard landing” (that is, crash into it) around the time of the planned landing date of February 23rd, engineers having calculated that by then, even if the rete of propellant loss slowed over several days and ceased, the craft would have insufficient reserves to make a controlled landing. However, by mid-week it was clear even this would not be the case; the leak had put Peregrine One on a much more direct path towards the Moon’s orbit than had been intended such that on January 12th, an status update from the company noted:

Peregrine remains operational about 238,000 miles from Earth, which means we have reached lunar distance! Unfortunately, the Moon is not where the spacecraft is now, as our original trajectory had us reaching this point 15 days after launch, when the Moon would have been at the same place.

– Astrobotic statement, Friday, January 12th

Peregrine One reached the distance of the Moon on Friday, January 12th, 2024 – much earlier than had been planned for the mission. As a result, the Moon was elsewhere in its orbit. Credit: Astrobotic

However, the one “good” piece of news through the week was that as time progressed, the propellant leak deceased, and some steps to help stabilise the vehicle – and maintain its orientation to the Sun such that its solar arrays could continue to received energy and power the vehicle’s systems – could be taken. These in turn allowed a number of the experiments on the lander to be powered-up. While they are not operating in their intended modes (or location), it is hoped that they will still be able to gather data on the radiation environment in interplanetary space around the Earth and the Moon.

The most recent projections from Astrobotic (January 14th) suggest that as the Lander has in sufficient velocity to complete escape Earth’s gravity well, it will likely start to “fall back” to Earth in the coming weeks, and orbital mechanics being what they area, most probably slam into the upper atmosphere and burn-up.

As it should have been: the intended flight place to get Peregrine One to the Moon. Credit: Astrobotic

Given Peregrine One’s involvement in the CLPS programme, NASA has been monitoring the Peregrine One situation closely, and on January 18th the agency and Astrobotic are due to convene a telecon in order to review Astrobotic’s efforts to recover the craft and what they have learned. In the meantime, agency officials have noted that the failure of Peregrine One to successfully achieve a lunar landing will not in any way impact CLPS.

Artemis 2 and 3 Slip

On January 9th, 2024, NASA announced America’s return to the Moon with crewed missions at the head of Project Artemis is to be further delayed.

In the announcement, made in part by NASA Administrator Bill Nelson, it was indicated that the upcoming Artemis 2 mission around the Moon and back, and intended to take place in November 2024, will now not take place before September 2025. Meanwhile, the first US crewed mission to the surface of the Moon will now occur no sooner than September 2026.

The reasons given for the delays relate most directly to Artemis 2. In particular, there are a number of new systems and capabilities in development as a part of the overall Artemis programme which are now far enough along that it makes sense to delay Artemis 2 to leverage them, as they offer increased safety at the pad and prior to launch – such as improved means for crew egress from the launch vehicle in an emergency, and faster propellant loading capabilities.

The overall plan for the Artemis 2 flight around the Moon, which will carry fours astronauts – three from the USA and one from Canada -, but which now not take place before September 2025. Credit: NASA

Another cause for the delay is on-going concerns about the performance of the ablative heat shield on the Orion Multi-Purpose Crew Vehicle (MCPV). Whiles the shield did its job and protected the unscrewed capsule of Artemis 1 during its passage back into the Earth’s atmosphere at the end of that mission in November 2022, it still showed signs that rather than charring in place, some of the material actually peeled away from the vehicle as it charred, which is not supposed to happen.

Finally, concerns have recently been raised about the electrical system managing the crew abort system rockets, designed to haul the Orion capsule and its crew clear of the SLS rocket if the latter suffers a serious failure during the initial ascent to orbit. As a result, further tests have been requested on that system.

I want to emphasize that safety is our number one priority. And as we prepare to send our friends and colleagues on this mission, we’re committed to launching as safely as possible. And we will launch, when we’re ready.

– Jim Free, NASA’s Associate Administrator

The announcement was, oddly, seen as a cause for vindication among some SpaceX fans – the private launch company has been cited as a potential reason for delaying the Artemis 3 programme, given they are still a long way from demonstrating they have the ability to supply NASA with an operational lunar landing vehicle and the means to get it to lunar orbit.

However, even the addition of a further 11 months to the Artemis schedule still leaves SpaceX with precious little time to achieve those goals in a manner which meets NASA’s safety requirements. As such, the concerns about SpaceX being able to meet current Artemis time faces, as highlighted (again) in 2023 by the US Government Accountability Office (which has an uncannily accurate eye for predicting programme slippages and their causes) still remain valid.

Continue reading “Space Sunday: lunar losses and delays; strings and rings”