Tag: Server Updates

SL project updates week 12/1: server, RTLP, viewer translation tool

Posted on by Inara Pey
Tugby! Rugby with tugboats - blog post
Tugby! Rugby with tugboats – blog post

Server Deployments Week 12

As always, please refer to the server deployment thread for the latest updates and information on the week’s roll-outs.

  • On Tuesday, March 17th, the Main (SLS) channel received the server maintenance package previously deployed to the three RC channels.  This comprises “internal improvements for premium users”
  • On Wednesday, March 18th, all three RC channels should receive the same new server maintenance package, comprising various internal fixes for the simulator code.

Commenting on the RD deployment at the Simulator User Group meeting on Tuesday, March 16th, Simon Linden said, “the code going to RC tomorrow doesn’t have anything you will notice, but helps us when we want to make some configuration changes.” Oz Linden followed-up his comment by adding, “that is to say, it allows us to make changes we used to have to roll code to make.”

Other Items

Restore to Last Position (RTLP)

As noted in my last SL projects update report, the Lab is considering deprecating the last of the simulator messaging support for the “restore to last position” (RTLP) functionality, which can still be found in some TPVs and can, albeit with some undesirable results, depending upon how it is used, to restore an item directly from inventory  and return it to its last recorded in-world position, relative to the region in which the user is standing.

Because the Lab are considering the future of the simulator-side support for the capability, and also as I’ve reported, the Firestorm team is seeking use cases from users on how RTLP is useful, in the hope of presenting the Lab with a reasoned argument on why RTLP, or some similar capability should be retained / provided.

Oz Linden - keeping an eye on feedback through the Firestorm blog on "restore to last position"
Oz Linden – keeping an eye on feedback through the Firestorm blog on “restore to last position”

Commenting on the effort, Oz Linden said, “I’ve been following that. some are supportable, other not so much. Very good food for thought, though, and at least as far as I’ve gotten … people are heeding the request to be civil and non-hyperbolic. I really appreciated that.”

Also commenting on RTLP, Simon said, “What I’ve always wondered with that … the viewer really has a lot of info to do this better. It seems like it could record a list of things as they are removed from a region, then later put them back and give you better feedback on what works and what doesn’t.”

A number of possible approaches to handling cases currently managed by RTLP were also raised during the discussion, but these were just ideas, although they were listened to positively by Oz and Simon. However, this does necessarily mean the Lab will not deprecate the simulator support required for RTLP at some point in the future as a part of dealing with inventory loss issues, or that they’ll necessarily replace it with other functionality. But they are listening and reading.

So again, if you do have a good, concise use case for RTLP which hasn’t so far been reported on the Firestorm blog post’s comments (not here!), do make sure you hop over there and write it up.

Viewer Translation Tool Issue

Nalates Urriah reports that the translation option within the SL viewer (and used by TPVs) is effectively broken for those wishing to use it for the first time (see: BUG-8794 “The Bing API used by the viewer is depreciated [sic]”).

This isn’t an issue within the viewer per se; rather it is a result of the older Bing translation tool WPI / widget having been deprecated by Microsoft, and the means to access it removed from the web page to which users are directed on clicking the Bing API link within Preferences > Chat  > Translation in the viewer.

However, this isn’t a matter of the Lab simply correcting the link used within the viewer; deprecating the “old” translation service means that any keys obtained by following links to the “new” service will not verify through the API currently used by the viewer, thus preventing the Bing translation service being used.

Microsoft have deprecated the existing Bing translation API / widget with the result that new translation keys will not work within the translation function in the viewer (official and those TPVs using the Lab's translate options)
Microsoft have deprecated the existing Bing translation API / widget with the result that new translation keys will not work within the translation function in the viewer (official and those TPVs using the Lab’s translate options)

However, as noted in both the notes from Microsoft, and in comments accompanying BUG-8794, existing verification key previously obtained using the “old” Bing API are still supported, and will still work; thus, this issue only impacts those trying to obtain a new key. As this matter has just been reported, there is no word from the Lab on how it might be handled.

SL project news week 11/1: server, viewer, group chat

Posted on by Inara Pey

Armenelos, Calas Galadhon; Inara Pey, March 2015, on Flickr Armenelos, Calas Galadhon (Flickr) – blog post

Server Deployments Week 11

As always, please refer to the sever deployment thread for the latest updates and information.

  • There was no Main (SLS) channel deployment on Tuesday, March 10th
  • On Wednesday, March 11th, all three RC channels should receive the same new server maintenance package comprising “internal improvements for premium users”.

When asked during the Simulator User Group meeting on Tuesday, March 10th whether the “internal improvements for premium users” was related to the change to the in-world receipt of off-line IMs, as mentioned at the last SBUG meeting, Simon Linden could only say, “I’m not supposed to announce anything, so I can’t go into details … but one thing we’re looking at this year is ways to make premium accounts better. This may or may not do something like that eventually.”

SL Viewer Updates

A new Maintenance RC viewer, version 3.7.26.299610,was released on March 6th. This includes multiple fixes and improvements as listed on the release notes and download page.

The Experience Keys viewer updated to version 3.8.0.299338 on Monday, March 9th, maintaining parity with the current release viewer.

Experience Tools

Although the Experience Tools viewer has been updated (see above), there is still no news on when Experiences might be fully deployed. In order to help build interest in Experiences a suggestion has been put forward to enable Experiences to be rated in terms of the number of people actively joining them (see BUG-6911), which could be optionally shown (at the Experience creator’s discretion in things like search listings, allowing people to judge Experiences by their popularity.

The Lab has considered allowing users to rate Experience themselves in a future update – but as point out in the JIRA comments, such a system could be open to gaming, much like the old avatar popularity ratings. BUG-6911 has been imported by the Lab, but it is currently unclear if the idea will be carried forward.

Group Chat

As also noted in my last updates, recent changes to the group chat service have seen up to a 20% failure rate in delivered messages. Simon Linden spent a fair amount of time during week #10 stabilising things once more, and notes that the situation taught the Lab more about how things might fail. He currently has a set of updates which may further improve things, and these are liable to be tested at the next Server Beta User Group meeting.

Other Items

Names Vanishing from Ban Lists

There have been reports of avatars added to a region / estate ban list or have been previously muted suddenly dropped from the list without an action on the part of the list owner. This might be connected to the old issue of bans made using radar on some older versions of v1-style viewers (notably Phoenix) failing to “stick”, or it may be something else, such as a failure to correctly update a ban / mute list.

Commenting on the subject at the Simulator User Group meeting, Simon said, “we’ve heard reports of that and have looked into it … if you ever can narrow down an instance of that happening, please note it in a JIRA … Our logs will record info about those changing but we have to know where and when to look

“I’m making wild guesses, but I think it would be either the viewer or the simulator making an update to the ban list, and somehow having bad data.   Perhaps an incomplete list gets into the picture, and using that as a basis for the update it drops people.   Our logs will show events like “MrNoisy was added” and “MrGoodBehaviour was removed” but finding the event is the missing part of the puzzle.

“If you have multiple regions in the estate, there’s another issue of having the changes sent out to all the regions.   We’ve seen failures there and I know it’s been worked on a few times (and suspected in some of these reports).”

So, if you do encounter a situation involving an apparent ban list failure, and can log the exact circumstances / details, please consider raising a bug report.

SL project updates week 10/2: server and viewer notes

Posted on by Inara Pey
RMS Titanic, Second Life
RMS Titanic, Second Life

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 deployments to the RC channels on Wednesday, March 4th.

Upcoming Server Updates

During the Server Beta User Group meeting on Thursday, March 5th, Caleb Linden, who now chairs the meetings, indicated that an upcoming deployment to the RC channel will include a change to the number of off-line IMs delivered when you log-in.

Currently, the cap is set to 25, but it’s not clear what the new limit will be, although it might vary (or be adjustable) depending on whether a user is a Basic or Premium member. This change will not affect the forwarding of off-line IMs to e-mail.

SL Viewer

The new Tool Chain Update viewer was promoted to Release Candidate status on Wednesday, March 4th. Version 3.7.26.299443 see a change to the tools used to build the viewer (e.g. the use of Visual Studio 2013, Xcode 6.1, and some other tools improvements). This update also incorporates the log-in screen update to a single button, replacing the need for the Log-in Screen RC viewer.

Future Viewer Updates

Avatar Layers Global Limit

In 2014, BUG-6258, “Popularity of Mesh Attachments Facilitates Need For More Alpha Layers” is a request to raise the number of alpha layers which can be concurrently worn, prompted the Lab to consider the introduction of a global limit on the number of clothing layers an avatar could wear,so that, like attachments, an avatar can wear as many clothing layers in any combination, up to that limit, rather than having individual limits enforced per clothing layer.

During the TPV Developer meeting in week #9, Oz Linden indicated that while there had been major progress on this idea since it had been first raised, something would likely be appearing later in the year. Since then. Whirly Fizzle has spotted a viewer code repository from Vir Linden: “SL-103 WIP – viewer enforces wearable limits based on total articles of clothing rather than per-type limit. Limit is artificially low for testing, will bump before release.”

This doesn’t mean new global limits on avatar cloting layers will be appearing in the next few weeks, but it does indicate that it is one of several avatar related projects he’s working on (together with the new Avatar Hover Height feature and fixing at least some of the current crop of attachment issues).

Notifications Changes

Also during the TPVD meeting in week #9, Oz commented that some “cosmetic” work was being done to the way notifications are presented through the viewer. Again, thanks to Whirly’s poking around, this would appear to be in connection with BUG-8000, “Separate transaction notices from group notice/invites or provide some means for sorting incoming notifications”, which has been imported by the Lab and is being worked on.

A preliminary version of the proposed new notification panel (see BUG-8000). Note that is is a work-in-progress and may be subject to change prior to release (image courtesy of Whirly Fizzle)
A preliminary version of the proposed new notification panel (see BUG-8000). Note that is is a work-in-progress and may be subject to change prior to release (image courtesy of Whirly Fizzle)

 Group Chat

Simon Linden is continuing to bang on things to try to correct issues that have arisen since the last set of updates at the end of week #9. According to Caleb Linden, who now chairs the Server Beta Group meetings, those groups that are affected are seeing up to a 20% failure rate in delivered messages.

Other Items

Rigged Mesh Crashers

Further to my last report on this issue, Whirly Fizzle (who is genuinely one of the great powerhouses in helping to keep SL rolling along) stepped up to provide a more detailed explanation of the issue based on her own extensive investigations into the matter (thanks Whirly! 🙂 ).

In her comments, Whirly notes that Chalice Yao has developed a debug  setting within her own NACL viewer setting specifically stop cap rendering of worn rigged meshes, and that Nicky Dasmijn from the Firestorm team is working on a patch for their viewer. However, while the setting works, it can also prevent “legitimate” rigged mesh items with high vertices counts from rendering.

Further discussion of the problem with regards to BUG-2082, which includes new viewer rendering controls, confirmed this would not help with the issues presented by this particular kind of rigged mesh crasher but it will prevent issues such as the animated mesh “tail of doom” which can cause viewer crashes as a result of overloading memory.

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

SL project updates week 9/1: server, viewer

Posted on by Inara Pey
China Grove - blog post
China Grove – blog post

Server Deployments, Week 9

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 will receive the same server maintenance package, which comprises:
    • A server-side fix for BUG-8297, “Unable to teleport anywhere using SLGO”
    • Improvement to server logging.

The SL Go teleport issue only affected users running the SL Viewer (SLV) supplied by OnLive, who run the SL Go service (it did not affect those using Firestorm on SL Go), and was the result of a recent server-side code clean-up which meant that OnLive’s SLV was essentially using an invalid channel name when instigating teleports, causing them to fail.

OnLive implemented a workaround for the issue on their side of things on February 3rd, however, the update included in the RC package noted above provides a fix on LL’s side of the connection as well.

SL Viewer

On Tuesday, February 24th, the Maintenance RC viewer, version 3.7.25.299021, was promoted to the de facto release viewer.  This release includes a large number of improvements and fixes to the viewer, as listed in the release notes.

This currently leaves just the new log-in viewer RC (version 3.7.25.298971 released on February 17th) and the Experience Tools RC (version 3.8.0.298001 last updated on January 15th) in the release channel for the time being.

Experience Keys / Tools

The initial release of Experience Keys / Tools is still awaiting various back-end updates to clear the Lab’s QA department, with the viewer remaining at RC status until that happens (see above). As previously noted in my Experience Keys reports, the initial release of the functionality will not support grid-wide experiences, although are likely to be on the roadmap for future enhancements.

Once released, the current iteration of the functionality is liable to be allowed to run for a number of months before the Lab starts making  (or releasing) updates, with Oz Linden commenting at the Simulator User Group meeting on Tuesday, February 24th, “there will be another round of improvements to Experiences at some point, but we’re going to give the first round some time to be adopted before we go too far with those.”

Group Chat

Group chat work is continuing, with the recent changes to handling server lock-ups reducing the number of reported freezes.

Simon Linden is also continuing to look at the code side of things, and specifically issues with group chat visibly “stalling” which switching between chat tabs and / or as a result of moving between regions. This work has been the subject of a series of “mini-tests” during the Server Beta User Group meetings held on Thursdays, and resulted in some recent code updates. Commenting on this at the SUG meeting, Simon said, “The new code also showed me details about one way the system fails, so I hope to make that better at recovering,” so further updates can likely be expected, although this may not be as broadly visible to many users as the initial group chat improvements.

SL project news week 7/1: miscellaneous; grid status page

Posted on by Inara Pey

Square Pegs in Round Holes, Kashmir Dreams; Inara Pey, February 2015, on Flickr“The Lost Town” – Square Pegs in Round Holes (Flickr) – blog post

News is a little light coming out of the Lab on projects right now, although there was a blog post on things made on Monday, February 9th, which I also blogged about. However, new for the start of the week is still a little on the light side.

Server Deployments

There are no scheduled server deployments for the week.

SL Viewer

It had been anticipated that week #6 would see the Tools update project viewer (version 3.7.25.298587) and the Avatar Hover Height project viewer (version 3.7.25.298129) both superseded by a release candidate. However, neither update occurred.

It is possible these updates will occur during week #7; however, for the time being, all of the LL viewers remain as they were at the end of week #6, and as recorded in my Current Viewer Releases page, namely:

  • Release version: 3.7.24.297623 (January 13th)
  • Release candidate versions:
    • Maintenance RC, version 3.7.25.298030 – this has a number of issues associated with it, which may prevent its promotion to the de facto release viewer (January 27th)
    • Experience Keys / Tools RC, version 3.8.0.298001 (January 14th) – this has been awaiting final server-side updates to the Experience capabilities
  • Project viewers:
    • Tool Update, version 3.7.25.298587 (January 28th)
    • Mesh importer, version 3.7.25.298441 (February 3rd) – a number of bug reports have already been filed for this viewer – see the JIRA filter list for details.
    • Avatar Hover Height, version 3.7.25.298129 (January 21st)
    • Viewer-managed Marketplace, version 3.7.21.296858 (November 19th, 2014)
    • Oculus Rift project viewer, version 3.7.18.295296 (October 13th, 2014).

Grid Status Page Relocated

As some have noticed, on Monday, February 9th, the Lab relocated the SL grid status page to a blog address, with a redirect from the “old” URL of status.secondlifegrid.net/.

However, the result has caused some confusion, notably as a result of breakage across sites and links referring to the “old” URL. Even some of the updates on the secondlife.com dashboard users see having been generating 404 errors as a result of the move.

Commenting on the change during the Simulator User Group meeting on Tuesday, February 10th, Simon Linden – who was out of the office when the change was made – said, “I don’t know what’s going to happen with the status page … but we know the shift caused issues … we heard a lot about it breaking things that relied on it.  I’m not sure what the solution will be.”

So… watch that space…