2021 SUG meeting week #39 summary

Hazelnut’s Kingdom, June 2021 – blog post

The following notes were taken from the Tuesday, September 28th, 2021 Simulator User Group (SUG) meeting. The meeting was recorded by Pantera Północy, and the video is embedded at the end of this summary. Note this summary focuses on the key points of the meeting; where there is something to report, the video should be referred to should full details of the meeting wish to be reviewed.

Server Deployments

See the deployment thread for updates.

  • There are no planned deployments for the SLS Main channel.
  • The RC channels will be subject to a rolling restart on Wednesday, September 29th. Due to technical constraints this, will update the simulator version number to 564195, however there are no changes in code or configuration from the currently deployed version 563375.

SL Viewer

There have been no updates to the current crop on official viewers to mark the start of the week, leaving the pipelines as:

  • Release viewer: version version, formerly the CEF Update RC viewer, issued July 24 and promoted August 10.
  • Release channel cohorts (please see my notes on manually installing RC viewer versions if you wish to install any release candidate(s) yourself):
    • Apple Notification Fix RC viewer, version, issued September 24 – this should remove the warning messages which are currently popping up.
    • Maintenance RC viewer updated to version, on September 21.
    • Simplified Cache RC viewer, version, dated September 17, issued September 20
  • Project viewers:
    • 360 Snapshot project viewer, version, issued September 3.
    • Performance Floater project viewer, version, issued September 2.
    • Mesh Optimizer project viewer, version, issued September 1.
    • Legacy Profiles viewer, version, dated October 26.
    • Copy / Paste viewer, version, dated December 9, 2019.

In Brief

  • Some are reporting an uptick in 502 responses to outgoing HTTP requests that is described as “not common, but common enough” to cause concern, although the requests usually go through as expected on retry. The uptick appears to coincide with the updates to HTTP-out proxies. The usual Jiras on target URL, source regions/objects, owners, etc., have been requested from those experiencing these issues.
  • Some are also reporting issues with texture loading taking longer of late, including textures that should be locally cached by the viewer. The simulator and messaging is being pointed to as a potential culprit, although a) this shouldn’t affect cached textures; b) aside from the initial object and texture information, textures (as with all assets) come via the CDN, not through the simulator.
    • It’s been suggested that changes to the Interest List in support of the 360º Capture project viewer could be the cause, and this hasn’t been ruled out.
    • Similar issues had been noted with Firestorm following its release. However these have tended to be in terms of initial viewer start-up at the start of a session (when VFS load seems to take abnormally long), but these do not appear to be related to this issue, as this appears to occur across all viewer flavours – official and TPV.
    • Again, Jira reports on the issue giving viewer details, locations and actual timing snapshots (using ALT-CTRL-3 to display the texture queue) would be useful to the Lab. Also tests using the TextureTest2 and MeshTest2 regions on Aditi (which are structured to test exactly this sort of thing) that can be reported would also be useful.
  • BUG-231113 “PRIM_POINT_LIGHT sets the wrong colour (not a duplicate)” has been accepted (and pending more detailed investigation). It is not clear if the viewer is amending the script-supplied light parameters prior to sending them to the simulator, or whether the change is on the simulator side of things.
  • The last part of the meeting comprised grumbling about blog reports apparently not being addressed (or possibly more correctly, not being addressed in a time frame those experiencing an issue – which may not be everyone or even a majority or users – want it to be addressed). In response, it was pointed out that there is a lot of working going on under-the-hood that is not user-visible, but nevertheless is of a high priority.