Crystal Gardens Estates, July 2015 (Flickr) – blog post
The following notes are primarily taken from the TPV Developer (TPVD) meeting held on Friday, July 10th. A video of the TPVD meeting is included at the end of this report, with any time stamps in the following text referring to it. My thanks as always to North for the recording and providing it for embedding.
Server Deployments – Recap
As always, please refer to the server deployment thread for the latest updates / news.
- On Tuesday, July 7th, the Main (SLS) channel received the same server maintenance package deployed to the three RC channels in week #27
- There was no RC deployments to the RC channels on Wednesday, July 8th, leaving all of the main grid on the same release.
An RC channel release planned for week #29 (commencing Monday, July 13th) will likely see some “db optimization around group stuff”.
The Mesh Importer RC viewer updated to version 18.104.22.1683230 on Wednesday, July 8th, with the Lab hoping this release fixes the majority of issues so far reported with that viewer.
On Thursday, July 9th, the Viewer-Managed Marketplace (VMM) RC viewer updated to version 22.214.171.1243315.
Viewer Promotion Options
The above updates mean that all four RC viewers currently in the release channel (except the obsolete platforms viewer, which isn’t intended for update), are on a par with the current release version of the viewer (Experience Tools).
However, it is not currently clear which might be promoted to the de facto release version. Any decision on this will be made on the basis of crash rates and overall performance.
[04:13] That said, the VMM viewer has contained a series if XML file breakages with the translation options, and a change in the target formatting for translations also appears to have been changed in the VMM viewer. The Lab believe a fix for the XML issue is in the updated referenced above, although there appears to be some concern that problems still exist. If so, it is unlikely that this viewer will be promoted until issues have been sorted.
Notifications Project Viewer
Also on July 8th, the Lab issued the Notification project viewer, version 126.96.36.1993211, which sees an overhaul of the way in which notifications – system, group, transaction, etc., are presented through the viewer. For further information on this release, please refer to my overview.
[08:10] As this is a project viewer, now is the time to test it and see if it is lacking functionality / options – the Lab will be far more willing to alter the code, should it be required, while the viewer is at a project status than they will be when it reaches RC, where the focus will be on fixing any bugs which may have slipped through.
Changes to Linden Damage
[10:00] The Lab have again acknowledged that the recent changes to the way the official viewer handles avatar damage messaging are not ideal. In short, damage cannot be set it the parcel level only; also, the viewer does not display the health meter on damage enabled parcels, but people can be “killed” and teleported home – for a full list of issues, see BUG-9422. There may be further news on this in due course, as Grumpity Linden (recently returned from maternity leave) will be looking at the issues.
Interest List Issues
[14:00] Some people are reporting what appear to be interest list issues (e.g. items not updating correcting in your in-world view when camming around, etc.) – see the likes of BUG-7084 for further details. However,commenting on this, Oz Linden said:
If there are issues with that, we need repros, because we haven’t got them. And we also need to be able to isolate whether the problem is that the various interest list messages are not being delivered properly, or whether the problem is that the assets aren’t being fetched properly, which is independent of that [the interest list messaging].
Any issues that look as if they might be interest list related must be tested and reported using the official viewer, and not with any TPV.
Avatar Shape Issues
[25:04] There have been reports of avatar shape issues and “corruptions” (e.g. BUG-9487). The Lab have acknowledged that they may have an internal issues of a similar nature (and BUG-9487 has also been triaged), however, if the issue is different, the matter will be imported for further investigation. One problem here is defining what is meant by a “corrupted” shape. The asset itself is unlikely to be be affected, which means it could either be the local copy of the asset being somehow modified, or an incorrect pointer has somehow been created – all of which needs clears steps to repro in order to investigate and ascertain.
[20:23] As noted above, project Big Bird (version 188.8.131.523130 at the time of writing) is thought to correct the majority of viewer-side attachment issues. However, this does not mean that all such issues are fixed; some might be server-side, etc., Both BUG-7761 and BUG-6925 refer to specific issues that have been reported.
An important thing to remember here – again – is that issues like this need to be tested and reported using the relevant Linden Lab viewer, not a third-party viewer.
This is not the Lab being awkward over matters or trying to avoid issues. It is simply because if an issue can be consistently reproduced on the Lab’s viewer points to it being directly related to their code; if a TPV is used – and with respect to all TPV coders – it is not always possible to determine if a problem is a result of code the Lab have supplied, or something a TPV may have done in modifying the code / viewer to suit the needs of their users. Obviously, if it is the latter, fixing the problem is outside of the Lab’s reach.
[01:25 and 11:33] Firestorm are currently waiting on VMM and the attachments fixes (project Big Bird) to be merged into the Lab’s de facto release viewer, as these will allow them to push ahead with there own merges and testing in preparation for the next Firestorm release. However, given the Lab would prefer to promote a viewer to release status every other week (and allowing for Firestorm’s own testing), it could be around 6 weeks before Firestorm updates (although the team already have VMM, the attachment fixes and the maintenance RC updates staged ready for merging).