![](https://live.staticflickr.com/65535/53703408940_3b3f36897b_3k.jpg)
Update: May 15th: The WebRTC test region is WebRTC Voice 1. Read more on WebRTC Voice in this official blog post.
The following notes were taken from the Tuesday, May 14th, 2024 Simulator User Group (SUG) meeting. They form a summary of the items discussed, and are not intended to be a full transcript, and were taken from my chat log and the video by Pantera – my thanks to her as always for 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):
- Every Tuesday at 12:00 noon SLT.
- In text (no Voice)
- 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.
Simulator Deployments
- On Tuesday, May 14th, the Main SLS channel was restarted without any deploy,
- On Wednesday, May 15th:
- The BlueSteel RC channel will be updated with the Spring Break Simulator update.
- The rest of the RC simhosts will be restarted.
- A small Snack channel has been set-up for WebRTC testing
(sorry, no region name available).
SL Viewer Updates
- Maintenance X RC (usability improvements), version 7.1.7.8974243247 and dated May 8th, was promoted to release status on Monday, May 13th.
The rest of the official viewers in a pipeline remain as:
- Release channel cohorts:
- Maintenance C RC (reset skeleton in all viewers), version 7.1.7.8820704257, May 6.
- Materials Featurettes RC viewer, version 7.1.7.8883017948, May 2.
- Maintenance B RC (usability updates / imposter changes), version 7.1.7.8820696922, April 29.
- Project viewers:
- WebRTC Voice project viewer, version 7.1.4.8947030231, May 8.
PBR Materials + Blinn-Phong Support
[Video: 7:45 and (discussion) 46:05-meeting end]
- Concern was raised over a quote of a comment by Runtai Linden I carried from the May 10th TPV Developer meeting; specifically:
Sometime between now and then, we’ll likely start making the LSL scripts that modify Blinn-Phong parameters modify their PBR equivalents, or do nothing when a PBR material is applied. So llSetColor, for example, would set the base colour, not the diffuse colour. That should make life a lot simpler for scripters going forward, as scripters have been giving us feedback that trying to do something simple like that with existing scripts is impossible as they have to do a check to see if a glTF material is applied, and if there is then use llSetPrimParams and if there isn’t, use llSetColor.
- This caused concern at the SUG meeting, and so Brad Linden Offered the following:
So, not officially speaking for Runitai, but I think his most important concern is that SL is trying to move towards standards compliance. and for objects with GLTF content attached, the only standards compliant way to display it is to fully implement GLTF PBR exactly as the Khronos group specifies it. so if an object has PBR attached, then displaying anything else is a “MUST NOT” behaviour: https://datatracker.ietf.org/doc/html/rfc2119#section-2.
Defining fallbacks for older viewers that have not implemented the spec, is potentially negotiable.
Any face that has a PBR material applied MUST be displayed using PBR
- Brad also pointed to a Feedback request where there is further discussion towards the issue of “PBR llFunctions”, including colour .
- The major source of concern raised on Runatai’s comment and Brad’s expansion is the belief that some SL users are unable to display PBR materials as they are too taxing on their systems; so if creators cannot offer a fallback position, they well leave SL due to the amount of content they cannot see correctly, couple with the view that maintaining the ability to keep llSetColor “as is” does not break with the glTF requirements, but allows those users to stay with SL until such time as they can upgrade their hardware.
- The counter to this was that there are users still on SL who have hardware unable to correctly render mesh, and that LL are a) working hard to get PBR performance up to a level where the majority of user hardware can support it and b) they do not want to pressure creators into having to support two different content creation / rendering approaches / specifications.
- Please refer to the video below for further comments on this issue, plus expect further discussions at upcoming Content Creatin meetings (see the SL public calendar for details of the latter).
In Brief
- [Video: 28:52-46:00] A discussion on Key Frame Motion and on the impact of scaling on KFM + possible, including an idea from Rider for a llSetScaleLimited function, which would scale an object as specified – unless doing so hits a defined LI limit (e.g. “increase the object size to 5x5x5 or stop scaling if the LI exceeds 8”) – the idea being to prevent an animated object from exploding in LI on scaling. This also saw a further suggestion of having a universal timestamp (server and viewer) to better sync operations,
† 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.