The following notes were taken from the Tuesday, May 18th, 2021 Simulator User Group (SUG) meeting. These notes relate to the core points of discussion; other topics may have ben raised without specific feedback from LL as actionable items, so please refer to the video at the end of this report for the full meeting and all points covered.
At the time of writing, there had been no server deployment thread available for review.
- Tuesday, May 18th saw no deployment to servers on the Main SLS channel.
- Wednesday, May 19th should see some of the RC channels updated with the new llOrd, llChar and llHash LSL capabilities. A further change is that the updated simulator no longer reports child agents as part of agents, as it has been doing so inconsistently.
- The remainder will keep to release 559679 with the llOpenFloater() function intended for use with Linden-owned Experiences – see my week #18 SUG summary for more.
From Rider Linden’s comments at the week #14 SUG summary:
LlOrd() will return the ordinal of the first character in a string, llChar() given an integer will return a single character string, and llHash() is a non-cryptographic 32 bit hash. I was looking for a way to just have an integer that had a reasonable change of being unique for an arbitrary string.
Use case I can see: Given an owner of two objects I want to select a chat channel with a low probability of colliding with other agents in the area.
The start of the week has seen no updates to the current crop of official viewers, leaving the pipelines as follows:
- Release viewer: Eau de Vie Maintenance viewer, version 18.104.22.1688266, dated April 23, promoted April 29 – No change.
- Release channel cohorts:
- Project viewers:
- Legacy Profiles viewer, version 22.214.171.1240519, dated October 26.
- Copy / Paste viewer, version 126.96.36.1993365, dated December 9, 2019.
- Project Muscadine (Animesh follow-on) project viewer, version 188.8.131.522999, dated November 22, 2019.
- 360 Snapshot project viewer, version 184.108.40.2069111, dated July 16, 2019.
- The Lab has a group working on various simulator physics issues and general health, some of which can generate errors (e.g. “Unable to create object that has caused problems in this region”). No ETA on when these might be deployed.
- Thought is still being given as to how to fix the dim ambient lighting seen on the Mainland since the introduction of EEP – a problem that appears to be harder to fix than people appreciate / understand.
- Questions have been asked if some of the simulator-side resource issues could be fixed if additional CPU cores could be allocated to support really busy regions – such as events, etc. Responding to this, Mazidox Linden, Lead Server QA Engineer said:
There are various hardware (and *maybe*) some software resources that can be in contention for any given set of simulators on a simhost, network, memory, CPU, IO, things like that. So allocating an additional core to a simulator fixes *maybe* one of those bottlenecks. If it’s the bottleneck affecting your performance. Which is a big if.
- There have been reports of teleport failure spiking recently, including viewer disconnects. Rider Linden is hoping to poke at the teleport code some more as time allows, but it appears the issue might be a communications issue between the receiving region and the viewer. Maxidox Linden explained the matter thus:
The destination simulator knows someone is supposed to show up, so it creates some space in the receiving warehouse. No one ever arrives to fill it … Our best guess (and it is a *guess*) is that it involves the destination region and the affected viewer waiting for each other to send something first.
The following video of the meeting is courtesy of Pantera Północy.