The following notes are taken from the TPV Developer meeting held on Friday, April 12th, 2019. A video of the meeting is embedded below, my thanks as always to North for recording and providing it. This was a relatively short meeting, with several periods of audio silence and text chat. The key points of discussion are provided below.
- The Estate Access Management (EAM) RC viewer updated to version 220.127.116.116190 on Friday, April 12th, 2019.
- As noted in my CCUG summary, the EEP viewer updated to version 18.104.22.1686104 on Thursday, April 11th.
All other viewer in the pipelines remain as:
- Current Release version 22.214.171.1245446, formerly the Love Me Render RC viewer, dated March 26, promoted April 2 NEW.
- Release channel cohorts:
- Project viewers:
- Linux Spur viewer, version 126.96.36.1999906, dated November 17, 2017 and promoted to release status 29 November – offered pending a Linux version of the Alex Ivy viewer code.
- Obsolete platform viewer, version 188.8.131.520847, May 8, 2015 – provided for users on Windows XP and OS X versions below 10.7. This viewer will remain available for as long as reasonable, but will not be updated with new features or bug fixes.
With the necessary back-end updates now made, it looks likely that the EAM RC viewer will be the next viewer to be promoted to de facto release status.
- The Lab continues to try to understand the root cause(s) of the teleport disconnects. So far, they can only confirm it is not specific to any single viewer.
- As previously indicated in my updates, the root cause of the issue is a race condition / timing issue – something that could be exacerbated by the distance of a user from the Lab’s servers (the grater the distance = the more time required for communications = the greater the chance of a timing issue / race condition).
- Similarly, a high packet loss between viewer and simulator(s) might increase the chances of a disconnect occurring.
- The problem remains in trying to identify precisely what has changed to cause any race condition / timing issue.
- As noted in this week’s SUG meeting summary, there was a server RC deployment on Wednesday, April 10th – version 19#19.04.09.526122,. This included additional logging to help capture further data on the teleport disconnects, particularly capturing where the region handshaking may be failing.
- Multiple regions have been replicated on Aditi, and having further enhanced logging enabled on them. This additional logging capability may be deployed to Agni in week #16, but not necessarily enabled, due to the performance impact it will have. However, the code will be in place should it be required.
Attachment Loss on Teleport
- The Lab now has a “solid” repro for this issue. As anticipated, much of the problem appears to be related to having too many scripted attachments stacked on the same attachment point (e.g. the right hand, the default attachment point, and often used by default by mesh clothing makers).
- However, the work on developing a fix has slowed as a result of resources being moved over to the teleport disconnect issue.
Asset UDP Messaging Deprecation
As noted in my SUG summary, it appears the code for the Asset UDP messaging deprecation didn’t work as anticipated, likely the result of one code element failing to merge correct. There will be a be a further RC deployment in week #16 with the corrected code.
A reminder that assuming the deployment is made and the code works as anticipated, anyone using very old viewers still reliant on UDP messaging for assets and which do not have support for HTTP messaging will not be able to receive any updates for the following: animations, body parts, clothing, gestures, landmarks, meshes and sounds whilst connected to regions on any RC channel.
- The are reports of issues with the EEP code interfering with Interest List culling, with Draw Distance having little effect on scene rendering (BUG-226752). This is being investigated.