Second Life Combat User Group: July 11th, 2024 summary

Credit: Rider Linden

The following notes were taken from the Thursday, July 11th, 2024 Combat User Group meeting. They form a summary of the core items discussed and responded to by Lindens, and are not intended to be a full transcript.

Meeting Overview

  • The Combat User Group exists as a forum to discuss improvements to the Linden Lab Combat System or LLCS to better support combat in Second Life.
    • The core idea is to provide additional events and capabilities which sit on top of LLCS to provide combat creators with better tools with which to create better combat systems for their specific scenarios.
    • It is not intended to be a complete combat system in and of itself.
  • The meetings are the result of a proposal document on improving the native damage system in SL, written by Rider Linden, and which is the focus for both the meeting and any work arising from them.
  • These meetings are conducted (as a rule):
    • By Rider Linden, with the support of Kyle Linden.
    • On alternating Thursdays (rotating with the Content Creation User Group) at 13:00 SLT. Meeting dates are recorded in the Second Life Public Calendar and at this location.
    • In local chat.
  • Discussion topics, requests, etc., can be found on the SL Feedback Portal Combat Board.
  • Additional details are available via the SL wiki Combat2 page.

Work In Progress

  • The current iteration of server-side Combat 2.0 support is due to start deployment to the Bluesteel simulator RC on Wednesday, July 17th as a part of the Summer Fun simulator update.
    • Linden Lab has carried out some testing to ensure regions which do not have the Combat 2 updates will continue to operate the same way they do now.
    • Rider Linden is going to have the Concord and Lexington Combat regions moved to the Bluesteel RC so they are available for testing after deployment of the update.
    • Issues / feedback should be reported via the Support Portal Combat Board.

Feedback: How to Help New Users Discover Combat Opportunities in SL

Product Manager Kyle Linden asked for suggestions on the kinds of questions new residents might ask to in order to discover and participate in SL combat activities.  Reponses included:

  • The basic questions: can combat / war games be played in Second Life? What kinds of combat are available? How do I find out more about them? How do I enrol? Where can I obtain weapons?
    • It was suggested a themed welcome hub with a selection of free weapons and some portals to newbie friendly combat regions could help solve some of these questions.
    • A themed welcome Hub might allow Combat Communities to apply for Community Gateway status and direct users signing-up through them to the “Combat Welcome Hub”.
  • A further suggestion was to have Combat added as a Search category.
  • Kyle Linden indicated LL was considering some newcomer friendly enhancements to linden Combat regions: teleporting to a safe parcel within them, where users might find a basic free weapon kiosk or random weapon spawner.
    • In support of this, it was suggested Linden Combat regions include a basic “Combat Experience” to ensure all permissions requests are either suppressed and / or correctly set and ensuring things like gestures for reload, semi/burst/auto, etc., are available.
    • It was also suggested that all entering the regions be required to accept the Experience in order to exit the safe parcel and participate in combat within the Linden Combat regions.

In Brief

  • As the initial Combat 2 updates have reached deployment, Rider considering folding the combat User Group meetings into the Tuesday Simulator User Group meetings.
    • Given there is already a lot of cross-over between the two, this makes sense.
    • The suggestion was made to conclude the Combat User Group with a combat meet- up on the Lexington region once deployment has completed. This would be the meeting currently scheduled for Thursday, July 25th.
  • It’s been reported that there is issue in which a damage object (generated by llRezObjectWithParams) collides with a non-avatar in the same frame, it does not actually do damage (see: Damage objects should send damage to the nearest recipient).
    • This is seen as a collision order issue (e.g. damage is always delivered to the first thing it hits – so this is a question of which gets the collision first).
    • Rider is aware of the issue, but is unsure how best to address the problem.
  • Additional Canny tickets:
    • Damage Over Time  – this raises potential shortfalls with applying damage over time. This is currently marked as Under Review, pending consideration for future implementation.
    • Rezzing delays affect all scripts in an object – this is not limited to being a Combat-specific issue. This is being tracked, and it is hoped LL will have a fix available in a near-term simulator maintenance release.
    • Improved Mouselook for Combat and Immersion – this has been a topic of discussion at several combat meetings. As has been noted, this requires a pull request / code contribution from NiranV Dean (Black Dragon developer), who has stated he will endeavour to do so, once he has had the time to fine-tune and bug-fix the code some more.

Next Meetings

  • Simulator User Group: Tuesday, July 16th
  • Combat User Group: Thursday, July 25th (final group meeting)
    • This will be a Combat get-together in the Lexington combat region.
    • Those with weapons and HUDs they are willing to share are asked to bring them to the meet-up.

2024 SL SUG meetings week #28 summary: 2K Bakes on Mesh

Infinite Darkness, June 2024 – blog post

The following notes were taken from the Tuesday,  July 9th, 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. No video this week.

Meeting Overview

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

Simulator Deployments

  • The SLS Main channel was restarted on Tuesday, July 9th, 2024.
  • On Wednesday, July 10th:
    • The BlueSteel RC is due to be updated with the summer Fun simulator update, which includes the initial Combat 2 updates from Rider Linden.
    • The remaining RC channels will be restarted.
    • However, at the time of writing a last-minute issue with Interest List updates meant the the Bluesteel deployment may be postponed.

SL Viewer Updates

  • Release viewer: version 7.1.8.9375512768, formerly the Graphics Featurettes RC viewer dated June 5 and promoted June 10th.
  • Release channel cohorts (please see my notes on manually installing RC viewer versions if you wish to install any release candidate(s) yourself).
    • WebRTC Voice RC, version 7.1.9.9688089989, July 1.
    • Atlasaurus RC (object take options; improved MOAP URL handling), version 7.1.9.9620320242, June 27.
    • Maintenance B RC (usability updates / imposter changes) 7.1.9.9555137545, June 21.
    • Maintenance C RC (reset skeleton in all viewers), version 7.1.9.9469671545, June 14.
  • Project viewers:
    • None.

2K Bakes On Mesh

Something that people might be excited to hear — we’ve officially started on 2k BOM support. It sounds like an easy thing to do, but it turns out that the service responsible for handling avatar baking hasn’t been touched in many years, and depends on an extremely old Linux viewer fork.

– Pepper Linden

  • Vir Linden has also pointed out that as well as updating the Bake Service (mentioned in Pepper’s comments) it is possible the entire wearable system layer system may also require updating. There is therefore no ETA at present on when this work will be completed.
  • The above led to a discussion on VRAM usage as a result of 2K textures on avatars, matters of Avatar Render Complexity (ARC – already well out of date and also ignores PBR), etc.
    • As a reminder, on PBR viewers, textures should have their resolution scaled to match screen resolution, should should help to some degree with VRAM use.

In Brief

  • It is possible that the implementation od glTF scene imports(once implemented) could lay the foundations for the updated of ARC as well as Land Impact.
  • There is apparently a potential issue with notecard searches and the number of returns generated, which could be in error. Rider Linden is looking into this.
  • There was an extended discussion on texture  / PBR UUIDs, issues with overrides, etc. Unfortunately, most of this went clean over my head.
  • A new feature request for llRegex* functions has been raised and is being tracked by LL.

† The header images included in these summaries are not intended to represent anything discussed at the meetings; they are simply here to avoid a repeated image of a rooftop of people every week. They are taken from my list of region visits, with a link to the post for those interested.

2024 week #27: SL TPVD meeting summary

Nathhimmel: Lavender Fields of Madame Loutre, June 2024 – blog post

The following notes were taken from my audio recording + the video recording by Pantera (embedded at the end of this summary) of the Third-Party Developer meeting (TPVD) held on Friday, July 5th, 2024. My thanks to Pantera as always for providing it.

Meetings Purpose

  • The TPV Developer meeting provides an opportunity for discussion about the development of, and features for, the Second Life viewer, and for Linden Lab viewer developers and third-party viewer (TPV) / open-source code contributors to discuss general viewer development. This meeting is held once a month on a Friday, at 13:00 SLT at the Hippotropolis Theatre.
  • For both meetings: dates and times are recorded in the SL Public Calendar, and they re conducted in a mix of Voice and text chat.
  • The notes herein are a summary of topics discussed and are not intended to be a full transcript of the meeting.

Official Viewers Status

[Video: 1:25-4:45]

  • Release viewer: version 7.1.8.9375512768, formerly the Graphics Featurettes RC viewer dated June 5 and promoted June 10th.
  • Release channel cohorts:
    • WebRTC Voice RC, version 7.1.9.9688089989, July 1.
    • Atlasaurus RC (object take options; improved MOAP URL handling), version 7.1.9.9620320242, June 27.
    • Maintenance B RC (usability updates / imposter changes) 7.1.9.9555137545, June 21.
    • Maintenance C RC (reset skeleton in all viewers), version 7.1.9.9469671545, June 14.
  • Project viewers:
    • None.

General Viewer Notes (Both Meetings)

  • The switch to working from multiple viewer RC branches to a single development branch is continuing.
    • This will mean in future there are likely to be fewer RCs in the pipeline than has bee the case for roughly the last decade (and sees the visible aspect of viewer development and release process swing back towards how it appeared prior to the switch to using RC channels).
    • Parallel tracking of viewer development will continue for a while, given the fact there are currently four RC viewers in flight.
  • The above change-over will not prevent contributions being accepted.

WebRTC

[Video; 5:00-7:28]

Summary

  • A new project intended to move Second Life away from reliance on the Vivox voice service and plug-in, and to using the WebRTC communications protocol (RTC=”real-time communication”). Roxie Linden is leading this work.
  • Key benefits:
    • WebRTC supports a wide range of real-time communications tools in common use (e.g. Google Meet), supporting audio, video and data communications, and is thus something of a “standard” approach.
    • Offers a good range of features: automatic echo cancellation, better noise cancellation and automatic gain control, much improved audio sampling rates for improved audio quality.
    • Opens the door to features and capabilities to voice services which could not be implemented whilst using Vivox.
  • In addition:
    • LL are are of some of the security concerns around WebRTC voice (e.g. risk of eavesdropping, exposure of users’ IP addresses, etc), and is actively working to block these through the use of an internal proxy service.
    • LL will be looking to Linux devs to help give feedback on how well WebRTC is working on their Linux viewers
  • Feature requests for WebRTC should be made via the WebRTC board on the SL Feedback Portal.

Status

  • Work has been on stabilising WebRTC and getting the viewer to RC status so that TPVs can look at it.
  • Overall, development work is in a “wrapping-up” phase.
  • Currently, LL is looking at August for a potential deployment across all of SL on the server-side.
    • This will follow the usual approach of roll-out to the simulator RC channels first, then to the SLS Main channel.
    • As a result, there will be some short-term issues around peer-to-peer, Group and ad-hoc voice connections between those on regions running the two different voice services (Vivox and WebRTC).
    • Depending on how the deployment goes (e.g. first to a single RC, then multiple RCs, then the SLS Main channel), it is hoped that any such issues will only be for around 2 weeks.
  • Viewers adopting the WebRTC code prior to or during this deployment period will be able to process both WebRTC and Vivox voice.

glTF Update

[Video: 7:42-13:23]

  • As a result of the Firestorm PBR release, Runitai Linden has been revisiting the issue of memory use in the PBR-enabled viewer code on lower-specification computers.
  • Geenz Linden is continuing to work on various glTF extensions, including glTF index of refraction (IOR) and transmission – with the work on the latter potentially being wrapped up.
  • Cosmic Linden has been tweaking the PBR terrain work for PBR transforms on terrain (one transform per material).
  • [Video 39:44-41:14] requests have been made for reflection probes in shapes other than cubes and spheres (e.g. cylinders, triangles, hemispheres) to account for more awkward interior space shapes (e.g. in roof areas). This is viewed as “highly unlikely” at the Lab.
    • However, the mirror capability may be extended to include sphere reflection probes at some point “if all goes well”.

PBR Terrain Painting

  • This is the next planned project for Cosmic Linden, and is in the very early stages of planning, so things are subject to potential change.
  • Currently, the thinking is:
    • The four PBR materials currently used for PBR terrain would remain available for use / painting.
    • The painting element would allow a user to define how these materials are mixed, rather than having to rely purely on the the height map.
      • E.g. if you have a paint map for a region, you’ll be able to blend the materials based on that, rather than having to use the height map, and define where areas of grass or rock or dirt, etc., appears on the ground.
    • The paint map is likely to initially be on the basis of one blended texture at region level (not parcel), although the resolution of the texture is still TBA at the time of writing.
    • The permissions for terrain painting will be based on ability to edit the height map (if you can alter the latter through the Region settings, then you’ll be able to use the terrain painting capability).
  • Terrain painting will be a significant departure in how terrain texturing has been managed, requiring a new entity to be introduced. This is also still being thought through, but it is unlikely it will be a new asset type stored on the asset servers.
  • [Video: 16:15-16:29] No decision has been made on making terrain painting open to scripted control.
    • Cosmic is open to feedback on how this might be used, if enabled (e.g. a scripted explosion leaving a detonation mark on the ground for a period of time).

In Brief

  • Reflections turn black when zooming in close is an issue which appears to be related to the use of mirror probes as well as “normal” reflection probes. If you are impacted by this, add your vote.
  • Auto-exposure under PBR (adjusting the general scene brightness when looking at one or more very bright objects in the scene), with people interpreting it as a bug, particularly with the release of Firestorm PBR.
    • It’s been suggested that a wiki page on how auto-exposure  works should be produced, to which people can be pointed to help them understand what it is and how it works. Or potentially a debug setting or similar to disable (with a warning things may not display correctly as a result).
    • Canny feedback has been requested on issues being encountered / suggestions for related features (such as the setting noted above).
    • This led to an extending general discussion on lighting and rendering – please refer to the video.
  • RLV/RLVa adoption by the Lab is still in discussion and described as something the Lab wants to do, but it does represent an extensive change to their viewer.
    • As such, it is likely that as contributions are made, they will be pulled into the official viewer incrementally (presumably with some going behind debug flags until such time as they can be properly enabled).
    • Overall, it now appears the Lab does want to support the full RLV/RLVa feature set, rather than just a sub-set thereof as had been previously indicated as a possible route.
  • Opening the PBR terrain painting to scripted control led to a conversation on scripted weather systems – such as being able to change the ground appearance to match the season; having the ground appear to be covered by snow when it snows, etc. There have been requests for this, but it is not something the Lab is currently working on.

 

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.

July 2024 SL Web User Group summary: MP on Mobile & MFA for MP

The Web User Group meeting venue, Denby

The following notes cover the key points from the Web User Group (WUG) meeting, held on Wednesday July 3rd, 2024. 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.

Note: This meeting was entirely text-based.

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.

Improvements and Updates from the Web Team Planned for the Coming Year

Marketplace on Mobile and MFA on the Marketplace

  • The Marketplace will have a first release of being mobile responsive in the coming weeks (“not months”).
    • This will be rolled out slowly so some users may see it before others.
  • This release will focus on making the the product listing pages and checkout page more responsive and display better at specific break points (including on mobile devices).
  • Once the initial work on making the above pages more responsive has been deployed, LL will be adding multi-factor authentication (MFA) to the Marketplace
    • This will be an extension to the current MFA implementation covering secondlife.com dashboards and the viewer.
    • As with the current MFA, it will be opt-in on the Marketplace, and required on logging-in (presumably, whenever a token has expired).
    • Information on enabling MFA on the Marketplace will be made available nearer the time it will be made available.
  • Alongside the MFA implementation, there will be likely be further changes to Marketplace search algorithm.
    • Once this work is deployed, LL will be looking at how it changes transactions, and receiving merchant feedback on the Feedback Portal.
  • After the MFA work and search updates, work will resume on making the Marketplace more responsive / mobile device friendly.
    • This work will focus on MP search and the shopping cart.
    • However, a fully responsive Marketplace is not anticipated before the end of the year.
  • In addition to the above, there will be some general quality of life updates on the MP, including things like a button to confirm clearing the shopping cart.

Additional MFA Discussion

The announcement of MFA coming to the Marketplace led to a further general discussion and exchange of ideas on the MFA implementation in general, including:

  • The need for better safeguards to prevent large-scale Linden dollar movements in the event of an account being compromised.
    • Even with MFA, an account is vulnerable to being compromised and its L$ balance being access through the viewer.
    • The suggestion was made that MFA should therefore be additionally requested when attempting to move large values of L$ from an account. This was combined with the idea of the same in the event of multiple transaction above a certain level in a short amount of time.
    • Obviously, what constitutes a “large transaction” and a “short amount of time” would require consideration and be balanced against users becoming frustrated the MFA process and then opting-out (thus defeating the purpose in having it).
  • This broadened into a discussion of MFA being triggered more in common with other web services: e.g. an alert being sent via e-mail if a log-in is detected from an unexpected / new device, an unrecognised location, etc., allowing the account holder to take action, if required.
  • There was a further request for e-mail based authentication or SMS code-based authentication.
    • E-mail has been promised in the past, but is potentially prone to easy compromise.
    • SMS + code is not seen as insecure, and not likely to be implement, particularly given the general move away from it that is taking place.
  • Kali Linden reiterated, the current plan is to enhance and expand the current MFA, not re-invent the wheel.

In Brief

  • Maps.sl:
    • Garfield Linden is overhauling maps.sl as an after-hours project. His focus is on:
    • Bringing it to feature parity with Maps-in-the-viewer.
    • Making it mobile-friendly (e.g. with a search bar that floats over the map tiles, like maps.google.com).
    • If anyone has simple ideas for how it might additionally be improved etc., input to him or via the Feedback Portal.
  • Changing to WUG meeting frequency (date / time):
    • The web team is looking to add ” a second web user group meet with a different time that is more accommodating for residents then our SLT time zone meeting”.
    • Noon SLT was considered (by the small number of attendees) as a preferable time.
    • Sntax Linden arbitrarily selected Tuesday, July 30th as the date for the first of these additional meetings- HOWEVER, 12:00 noon on the 30th July brings any WUG meeting directly into conflict with the Simulator User Group meeting (and there is audience cross-over between the two). As such, the date / time of any additional WUG meeting has yet to be confirmed.
    • Ironically, since the request was made for an additional meetings (initially on the basis of getting more frequent updates / input, rather than issues over the time), attendance at the WUG meetings has been in decline.

Next Meeting(s)

  • Wednesday, August 7th, 2024, any alternate TBC – check the SL public calendar.

2024 SL SUG meetings week #27 summary

Kingsand, June 2024 – blog post

The following notes were taken from the Tuesday,  July 2nd, 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):
  • 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

  • No deployments for the week, but all channels will be restart per usual schedule.

Coming up as the next simulator update is Summer Fun, which is currently with the Lab’s QA team. Following that will be Picnic, which among other things will include the following LSL functions:

  • llFindNotecardText
  • llFindNotecardTextSync)

SL Viewer Updates

The webRTC RC viewer updated to version 7.1.9.9688089989 on July 1st, 2024.

The rest of the current official viewers remain as:

  • Release viewer: version 7.1.8.9375512768, formerly the Graphics Featurettes RC viewer dated June 5 and promoted June 10th.
  • Release channel cohorts:
    • Atlasaurus RC (object take options; improved MOAP URL handling), version 7.1.9.9620320242, June 27.
    • Maintenance B RC (usability updates / imposter changes) 7.1.9.9555137545, June 21.
    • Maintenance C RC (reset skeleton in all viewers), version 7.1.9.9469671545, June 14.

Luau Projects

These note are related to the Product and Engineering Town Hall at SL21B,when it was announced Luau VM is to be implemented on the server-side, eventually replacing Mono VM.

  • Signal Linden is putting together a technical FAQ about lua with has more detailed answers about “why lua and not [insert option]” and “how is lua faster than mono” etc.
  • Pepper and Rider Linden confirmed part of the work planned will allow for shadow execution of scripts under the Luau and Mono VMs during testing, which will ensure that all output of functions are the same.
    • This shadowing will likely be only be visible to the Lab.
    • Once LL is convinced both behave the same, the switch to using the Luau VM. At that point, the anticipated memory and execution time improvements should become visible.
    • Finally LL will allow a switch to compile either LSL2 or Luau.
  • Signal further indicated:
    • That with the switch to lauau on the back-end, code can be written in either LSL2 or Luau.
    • That both the current Lua client-side project and the announced luau back-end work, whilst separate projects will both leverage Luau, not Lau.
  • Pepper Linden confirmed LSL functions will continue to be maintained, but using Lua will allow for the creation of versioned functions for Lua scripts, providing a more flexible means to update functions without the worry of breaking content.
  • This discussion took up most of the meeting – please refer to the video for more.

In Brief

Please refer to the video for the following and other topics discussed:

  • Leviathan Linden is hoping to provide an updated GameControl viewer download. It will contain no additional capabilities, but will be updated to the current viewer development branch. However, GameControl will now be behind a single UI setting which will need to be set in order to see its UI.
  • Monty Linden confirmed that the first batch of teleports / region crossings  work will now likely surface in the Picnics simulator update.

† The header images included in these summaries are not intended to represent anything discussed at the meetings; they are simply here to avoid a repeated image of a rooftop of people every week. They are taken from my list of region visits, with a link to the post for those interested.

2024 SL SUG meetings week #26 summary

Simurg, June 2024 – blog post

The following notes were taken from the Tuesday,  June 25th, 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):
  • 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

  • No deployments for the week, but all channels will be restart per usual schedule.

Coming up as the next simulator update is Summer Fun, which is currently with the Lab’s QA team. Following that will be Picnic, which is still in the process of being put together.

SL Viewer Updates

No updates to the current official viewers, leaving the list as:

  • Release viewer: version 7.1.8.9375512768, formerly the Graphics Featurettes RC viewer dated June 5 and promoted June 10th.
  • Release channel cohorts (please see my notes on manually installing RC viewer versions if you wish to install any release candidate(s) yourself).
  • Project viewers:
    • None.

In Brief

Please refer to the video for the following and other topics discussed:

  • Leviathan Linden is putting the GameControl feature behind a debug settings option, and then rebasing that onto the viewer _develop_ branch. This will help ensure the functionality is available in future viewer updates, ready to be enabled when the corresponding simulator support has been deployed.
  • A reported issue with llDetectedTouchPos is is the queue of issues the viewer team will be / are looking at.
  • The functionality gap with llSetLinkAlpha() and PBR Materials, and which has workarounds on the wiki using llSetLinkPrimitiveParams() and PRIM_GLTF_BASE_COLOR, is due to be more properly resolved for when controlling larger linksets.
  • Monty Linde noted that the first batch of teleports / region crossings  work is in line for the release after the Summer Fun simulator update – however, vehicles are not specifically part of this work.
    • This led to a general discussion on vehicular region crossings.
  • A further discussion on the Combat project – this will be covered in the Combat Group update following the meeting on June 27th.
  • A general discussion on getting world map tile information, focuses around the request for llGetRegionWorldMapTile.

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