2026 week 47: SUG Leviathan Office Hour

The Simulator User Group meeting place at Longfellow

The following notes were taken from the Tuesday, November 17, 2026 Leviathan Office Hour, the “off-week” sessions of the Simulator User Group (SUG) meeting. These notes form a summary of the items discussed, and are not intended to be a full transcript. A video of the meeting by Pantera is embedded at the end of this summary – my thanks to her 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 is held every other Tuesday at 12:00 noon, SLT (holidays, etc., allowing), per the Second Life Public Calendar.
  • The “Leviathan Office Hour” meetings are held on the Tuesdays which do not have a formal SUG meeting, and are chaired by Leviathan Linden. They are more brainstorming / general discussion sessions.
  • Meetings are held in text in-world, at this location.

Simulator Deployments

  • The SLS Main channel was restarted on November 17, 2026 with no deployment.
  • The new simulator update – code-named Plum – has been current, but it was not clear if any deployment would be made to one or more RC channels this week. This update includes a memory leak fix and a physics crash bug.

General Updates

Interest List

  • Leviathan is currently working on fixes for some issues with the Interest List (the logic that figures out what is in view and send objects updates), trying to finish-up work started earlier in the year.
  • Unfortunately, not all of the work he hoped to complete made it into the current cut of the Plum simulator update. This includes “Interest List speed-up work” – an attempt  to help save some time and bandwidth with an update to how KillObject messages (messages sent to the viewer telling it to stop rendering specific objects for whatever reason – they are no longer in draw distance; they are temp rez and have died; they have been deleted or returned, etc.).
    • Currently, these messages are sent to all viewers in a region, regardless as to whether the viewer is actually rendering the object in question or not – a change that was made a good few years to ago to try to address “ghost objects” – items in a region that had been deleted, but while a viewer had received the data relating to where they are and what they look like, it had not received the KillObject message, and so would continue to render the object when “seen”.
    • Therefore, Leviathan is now working to try find the middle ground between these to extremes, and handle some race conditions which can cause further issues.

Game_Control

Leviathan isn’t actively working on this, however:

  • Questions work asked as to which game control pads work the the new game_control capability and which do not. Those support the SDL3 API should work – however, as Leviathan Linden noted, for those who have a controller is to try it – it will either work. Or not.
  • Leviathan noted that code to gather stats on the number of game controllers being used has been added to the viewer, but it’s too soon it the scheme of things to start meaningfully drawing on the data.
  • There have been some bug reports of controllers being “lost” during region crossings (what currently amounts to 1 loss per around 50 crossings), and that control permissions are lost if someone logs-out for more than 60 seconds when using a controller.
  • Leviathan does expect to make “another pass or two” at the capability – one will likely be bug fixes. He also noted that as rumble feedback has been frequently been requested, he may look at adding that at some point.
  • He also noted that MIDI support was also requested early-on in the work, but this seems to have gone by the wayside as a request, although his comment sparked a conversation in the meeting.
  • Leviathan also asked for good use-case ideas for game_control’s “cursor mode” (currently, game_control will allow some control of the mouse cursor & track the cursor’s position even when it is moved via a mouse / trackball, but use-cases to build on this haven’t been fully expressed).

General Discussion

Please refer to the video, below.

  • As well as the Interest List work, Leviathan has been trying to make the LLSD implementation more thread-safe on the server in the hope of resolving some server-side crash issues. However, this work also has yet to be merged into a simulator code update.
  • Pepper Linden is aware of some region crossing issues, where the recent region crossing updates might cause a temporary vehicle to get returned during a region crossing. They had an upcoming fix for that.
  • The game_control discussion rolled into one during the last 20 minutes of the meeting through until the end on the need for better screen resolution functions to allow for accurate cursor tracking via scripts, and which do not require user-side set-up / additional calculations, etc.
    • Concerns were raised that gathering screen resolution can by used as a data tracking point, raising security concerns (e.g. it could be used in “finger print matching” tying specific avatar accounts to specific system set-ups), which is one of the reasons it thus far has not been made a function within the viewer.
    • The suggestion was made that if a function to gather screen resolution / window size is added to something like game_control (or elsewhere), it should have a viewer-side option to toggle it off to prevent the data being sent to other viewers.

Date of Next Meetings

  • Formal SUG meeting: Tuesday, November 24, 2026.
  • Leviathan Linden: Tuesday, December 1, 2026.

Have any thoughts?