Category: SL Tech

SL project updates week 10/1: server, general news

Posted on by Inara Pey

Leka, Nordan om Jorden; Inara Pey, March 2015, on Flickr Leka, Nordan om Jorden (Flickr) – blog post

Server Deployments

Tuesday, March 3rd, saw the Main (SLS) channel receive the server maintenance package deployed to the RC channels in week #9. This includes:

  • A server-side fix for BUG-8297, “Unable to teleport anywhere using SLGO”
  • Improvements to server logging.

There were no scheduled deployments to the RC channels on Wednesday, March 4th.

Group Chat

Following the last deployment of back-end group chat changed during week #9, some large groups with active group chat have reported an increase in issues of message failures, although they appear to do so somewhat randomly, with some people seeing them and others simply not receiving them at all.

Commenting on the problem at the Simulator User Group meeting on Tuesday, March 3rd, Simon Linden summarised the situation thus:

In short, yes, it’s cranky, and yes, we’re (as in I am) looking at it … the chat server itself is actually running better than before, believe it or not. A back-end service it relies on, what we call “agent presence” [used to help locate someone on the grid], seems to be having new problems, so the changes may have added load to those servers and is causing problems, or something else unexpectedly changed … [So] some people don’t get the messages when chat is failing … it’s dropping sending some updates and messages when it times out with some other internal requests.

Further updates will be provided as the Lab / Simon continues to look at the problems.

CDN Notes

There have been recent reports of people experiencing slow texture and mesh load issues, leading to questions concerning the CDN service (although some of the issues that have been mentioned might be related to local caching more than the CDN). In particular questions have been asked as to how long a CDN server retained its cache of data relating to regions prior to going “cold” and requiring a “reload” from the SL services. Commenting on this at the Open-source Developer meeting on Monday, March 2nd, Oz Linden said that some CDN caches do age out more quickly than others.

The Lab has also been experimenting with more than one CDN provider, and are continuing with different CDN configurations as well to further tune things, as well as continuing to measure results; so we may yet see further changes  / improvements, and a possible decrease in instances that may be related to “cold” CDN loads.

Other Items

Rigged Mesh Crashers

The Server Beta Meeting on Thursday, February 26th saw the issue of a “new” mesh crasher being used on the grid. This is essentially a deliberately corrupted rigged mesh attachment which, when worn will cause viewers around it to immediately crash, with no warning or ability to take preventative action, such as muting the offending avatar.

Just over a year ago, some advice was given on how to counter graphics crashers by adjusting the viewer’s debug settings, and some people many be getting pointed towards it again in order to avoid being affected by the “new” crasher.

However, changing the specified debug settings can lead to a failure to render much of what you actually want to see, as noted in  this comment following the article. At the time the advice was given, the Firestorm team tracked many of the problems their users were experiencing directly to the settings having been changed. Ergo, if you are pointed to this particular article as a means of combating graphics crashers, please keep in mind you may gain undesirable results, and keep a note of the original settings so you can switch back to them should this be the case.

During the discussion on this matter at the SBUG meeting, speculation was raised on whether or not the forthcoming new viewer rendering controls (see: STORM-2082). opinion is divided, as the viewer downloads the data which may cause a graphic crash and starts processing some of it in order to determine what to render or not, and even this initial processing could be enough to crash it.

SL Feed Issues

There has been an uptick in the number of snapshot uploads to the SL feeds failing over the course of the last week, with some additionally reporting issues of comments failure to appear / “loves” failing to stick. Some users also reported issues over the weekend with web profiles failing to load, and a JIRA (see BUG-8677) was logged on this issue on March 3rd.

The last several days have seen people again encounter issues with snapshots failing to process / display in their feeds
The last several days have seen people again encounter issues with snapshots failing to process / display in their feeds

Whether the two issues had a common cause isn’t clear, but as the latter has been resolved, and you are one of those continuing to experience snapshot upload failures, please file a JIRA providing as much information as possible (links to any feed post with a missing snapshot, date / time of upload, number of failures, etc.).

Firestorm TTT: the clean install

Posted on by Inara Pey

firestorm-logoUpdate, March 10th: In response to feedback following the release of this video, Jessica released a more in-depth video examining clean isntalls, settings back-ups, etc. The new video can be found here.

The Firestorm Tool Tip Tuesday video for March 3rd, 2015, covers what can be a thorny and intimidating issue: that of performing a clean install of the viewer.

In an ideal world, clean installs wouldn’t be needed. However, there are times when installing a newer version of a viewer over an existing version, that things which shouldn’t happen do happen, and things that should have happened don’t happen correctly. And while the frequency with which people are asked to perform clean installs have decreased in recent times for most viewers, they can still be the first step in avoiding later issues.

Where Firestorm is concerned, and given it has so many additionally exposed features with supporting UI elements and so on, the chances of something hiccuping during an install and causing problems later cannot be overlooked. Hence why, when releasing a particularly complex update to the viewer, or when dealing with support requests from users after a complex update being released, Firestorm support will often advise / ask if a clean install has been used with the new release.

Firestorm's settings backup feature can help remove some of the pain involved in a clean install, by allowing you to save many of your preferred global and account setting locally, and then quickly restore them after a clean install of a new version of the viewer
Firestorm’s settings backup feature can help remove some of the pain involved in a clean install, by allowing you to save many of your preferred global and account setting locally, and then quickly restore them after a clean install of a new version of the viewer

To make things easier, the Firestorm team has provided additional capabilities within the viewer which allow you to not only save things like your chat logs, etc., to a dedicated folder to avoid them being lost as a result of a clean install (as is the case with all viewers), but they’ve provided a means to back-up and restore all of your viewer settings. However, even with these capabilities, performing a completely clean install can be a daunting task for many.

So in this video, Jessica takes you through her preferred method of running a clean install on a PC – starting from ensuring all or logs files and setting are safely saved  / backed-up through to launching the viewer after a clean install and restoring all of your settings.

 

2015 viewer release summaries: week 9

Posted on by Inara Pey

Updates for the week ending: Sunday, March 1st, 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

LL Viewer Resources

Third-party Viewers

V3-style

  • No updates.

V1-style

  • Cool VL Viewer – Stable branch updated to version 1.26.12.33, and Experimental branch to 1.26.13.1, both on February 28th (release notes for both).
  • Singularity release a supplemental update, version 1.8.6.6157 on February 27th – core updates: a fix for AMD users wishing to use the latest AMD Catalyst drivers (release notes)

Mobile / Other Clients

  • LittleSight for Android updated to version 1.6.1.0 on February 22nd – core update: changing the default log-in to a user’s home location to avoid log-in failures.

Additional TPV Resources

Related Links

Volumetric lighting: soon for SL?

Posted on by Inara Pey

Blackdragon logoUpdate, March 11th: The capabilities described below are now available in Black Dragon 2.4.1.9, which I’ve overviewed here.

Update, March 4th: Niran is continuing to experiment with shaders, and has posted an interesting snapshot taken under water.

NiranV Dean has always enjoyed a reputation for pushing the limits of the the viewer, first within his Niran’s Viewer, and more recently with his Black Dragon viewer.

A lot of the work he does builds on code developed by Tofu Buzzard – such as with his implementation of screen space reflections and, more recently, Godrays. This work, coupled with his own, has enabled him to earn a reputation for producing a viewer with rich graphical capabilities.

Now Niran is pushing the limits again, using both his one code and elements such a Tofu’s Godrays to bring something to Sl people have long wanted to see: volumetric lighting effects.

On Sunday, March 1st, he released a stunning video showing the work to date. When watching it, be aware that while the camera is moving, everything else is static, other than the grating in the ceiling of the room. When you’ve got that, note how the grating not only casts shadows on the floor, it actually breaks up the light falling through it, just as would happen in real life where light rays hit a solid object and are broken up by it.

“The original Godrays are from tofu,” Niran says of the work. “The problem was, they only worked on objects and terrain; they got cut off on the sky. So I’ve worked on that, and added some code to my viewer, which was really the first iteration of things we saw on my viewer [the updates with Godrays from 2014].

“Since then, I’ve been working on improved resolution and smoother Godrays, moving things to another shader, which brought it’s own problems. Most recently I’ve been moving to another shader for depth of field and improved shadows.”

Interest in the work Niran has been doing has been expressed by the Lab, and he will be offering it as a code contribution for them to consider, although he still has some further work to do.

The first of this is to introduce a global fading effect on the Godrays such that they appear to fade away as an observer looks away from the sun. The basic code is already there, but is disabled in the video, as Niran is still working on things. He hopes to be able to offer the fading effect as a toggle on / off option once the work has been completed.

“The other work still to be done is with particles,” he told me. “Since these Godrays are in the final depth of field shader, they also share the same problems. So, if I can move it into a separate shader on top of everything else, it should resolve the remaining issues, and everything should be good to go.

Of course, contributing code to the Lab doesn’t always mean adoption by the Lab; there can be many intervening factors that prevent the latter. However, Niran is quietly confident his work will be adopted. But if not, “well, there’s always my viewer with it!” he tells me with a wink and a smile.

SL project updates week 9/2: TPV meeting, SL roadmap notes

Posted on by Inara Pey

Less Than Three, Special One; Inara Pey, February 2015, on Flickr Less Than Three, Special One (Flickr) – blog post

The following notes are primarily taken from the TPV Developer meeting held on Friday, February 27th,  a video of which is included at the end of the article (my thanks as always to North for recording it and providing it for embedding), and any time stamps contained within the following text refer to it.

Server Deployments Week 9 Re-cap

As always, please refer to the server deployment thread for the latest news and updates.

  • There was no deployment to the Main (SLS) channel on Tuesday, February 24th
  • On Wednesday, February 25th, all three RC channels received the same server maintenance package, which comprises:
    • A server-side fix for BUG-8297, “Unable to teleport anywhere using SLGO”
    • Improvement to server logging.

SL Viewer

Viewer-Managed Marketplace Project Viewer

[0:35] As noted at the last TPV Developer meeting, the VMM functionality still has some issues that are being worked on. some of these appear to be on the back-end of things, rather than within the viewer itself. As such, it is unlikely that there will be further updates to the viewer in the near future while these are being addressed.

Experience Tools Viewer

[0:50] The Lab is also continuing to work on the back-end of things for Experience Tools / Keys. This work is apparently focused on overall robustness of the service prior to fully deploying it to the grid. As no viewer-side changes are anticipated as a result of this work, the viewer itself should be ready for promotion to the de facto release viewer once the Lab is ready to go with things.

Avatar Hover Height Project Viewer

[4:21]  Vir Linden is continuing to work on a couple of the bugs uncovered during testing. One of these is related to leg position issues, which can see an avatar’s leg “buckle” if the position is adjusted downwards such that the feet sink into the ground, becoming more and more pronounced the lower the avatar is set. Currently, there is no ETA on providing a fix for this.

Mesh Importer Viewer

[5:47 – via chat]  It is anticipated that the Mesh Importer project viewer (currently version ) will receive an update in week #10.

Tools Update Viewer

[6:56] A line has been drawn under the current set of changes to the viewer-side build tools, so the aim is now to get the viewer in the release channel.

However, there are further changes already being queued behind the current set of updates, many of them contributed by open-source developers, which the Lab believe will further improve the viewer build process. As such, it is likely that there will be further updates to the viewer in relation to the build tools, most likely in the form of a “build clean-up” viewer, which will likely include all of the agreed updates which didn’t make it into the current version of the build tools viewer code.

The hope is that, moving forward, all viewers – LL’s own and TPVs  – can, as far as possible, be built using the same tool set the only difference being whether or not a TPV sets a build switch to use proprietary libraries (e.g. Havok) or not.

Group Chat

[2:10] The Lab continues to roll-out updates as a result of this work, and updates focused on the issue of group chat servers themselves stalling, and they are confident that progress is being made. This is supported by anecdotal evidence from moderators of large groups with active chat, who are indicating the instances of visible server slow-down / stalling have been decreasing over the past week or so. Commenting on this during the TPVD meeting, Oz Linden said, “we haven’t declared victory in this yet, but it’s looking a lot more stable.”

In the meantime, some groups are reporting performance issues whereby for short periods – measured in terms of 2-3 minutes, where group chat messages won’t go through at all, and no time-out message is being displayed by the viewer, while other messages are being delayed, but then getting through, but without the massive roll of delayed messages. These may be related to previous changes made to improve the overall performance of group chat, and news of the problems is being taken back to the Lab for investigation.

Attachment Reliability

[4:39] As I most recently reported in week 8, there are on-going issues related to attachments. Vir Linden has also been investigating these, and there is a project viewer in development which includes fixes for those issues the Lab has been able to consistently reproduce. Unfortunately, the infamous BUG-6925 is not among these, but Vir hopes that the updates he’s been making will address it to some degree.

There is currently no ETA for the project viewer, but the Lab hopes that when it does appear, they’ll get some clear and constructive feedback on what it does and does not seem to address.

Continue reading “SL project updates week 9/2: TPV meeting, SL roadmap notes” →

Singularity provides update to address AMD Catalyst driver issues

Posted on by Inara Pey

singularityUpdate, March 21st: AMD have release a new set of Catalyst™ drivers, version 15.3 beta, which include a potential fix for the rigged mesh issues – see my notes here.

As I’ve previously reported in this blog, recent AMD Catalyst™ driver updates have resulted in numerous issues for SL users running AMD graphics cards and attempting to use the latest driver updates. These started with the 14.9.1 drivers, but which became particularly pronounced with the  14.9.2 drivers failing to render rigged mesh unless hardware skinning is disabled (see: BUG-7653), problems which increased with AMD switched yo automatic updates with the release of their 14.12 drivers.

In December 2014, Yoho Waco offered a workaround for the problems affecting more recent drivers (e.g. 14.12) using the 14.9 DLL files to overcome some of the issues presented by those drivers, and which should work for most viewers. With Yoho permission, I offered his workaround as an article in its own right, and DMC Jurassic reported the same approach could be used with 1.4.4 driver DLL files to resolve issues caused by both the more recent driver updates and those cause by the 14.9.2 driver update.

Recent AMD Catalyst™ drivers (1.4.9.2 onwards) have been problematic for Sl users, presenting a series of mesh rendering problems as a result of changing openGL support within the drivers (image courtesy of Maestro Linden, click for full-size)
Recent AMD Catalyst™ drivers (1.4.9.2 onwards) have been problematic for Sl users, presenting a series of mesh rendering problems as a result of changing openGL support within the drivers (image courtesy of Maestro Linden, click for full-size)

Now the Singularity team have stepped up, offering their users who use AMD graphics cards and who have particularly been affected by the rigged mesh issues found when using the more recent Catalyst™ drivers.

Version 1.8.6.6157 of the viewer, released on February 27th, 2015, is labelled as a “supplemental” update to the viewer because, as the release notes state, it only provides a fix for this particular set of problems, and offers no additional updates to the viewer as a whole.

Therefore, if you are not affected by the Catalyst™ driver problems, there is no need for you to update. However, if you have been affected by the problems, then this update could well be for you.

Related Links

With thanks to Maya Rosenstar for the pointer.