Day: October 17, 2023

2023 SL SUG meetings week #42 summary

Posted on by Inara Pey
Dwejra, August 2023 – blog post †

The following notes were taken from the Tuesday, October 17th Simulator User Group (SUG) meeting. They form a summary of the items discussed, and is not intended to be a full transcript.

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.

Server Deployments

  • No deployments for the week (again). However, all simhosts (SLS Main and RC) will be restarted.

Upcoming Deployments

Viewer Updates

The current batch of official viewer versions is as follows:

Potential for Games Controller Use

  • This work sees the introduction of a new LSL event called game_control, the format for which Leviathan defined as:
game_control(key id, list buttons_edge_down, list buttons_edge_up, list buttons_down, list axes). Lots of lists, but that was necessary to support treating the keyboard as a “big controller with lots of buttons”. I created some docs for the game_control stuff on the LSL wiki.
  • Leviathan also noted there should be a GameControl category page, at the time of writing the link to it had yet to be added to the game_control wiki page.
  • The server work is now considered wrapped, and the focus is on the viewer support.
  • Overall, the work is seen as an initially simple pass to provide basic support for the use of game controllers in SL and intended to get things rolling; so capabilities such a building a “virtual game controller”, as requested at previous meetings are not available. However, he noted that, “Once the network protocol is nailed down and the script stuff… it will still be possible to modify the viewer. “
  • Key points of note include:
    • The feature doesn’t require permissions, but can be enabled via checkboxes in the viewer UI. However, Leviathan noted it could be piggybacked on controls permissions.
    • Subject to testing, the keystrokes are the remapped ones according to other UI settings.
    • The capability currently only works for attachments and seats, it cannot be used for avatar movement.
    • Doesn’t as yet support controller gyro, or rumble feedback nor support for trackpad position for game controllers that have it, nor does it support the use of mouse position recognition and buttons.
    • The above two points have a potential to be added later, “perhaps”.

In Brief

  • The official blog post on the deployment of a simulator update to resolved the communications / bandwidth issue referenced in recent CCUG meeting summaries was referenced.
  • Two feature requests for avatar movement were raised – BUG-234557 and BUG-233175 – leading Rider to note:
Adjustable avatar movement would be possible… the only thing about it that gives me pause is… I know how delicately tuned the avatar motion logic is under the hood, to allow for walking up low ledges, friction when stopping, and how the avatar tries to stand still when at rest but still be “bumpable” by other avatars and objects.

This led to an extended discussion on avatar movement and options for allowing the use of a velocity model for avatar movement (thus allowing for avatars moving at different walking speeds, etc). This lead to a broader discussion on avatar movement / animations, etc., which touched on the dormant puppetry project.

  • HTTP work. Rider Linden noted he is back to working on his HTTP code and simulator asset handling refactoring, and is hoping to get the underpinning code refactor completed in the next week(ish) and then work on the asset management side. This led to a request for the issue of Modify items becoming labelled as No Mod for the owner when a No Mod item is place in its contents & then taken back to inventory (even though the item still have Modify permissions), which in turn generated a request for a Jira report.

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