Category: SL User Group Meetings

2022 Puppetry project week #49 summary

Posted on by Inara Pey
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, December 8th 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.
  • There is also a public facing Kanban board with public issues – those experiencing issues can also contact Wulf Linden.
  • Those wishing to submit code (plug-ins or other) or who wish to offer a specific feature that might be used with Puppetry should:

Further Information

Meeting Notes

Viewer and Plug-in Updates

  • A new version of the Puppetry project viewer – version 6.6.8.576972 was issued on December 8th, available on the Alternate Viewers page (until a further version is issued).
    • This version includes an overhaul to the protocol used between LEAP plug-ins and the viewer. For example, Inverse Kinematics calculations are done earlier in the process which will make viewer performance better when more than one avatar is using Puppetry.
    • Please be certain to use both a new viewer and a new set of plug-ins from https://github.com/secondlife-3p, and update any projects or code you might be working on.
    • This version may have a crash bug.
  • Leviathan Linden is still working on updating the wiki documentation to reflect the new API.
Leviathan Linden demonstrating the use of puppetry to move his avatar whilst doing the “pane of glass” mime in front of a suitable capture device. Note that his legs remain static (moving in line with his hips) as puppetry does not (yet) support full body tracking
We changed the way Puppetry expects to get its data for two reasons: 1) we want to only do IK for your own avatar, then just send the joint rotations to everybody else; 2) if someone writes a plug-in that happens to know best what all the joint rotations should be (e.g. it has done its own IK, or is doing full mocap) then it can just specify all parent-frame rotations of the joints. So, now that THAT plug-in mode is unblocked, we can start trying to fix our own IK.

– Leviathan Linden explaining the changes to the way puppetry and managed by the viewer

In Brief

  • There are currently no updates to the Inverse Kinematics (IK); it is described as being “hard”.
  • It has been suggested that the viewer could “do more” in respects of IK, etc.
    • However, this information needs to be transmitted to other viewers able to “see” what is going on, which requires messaging and updates through the simulator, which can lead to the viewer being less than trustworthy in terms of what it is showing and what is going on (due to missed updates, etc due to the bandwidth load).
    • But, if the simulator is tasked with managing all the computations for IK and sending the results to connected viewers (reducing the amount of traffic and potential loss of messaging), it puts a potentially high compute load on the simulator (imagine the simulator trying to manage the IK for 50+ avatars at an event, tracking the movement, interactions, etc.).
    • A potential trade off here is to have a viewer run the IK calculations for the avatar it is controlling, and package that information for streaming to other viewers connected to the region’s simulator with minimal sanity checking (e.g. to ensure the avatar’s position in the viewer is properly constrained to within a few metres of its location as calculated by the simulator). On receipt, the sanity-checked data can then be played back without the need for the receiving viewer having to carry out IK calculations for itself on the avatar(s) it is “watching”, and carrying out some minimal sanity checks of its own.
  • Rider Linden is investigating having the simulator track the motion from a puppetry viewer in a way that does not impact simulator performance “too badly”. The options he’s looking at are:
    • Having the simulator suck the data out of the puppetry messages as they are sent through it, or
    • Using a new message the viewer can use to report the locations of it’s attachment points, and the simulator tracks these – which Rider sees as the preferred option.
    • This later method could – among other things – be expanded to work with animations in general. In addition, if tied tied in to the entire animation system (viewer computes its animation frame puppetry+legacy) to produce results, then the results could be made to scripts.
    • In regards to interfaces for this, Rider is of the opinion that scripts should reference attachment points since those can act as proxies for bone locations and most general creators, scripters and residents are familiar with them. and it avoids having to introduce a new concept of bones into LSL.
  • Collisions: the above spawned a related discussion on providing additional data such as geometry information (e.g. spherical bounding radius or a shape approximation) to allow collisions to be enabled from IK, and allowing “snap to” functionality (e.g. you reach for a glass and the avatar hand snaps to it on detecting the collision).
    • However, rather than allowing allow physics collisions on an attachment points (which might over-complicate the avatar model in the Havok physics engine), Rider suggested having a property (sphere) that could be set on an attachment that enabled it as a physics volume.
My thought is that collision aware attachment points, along with being able to detect and set their positions in space will be enough to get us 90% of the way towards being able to hold hands in world.

– Rider Linden

  • Leviathan noted there was a bug where an avatar with non-unity scale on its bones would be broken under puppetry (misalignment of bones). This should now be fixed, but it allowed him to add the theoretical ability to modify the scale of a joint in its parent-frame (an example plug-in script to demonstrate ho this works has yet to be written).

Date of Next Meeting

  • Thursday, January 19th, 2023, 13:00 SLT.

December 2022 Second Life Web User Group summary

Posted on by Inara Pey
The Web User Group meeting venue, Denby

The following notes cover the key points from the Web User Group (WUG) meeting, held on Wednesday, December 7th, 2022.

These meetings:

  • Are held in-world, generally on the first Wednesday of the month – see the SL public calendar.
  • 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.

Marketplace

Marketplace Elastic Search Overhaul

[Video: 4:29-7:00]

  • The drive to get the MP search updates release is continuing.
    • It had been hoped that this would be completed by US Thanksgiving, but last minutes issues resulting from the sheer size / volume of the MP (which cannot be replicated in test environments) prevented this from being achieved.
    • The aim is now as soon as everything is working as anticipated.
    • Those using the Marketplace recently may have noticed some glitches with search – this has been due to the Search team banging on things under the hood in order to get the updates deployed.
  • This work is essentially the same kind of back-end update as carried out with Web search a few months ago, with the emphasis on faster, more robust performance, together with new search options, including:
    • Merchant and store names will no long be searched in product searches.
    • Wildcard (e.g. using *) will be possible.
    • Better exact matching against search terms
    • 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).

Marketplace Styles

[Video: 7:15-7:54]

  • 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. As such, Styles will not be deployed in 2022, but will be the first MP update for deployment in 2023.
  • 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.

Marketplace Refresh / Rebuild

  • This is still being looked at as a primary project for development and possible initial deployment in 2023, and as such will likely form a focal point for discussions and feedback through Web User Group meetings in 2023.
  • The work will at least comprise a refresh of the Marketplace appearance and the addition of further desired functionality; because of this, there is a push within LL to completely rebuild the Marketplace from the ground-up.
  • [Video 13:54-14:05] Any rebuild of the Marketplace would not require merchants to re-upload there items: a migration of listings from the current MP to any new MP would be provided.

New “Plus” Subscription Level and Beyond

[Video: 8:00-10:34]

  • The Plus subscription level was launched on November 18th, 2022 – for details please refer to the official blog post and my own reporting on the release.
  • Work is continuing to bed this in alongside of the other subscription options.
  • The Lab is generally pleased that the majority of users appeared to understand what they were trying to achieve within the introduction of Plus.
  • Plus is the last of the currently-planned subscription options the Lab has on the boards, and there are currently no plans to make further offerings available.
  • However, consideration is still being given to providing future possible options, such as:
    • A “Premium A-la Carte” level whereby your subscription fees are based on the options you select from a list.
    • Subscriptions based on specific interests (such as a “creator subscription”.
    • BUT these are only in the “Soon™” phase, indicating they are a feature or capability Linden Lab would like to implement, but which is not far enough along in development to determine if or when it might / could / will be implemented.
  • [Video 21:19-22:42] Will subscriptions ever support payment in Linden Dollars?
    • This is being considered, although the overall implications, etc., have yet to be fully understood.
    • In particular, it could have ramifications on the status of the Linden Dollar (which is not at present regarded as a virtual currency, but could be if it were to become a recognised payment system for benefits.
    • As such this is an idea that is not even in the “Soon™” criteria of thinking; however, there is an internal goal to make it possible to pay for “all things” SL-related in L$ – the questions are really what will this do to the Linden Dollar in making it a virtual currency; how will that effect how the LindeX will function / be regulated, how Tilia can support such a move, etc.

In Brief & Q&A

Video, 17:00 onwards, unless indicated.

  • [Video: 12:10-12:54] Real-time population stats:
    • The Lab is working on improving the ability for the Destination Guide to provide a real-time reflection of the number of avatars within a specific in-world location.
    • Should this be achievable, the capability will be extended into Search so that Places searches will return the number of avatars within the location at the time of the search.
    • This work might be completed by 2022 year-end.
    • [Video: 14:20-14:54] Concerns were raised over the use of unregistered bots (i.e. avatars not correctly flagged as Scripted Agents) to game the numbers. LL is aware of the unregistered bot issue across Second Life, but outside of users reporting them on finding them, there is no easy solution to this issue.
  • [Video: 19:00-19:36] With the acquisition of CasperTech, will Caspertech Drop Boxes and vendors be integrated into the Marketplace?  Yes. However, what form this will take and when it might be undertaken has yet to be determined internally at the Lab / with Casper Warden.
  • [Video: 23:22-29:42 + via text earlier in the meeting] The suggestion was made to make OpenSpace regions (aka Void or Water regions – not to be confused with the 2008 OpenSpace offering which morphed into Homesteads in 2009) as a part of a “Super Premium” offering (+ a nominal tier fee on to of the subscription fee) purely for use as private homes.
    • These regions have a Land Capacity of 1000, and are limited to 10 concurrent avatars, and are regarded as being for light use and a special purchase via support with the requirement that the purchaser must hold at least one Full private region.
    • While the idea was taken under advisement, such a offer could still impact the existing private estate market, and so would have to be considered carefully.
  • The OpenSpace discussion further raised the idea of having these regions potentially on an on-demand basis (e.g. only spun-up when avatars are present within the regions. H
    • However, it was pointed out that regions, whether “up” or “down” require grid slots, and the infrastructure configurations means that grid slots have underpinning hardware, so there is still a potential hardware cost, regardless of whether a region is spun up for use or not.
    • As such, this cost impact would have to be resolved in order for regions (or a specific region type) to be made available through an on-demand system.
  • [Video; 30:11-30:35] Land ownership Overhaul:
    • As noted in previous WUG summaries, this is 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.
    • A focus at the moment is on defining what “land” and the associated terms around it actually means (e.g. what is “renting land”? Where can land be rented? How is it rented?, etc.) .
    • The first element that will be surfaced is a new Land Portal, a central hub from which to get to all aspects of land “ownership”.
  • For all other discussion points,  please refer to the video below.

Next Meeting

  • Wednesday, January 4th, 2023. Venue and time per top of this summary.

 

 

2022 SUG meetings week #49 summary

Posted on by Inara Pey
Perpetuity, October 2022 – blog post

The following notes were taken from the Tuesday, December 6th, 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

This week will see all simhosts on all channels restarted, but no deployments.

The hoped-for RC release (which includes a fix for BUG-229301 “Maximum Memory allowable by scripts not being reset until teleport or relog”) has been delayed as a result of a fix being required for an odd crash which could cause some regions to crash on starting. This has now been resolved, but the fix needs to pass through a QA cycle before any release is made, so the deployment should now occur in week #50.

Available Official Viewers

This list reflects those viewers available via Linden Lab.

  • Release viewer: version 6.6.7.576223 – MFA and TOS hotfix viewer – November 1 – No change.
  • Release channel cohorts (please see my notes on manually installing RC viewer versions if you wish to install any release candidate(s) yourself).
    • Performance Floater / Auto-FPS RC viewer, version 6.6.8.576737, November 28.
    • Maintenance P (Preferences, Position and Paste) RC viewer version 6.6.8.576863 Monday, December 5.
    • 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.576966, December 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.
    • Love Me Render (LMR) 6 graphics improvements project viewer 6.6.2.573263, July 21.

In Brief

Refer to the video below for more information on the following:

  • There is a generic Puppetry-related discussion (Kinnect), but as there is a Puppetry meeting due on December 8th, so any updates will be covered in my summary of that meeting.
  • There is a similar generic discussion on the complexities of the PBR Materials Project, which is covered in my CCUG updates.
  • A discussion on potential LSD bugs / issues – no specifics from LL’s side, as Rider Linden (who runs the LSD project) was absent the meeting.

 

2022 week #48: CCUG meeting summary

Posted on by Inara Pey
Village de Roqueblanche, October 2022 – blog post
The following notes were taken from my audio recording and chat log of the Content Creation User Group (CCUG) meeting held on Thursday, December 1st 2022 at 13:00 SLT.  These 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. Note: unfortunately, my recording software failed at the 50 minute mark of the meeting, so the end of the meeting and the after-meeting discussion were not recorded, so some discussion points are missing from this summary.

Official Viewers Status

Available Viewers

On Friday, December 2nd, the PBR Materials project viewer updated to version 7.0.0.576966 on Friday December 2nd. This viewer will only function on the following Aditi (beta grid) regions: Materials1; Materials Adult and Rumpus Room 1 through 4. The following reflect the rest of the current official viewers available through Linden Lab.
  • Release viewer: version 6.6.7.576223 – MFA and TOS hotfix viewer – November 1 – No change.
  • Release channel cohorts (please see my notes on manually installing RC viewer versions if you wish to install any release candidate(s) yourself).
    • Performance Floater / Auto-FPS project viewer, version 6.6.8.576737, November 28.
    • Maintenance P (Preferences, Position and Paste) RC viewer version 6.6.8.576812 on Monday, November 28.
    • VS  2022 RC viewer, version 6.6.8.576310, issued November 4 – utilises Visual Studio 2022 in the Windows build tool chain.
  • Project viewers:
    • Puppetry project viewer, version 6.6.3.575529,  issued on October 12.
    • Love Me Render (LMR) 6 graphics improvements project viewer 6.6.2.573263, July 21.

General Viewer Notes

  • The Lab is aiming to get the Maintenance P RC viewer promoted to release status before year-end.

glTF Materials and Reflection Probes

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 project viewer is available 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.

Status

  • Please also see previous CCUG meeting summaries for further background on this project.
  • Bugs and regressions continue to be reported via the project viewer on Aditi,  and it is now unlikely the project will advance to a release state before early 2023 (end of 2022 always seemed ambitious).
  • Despite hopes to the contrary, a lot of legacy content is impacted when rendered via the glTF PBR path,  largely as a result of using linear alpha blending.
    • As a result, LL are working on turning to smooth around some of the edge cases without having to introduce a code fork in the viewer between “legacy” alpha handling and PBR alpha handling.
    • The aim remains to preserve as much of the appearance of legacy content under PBR rendering and reflection probes, without necessarily being slaved to preserving its looks over time. The major exception to this is would be situations where PBR rendering reveals seams between layers.
    • However, if it proves necessary, an “opt out” button will be provided to switch out of linear alpha blending.
  • mikkTSpace tangents affect all objects rendered in the PBR viewer. Unfortunately, due to the way mesh data has been stored prior to the PBR viewer, this means that creators wishing to get exactly the same results in their mesh models as they saw in their tool of choice (e.g. blender, etc.) when building their models, they will need to re-upload those models. This might result in a slight increase in the object’s Land Impact, if done.
    • This does mean, however that all tangents on uploaded meshes will be correctly handled going  forward.
  • Capabilities will change with the PBR viewer: for example, there will be a basic glTF materials editor within the viewer; texture will rotate from a corner, rather than the centre (per the glTF specification extension for texture transforms); the upload will allow for the upload of individual materials from a glTF file.

Bakes on Mesh and Materials

  • Providing materials support to Bakes on Mesh has been a long-standing request which has been thus far resisted by the Lab on the grounds of the impact it would have on the Bake Service  – both in terms of code updates and the potential number of servers used.
  • However, at the CCUG, Runitai and Vir floated the idea of materials on Bakes on Mesh being added – but only for the PBR rendering path. This would “drastically” cut down on the amount of back-end work required to make materials on BOM possible, and would mean that all avatar wearables would be Materials-capable.
  • This is not something that has been currently road mapped for implementation at any time by LL, and it would require time and effort to determine a mechanism to manage it, but the support were there for it, it is something that might be considered.
  • If this work was carried out, it might also pave the way for terrain painting – another popular request.
  • As PBR Materials is released, it will become the focus for SL going forward; whilst efforts will be made to ensure “pre-PBR” contact continues to look right, whether or not work is put into trying to “pull” legacy materials content into PBR is questionable, simply because the layered complexity of the underpinning code =, the updating / altering of which can result in content breakage.

In Brief

  • As noted in the summary of the last meeting, there are reports that the PBR project viewer generating some 10% more CPU temperature and 17% more GPU temperature.
    • LL are working on updates they hope will see any GPU increases return to the levels of the current release viewer.
    • Issues with CPU temperature are not believed to be related to PBR, but more to general texture rendering, where a couple of errors have crept in and are being actively corrected.
  • LODs and Land Impact:
    • Lower value LODs on models. Some creators attempt to “game” Land Impact by having extremely low values as their low-end models, thinking they are “never seen”; unfortunately, these are seen by people running SL on very low-end machines and thus can account for new users feeling SL “looks rubbish due to the official viewer defaulting to a RenderVolumeLODFactor of 1.25.
    • The RenderVoumeLODFactor setting will be more dynamic be default in the upcoming Performance Floater / Auto FPS viewer, although extremely lower LODs on models should still be avoided.
    • More broadly, LL is still considering how to better adjust the Land Impact system and the mesh uploader so that creators are not penalised for creating accurate LODs on their models (one of the goals originally stated for project ARCTan).
  • Linden Lab will be closed over the holiday period from end of business on Friday, December 23rd, 2022 through until start of business on Tuesday, January 3rd, 2023 (except for urgent support cases).

Next Meeting

  • Thursday, December 15th, 2022.

2022 SUG meetings week #48 summary

Posted on by Inara Pey

Moorcroft, October 2022 – blog post

The following notes were taken from the Tuesday, November 29th, 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

This week will see all simhosts on all channels restarted, but no deployments.

There should be a new RC release available in Week #49 (commencing Monday, December 5th, 2022. This should include a fix for BUG-229301 “Maximum Memory allowable by scripts not being reset until teleport or relog”.

Available Official Viewers

On Monday, November 28th:

  • The Performance Floater / Auto-FPS project viewer was promoted to RC status with the release of version 6.6.8.576737.
  • The Maintenance P (Preferences, Position and Paste) RC viewer re-upped to version 6.6.8.576812.

The rest of the official viewer currently available official viewer remain as follows:

  • Release viewer: version 6.6.7.576223 – MFA and TOS hotfix viewer – November 1 – No change.
  • 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.
    • Puppetry project viewer, version 6.6.3.575529,  issued on October 12.
    • Love Me Render (LMR) 6 graphics improvements project viewer 6.6.2.573263, July 21.

In Brief

Refer to the video below for more information on the following:

  • There has been a noticed uptick of objects failing to rez / render (see this forum thread). Whilst the issue has been around long enough to have been reported at least once (see: BUG-9439) and for workarounds such as ALT-zooming out  a long distance from a region and the using ESC to “jump” back to it, it is thought it issues might be related to the Interest List (simply put, the exchange of data between simulator and viewer as to what is in the region, what you should be able to see, how / when it is updated, etc). LL have noted the uptick  in issues, although no underpinning cause has been indicated, although there is an internal lean towards the Interest List theory.
I’m fairly certain that the current vanishing object issue is in the Interest List. I’m not sure what we changed that could have aggravated though. I’ve been seeing it pretty regularly for about a month now.

– Rider Linden

    • The discussion of this issue takes up the majority of the meeting, and touches other issues related to object rendering, / rezzing / re-rendering, and also includes views on improving the robustness of the Interest List as a whole – including a capability function (for which LL has requested a Feature Request Jira).
  • There is some further discussion on combat in Second Life,  and the need for improved projectile systems and generally improving the current capabilities. This follows on from the last meeting, and involves this forum discussion.
  • The final 10 minutes of the meeting touches on potential updates to the recently release Linkset Data (LSD)

 

2022 SUG meetings week #47 summary

Posted on by Inara Pey

Green Story, September 2022 – blog post

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.