The following notes were taken from the Tuesday, November 22nd, 2022 Simulator User Group (SUG) meeting. They form a summary of the items discussed and is not intended to be a full transcript. A video of the entire meeting is embedded at the end of the article for those wishing to review the meeting in full – my thanks to Pantera for recording it.
Server Deployments
At the time of writing, a server deployment thread had yet to be published.
On Tuesday, November 22nd, the Main SLS and Events channels were updated with the single fix designed to keep regions from running out of voice connections (BUG-229984 “Voice chat is not working” and BUG-7371 “Voice cannot connect”).
On Wednesday, November 23rd, simhosts the RC channels will be restarted without any deployment.
Upcoming Simulator Releases
The run of simulator updates through to the new year will likely comprise:
Link sounds will most likely the last roll of the year (this should behave exactly as though you had a script in the linked prim and called llPlaySound from that prim).
llGetSimStats updates are liable to be the first update of 2023.
llHTTPRequest updates (see below) will likely follow later in January 2023.
LSDFindKeys sorting updates will most likely be fixed in the first simulator maintenance release for next year.
Available Official Viewers
No changes to any of the current batch of official viewers, leaving them as follows:
Release viewer: version 6.6.7.576223 – MFA and TOS hotfix viewer – November 1 – No change.
Release channel cohorts:
Maintenance P (Preferences, Position and Paste) RC viewer version 6.6.8.576431 on Monday, November 14.
VS 2022 RC viewer, version 6.6.8.576310, issued November 4 – utilises Visual Studio 2022 in the Windows build tool chain.
Project viewers:
PBR Materials project viewer, version 7.0.0.576331, issued on November 3.
This viewer will only function on the following Aditi (beta grid) regions: Materials1; Materials Adult and Rumpus Room 1 through 4.
Puppetry project viewer, version 6.6.3.575529, issued on October 12.
Performance Floater / Auto-FPS project viewer, version 6.6.5.575378, October 4.
Love Me Render (LMR) 6 graphics improvements project viewer 6.6.2.573263, July 21.
In Brief
BUG-232171 “Issue with regions becoming full, but still showing available prims” – this is been causing noticeable issues recently, with a lot of speculation that it may be a griefing vector. However, the important point with the issue is that LL know what the cause actually is, and will be addressing it.
BUG-229382 “Vehicles stopping dead at region borders” may be related to this issue.
BUG-BUG-227303 “collisions makes a script stop running and revert its mono status” was also raised later in the meeting in relation to Mono concerns.
Concerns have been raised about bout removing the LSO bytecode compiler (non-Mono), leaving only the Mono compiler (the run-time environment for LSO scripts would remain – it just wouldn’t be possible to compile new scripts via the LSO compiler or re-compile updated scripts using it).
These issues (apparently related to rapid rezzing of objects and / or some vehicles the Mono control scripts behaving badly at region crossings) have not been the subject of any bug report(s) and so lack documented details. A Jira has been request.
A core part of the meeting was given over to combat systems and providing improved means of projective operation (in part related to the Mono discussion above) – please refer to the video for details.
BUG-37727 “Regex for LSL” may have a better chance of being implemented now that Regex is exposed to LSL via Linkset Data.
With the implementation of LSD, an suggestion has been made to add publicly editable key-value pairs that could be set in the build window via object owners, and then accessed via scripts using an interface similar to Linkset Data. A similar suggestion has also been made within the forums, however, that does not appear to be a feature request Jira for these ideas (at least at the time of writing this summary).
BUG-232551 “We need significantly more RAM for scripts in non-attachments” was raised in discussion; it has been accepted by the Lab, but no indication of when it it might be actioned, or how.
Rider Linden is playing some enhancements to LSL for 2023, including (but not limited to) allowing a response to an HTTP request with the contents of a notecard.
My audio recording and chat log of the Content Creation User Group (CCUG) meeting held on Thursday, November 17th, 2022 at 13:00 SLT.
My audio recording and chat log from the Third-Party Viewer Developer (TPVD) meeting held on Friday, November 18th, 2022 at 13:00 SLT. Pantera attended the meeting, but was unfortunately held-up beforehand, so around the first 10 minutes is absent from her video (embedded at the end of this summary).
Both meetings are chaired by Vir Linden, and their dates and times can be obtained from the SL Public Calendar.
This is a summary of the key topics discussed in the meeting and is not intended to be a full transcript.
The following reflect the list of current official viewers available through Linden Lab.
Release viewer: version 6.6.7.576223 – MFA and TOS hotfix viewer – November 1.
Release channel cohorts:
Maintenance P (Preferences, Position and Paste) RC viewer version 6.6.8.576431 on Monday, November 14.
VS 2022 RC viewer, version 6.6.8.576310, issued November 4 – utilises Visual Studio 2022 in the Windows build tool chain.
Project viewers:
PBR Materials project viewer, version 7.0.0.576331, issued on November 3.
This viewer will only function on the following Aditi (beta grid) regions: Materials1; Materials Adult and Rumpus Room 1 through 4.
Puppetry project viewer, version 6.6.3.575529, issued on October 12.
Performance Floater / Auto-FPS project viewer, version 6.6.5.575378, October 4.
Love Me Render (LMR) 6 graphics improvements project viewer 6.6.2.573263, July 21.
General Viewer Notes
There is unlikely to be any major changes to the list above in week #47, as this is a short working week for the Lab due to the Thanksgiving holiday (Thursday / Friday).
Github Changeover and Streamlining the Code Contributions Process
Github Work
As previously announced, there is an initiative to improve continuous update integration in the viewer and improve the viewer deployment process.
For TPVs and developers, the most visible aspect of this is moving the viewer repositories from BitBucket to Github. This includes the viewer code base and the other public code bases currently in BitBucket (Autobuild, LLCA, etc.).
There is still no firm date as to when the actual switch-over to using the new repositories will occur, but the viewer development team is working steadily towards it, and the plan remains to provide plenty of advanced warning to TPVs on when LL plan to cut over to the new repositories before making a clean cut-over.
Status
The switch-over to using Github is now slated for “early in the morning” (PST / SLT) on Monday, November 21st, 2022.
This means that from the point of switch-over, the Bitbucket repositories will be locked and carry a warning that they are no longer current, and developers / viewer builders should use the GitHub repositories, as directed to in the warning.
The master viewer branch is already up-to-date on GitHub as of Friday, November 18th, 2022.
Notes on the switch-over were posted to developers on the open-source developers list.
There is no plan in place to phase out the Bitbucket repositories immediately, but they may well be removed in time.
PBR: Materials and Reflections
Project Summary
To provide support for PBR materials using the core glTF 2.0 specification Section 3.9 and using mikkTSpace tangents, including the ability to have PBR Materials assets which can be applied to surfaces and also traded / sold.
To provide support for reflection probes and cubemap reflections.
The overall goal is to provide as much support for the glTF 2.0 specification as possible.
The viewer is available as a project viewer via the Alternate Viewers page, but will only work on the following regions on Aditi (the Beta grid): Materials1; Materials Adult and Rumpus Room 1 through 4.
The focus is currently on reviewing bugs reported by those testing the viewer, and creators using glTF PBR workflows to create content are encouraged to test out their content on the project viewer to ensure things look as expected when imported into SL.
One aspect of SL that does require testing is EEP assets; changes have had to be made to the shaders which mean that commercial EEP settings may not render as expected (things like haze density my be modified, etc).
EEP creators may therefore want to test their settings using the project viewer, and Jira issues – please include “non PBR viewer” shots of how the settings should look and shots taken with the PBR project viewer for easier comparison / understanding of the issues seen.
Issues with alpha blending are being investigated – particularly linear space alpha blending and how best to carry forward “pre-PBR” alpha blending, which does not use linear space.
It has been reported that the PBR project viewer generating some 10% more CPU temperature and 17% more GPU temperature – this may be the result of the viewer having to work that much harder with PBR in order to maintain frame rates.
Reflection probes: concern was again raised over people excessively using probes (e.g. attaching them to all their products / objects they own).
Providing a means for users to disable probes attached to objects they purchase has been previously discussed within the project / CCUG meetings.
It is hoped the latter (people just randomly setting-up probes all over their house / land) can be mitigated against through a mix of education and explicit warnings / actions in the viewer.
Concern was also raised about the potential of localised reflection probes (essentially an invisible prim) could interfere with intended interactions (e.g. a probe enclosing a chair could block people’s ability to sit on the chair). If cases like this are found in testing, a request has been made for bug reports.
The PBR viewer does include a Build / Edit option to “ignore invisible prims” so that when building / editing, an attempt to select an object within the volume of a reflection probe prim will ensure the object is selected, not the probe prim, but it is acknowledged that this kind of operation needs to be better integrated with other mouse click options.
It was noted that this project also marks the start of the deprecation (and eventual removal) of some real-time console performance reports, such as Fast Timers.
It has been reported that some testing the PBR viewer are finding that within the texture console, Bias is constantly being reported at 5 (which tends to cause texture thrashing in non-PBR viewers). However, within the PBR viewer a Bias of 5 should indicate that the viewer is swapping – and keeping to – a lower texture resolution, and so should not result in any texture thrashing.
Screen Space Reflections (SSR)
LL does have a “subtle” SSR system working to replace Linden water reflections as currently rendered.
There is some further work to be carried out before it is “viewer-ready”, with the focus being on ironing out the bumps and cleaning-up bugs.
It was made clear that while this implementation of SSR will be applicable to scenes as a whole, it is not intended to be a replacement for creating mirrors – and so expectations should be set accordingly.
CCUG Meeting Specific Notes
The majority of the meeting was given over to a general discussion, per the cliff-notes below:
VR hardware and Second Life:
While frame rates are not so much an issue now in broad terms, there is still the need to get a high frame rate on a consistent basis for VR viewing to be enjoyable – and this is still not a giving with SL.
However, VR isn’t just about headsets; its about the “full” experience in using a range of associated peripherals: controllers, haptic gloves, the ability to have a “full-body experience” that VR users would want and expect, such as seeing your hand and arm when going to pick something up, being able to grip an object in your hands and feel responses from it when using it (e.g. the strike of a blade against another or a baseball sat against the ball, etc.).
The level of support for this more complete sense of immersiveness requires some extensive re-engineering of Second Life (e.g. facilitating a full and proper Inverse Kinematics system as a single example).
The Puppetry project may facilitate some work towards this. However, the focus of this project is not on providing any form of in-depth VR support (it is intended to work with a broader range of peripherals, notably webcams, although use of some VR software support via OpenVR is being considered), being intended for use by as broad a cross-section of SL users as might be interested in it.
Another problem is determining what people want from VR; is it purely a mechanism for games, or does it need to be capable of “realistic” social interactions (some do still proclaim games, other demand social capabilities; the truth is probably more a blending of the two, just like life in the physical realm).
New users and their experience:
Much was made of the need for a completely new avatar system (LL is actually working on a new all-mesh “starter avatar”, but using the existing skeleton) – but overhauling / replacing the current avatar system raises its own compatibility / market issues.
A fair point was raised by LL concerning the use of eviction / ban scripts that specifically ban avatars that are less than X days old and / or avatars that do not have Payment Information On File.
These tend to get used at event spaces etc., to try to prevent griefers / trolls using throwaway accounts from accessing the space, rather than using other available moderation tools (which, admittedly tend to require human intervention with the right permissions, which might not always be available).
The problem here is that often, a “genuine” new user will often sign-up, go through the new user experience, then try to go to a event – only to immediately find they are denied entry or are ejected without warning or explanation, and as a result, they log-out.
The need for improved tools to handle griefing and trolling are likely required – but no discussion on what form these might take.
Audio: a general conversation on the potential of “full” spatial audio, including directional (e.g. so an audio stream at a disco appears to be coming from the speaker system in the venue) and also sound volumes.
Nothing is currently planned for audio in the roadmap, but it was noted that the first test of using volumes (reflection probes) is in Aditi testing, and LL will obviously seeing how well that works.
It was made clear that scripts will “NEVER” be allowed to create new assets (so no ability to generate notecards from a script). One of the reasons cited for this is the cost of storing assets if there is an uncontrolled ability to generate them through scripts (particularly given SL’s asset count is already in the petabytes range in terms of storage).
TPVD Meeting Specific Notes
Atlassian Jira and Bug Reporting
Atlassian has announced it will be restructuring how it licenses the Jira bug reporting product from 2024 onwards. Currently, LL can run a public-facing Jira reporting system that effectively allows every Second Life user to create an account on it to view all the public SL bug reports and feature requests.
Under the 2024 pricing restructure (which will be pretty much per-account), this will be prohibitively expensive for LL, so they are starting into the process of looking for an alternative means to provide some form of user-facing bug reporting mechanism.
one option being considered is to continue to use Jira internally (where the number of licensed accounts can be controlled), and use a different mechanism for public bug reporting, with a bridge between the two.
Another is to move away from Jira entirely.
No decision has been made as yet, but as Firestorm also use Jira, the suggestion has been made that the two develop a joint plan to resolve the situation in terms of future tools.
The topic lead to a general discussion on possible options, but no conclusions drawn – and there is sufficient lead-time on the matter for various options to be looked into, allowing for the time required to transition to any alternate that might be selected / finding the means to keep the wealth of information on the SL Jira available for reference.
General Notes
There is a report that Active Voice on at least some viewers is not updating correctly (e.g. following a teleport, and it is proving easier to enable / disable Voice morphing vie the menu than to disconnect / reconnect Voice in order to correct.
The issue here is not so much which is the preferred method to correct the problem, but whether the Active Voice list failing to update is a widespread issue with viewers, and whether it can be reproduced on the official viewer & a bug report raised.
Beq Janus has written a post on alpha blending issues (see: Alpha blend issues? Get them sorted – subtitled Making it easier to avoid alpha-clashes with Second Life and OpenSim outfits). Rather than have me decimate the discussion, please refer to the video fat 35:56 through video end for more.
The following notes were taken from the Tuesday, November 15th, 2022 Simulator User Group (SUG) meeting. They form a summary of the items discussed and is not intended to be a full transcript. A video of the entire meeting is embedded at the end of the article for those wishing to review the meeting in full – my thanks to Pantera for recording it.
Server Deployments
At the time of writing, a server deployment thread had yet to be published.
On Tuesday, November 15th, the Main SLS and Events channels were updated with simulator version 576376, making the new Linkset Data capability grid-wide.
On Wednesday, November 16th, the simhosts on the RC channels should receive a new simulator update, this one containing a single fix designed to keep regions from running out of voice connections (BUG-229984 “Voice chat is not working” and BUG-7371 “Voice cannot connect”).
Linkset Data (LSD) – Brief Notes
Linkset Data is a new collection of script functions and one optional event that reads and writes key-value-pairs to a small 64kb table of data that is part of a root object.
It works similarly to Experience Key-Value store, but:
It does not require an underpinning experience – the data lives with the object that sends and receives the data.
Only scripts in the same linkset will be able to read the data written with this feature.
The run of simulator updates through to the new year will likely comprise:
Link sounds will most likely the last roll of the year (this should behave exactly as though you had a script in the linked prim and called llPlaySound from that prim).
llGetSimStats updates are liable to be the first update of 2023.
llHTTPRequest updates (see below) will likely follow later in January 2023.
LSDFindKeys sorting updates will most likely be fixed in the first simulator maintenance release for next year.
Available Official Viewers
The Maintenance P (Preferences, Position and Paste) RC viewer updated to version 6.6.8.576431 on Monday, November 14th.
All other official viewer remain as follows:
Release viewer: version 6.6.7.576223 – MFA and TOS hotfix viewer – November 1.
Release channel cohorts:
VS 2022 RC viewer, version 6.6.8.576310, issued November 4 – utilises Visual Studio 2022 in the Windows build tool chain.
Project viewers:
PBR Materials project viewer, version 7.0.0.576331, issued on November 3.
This viewer will only function on the following Aditi (beta grid) regions: Materials1; Materials Adult and Rumpus Room 1 through 4.
There are unconfirmed reports that GPUs are running noticeably hotter with this viewer than other viewer.
Puppetry project viewer, version 6.6.3.575529, issued on October 12.
Performance Floater / Auto-FPS project viewer, version 6.6.5.575378, October 4.
Love Me Render (LMR) 6 graphics improvements project viewer 6.6.2.573263, July 21.
llHTTPRequest Updates
Rider Linden is proposing changing the way we do accounting for CUSTOM_HEADERS.
Currently, headers of no longer than 253 bytes each are allowed.
Rider plans on changing this so that as many headers, each as long as is required, can be stored, to a maximum of 4096 bytes.
This is in recognition that there are a number of applications that require security headers which can blow through that 256 byte limit.
In Brief
BUG-232037 “Avatar Online / Offline Status Not Correctly Updating” – this is unlikely to be addressed until 2023, as the remaining simulator update slots for 2022 now have updates assigned to them.
BUG-232918 “Adding Friend will make all other friends appear offline” – this is newly reported bug, and should be kept in mind if experiencing issues with your Friends list.
BUG-227303 “collisions makes a script stop running and revert its mono status” opened in 2019, was raised, but has yet to be deeply investigated by LL.
The meeting included a further discussion on LSDListKeys and LSDFindKeys (e.g. negative index support). Please refer to the video below for this and the rest of the meeting.
Puppetry demonstration via Linden Lab – see below. Demos video with the LL comment “We have some basic things working with a webcam and Second Life but there’s more to do before it’s as animated as we want.”
The following notes have been taken from chat logs and audio recording of the Thursday, November 10th Puppetry Project meetings held at the Castelet Puppetry Theatre on Aditi. These meetings are generally held on alternate weeks to the Content Creation User Group (CCUG), on same day / time (Thursdays at 13:00 SLT).
Notes in these summaries are not intended to be a full transcript of every meeting, but to highlight project progress / major topics of discussion.
Project Summary
Previously referred to as “avatar expressiveness”, Puppetry is intended to provide a means by which avatars can mimic physical world actions by their owners (e.g. head, hand, arm movements) through tools such as a webcam and using technologies like inverse kinematics (IK) and the LLSD Event API Plug-in (LEAP) system.
Note that facial expressions and finger movements are not currently enabled.
Most movement is in the 2D plain (e.g., hand movements from side-to-side but not forward / back), due to limitations with things like depth of field tracking through a webcam, which has yet to be addressed.
The back-end support for the capability is only available on Aditi (the Beta grid) and within the following regions: Bunraku, Marionette, and Castelet.
Puppetry requires the use of a dedicated viewer, the Project Puppetry viewer, available through the official Second Life Alternate Viewers page.
No other special needs beyond the project viewer are required to “see” Puppetry animations. However, to use the capability to animate your own avatar and broadcast the results, requires additional work – refer to the links below.
There is now a Puppetry Discord channel – those wishing to join it should contact members of LL’s puppetry team, e.g. Aura Linden, Simon Linden, Rider Linden, Leviathan Linden (not a full list of names at this time – my apologies to those involved whom I have missed).
Bugs, Feature Requests and Code Submissions
For those experimenting with Puppetry, Jiras (bug reports / fixes or feature requests) should be filed with “[Puppetry]” at the start of the Jira title.
The puppetry team is working on updating the viewer and LEAP plug-in, and an update to the project viewer is liable to be released in week #46.
This viewer includes:
The ability to move the avatar pelvis.
Ability to stretch other bones – although this is awaiting testing at the time of writing. However, the reference frame scale is that of the normal puppetry targets, so you would have to scale the data correctly; therefore additional work on this is required to provide a way for the plug-in to get the data necessary to know now to scale individual joint bones (e.g. change their parent-relative positions).
It still won’t be possible to clear puppetry target/config data, which remains on the teams “to do” list.
Aura Linden noted the new LEAP module it initialises on-demand rather than via instantiation (as with puppetry). LL will provide demos of using the new module.
Kincect v2 Support
Simon Linden has been working on an experimental plug-in taking inputs from a Kincect v2 device.
He describes the the code as being “pretty rough” and using only basic geometry, but it allows avatar elbows / arms to be moved around.
This work in part utilises the data syntax described in OPEN-366 “Simplify Puppetry Configuration Through LEAP”, the new protocol proposed by Leviathan Linden as per previous meeting notes.
The code is not ready to be pushed to a public branch as let, and doing so is somewhat dependent on feedback from developers /creators.
Avatar Constraints / Interactions
OPEN-368 “[Puppetry] [LEAP]: Location Constraints” – LL have indicated there is “much” within this Jira they would like to support “eventually”.
The feeling at the Lab is that constraints can “definitely” be improved – although what this may look like has yet to be properly determined. However, the general feeling is that there should be constraint data associated with a given skeleton, for example, so we’re not just imposing a human-centric model on the SL avatar.
A good portion of the meeting was given over to a general discussion of how best to handle puppetry and avatar animations – and the potential to need to move away from canned animations and provide a more direct means of avatar animation.
Avatar-object interactions are potentially complex issue (e.g. how can an avatar accurately take and hold an in-world object – say an apple) through puppetry? If the apple is a physical object, does it collide when held? Does it become an attachment? If the latter, how is this registered, together with hold is it properly released from the attachment system? etc.).
A suggestion for handling avatar’s handling objects is to have some for of temp-attach system or to use a key frame motion (KFM) system to match the position to the avatar’s hand, allowing the avatar can hold the object without directly “owning” it (thus also avoiding permission system issues).
Collisions also raise questions: avatar arms currently do not collide, and so would not under puppetry. So what about cases of simple interactions – flicking a light switch or similar. These are not “proper” collisions per se, but are rather event-triggered; how can this be managed if there is no actual collision between the scripted object and an avatar’s arm / hand to trigger the associated event?
In Brief
It has been suggested that a version number is included in puppetry-related messaging, so that changes to message formats are not read by versions of the viewer unable to do so, thus reducing the risk of crashes during development / testing.
It has been indicated that puppetry will eventually have LSL support for LEAP. Although what form this will take and how the simulator will track things is still TBD, as currently animations are entirely viewer-side and untracked by the simulator.
There is concern that understanding of the potential of the puppetry project isn’t being fully understood by creators (and others) as it is being seen more as a “VR thing” than an ability to much improve avatar animations and their supporting systems / constraints, including the IK system.
How to manage network latency also formed a core discussion, together with making better use of the Havok physics sub-licence to allow the viewer do a lot more of the work, and simply stream the results through the simulator to other viewers.
The following notes were taken from the Tuesday, November 8th, 2022 Simulator User Group (SUG) meeting. They form a summary of the items discussed and is not intended to be a full transcript. A video of the entire meeting is embedded at the end of the article for those wishing to review the meeting in full – my thanks to Pantera for recording it.
Server Deployments
At the time of writing, a server deployment thread had yet to be published.
On Tuesday, November 8th, the Main SLS and Events channels were restarted without any simulator update being deployed leaving them on simulator version 575585.
On Wednesday, November 9th, simhosts on the RC channels will again updated with simulator release comprising the new Linkset Data capability (see below for more).
Whilst originally deployed on Wednesday, November 2nd, 2022, this release had to be rolled by on Friday, November 4th, 2022. See BUG-232866 “Each parcel is using the Region’s environment instead of the Parcel’s environment settings”.
Available Official Viewers
No changes to the current set of official viewers at the start o the week, leaving the list as:
Release viewer: version 6.6.7.576223 – MFA and TOS hotfix viewer – November 1.
VS 2022 RC viewer, version 6.6.8.576310, issued November 4 – utilises Visual Studio 2022 in the Windows build tool chain
Maintenance P (Preferences, Position and Paste) RC viewer version 6.6.8.576321, November 3.
Project viewers:
PBR Materials project viewer, version 7.0.0.576331, issued on November 3.
This viewer will only function on the following Aditi (beta grid) regions: Materials1; Materials Adult and Rumpus Room 1 through 4.
There are unconfirmed reports that GPUs are running noticeably hotter with this viewer than other viewer.
Puppetry project viewer, version 6.6.3.575529, issued on October 12.
Performance Floater / Auto-FPS project viewer, version 6.6.5.575378, October 4.
Love Me Render (LMR) 6 graphics improvements project viewer 6.6.2.573263, July 21.
Linkset Data (LSD)
Linkset Data is a new collection of script functions and one optional event that reads and writes key-value-pairs to a small 64kb table of data that is part of a root object.
It works similarly to Experience Key-Value store, but:
It does not require an underpinning experience – the data lives with the object that sends and receives the data.
Only scripts in the same linkset will be able to read the data written with this feature.
Important Note for the initial deployment:
Like all scripts containing new LSL functions, scripts running LinksetData calls will only run on regions running version 2022-10-27.576126 or newer (so only the RC channels to start with).
However unlike some other functions if you move an object containing Linkset Data (or teleport wearing an object containing Linkset Data) from a region that supports the capability to a region that does not support it, all Linkset Data stored with the object will be lost, even if you go back to a region that supports the feature.
This limitation will no longer exist once the back-end support for the capability has been deployed to all regions on the Main grid.
BUG-232037 “Avatar Online / Offline Status Not Correctly Updating” – this is unlikely to be addressed until 2023, as the remaining simulator update slots for 2022 now have updates assigned to them.
LL believe that they may have a fix for the Group chat issue of open Group chats appearing to freeze in their viewer tab, requiring the chat be closed and re-opened. The fix is being tested on Aditi.
The meeting revolved around a discussion on LSDFindKeys and sorting – please refer to the video for details.
llGetSimStats is getting “new fangs” (essentially everything from the Statistics floater is being added). The update is to be deployed in the New Year. Further information available in the meeting video.
Extended chat ranges within regions: this is described as “still in the works”. Apparently, there have been concerns about privacy on the viewer side which mean that, until addressed, extended chat range will remain a Linden only function.
Are usually chaired by Reed Linden, who is the Lab’s Product Manager for the Second Life front-end web properties (Marketplace, secondlife.com, the sign-up pages, the Lab’s corporate pages, etc.).
A video of the meeting, courtesy of Pantera, can be found embedded at the end of this article (my thanks to her as always!), and subject timestamps to the relevant points in the video are provided. Again, the following is a summary of key topics / discussions, not a full transcript of everything mentioned.
All of the currently planned updates are complete and are awaiting the opportunity to “turn them all on”. This will likely happen (with an announcement) ahead of US Thanksgiving, 2022.
Some of the noted updates include:
Merchant and store names will no long be searched in product searches.
Searches for exact matches (using quotation marks around search descriptors) has been added.
Wildcard (e.g. using *) will be possible.
The back-end supports fuzzy matching to better handle typos when inputting searches.
There should be a noticeable increase in speed of search results being returned.
Once running, these updates will allow LL to add-in the relevance engine AI to the Marketplace search (as a separate API entity to the relevance engine already running on the web search).
Work will resume on Marketplace Styles (allowing multiple colours, etc., for an item to appear within a single listing rather than each requiring its own listing) as soon as the MP Search updates are officially enabled.
It is hoped this capability will be available towards year-end.
It will obviously be up to merchants as to whether they use it to group variances in a product within a single listing or continue to list them separately – single listings for multiple versions of an item will not be mandatory.
A complete re-write of every route by which users can obtain and hold land, from Premium (+Plus) Linden Homes, obtaining Mainland (incl. Abandoned Land), and private island regions, and renting from private estates.
The first element of the land work to be user-facing will be the new Land Portal, a central hub from which to get to all aspects of land “ownership”.
Overall, this work is not liable to be surfaced much before the end of 2022.
When it does, it should be looked upon as a template / proof of concept for overhauling the rest of the Second Life web properties to give them a coherent appearance; make it easier to maintain existing web portals and pages and to add new ones; make SL’s web presence more performant overall and ensure it works on mobile devices as well as desktops / laptops.
The new subscription option is to be called simply (if possibly confusingly) “Plus”.
This is designed to sit between Basic and Premium.
Its core intent is to unlock the ability to hold land on the Mainland, although it will have a modest stipend associated with it + a small bump in the number of allowed Groups.
Pricing is subject to the formal announcement that Plus is available, which is anticipated as being by the end of November.
It is hoped that once available and given time to determine how it performs / users respond to Plus, that further subscription levels – which may possibly include an “a-la carte” option – can be defined and added to the selection.
Premium Plus (and Premium) to be Renamed in the future?
It was suggested that the new subscription level would be better named “Basic Plus” – something that was not dismissed by Reed as an informal means of referencing it.
However, the Lab is apparently considering single-word names for all current and future subscription offerings, and Reed indicated that if this is the case, then Premium Plus is likely to be renamed at some point in the future, and this renaming might extend to Premium as well.
In Brief
It is hoped that a future Marketplace update will allow store owners to have access to search metrics for their items (e.g. which items are being popularly searched / purchased, etc.). However, this is not part of the Search updates described above.
The web properties updates will likely include improvements to the web version of the World Map. However, what these changes may be & which they might be implemented is very much still TBD.
Web profiles will not be entirely shut down for as long as the profile Feed remains popular with users – this is the one element of Web Profiles that has not been moved back into the viewer (and appears unlikely to do so).
It has been noted that if a user has the Profile Feed set to Private, the new Legacy Profile viewer code shows a broken version of their web profile in the Web tab.
For all other discussion points, please refer to the video below.
Next Meeting
Wednesday, December 7th, 2022. Venue and time per top of this summary.
Inara Pey: Living in a Modemworld 