Space Sunday: Mars rocks and space taxis

NASA’s Perseverance Mars rover took this selfie on July 23rd, 2024 (sol 1,218 of the mission). The “arrowhead” rock dubbed “Cheyava Falls” is centred in the image. The white spot on surface of “Cheyava Falls” is one of two points “cleaned” of surface dust so the rover could examine the composition of the rock’s surface directly. The second spot was used by the rover’s drilling mechanism to obtain a core sample of the rock, the hole for which as be seen just below the abrasion patch. Credit: NASA/JPL / MSSS

On July 25th, NASA released a statement on a recent find made by the Mars 2020 rover Perseverance as it continues to explore an ancient river outflow delta within Jezero Crater on Mars.

The statement relates to a rather unusual arrowhead-like rock NASA has dubbed “Cheyava Falls” which attracted interest both due to its general shape and the fact its surface has white veins of calcium sulphate—minerals that precipitate out of water – running across it. More particularly, between the veins, Perseverance imaged tiny mineral “leopard spots”, whitish splotches ringed by black material.

On Earth, such spotting can form when organic molecules react with hematite, or rusted iron. These reactions, in turn, can fuel microbial life. “Cheyava Falls” is the first time they’ve been seen on Mars, and so it is understandably a cause for interest and some excitement, and marked the rock – measuring around a metre in length and half a metre across at its widest, – and a target for more detailed study.

Captured on June 12th, 2024 (sol 1,178) this 360-degree view of the region dubbed “Bright Angel”, the outflow plain on the edge of Jezero Crater in which “Cheyava Falls,” is located. The 346 images making up this view were captured using the MastCam-Z instrument on the rover’s mast and stitched together after being sent back to Earth. The colour of the completed mosaic has been enhanced to bring out subtle details. Credit: NASA/JPL / MSSS

This commenced with analyses of various parts of the rock using instruments mounted on the turret at the end of the rover’s robotic arm, notably SHERLOC, PIXL and WATSON.

SHERLOC – the Scanning Habitable Environments with Raman & Luminescence for Organics & Chemicals  – revealed the compounds both within the white veins and on the surface of the rock as a whole, are consistent with those known to be involved in the advent of life. Meanwhile, WATSON, the Wide Angle Topographic Sensor for Operations and eNgineering imager associated with SHERLOC was able to provide detailed images of the “leopard spots” and the calcium sulphate veins, revealing multiple other minerals to be present, some of which contain elements which might assist in the formation of life; whilst the Planetary Instrument for X-Ray Lithochemistry (PIXL) instrument confirmed the “leopard spots” themselves contain both iron and phosphate, and so might possibly have once powered organic processes.

Captured on July 18th, 2024 (sol 1212 of the mission) using the WATSON imager aboard the NASA rover Perseverance, this image of the rock dubbed “Cheyava Falls” show to of the large white calcium sulphate veins running across the rock, and between them bands of material whose reddish colour indicates the presence of hematite, covered in millimetre-sized light patches surrounded by a thin ring of dark material, and referred to as “leopard spots”. Similar spots can form on sedimentary terrestrial rocks and are frequently an energy source for microbes. Also annotated is one of a number of nodules of pale green olivine. Credit: NASA/JPL / MSSS

This is the first time that a combination of all three of these types of deposit have been found in a single location on Mars, thus raising even more interest in “Cheyava Falls” and potentially making  it the strongest contender yet for indicating basic microbial life may have at one time existed on the planet. However, as the science team has noted, the situation is far from clear.

On Earth, whilst they are noted for their association with microbial life, “leopard spots” are initially the result of an abiotic chemical reaction. So even if the same processes were at work on Mars and may have eventually gone on to feed Martian microbe which may have come about courtesy of the other processes at work in the rock, it is also possible other factors intervened which halted any microbes getting a kick-start with life. In this, matters are complicated by the presence of olivine mineral fragments in the rock.

Olivine is a product of magma – and magma is not friend to organics, as such, their presence in the rock suggest they and the phosphates may have been deposited at temperatures too great to allow organic material to survive, but the phosphates were deposited into veins and pits in the rock after it had been initially laid down as sedimentary mud and compressed into rock, thus giving rise to the veins and spots.

To understand how the rock may have formed, the rover was instructed to take a core sample of “Cheyava Falls” on July 21st, and only the 22nd rock sample to be taken by the rover since it arrived on Mars in February 2021 – the being due to drilling operations having been cut back as a result of a series of issues with the drill mechanism and a desire to avoid it failing prematurely as a result of wear and tear.

Some of this sample will be analysed by the rover itself using its on-board lab. Unfortunately, while this may reveal more of the rock’s history, its unlikely to definitive answer the question of whether microbes might have once nommed on the minerals in the rock; there are simply too many variables involved for the rover’s limited capabilities to reach such a definitive conclusion on its own.

Captured using the front right Hazard Avoidance Camera A on the the rover’s chassis, this image shows Perseverance with the turret of its robot arm positioned over “Cheyava Falls”, ready to drill a core sample. This image was captured at the local mean solar time of 15:16:29 on July 21st, 2024 (sol 1215 of the mission. The image is unprocessed and show natural daytime lighting on Mars. Credit: NASA/JPL / MSSS.

As such, the material gathered in the sample would need to be returned to Earth. For this to happen NASA need to sort out how it is going to managed getting the sample – and others Perseverance has gathered (and in some cases already cached on the Martian surface). The problem here being that, as I’ve noted in previous Space Sunday updates, is that NASA has no clear idea as to how such a sample return mission might be completed; its original planes for far too complicated and way too costly – estimates by the agency’s own Office of Inspector General (OIG) pushing the mission upwards of US $9 billion – making it impractical and prompted NASA to re-think the whole thing.

Given this, the mystery of “Cheyava Falls” is liable to remain long after Perseverance has moved on in its exploration.

Boeing Starliner: “Hot Fire” Test Success, But No Return Date

In my previous Space Sunday update, I provided an update on the Boeing CST-100 Starliner Crew Flight Test (CFT) mission to the International Space Station (ISS), but things were hanging in the balance, as there were tests taking place at the time which could determine the vehicle’s readiness to make a return to Earth.

At the risk of repeating myself, Starliner vehicles use two propulsion systems: four larger orbital manoeuvring and attitude control (OMAC) system, used for making significant manoeuvres, and 28 smaller reaction control system (RCS) thrusters used to carry out precise manoeuvring and also to help stabilise and fine tune the vehicle’s pitch, yaw and roll during and after use of the OMACs. Four sets of thrusters, each comprising an OMAC unit and seven RCS units, are equidistantly places around the Starliner’s service module in external units called “doghouses”. During the flight up to the ISS, the RCS thrusters in particular suffered a series of issues and helium purge line leaks.

Since then, NASA and Boeing has been working through matters, delaying the return to Earth for both the vehicle and its crew of Barry “Butch” Wilmore and Sunita “Suni” Williams. Most recently, comparative testing between “doghouse” units on Earth and those on the Starliner in orbit revealed large temperature spikes occurring within latter’s doghouses when pulse-firing the RCS thrusters immediately after the used of the OMACs – and these spikes are believed to be the cause of leaks detected in the RCS helium purge lines and cause the failure of one of the RCS thrusters.

To combat this, Boeing and NASA have been developing an alternate procedure for the use of the RCS systems in an attempt to eliminate the noted temperature spikes in the “doghouses”, and the tests carried out on July 27th aboard Calypso were designed to test these new procedures. Following an initial review of the test data, NASA issued a statement noting:

The test involved firing 27 of the spacecraft’s 28 jets for short bursts, moving through them one at a time to check thruster performance and helium leak rates. Preliminary results show all the tested thrusters are back to preflight levels based on thrust and chamber pressure.
As part of the test configuration, all helium manifolds, which control and direct the flow of helium, were opened allowing engineers to continue evaluation of Starliner’s helium supply and leak rates. The teams verified Starliner continues to show the margin needed to support a return trip from the station.

– NASA Hot Fire Test statement, July 30th, 2024

Boeing CST-100 Starliner major vehicle elements. Credit: Boeing

In other words, there is currently a high confidence within NASA and Boeing that Starliner is fit for purpose in being able to bring Wilmore and Williams back to Earth.

However, prior to a final decision being made in this regards, a formal return readiness review meeting must be held. This is a necessary step to certifying a vehicle which has experienced issues is believed to be fit for a return to Earth, and which usually sees a target date for its return is identified.

Prior to the hot-fire test, NASA indicated this meeting might take place during the week immediately after the test; but on August 2nd, NASA indicated it would not occur any earlier than the week commence August 5th, so as to allow further review and vetting of the test results. This resulted (again) in a lot of social media driven speculation NASA were about to “abandon” Starliner.

This speculation appears based on unlinking a number of suppositions: that: a) NASA’s delay with the readiness review meeting shows “something is wrong”; b) as NASA is still prepping the four-person Crew 9 for launch to the ISS on August 18th, but doesn’t have room for it to dock (there are only two docking ports on the ISS which can be used by Crew Dragon, one of which is occupied by the vehicle used by the 4-person Crew 8, and the other by Starliner); ergo, c) NASA “must” be considering sending Starliner back to Earth uncrewed, in order to make way for the Crew 9 flight.

While it is true that that data may yet surface that warrants NASA to consider returning Calypso to Earth uncrewed and looking to other means to bring Wilmore and Williams home, there is absolutely no evidence for this being the case at this point in time. Further, it’s actually not the only contingency NASA has at its disposal.

If the confidence in Starliner remains high, but the return cannot be completed until after August 18th (and assuming Crew 9’s launch is not itself delayed), the agency could opt to bring Crew 8 back to earth ahead of the launch of Crew 9. Doing things in this order would not be optimal – but it is possible. However, as it stands, and as Steve Stich, NASA’s Commercial Crew Programme Manager, has made it clear where NASA’s focus for Starliner lies.

I think we’re starting to close in on those final pieces of the flight rationale to make sure that we can come home safely, and that’s our primary focus right now. We have contingency options; NASA always has contingency options … But right now we’re really focused on bringing Butch and Suni home on Starliner.

– NASA Commercial Crew Programme Manager Steve Stich

Outside of this, and following the July 27th tests, Boeing issued its own statement noting that return preparations are underway, and has held an “integrated simulation”  – essentially a full dress rehearsal of Starliner and Calypso’s departure from the ISS and return to Earth, involving ground controllers and Wilmore and Williams in readiness for readying for “potential returns throughout August”.

In addition the ISS crew used the station’s CanadArm 2 robotic arm to complete a visual inspection of Starliner’s exterior – both the Calypso capsule and the service module. Such inspections are a normal part of preparing for a vehicle’s departure from the ISS. All of which seems to underline Boeing and NASA are fully expecting Williams and Wilmore to return to Earth aboard the vehicle.

In the meantime, and in news unlikely to sit well with Boeing shareholders, the continuing issues with the Crew Flight Test have resulted in Boeing taking a further US $125 million charge from NASA. This brings the total amount charged to Boeing as a result of the delays across the entire Starliner programme to US $1.6 billion against NASA payments to Boeing for Starliner development totalling US $5.1 billion.

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