The following notes were taken from the Tuesday, March 9th, 2021 Simulator User Group (SUG) meeting.
Please refer to the server deployment thread for the latest news and updates.
- Tuesday, March 9th saw the servers on the SLS Main channel updated to server release 556255, containing “some internal tweaks related to launching region”.
- There are no planned RC channel deployments scheduled for Wednesday, March 10th.
There have been no updates to the current pipeline of official viewers at the start of the week, leaving them as follows:
- Current release viewer: version 18.104.22.1685567 (Jelly Doll improvements) originally promoted February 17th, and re-established as the default viewer following the rollback of the Simple Cache viewer.
- Release channel cohorts:
- Project viewers:
A simulator version currently in QA at the Lab has some region crossing changes in it. It is hoped the updates will take some of the load off of agents trying to enter crowded regions. The engineering team also intend to look at the protocol for moving an agent from region to another; however, this is viewed as “a much larger project” that has yet to be started.
- Group chat is being tweaked. It is hoped that an update will be ready for deployment Soon™.
- Map tiles continue to be worked on, but not fully fixed. However, some updates to the World Map are being seen.
- HTTP 5xx errors: some with internal services reliant on external web pages for data have been seeing an uptick in 5xx HTTP errors (see BUG-229660 and BUG-230059 as examples). Some this may be more directly related to the external service hosting the web pages (Cloudflare), while some are apparently seeing 503 errors when regions are down (rather than 404s), but are seeing recoveries once the region is back.
- BUG-229871 TP issues: some people are experiencing teleport issues whereby they cannot teleport back to any region they’ve previously successfully teleported to previously in the same session, but are disconnected. This is being investigated. It has been suggested by some users the issue might be related to a past similar issue that was the result of a local firewall or router setting issue.