The following notes were taken from the Tuesday, April 6th, 2021 Simulator User Group (SUG) meeting.
Please refer to the server deployment thread for the latest news and updates.
- There are no planned SLS Main channel deployments.
- Wednesday, April 7th: the SLS RC channels should all be updated with simulator release 557694, defined as containing “internal fixes an tweaks”.
Last week we ran into an unanticipated glitch and had to push the RC roll back to this week. So, this week we’ll be pushing out the next Maintenance simulator to all the RC channels.
– Rider Linden on the upcoming deployment
There have been no official viewer updates to mark the start of the week, leaving the pipelines as:
- Release viewer: Custom Key Mappings RC viewer, version 184.108.40.2067391, dated March 24, promoted March 27 – NEW.
- 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:
- Legacy Profiles viewer, version 220.127.116.110519, dated October 26.
- Copy / Paste viewer, version 18.104.22.1683365, dated December 9, 2019.
- Project Muscadine (Animesh follow-on) project viewer, version 22.214.171.1242999, dated November 22, 2019.
- 360 Snapshot project viewer, version 126.96.36.1999111, dated July 16, 2019.
On Monday, April 5th, Maestro Linden posted on changes made to Group Chat to try to improve overall message handling. The change appears to have met with with mixed results, with some seeing no real change in how their group chat sessions are affected. There may also been some related unintended consequences, some some reporting the following:
- Some people are finding they have to make multiple posts for group chat to finally open and their chat to be seen by everyone, otherwise their group chat remains silent. It is not clear if this happens across all their groups, or just some.
- Messages for some still appear to be failing with a degree of measurable regularity.
Commenting on the situation, and in lieu of Jira reports, Rider Linden commented:
As far as group chat. We know that it is a problem and we’re going to continue to work on it from our end.
New LSL Capabilities?
This from Rider Linden:
I’m proposing the following three LSL functions llOrd, llChar and llHash. 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.
This approach wouldn’t be cryptographically secure, but would be convenient.
This many be the start of ongoing work to provide new / improved LSL capabilities, with it being indicated that feature requests BUG-227663 “[Feature Request] llGetInventoryAcquireTime()” and BUG-227641 “Play/Loop/Stop sounds in linked primitives other than the primitive where the script exists” may also be considered for implementation.
- Some people are reporting Voice issues – Voice failing to start, or Voice simply not working in a region unless others are already there and using it. It’s not clear have widespread these issues are, or whether bug reports have been raised.
- BUG-229871 “Unable to re-enter or teleport to a region that I’ve been to during same session” – Linden Lab is still trying to consistently reproduce this issue. In discussing the problem, Maestro Linden noted:
One interesting case was somebody reporting that they were able to reproduce the issue 100% of the time until they replaced a faulty coaxial cable – which makes me think that packet loss could somehow be to blame (disconnecting from the simulator the first time in some unclean manner due to time-out?).
- Getting inventory syncing between Agni and Aditi working once more is also being worked on, with the hope that the fix will be available Soon™.
- Work on Map tiles is progressing, but still no ETA on when the remaining fixes are liable to be deployed. Again, in lieu of a fix, people can use the following alternatives, each with its own functionality: