2022 SUG meetings week #7: summary

Bordeaux, France, January 2022 – blog post

The following summary notes were taken from the Tuesday, February 15th, 2022 Simulator User Group (SUG) meeting. It forms a summary of the items discussed, and a video of the entire meeting is embedded at the end of the article – my thanks to Pantera for recording it.

Server Deployments

  • There was no deployment to the SLS Main channel on Tuesday, February 15th, 2022, but the simhosts were restarted.
  • Wednesday, February 16th should see the RC channels updated with simulator release 568051, postponed from week #6, and which includes a series of bug fixes (including one for BUG-230771 “llRequestUsername returns invalid data when invalid key is provided”) and adds a feature to LSL: OBJECT_ACCOUNT_LEVEL flag to llGetObjectDetails(): when called on an agent in the region, returns the agent’s premium status.

Available Official Viewers

This list reflects those viewers available via the first four links in the LL Viewer Resources section, below.

  • Release viewer: version version 6.5.2.567427 – Mac Voice hotfix viewer, January 13 – no change.
  • Release channel cohorts (please see my notes on manually installing RC viewer versions if you wish to install any release candidate(s) yourself).
    • Maintenance RC viewer, version 6.5.3.567451, issued on January 20th, combining the Jenever and Koaliang Maintenance viewers.
    • The Tracy Integration RC viewer version 6.4.23.563771 (dated Friday, November 5) issued Tuesday, November 9.
  • Project viewers:
    • Performance Improvements project viewer version 6.6.0.567604, dated January 24.
    • Mesh Optimizer project viewer, version 6.5.2.566858, dated January 5, issued after January 10.
    • Performance Floater project viewer, version 6.4.23.562625, issued September 2.
    • Legacy Profiles viewer, version 6.4.11.550519, dated October 26, 2020.
    • Copy / Paste viewer, version 6.3.5.533365, dated December 9, 2019.

In Brief

  • A request was (again) made to have simulator behaviour change such that vehicles hitting a parcel ban  / ban lines are “bounced” (much like they do on reaching an edge of the grid) rather than avatars being unseated / dumped and the vehicle returned to the owner’s Lost and Found.
    • This has been requested before, but rejected.
    • During the meeting, the idea was referred to as something that “might be possible”, although it would require protocol changes, if tackled.
    • An alternative suggestion put forward (by a user) was to have a vehicle given the lowest access permissions among those avatars seated on it. That way, if any agent attached to an object cannot enter a parcel, the vehicle would treat that parcel as a solid obstruction. This was seen as potentially more “doable” idea, and a formal Jira Feature Request was asked for – see BUG-231802.
  • A request was made for a grid-wide KVP (or KVP-style) database (as is available to Premium members under the Experience Keys system) to be made available that could be used as a permanent data store (see BUG-231801) available to all who need it.
    • Some of the ideas put forward around this at the meeting included updating the script engine so that scripts can dynamically write data to note cards – something as seen as problematic by the LL or have the viewer use local storage for data generated for use by the avatar (e.g. from a HUD) – something that could be an issue if data is stored on one machine is needed when on another device.
    • Cost of storage was noted as a possible issue, with the suggestion that perhaps (and whilst not permanent) KVP-like storage could be made available along the lines of Local Textures: the data is available for use for as long as a person is logged-in, after which the storage used would be cleared.
    • A further alternative suggestion made by LL – again, note the word suggestion – was the provision of a LSL API that could be used to access AWS services like Dynamo – that is, LL supply API and data movement, users wanting to use the capability supply the account and credentials. This was suggested with an idea of soliciting feedback on the idea.
    • A suggestion was also put forward for a new asset type specifically designed for read / write data storage, but capped at (say) 64 KB.
    • Again, this was a discussion – there are currently no plans to implement any of the above.
  • An issue with uniformly applying EEP settings across multiple regions in an estate via scripted means and smoothly applying it to avatars into and through the estate. A specific bug requiring rectification via the use of fast timers has been identified, together with a possible improvement to handling EEP settings via script. A bug report (BUG-231806) and a couple of feature requests (BUG-231807 and BUG-231808) have been filed on the matters – please refer to them and the video for more.
  • There was a lot of text chat around Avatar Expressiveness – however, as most of this was was subjective and the Lab is not yet in a position to provide further information on the capability, I’ll leave it to the video, below.