2015 viewer release summaries: week 28

Updates for the week ending: Sunday, July 12th, 2015

This summary is published every Monday, and is a list of SL viewer / client releases (official and TPV) made during the previous week. When reading it, please note:

  • It is based on my Current Viewer Releases Page, a list of all Second Life viewers and clients that are in popular use (and of which I am aware), and which are recognised as adhering to the TPV Policy. This page includes comprehensive links to download pages, blog notes, release notes, etc., as well as links to any / all reviews of specific viewers / clients made within this blog
  • By its nature, this summary presented here will always be in arrears, please refer to the Current Viewer Release Page for more up-to-date information.

Official LL Viewers

  • Current Release version: 3.8.0.302622, June 30 – no change
  • Release channel cohorts (See my notes on manually installing RC viewer versions if you wish to install any release candidate(s) yourself):
    • Viewer-managed Marketplace RC viewer updated to version 3.8.1.303315 on July 9th – allows Merchants to manage inventory associated with Marketplace Listings from within the viewer (download and release notes)
    • Importer RC viewer version 3.8.1.303230 released on July 8th – provides a modified mesh uploader  (download and release notes)
    • Maintenance RC viewer updated to version 3.8.1.303166 on July 7th – comprising some 50 updates, fixes and features (download and release notes).
  • Project viewers:
    • Notifications project viewer version 3.8.1.303211 released on July 8th – new Notifications floater separates incoming notifications into System, Transactions, Invitations, and Group. It provides a better way to view, interact with, prioritize and manage incoming notices for busy residents (download and release notes).

LL Viewer Resources

Third-party Viewers

V3-style

  • Black Dragon updated to version 2.4.3.6 on July 9th (Notifications update with rendering improvements – release notes) and then to 2.4.3.7 on Monday July 13th (Maintenance RC update – release notes).

V1-style

  • Cool VL Viewer Stable branch updated to version 1.26.14.0 on July 11th – core update: inclusion of VMM code into Stable branch (release notes); the Experimental branch temporarily removed in preparation for implementing the Lab’s CEF updates.

Mobile / Other Clients

  • Radegast updated to version 2.18 on July 9th – core updates: support for Group Bans and several smaller updates (download and release notes) .

Additional TPV Resources

Related Links

 

Second Life project updates 28/2: TPV Developer meeting

Crystal Gardens Estates Inara Pey, July 2015, on FlickrCrystal 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”.

SL Viewers

Viewer Updates

The Mesh Importer RC viewer updated to version 3.8.1.303230 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 3.8.1.303315.

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 3.8.1.303211, 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.

Other Items

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.

Attachment Issues

[20:23] As noted above, project Big Bird (version 3.8.1.303130 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.

 Firestorm Update

[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).

Black Dragon: notifications and shadows

Blackdragon logoOn Thursday, July 9th, NiranV Dean released version 2.4.3.6 of his Black Dragon viewer.

The release brought with it a rapid-fire implementation of the Lab’s new notifications update from LL, which comes a little ahead of the curve, given the Lab prefer their code to be integrated into TPVs once it reaches RC status, and can be regarded as somewhat more stable than might be the case with a project viewer release. However, the code is such that it is apparently easy to manage should updates be forthcoming as that project progresses.

In implementing the notifications update, Niran has made some subtle changes to the notifications floater itself, improving the overall layout, although the overall functionality is pretty much as offered through the Lab’s current project viewer. Rather than describe the functionality here, readers are invited to read my overview of the project viewer.

The other major update with this release of Black Dragon release is related to shadows and lighting, and specifically, the uncoupling of shadow rendering from draw distance.

Because shadow rendering has been bound to draw distance, shadows tend to fade away the closer they are to your draw distance limit, with the result that the further objects are away from you, the less well-defined their shadows appear / the less shadows may influence how they appear, with objects close to the edge of your draw distance sometimes appearing shadowless.

With this change, Niran has added a new slider to the Display tab of Preferences, allowing the user to independently set a “shadow rendering distance”, thus allowing a better rendering and representation of shadows independent of draw distance.

Black Dragon 2.4.3.6: the new shadow rendering distance slider
Black Dragon 2.4.3.6: the new shadow rendering distance slider in Preferences. A similar slider is also in the Machinima sidebar

The result is a much improved depth of view in-world, and greatly enhanced snapshots (see Niran’s samples accompanying the viewer’s release notes).

By-and-large, extending the shadow rendering distance shouldn’t result in any appreciable performance hit. However, there is a caveat, as Niran explains:

Increasing the shadow draw distance will reduce the overall shadow precision, because shadows are split into shadow clip planes, 4 shadow textures if you will, these shadow textures have a given resolution (which you can set in preferences), increasing the shadow rendering distance scales up all 4 planes equally, increasing the area one texture has to cover, reducing the precision in that area obviously. You could counter this by increasing the shadow resolution or multiplier, but that would impact frame rate.

A side benefit of this, as Niran notes, is that because volumetric lighting is calculated via the shadow clip planes and shadow maps, increasing the shadow rendering distance enhances the volumetric lighting effects in the viewer. Again, check the sample images Niran provides with the release notes.

Other updates in this release include:

  • Re-enabling of the experimental auto-hiding of the Textures, Sounds, Calling Cards, Landmarks, Notecards, Scripts, Photo Album, Animations, Gestures, Favourites and My Outfits folders in Inventory (debug: DebugHideEmptySystemFolders)
  • Disabling of the auto-hiding of empty folders by default
  • Improvements to SSAO defaults
  • Freeze world and mode toggling issues, as reported in STORM-2118, fixed and implemented in this Black Dragon release
  • Further RLVa updates.

As always, for the full range of changes / updates, please refer to the release notes.

Additional Links

Radegast updates to 2.18

Radegast is a third-party Second Life / OpenSim client which has proven to be especially popular with those on low-end systems over the years, and gained a solid level of support from the visually impaired, who found the client a lot easier to use than a full viewer – so much so that a special accessibility guide was produced, and special classes held in using the client.

Sadly, ongoing health issues impacting Latif Khalifa, Radegast’s creator, reached a point where, in November 2014, he had to signal that he was unable to continue maintaining the client, although he ensured the source code remained available for anyone who wanted to do so on behalf of the community.

Well, the good news is that on Thursday, July 9th, Radegast was updated to version 2.18. The even better news is that the person making the update was – Latif Khalifa!

The new update brings a number of improvements to the client, which the release notes list as:

  •  Support for Group Bans (RAD-471)
  • Double click on inventory item to wear/attach (RAD-472)
  • RLV support for @acceptpermission (RAD-500)
  • New Automatically Accept Dialogue Function (RAD-490)
  • A fix to allow the main window to minimize to the system tray correctly (RAD-497)
  • Add log-in support for SirinHGpole-Grid to the grid manager (RAD-503).

The Group Ban functionality in Radegast operates the same way as for any viewer:

  • Avatars can be banned from a group by either selecting them in the group members list if they are already a member and using the Ban button (below left), or by using the Group Ban Picker to ban one or more avatars pro-actively from joining the group by using the Ban … button in the Banned Residents tab (below right)
  • Group Ban capabilities can be be awarded to any role in the group by enabling the GroupBanAccess option in the  Allowed Abilities section of the Roles sub-tab.
The Radegast 2.18 update adds Group Bans to the client
The Radegast 2.18 update adds Group Bans to the client use the Ban button in the Members and Roles list to eject and ban a person in the group; use the Banned Residents tab to track those previously banned or to pro-actively ban users from joining the group.

For those unfamiliar with Radegast, it is a full feature but lightweight client able to run on Windows, Linux and Mac OS. It provides pretty much all of the capabilities found in a full viewer, including full inventory management, mesh upload capabilities, voice support, etc.. In addition, it has a few options of its own such as an API for plug-ins, speech recognition and an AI capability (ALICE).

For those who may be without their viewer for some reason, but would prefer to see what is going on in-world, the Windows and Linux versions of Radegast provide a 3D scene renderer in which you can see the world and move around in it, chat with others and – via the Objects option – interact with the things you see around you.

Radegast's in-world view option (the Scene Viewer)
Radegast’s in-world view option (the Scene Viewer) – note this does not support windlight, etc.

All of this has made Radegast a flexible, usable and popular client, and if you’d like to know more about it, please refer to my Radegast coverage in this blog.

Given Latif is still recovering from illness, this update may not signal his full return to supporting Radegast; when I did ask him about this update, he replied, “there were several updates, such as group bans that were done, but unreleased. So why not get them out ;-).” As to the future, we’ll have to see what comes along; but certainly, seeing Latif back in the saddle with this release is great.

Related Links

Lab issues notifications project viewer

secondlifeOn  Wednesday, July 8th, the Lab issued their notifications project viewer, which sees an overhaul of the way in which notifications – system, group, transaction, etc., are presented through the viewer.

The viewer has been in the works for a while, and is the direct request of a feature request put to the Lab by Aki Shichiroji back in 2012 (see BUG-8000), and which has more recently been working its way through the Lab’s work list to appear in project form on July 8th.

The release of the project viewer, version 3.8.1.303211, was accompanied by an official blog post on the subject, which reads in part:

The Notifications Project Viewer is an improvement for sorting your notifications. This new feature is based on your feedback: a notifications floater with four tabs sorting your incoming notifications into System, Transactions, Invitations, and Groups and allowing better interaction with them as well.  Those who deal with high volumes of money transactions, group notices, group invites, or inventory transfers now have a better way to review their messages and identify which notices need immediate attention.

The images below show the floater and its four tabs:

The new Notifications floater - see below for explanatory notes
The new Notifications floater – see below for explanatory notes

Multiple notifications within a tab are initially shown compressed (above left). Clicking on the down pointing arrow button for a specific notification (highlighted in red, above left) will expand that particular notification within the floater (above right), with scroll bars allowing you to scroll down through an individual notification or through the notifications within that tab.  Clicking the up point arrow button (highlighted in blue, above right) will compress an expanded notification.

As with the current notification system within the release viewer, individual notifications can be deleted from any tab by clicking the X button. There are also additional buttons within the panel for collapsing all expended notifications or deleting all notifications within the currently displayed tab (i.e. clicking Delete All with the System notifications tab will delete all notifications in that tab but not all of your notifications in general).

A further improvement to the way notifications are displayed is that a time stamp for when a notification was sent / received is now clearly visible, both in the collapsed and expanded views for all notifications. The presence of any attachment is also indicated by the use of a paper clip symbol.

Given this is a project viewer, the Lab is requesting feedback and bug reports via the Second Life JIRA.

A couple of issues have been filed already. One of these – BUG-9625 – points out that the notification floater currently fails to include any means of accepting a group invitation; the only way of accepting an invitation in the project viewer at present, is to click on the button displayed in the initial pop-up (which will still be displayed as usual).  Expect this to be created in due course as the project viewer is updated.

Also, do keep in mind this is a project viewer, and currently not intended for prime time use.

Related Links

Second Life project updates 28/1: server, viewer

Umbral Photography, Hydra Isles; Inara Pey, July 2015, on FlickrUmbral Photography, July 2015 (Flickr) – blog post

Server Deployments

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.

As noted in my project update for week #27, BUG-197 referred to in the package release notes relates to an issue whereby a user can’t see any of their local chat on a region or parcel, and nor can anyone else, due to a scripted object which is spamming chat so badly, the chat throttle kicks in, but no warning would be provided to inform the user this was the case. with the deployed change, the user will now get a message about the chat throttle being hit, but unfortunately, the system will not identify the spammy object (so it might be removed / returned, if possible).

There will be no RC deployments to the RC channels on Wednesday, July 8th, leaving all of the main grid on the same release. A new RC deployment, described as a “minor update” is in preparation for deployment to the RC channels in week #29.

SL Viewer

On Tuesday, July 7th, The Maintenance RC viewer was updated to version 3.8.1.303166, bringing it into line with the attachments RC viewer updated in week #27, and just leaving the Viewer Managed Marketplace viewer to be updated in the release channel, which will likely happen later this week.

Chromium Embedded Framework

At the Monday Open source Developer’ meeting, Oz Linden indicated that an anticipated project viewer,  the Chromium Embedded Framework (CEF) viewer which will provide media support via HMTL 5, should be appearing “Pretty Soon”™.  While Quicktime and Flash  may work on this viewer for some users, given the age / status of both, the Lab does not plan to support either going forward, and recommends media creators migrate to HTML 5.

It had been hoped that this viewer would have been out by now; however there appear to be one or two issues still to be resolved. “I heard the developer working on it today say he was deep in the middle of keyboard issues,” Simon Linden said during the Simulator User Group meeting on Tuesday, July 7th. “Getting frameworks like that to cooperate with OS events like keyboard, mouse and screen is always tough.”

Experience Keys / Tools

Simon is continuing to work on tweaks to the Experience Keys / Tools code, and in doing so passed an interesting comment at the Simulator User Group meeting.

“I’ve been working on updating the KVP code that runs on our server,” he said, “and had the most frustrating time integrating the newest version into our code … The code we have is dated and we should have better performance and stability with their latest.”

Quite what the difference is between “our” and “their” code might be isn’t entirely clear at this point in time – although the question was asked during the meeting, and may well be asked again in the future.

Simon also hopes to put some work into getting KVP access moved onto a separate thread to ordinary asset handling. As previously mentioned in these updates, that KVP access is currently on the same thread as asset handling can, at times, cause issues, as noted in BUG-8946.

Group Chat

The recent improvements made to group chat continue to make themselves felt, with many reporting that the old issues of lag with the chat on large groups has largely dissipated. Such are the improvements that Whirly Fizzle has suggested that http://isslgroupchatstillbroken.com/ should be updated. Even so, despite all the the improvements, Simon has indicated that there are still “a few things” he’d like to tweak a little more.