December 2023 SL Web User Group (WUG) meeting summary

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 6th, 2023. They form a summary of the items discussed and is not intended to be a full transcript. A video of the meeting, recorded by Pantera Północy, is embedded at the end of this summary – my thanks as always to Pantera for recording it and making it available.

Meeting Overview

  • The Web User Group exists to provide an opportunity for discussion on Second Life web properties and their related functionalities / features. This includes, but is not limited to: the Marketplace, pages surfaced through the secondlife.com dashboard; the available portals (land, support, etc), the forums.
  • As a rule, these meetings are conducted:
    • On the first Wednesday of the month and 14:00 SLT.
    • In both Voice and / or text.
    • At this location.
  • 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.

Marketplace

Supporting PBR Creations

Sntax Linden opened the meeting to idea as to how LL can support makers of PBR content via the Marketplace. Key feedback included:

  • At least a clear category distinction for PBR-enabled items.
  • More preferably the ability for creator to indicate whether their product is “classic Materials” (or some such – the technical term is “Blinn-Phong”, which is likely a confusing mouthful for most users) or “PBR-enabled”, in the same manner as they can note a product as “100% Mesh” or “Partial Mesh”.
  • Some form of iconography on listing pages to indicate content (e.g. whether it is mesh (or partial mesh) and / or PBR enabled and / or rigged for wearing primary and secondary types; or whether it is “classic Materials (or some such), with/without baked lighting, etc.).
    • The problem here is that if the icons become too granular, they risk becoming confusing / off-putting when seen in listings and / or the simply confuse users unfamiliar with the MP, unless some form of cheat sheet / icon key is provided on every listing.
    • The above might be mitigated against if the icons are set with tooltip, so that when moused-over, the tip displays a brief description of the icon’s meaning.
  • If icons were to be used, have them act as filters to help narrow / manage searches.
  • Addition of specific search filter such as mesh+rigged+baked and lighting+PBR.
  • Further filters in the left-side filter list to distinguish PBR components / kits (e.g. Building and Object components → PBR Materials).
  • This broadened into a more general discussion on a greater use of distinguishing icons (with tooltips) within listings Marketplace in general.

Senra and Mesh Bodies

  • The above also focused on the Senra avatars, and the need to distinguish creations for these so that new users using the Senra avatars can more easily find clothing and accessories to fit them.
  • The above seems particularly pertinent given the “official 1.0” release of Senra made on Wednesday, December 6th, 2023 (the August release of the avatar now being referred to as a “beta” release), so there is potentially going to be an uptick in creator-provided content for Senra.
  • This raised the question of a generic category and filters for mesh body types for easier product location (e.g. Human, Animals, Monsters, Fantasy, etc.) – although this could be subject to confusion when listing / trying to find things like anthropomorphic mesh characters.
  • Garfield Linden suggested an open-ended tagging system for mesh body support: creators could freely input the supported mesh body as a tag, selecting from a drop-down that shows how many other products currently have each tag applied, with the ability to arbitrarily add new tags to the system. These same tags could then be used by residents to filter their search results.
    • Potential problems here are with scalability / accuracy: how many creators will select tags as opposed to just typing in their own? How unwieldy would this eventually make the drop-down list? How will the tag list be managed to prevent cluttering with typos (e.g. “nial” for “nail”, etc.) & the consequent accidental use of mistyped tags?
    • A suggested solution for the above is to have the field used by creators to add tag names actually display the total number of times an entered tag has been used (so a typo will hopefully show 0). This could also provide an easier means for creators to select existing tags without having to necessarily use a full drop-down list for tags.

In Brief

  • The Linden Homes store (see: Looking at the New Linden Homes Store) is to gain search filters for finding themes easier, and also notifications. These should be deployed before year-end.
  • There is a known issue with Marketplace fuzzy search such that partial names may not produce anticipated results.
  • There was a general discussion on keyword abuse – including some stores using what might be regarded as keywords in product titles (e.g. the use of “bed” in the name of tattoos), which can skew search results (although may not always be intentional).
  • There was a repeated request to prevent Marketplace stores using stars in their names, enabling them to show up in searches using the star rating system. This is something the Lab is looking at.
  • The end of the meeting includes a general discussion on possible improvements in Marketplace gifting (e.g. allowing direct gifting, without having the items go to the user’s main shopping basket). This was coupled with requests with a more flexible shopping basket system (e.g. having the ability to use a basket to store items for later purchase, whilst also being able to purchase a selection of options within it when going to the check-out).
  • LL is still mulling how to best integrate CasperVend with the Marketplace.
  • Please refer to the video below for other topics.

Next Meeting

  • Wednesday, January 3rd, 2024.

2023 SL SUG meetings week #49 summary

Castle Dracula, October 2023- blog post

The following notes were taken from the Tuesday, December 5th 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 meeting is embedded at the end of this summary, my thanks as always to Pantera for recording the meeting and providing it.

Meeting Overview

  • The Simulator User Group (also referred to by its older name of Server User Group) exists to provide an opportunity for discussion about simulator technology, bugs, and feature ideas.
  • These meetings are conducted (as a rule):
  • They are open to anyone with a concern / interest in the above topics, and form one of a series of regular / semi-regular User Group meetings conducted by Linden Lab.
  • Dates and times of all current meetings can be found on the Second Life Public Calendar, and descriptions of meetings are defined on the SL wiki.

Simulator Deployments

  • Tuesday, December 5th: the SLS Main channel was re-started without any simulator updates being deployed.
  • Wednesday, December 6th: the “Fall Colours” maintenance update may be expanded across all RC channels from BlueSteel / Preflight. This update includes llRezObjectWithParams, llIsFriend, but will not include the game controller updates.
    • However, following its initial deployment in Week 48, “Fall Colours” was found to have bugs with collision sounds (e.g. transferring them across region boundaries and with being able to silence them), with the result that the sounds can be repeated multiple times (see: BUG-234757 “Repetitive Collision Sound?” and this forum thread). As a result, at the time of the meeting, LL were still discussing whether or not to consider these issues as “blockers” against the release being more widely deployed.
    • If the deployment to all RCs goes ahead in the next week or two, it will represent the last server deployment for 2023.

No Change Window

  • The end-of-year No change window for simulator and official viewer releases will come into effect on the week commencing Monday, December 18th, 2023 and will remain in place until Tuesday, December 2nd, 2024.
  • Linden Lab offices will be closed for all but emergency support from close of business Friday, December 22nd, 2023, and will re-open on January 2nd, 2024.

Viewer Updates

On Tuesday, December 5th, the Maintenance-W RC viewer updated to version 7.1.1.7088402585.

Other viewers in the pipe remain as:

  • Release viewer: version 7.0.1.6894459864, the glTF / PBR Materials viewer, issued November 17, promoted November 28.
  • Release channel cohorts:
    • Maintenance V(ersatility) RC viewer, version 7.1.1.7039128750, December 1.
    • Maintenance X RC, version 6.6.17.6935636398, issued November 21 – usability improvements.
    • Maintenance Y, version 6.6.17.6935642049, issued November 21 – My Outfits folder improvements; ability to remove entries from landmark history.
    • Emoji RC viewer, version 6.6.15.581551, August 31.
  • Project viewers:

Game Controllers

  • Leviathan Linden has previously considered the idea of changing the signature of the LSL event to provide per-channel info (input, value) rather than all of the controller state (buttons masks + all axes). However, he has discovered that such an event system would make it difficult to handle multi-modal input: e.g. some_button + axis_state.
  • This is because the state of each input would arrive in different events, and the order or arrival would matter, with Leviathan noting what he already has in place would likely win out in the end, negating any changes.
  • Currently, he is trying to make it possible to supply game_control input with keyboard input, but without having to completely rewrite the keyboard mapping and other related UI.
  • The Gingerbread maintenance branch with the prototype game_control feature has been redeployed to the Beta grid, and can be found on the following Aditi regions: Aegis Island, Blake Sea – Turnbuckle, Cloud Sandbox 1, Cloud Sandbox 2, Firestorm Aerodrome, Gothlauth, Hona Lee Puff, Jigglypuff, Laefeon, LR151, LR 152, Mauve, Moonberry, Morris, SG2, and Smithereens.
  • A point to note here is that the game controller work does not currently support 3dConnexion SpaceNavigator Mouse many of us use for things like flycamming, photography, filming, etc., but he is promised not to break support for the SpaceNav functionality.

In Brief

  • Combat Updates:
    • Rider Linden has published his outline document on improving SL’s combat capabilities, which can be found within the combat systems discussion thread on the forums. Feedback is requested from users engaging in combat games in SL.
    • This lead to a discussion on combat capabilities and needs throughout the rest of the meeting – please refer to the video below.
  • A question was asked on fog and distance hazing, this is something the graphics team hope to implement within the on-going glTF project – see: 2023 week #46: SL CCUG meeting summary: PBR status & current release plan.
  • BUG-234598 “Avatar hit box rotating bug” has been accepted by LL, but is proving difficult to reproduce.

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

2023 SL viewer release summaries week #48

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

Updates from the week through to Sunday, December 3rd, 2023

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.0.1.6894459864,the glTF / PBR Materials viewer, issued November 17, promoted November 28 – NEW.
  • Release channel cohorts (please see my notes on manually installing RC viewer versions if you wish to install any release candidate(s) yourself).
  • Project viewers:
    • No updates.

LL Viewer Resources

Third-party Viewers

V6-style

  • Alchemy – GLTF PBR 7.1.1.2251 (Beta build) November 30 (Beta build, but listed here due to the official release of PBR Materials in SL) – download and release notes.
  • Black Dragon updated to version 5.0 (PBR) on December 2 – release notes.
  • Firestorm updated to version 6.6.16.70339 (non-PBR) on November 29 – release notes; my overview.

V1-style

  • Cool VL viewer updated to version 1.32.0.0 (Stable) (PBR) on December 2 – release notes.

Mobile / Other Clients

  • No updates.

Additional TPV Resources

Related Links

2023 week #48: SL TPVD meeting summary + PBR Update

Moochie All Hallows, October 2023 – blog post

The following notes were taken from my chat log transcript and audio recording of the December 1st, 2023 Third Party Viewer Developer (TPVD) meeting, together with the video recording of the meeting made by Pantera – my thanks to her as always for making it and allowing me to embed it in these summaries.

Meeting Overview

  • 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.
  • As a rule, these meetings are:
    • Generally held once a month  the third or fourth Friday, at 13:00 SLT at the Hippotropolis Theatre. See the SL Public Calendar for specific meeting dates.
    • Open to all with an interest in viewer development.
    • Conducted in a mix of text and voice.
  • The notes herein are drawn from a mix of my own chat log and audio recording of the meeting, and are not intended to be a full transcript.

Viewer Updates

  • The glTF / PBR Materials viewer, version 7.0.1.6894459864, was promoted to de facto release status on November 28.
  • The Maintenance V(ersatility) RC viewer updated to version 7.1.1.7039128750 on December 1.

The rest of the current crop of official viewers remains as:

  • Release channel cohorts:
    • Maintenance X RC, version 6.6.17.6935636398, issued November 21 – usability improvements.
    • Maintenance Y, version 6.6.17.6935642049, issued November 21 – My Outfits folder improvements; ability to remove entries from landmark history.
    • Maintenance-W RC viewer, version 6.6.17.6935629493, November 21.
    • Emoji RC viewer, version 6.6.15.581551, August 31.
  • Project viewers:

General Viewer Notes:

  • The promotion of the PBR Materials view marks the second promotion of a viewer built using the Github Actions build page.
  • It is uncertain whether or not there will be a further viewer promotion in 2023. If there is, the most likely candidate would by the Emojis viewer, although at the time of writing, this had had to go through the Github build process (which it naturally will when merged with the release viewer code-base).

PBR Materials Update

[Video: 1:23-8:55]

  • PBR Materials was shipped with a number of known bugs and issues, none of the former of which were considered to be significant enough to block the release, whilst some of the latter required further investigation for repros, etc., and the Lab decided to release whilst investigating.
  • This means a maintenance update is already in progress which will continue additional fixes, and this will also be used to catch issues and bugs reported post-release.
    • One of the post-release bugs uncovered is that – for reasons unknown – disabling transparent water impacts animation playback; see: BUG-234759.
    • Another issue revealed by PBR is that the viewer draws Linden Water twice. (not the entire scene, an issue previously remedied, just Linden Water), and this is being corrected.
  • The request is for bug and issues to keep being reported, simply because PBR Materials now has far more eyes on it, and so things that may have been missed due to the limited number of eyes on things in testing / the multiplicity of ways people use SL, means that some edge-cases, etc., may have been missed.
  • A question was asked if LL had considered off the exposure adjustments (adjusted within a set range through the Sky settings) to prevent the viewer from rendering some scenes excessively bright.
    • The response to this was that the exposure is tied to tone-mapping and a controlled HDR range, as such LL would rather users adjust to designing environments in accordance with the new (glTF-defined) tone mapping, then introducing more granular options into the viewer (such as which tone mapper to use).
    • [Video: 14:58-15:55] However, it was also noted that if TPVs wish to provide their own tone mapping options, this would not be seen as violating the so-called “shared user experience”, as they are regarded as post-processing effects (then don’t actually physically manipulate how objects appear in-world) and they are subjective in how they are seen by individual users.
  • [Video 25:25-33:27] A broader mention of additional glTF work – scene import, hierarchies, etc., some of which is mentioned in my simple  introduction to PBR Materials.
    • Part of this future work will be to look at how automatic LODs for mesh objects are produced, and whether to continue to support them through the uploader (which is limited in its abilities) or to direct content creators to other solutions for generating LODs prior to upload (e.g. via Simplygon and Blender).
    • This conversation also encompasses various limitations common to SL which glTF might alter / improve upon as it is further adopted (such as meshes currently being limited to eight faces due to the platform’s data entry model regarding meshes as prims), plus the potential impacts of changes. Please refer to the video for specifics on this discussion.

Performance Issue

[Video: 3:01-6:10]

  • One issue that is proving hard to consistence repro is that of frequent slow-downs with NVIDIA GL drivers which can result in significant FPS loss in the viewer – see: BUG-234706 for more details.
  • At the time of writing, both LL’s QA and others are trying to consistently repro the problem, however, so of the thinking is is related to a mix of CPU core and GL optimisations running on the host system.
  • The concern here is that where it has been repro’d, it has been with systems using 8-core CPUs and NIVIDIA GPUs (although what the correlation between the two might be in terms of a cause for the problem, is unclear), which could impact a fair percentage of SL users if it proves to be a widespread issue (particularly if it is unresolved when Firestorm makes a PBR release).
  • Those who feel they are experiencing a performance loss over time logged-in which reflects the notes presented in the bug report, and who can dig down into their system data for possible causes, are asked to add relevant comments to the Jira.

In Brief

“Disappearing Objects” Issues

[Video:  9:06-11:45]

Some of these may pre-exist PBR or be related to the PBR release:

  • Objects not rendering at log-in due to the inventory frame load locking main processing with the result that messages to the viewer about some in-world objects are simply dropped, and they are never rendered other than via a re-log (or TP out / back?). LL has a fix for this in progress, but as it causes some additional issues, not ETA on when it might be deployed.
  • There is an issue with mesh objects in particular not rendering (see BUG-234700 “[GLTF] Mesh objects randomly not rezzing properly at login”), but it is currently unclear if this is related to the above issue or the result of something else.
  • BUG-234616 “[PBR] Lights outside of camera frustrum are not rendered until within camera frustrum” – has been accepted by LL, but is still an open issue under investigation.

General Notes

  • [Video: 13:18-13:54] The “Fall Colours” simulator update (currently on the BlueSteel and Preflight RC channels) has a bug related to collision sounds (see: BUG-234757 “Repetitive Collision Sound?” and this forum thread) which is under investigation. It was also noted that Fall Colours is liable to be the last simulator update for 2023.
  • [Video 17:24-25:15] The question was asked if LL would accept either the entire RLVa API (Restrained Life Viewer alternative, as maintained by Kitty Barnett and used by several third-party viewer and analogous to RLV) or a subset thereof.
    • RLV/a have been shown to have a wide range of uses outside of their original intent, some of which have, to a degree been matched / had some level of equivalence via things like Experience Keys in the viewer, while others still remain useful for multiple applications – such as the use of either to manage wardrobe / outfit systems, for example).
    • The short response to this via Runitai and Vir Linden was “probably”, as LL are aware that the widespread use of RLV/a features does create something of a schism between TPVs and the official viewer. As such, a pull request of code / the opportunity to discuss has been offered.
    • This led to a wider conversation on how RLV/a works and just what form of open-source platform SL should be in terms of extensibility / code contributions – please refer to the video for more.
  • [Video 33:41-34:20] Linden Lab Office Closure for Holidays: Linden Lab will be closed other than for emergency coverage from end of business on December 22nd through until start of business on January 2nd, 2024.
    • This means that a No Change window for simulator and official viewer releases will be in place from Monday, December 18th, 2023.
  • [Video: 36:16-41:21] HTTP/2 multiplexing:
    • There is a project in development for upping the simulator and viewer to HTTP/2 (although the viewer will require a Curl update in order to handle it).
    • Requests have been made to extend this work to encompass the Asset Store, which internally at the Lab is seen as a nice to have / good to have, but no actual work in that direction in currently in-hand.
  • [Video: 48:00-End] General discussion on better support for the viewer on Linux, segueing into a discussion of possibly adopting voice options other than Vivox, and what needs to be improved within voice in general.

Next Meeting

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

Firestorm 6.6.16: year-end maintenance

IMPORTANT NOTE

It has been confirmed that Firestorm 6.6.16.70339 has a bug within the client Animation Override (AO) which is affecting multiple users. Because of this, version 70339 is being withdrawn from the Firestorm download page, and will be replaced once a version with the necessary fixes is available. In the meantime, those affected by the issue (not all Firestorm users necessarily are) should consider rolling back to release 6.6.14 to escape the problems. 

More on this available via the official Firestorm blog.

On Monday November 27th, 2023 (SLT), the Firestorm team released version 6.6.16.70339 of their viewer. This is another release to bring Firestorm up to parity with the more recent releases from Linden Lab as well as adding some new / improved options from the Firestorm team. It is also important for two additional reasons:

  • It clears a path for Firestorm to move towards a PBR Materials release in line with the Lab’s move to PBR Materials / reflection probes.
  • It provides a final 32-bit Windows build of the viewer. Going forward, only the 64-bit Windows version will be built and released. See below for more.
Table of Contents

When reading the following, please note:

  • This article is not intended to cover every update / change / improvement within the release. These can be found within the Firestorm 6.6.16. release notes, which also provide full credit details for the changes.
  • This review focuses primarily on the new features included with Firestorm 6.6.16, together with an overview of its parity with Linden Lab’s official viewer code base and and overviews of various updates, improvements and fixes I believe will be of specific interest to Firestorm users in general.

Finally, I have not had time to personally try this release to any great extent, so am not offering any personal feedback on it.

Please note this release is not a Firestorm PBR release. PBR support will be in the next update.

please see A simple introduction to PBR materials, reflection probes & glTF in Second Life if you are unfamiliar with terms such as PBR.

General Notes

Installation

  • Only download Firestorm from the Firestorm website. Do not utilise and other third-party site purporting to offer the Firestorm viewer, and remember Firestorm will never ask for log-in credentials in order to download a release version of their viewer.
  • There is no need to perform a clean install with this release if you do not wish to.
  • Do, however, make sure you back-up all your settings safely so you can restore them after installing 6.6.16.

Version Blocking

As per the Firestorm’s teams standard practice of only supporting 3 active versions of the viewer at any time, note that version 6.6.3 will be blocked from accessing Second Life three weeks from the date of version 6.6.16’s release.

End of 32-Bit Windows Builds

Linden Lab has recently moved their automated viewer build process to Github Actions (GHA) – see here for more. The positive side of this is that Firestorm is particularly well-placed to leverage this change, reducing their own overhead in maintaining a build process whilst also producing more frequent updates. The negative side, however, is that in making this move, Linden Lab removed all of the code libraries required for building a 32-bit Windows version of the viewer.

This means Firestorm 6.6.16 will be the last Firestorm release to support Windows 32-bit, bringing the windows version into line with the Linux and Mac versions

A Note on Inventory Updates

This viewer includes numerous Inventory updates (see below), some of which see changes to the way in which communications between the inventory service and the viewer re managed. Whilst these changes fix a long-standing bug wherein some deleted items became orphaned from the inventory folders and thus invisible, they also mean that these “orphaned” items will now be restored to your Lost and Found folder. So you might want to check Lost and Found and ensure everything in it  is for deletion – or move any returned treasures elsewhere before clearing it.

As this re-creation of old items in Lost and Found can occur randomly, JIRA has been raised with the Lab – see BUG-234508.

Linden Lab Updates

Firestorm 6.6.16.70339 is fully merged up to the following recent Linden Lab viewer releases:

Inventory Extensions

  • The Inventory Extensions pop-up notification

    Viewer version 6.6.15.581961, October 2023.

  • Core features – Inventory item preview image; single folder inventory view. See below for a short overview.
  • Updated Object Profiles: right clicking an inventory item → Properties will display an update profile, which includes the ability to view an associated thumbnail (and create one if there is not one available).
    • Firestorm users can switch back to the old object profile via Preferences → User Interface → Interface Windows → Use Legacy Object Properties
  • Notes:
    • When using the inventory extensions for the first time, the pop-up shown on the right will be displayed.
    • This version of Firestorm includes and upstream fix from that Lab to suppress false reports of packet loss and log spam noise when visiting GLTF enabled regions on a non-PBR-enabled viewer. See BUG-234550.

Maintenance U – Upbeat Upgrades

  • Viewer version 6.6.14.581101, August 2023.
  • Core updates:
    • Increased limits to the number of Estate Managers and Ban list entries in Estates.
    • A move to VLC for improved parcel audio playback (streaming audio).
    • New option: Show Ban Lines On Collision (World → Show) when enabled, will only show ban lines around parcels will only be visible on collision, rather than whenever they are within draw distance.

Inventory Extensions Summary

The Inventory Extension viewer introduced two new features intended to make browsing the contents of your inventory easier. These comprise:

  • Inventory Item Preview – the ability to include thumbnail images (either your own or supplied by the item’s creator) of items within inventory (clothing, body parts, accessories, attachments). These images are persistently linked to the item / folder (unless intentionally deleted or changed) and displayed whenever the mouse pointer is hovered over the related element.
  • Single Folder view: the ability to see the contents of a single inventory folder in its own window.

The Item Preview capability comprises two parts:

  • The ability to view the included thumbnail images on on mouse-over, as noted above.
  • A dedicated tool for creating thumbnail images, as shown below, right
    • Note that thumbnails can also be created via an object’s Properties floater.
Elements from the Inventory Extensions capabilities – view and generating thumbnail images

The Single Folder View allows users to open an Inventory folder within a floater of its own, allowing the contents to be viewed without distraction, with them displayed in in one of three ways:

  • Gallery view – displaying only the thumbnails of those items in the folder for which thumbnails have been created.
  • List View – all of the folder’s contents, displayed much as they are seen within the open folder in Inventory.
  • Combination View – those items with an associated thumbnail will have that thumbnail displayed, those which do not will be listed.

Any folder in Inventory can be opened in this manner by right-clicking on it and selecting Open In New Window from the Inventory Context Menu. Further, the floater displaying the open folder includes:

  • Search (including filtering options) and navigation controls at the top of the floater.
  • The same tools for accessing additional Inventory management options at the bottom of the floater as those found in the main Inventory panel, together with and additional trash can icon to which items can be dragged-and-dropped to move them to Trash (or can be clicked on when one or more items are selected to move all of them to Trash).
The Single Folder View (right) as supplied by Linden Lab and incorporated in Firestorm 6.6.16, and the menu option used to access it. Note the floater here is set to display in the combined view, in this case showing the thumbnail image supplied by the item’s creator 

Important note: Firestorm has had a “Show in new window” option offering similar (but with lesser functionality). This option remains in the viewer for the present, but may be removed in the future. Unfortunately, the Context Menu option for accessing it is displayed directly above the new Open In New Window option (see image above), and the two should not be confused.

Further information on the above capabilities can be found in Looking at the Second Life Inventory Extensions Project Viewer – this blog.

Firestorm Updates

Inventory

Browser-Style Navigation
Inventory browser-style navigation

The ability to page back and forth between visited Inventory folders in a manner akin to the page back / forward buttons in a browser, and to move back up the folder tree via a similar button. These can all be found in the top left of Inventory floaters.

Inventory Settings

Firestorm 6.6.16 adds a new option called Inventory Settings to the gear icon in the lower-left corner of all Inventory floaters. When clicked, it will display a floater defining how the Inventory view button (again found at the bottom of Inventory floaters, to the left of the Elements count) and how the Show in Inventory option (right-click on an attachment you are wearing and select from menu) and the Find Original option Inventory option (used with inventory links) all behave.

See the images below for both the menu option and the floater it displays with its options.

The Inventory Settings option and floater. Use the radio buttons to set the options in the latter

Preferences

  • New option for sorting in “Attach to” menus:  Preferences → Firestorm → Build 2 → Sort Attachment Spots in “Attach to” Menus Alphabetically (Requires Restart).
    • When enabled, attachment spots are sorted alphabetically after a restart.
    • When disabled, attachment sports are ordered according to the hierarchy for alpha priority.
    • See: FIRE-33127.
Preferences update – sorting “Attach to” menus

UI Updates

  • Menus: the Help → Report Problem now redirects to an informational  / instructional page on obtaining help from both the Firestorm team and Linden Lab, as shown below.
The new Firestorm Help informational page

Rendering

The issues with motion blur / ghosting after enabling /  disabling Shadows has been fixed. This also fixes the related bug that caused saved snapshots to be too dark when Shadows were disabled if Ambient Occlusion was disabled. See: BUG-234275BUG-234461 and FIRE-33151.

Other Updates of Note

Firestorm 6.6.16 includes numerous bug fixes and improvements  – notably with viewer skinning in light of the new Inventory Extensions UI elements, and numerous small improvements to UI element layouts. Please refer to the release notes for details.

Library Updates

  • FMOD Studio updated to version 2.02.18 – Release Notes.
  •  KDU updated to version 8.3.

Linux Updates

  • CURL changes: as the use of CURLINFO_SIZE_DOWNLOAD and CURLINFO_SPEED_DOWNLOAD has been deprecated since Curl version 7.55 (2017), the respective replacements are CURLINFO_SIZE_DOWNLOAD_T (documentation here) and CURLINFO_SPEED_DOWNLOAD_T (documentation here). This change will correct the deprecation warnings when compiling with newer versions of curl on Linux.
  • Library Updates:
    • SDL updated to version 2.28.4.
    • Curl library updated to version 8.3.0.232750741.
    • Nghttp2 library updated to version 1.56.0.232750738.
    • OpenSSL library updated to version 1.1.1w.232750656.
  • The IME checkbox has been renamed from “Use IME Text Input” to “Enable Full IME Support” per FIRE-32074.

OpenSim Updates

  • For OpenSim the Estate Ban limit and number of Estate Managers remain at 500 and 15 respectively, and the new Second Life limits of 750 and 20 respectively are ignored. OpenSim developers will need to add server-side support to enable the higher limits on their grids to make use of the increasing in the viewer.
  • A fix has been implemented for a potential region crossing crash.
  • General note: OpenSim does not current support the Inventory Extensions features outlined above.

2023 SL SUG meetings week #48 summary

Witherwood Thicket, October 2023 – blog post

The following notes were taken from the Tuesday, November 28th 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 meeting is embedded at the end of this summary, my thanks as always to Pantera for recording the meeting and providing it.

Apologies for the lateness of this summary, RL is not playing nice at the moment.

Meeting Overview

  • The Simulator User Group (also referred to by its older name of Server User Group) exists to provide an opportunity for discussion about simulator technology, bugs, and feature ideas.
  • These meetings are conducted (as a rule):
  • They are open to anyone with a concern / interest in the above topics, and form one of a series of regular / semi-regular User Group meetings conducted by Linden Lab.
  • Dates and times of all current meetings can be found on the Second Life Public Calendar, and descriptions of meetings are defined on the SL wiki.

Simulator Deployments

  • Tuesday, November 28th: support for PBR Materials was deployed to the SLS Main channel, making it grid-wide.
  • Wednesday, November 29th: the “Fall Colours” maintenance update should be deployed to the BlueSteel RC. This will include llRezObjectWithParams, llIsFriend, but will not include the game controller updates.
  • “Fall Colours” is liable to be the last simulator update for 2023.

Viewer Updates

The glTF / PBR Materials viewer, version 7.0.1.6894459864, dated November 17th, was promoted to de facto release status on November 28th, in line with the grid-wide deployment of PBR Materials.

Other viewers in the pipe remain as:

  • Release channel cohorts:
    • Maintenance X RC, version 6855926535, issued November 21 – usability improvements.
    • Maintenance Y, version 6.6.17.6935642049, issued November 21 – My Outfits folder improvements; ability to remove entries from landmark history.
    • Maintenance-W RC viewer, version 6.6.17.6935636398, November 21.
    • Maintenance V(ersatility) RC viewer, version 6.6.17.6898288582, November 20.
    • Emoji RC viewer, version 6.6.15.581551, August 31.
  • Project viewers:

Game Controllers

  • The code remains under internal review at the Lab, particularly around the UI elements needed to support it in the viewer.
  • Runitai Linden has suggested seeing if it is possible to support a system where the scripter can specify custom input names, which show up in the UI with a select-and-toggle method of mapping game device inputs to those channels, as Leviathan Linden explained at the meeting:
Suppose you were making some custom game with very custom input names (e.g. not “Strafe” and “Jump”), like a Twerking game and you wanted “Wiggle”, “Waggle”, and “Bop” to be the names of your inputs. The scripter would be able to call something like… llGameControlMappings([“Wiggle”, GAME_CONTROL_AXIS_0, “Waggle”, GAME_CONTROL_AXIS_3, “Bop”, GAME_CONTROL_BUTTON_2]); The viewer would then get that info and be able to provide custom UI for setting those input names to the various axes or buttons on whatever device you happen to be using.

– Leviathan Linden describing a proposed custom button names for games controllers

  • This led to an extended discussion on game controller, mapping buttons, options and approaches.
  • Leviathan also noted the current version of the back-end support for games controller will be made available on a simulator channel on Aditi (the Beta grid) later in the week.

In Brief

  • The straw man document Rider Linden has been putting together on combat system improvements is now being circulated within the Lab for comments and feedback. Expect more probably in the new year.
  • The above, together with BUG-233210 “Third Person View With Mouselook Functionality”, led to a discussion on camera positions, remote vehicle control, etc., which in turn led to a broad conversation on camera placement options and camera control.
  • Region Crossings: no major update from Monty, who has been out of the office.
  • A mixed discussion on frame rates (including confusion between server-side frame rates and client FPS performance), region crossings co-habiting regions which are adjoining one another as a defined group on the same simhost server, and much else that was mostly user-side in terms of input. Please refer to the video below.

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