Category: SL Tech

SL projects update week 10/1: server, viewer, JIRA

Posted on by Inara Pey
A typical Simulator UG meeting (stock)
A typical Simulator UG meeting (stock)

Server Deployments: week 10

As always, please refer to the server deployment thread in the forums for the latest updates / changes.

Main (SLS) Channel

On Tuesday March 4th, the Main channel was updated with the infrastructure update deployed the RC channels  in week 9.

Release Candidate Channels

On Wednesday March 5th, the three RC channels should be updated as follows:

  • BlueSteel and LeTigre should receive a new server maintenance project which contains the following bug fixes:
    • Fixed a bug in which the server release notes link in “About Second Life” would sometimes fail to appear
    • Fixed a bug in which certain objects had incorrect status when crossing between regions
    • Fixed a crash mode
  • Magnum will remain on the same version as week 9, which comprises the infrastructure update and enables support for a new version of the inventory service, AISv3.  To make use of this new feature, login with the Sunshine Project Viewer.

SL Viewer Updates

The Merchant Outbox viewer appeared as a release candidate (version 3.7.3.287344) on Monday March 3rd. This viewer addresses some of the problems affecting some users when using the Merchant Outbox, as specified in the release notes and my report here.

A new Snowstorm viewer is expected to surface in the viewer release channel as an RC the near future. Among other things, this should contain STORM-1831, which is designed to improve syntax highlighting in the viewer’s LSL editor by allowing the viewer to obtain the information required for syntax highlighting directly from the simulator the viewer is connected to. The server-side support for this was deployed at the start of 2014, and the viewer code,  contribution from Ima Mechanic with help from Oz Linden,  has been a little held-up in making its way through the Lab’s QA process. However, referring to it at the Simulator User Group meeting on Tuesday March 4th, Oz indicated the code is now on the “home stretch”.

JIRA Re-opening

There is still no news as to when this week the JIRA will be re-opened. There is also a question as to whether the re-opening will allow all reports to be viewed by anyone, or whether it will only apply to those reports filed once it has been reopened. Note that this is currently a question over the re-opening, not an actual official statement from the Lab. We’ll doubtless learn more once the necessary changes have been made to open-up the JIRA system once more.

Other Items

llSetKeyframedMotion: object stalls and autoreturn defeats

Prior to his departure from the Lab, Andrew Linden was approached by Talarus Luan about issues with llSetKeyframedMotion. Essentially, a number of issues have been reported with objects (such as vehicles) using the function, including:

  • SVC-7556 – Objects with llSetKeyframedMotion() stop running after region restarts (Talarus’ issue)
  • SVC-7787 – Objects using llSetKeyframedMotion() can defeat a parcel’s autoreturn if they travel to and from another parcel
  • BUG-1624

Responding to the issue of SVC-7556, Simon Linden said, “suspending in the middle of KF motion and resuming with that huge time jump sounds really ugly. I haven’t tried it, but if you want to code for that, it might be best to detect the region restart event, reset the position and re-start the key frame motion.” In terms of the Lab dealing with it, he admitted, “given the other things that need attention, it’s not likely to get to the top of the list soon.”

With regards to SVC-7787, his news was in a similar vein, “That is how parcel timing is designed … it measures the current time in the parcel, so if you leave and come back, it’s reset. So there’s a loophole there, yes … and I don’t think we’ve come up with a good alternative. “

Merchant Outbox viewer reaches release candidate status

Posted on by Inara Pey

Even with Direct Delivery being the norm now for SL Marketplace deliveries, some SL merchants are still experiencing problems with the Merchant’s Outbox functionality. To help deal with this, the Lab issued a project viewer at the start of January 2014 which included a number of fixes for some of the issues being encountered.

On March 3rd, this Merchant Outbox viewer moved to the viewer release channel as a release candidate viewer – version 3.7.3.287344. The core issues addressed by this viewer are listed in the release notes as:

  • ACME-1219 Merchant Outbox viewer crashes on Exit on Windows 7
  • ACME-1220 User needs to click OK twice to dismiss Merchant Outbox notification
  • ACME-1221 Merchant Outbox Initialization fails with 404 error with new account in Merchant Outbox viewer
  • MAINT-2287 Merchant Outbox panel unusable and unrecoverable if outbox folder disappears
  • MAINT-2301 Send to Marketplace from Merchant Outbox says it fails when it doesn’t
  • MAINT-2452 Merchant outbox with genuine failure “409 conflict” causes all further imports to fail
  • MAINT-3319 Merchant outbox: Second Life 3.6.8 (282375) build – results when user has a merchant outbox misplaced in inventory.
  • MAINT-3320 Viewer crash when deleting trash which contains Merchant Outbox

(Note that while JIRA links are given, they will result in a permission violation warning until such time as the JIRA is re-opened, which is anticipated for later in week 10.).

So, if you have been encountering issue with the Merchant Outbox, and while it may not solve all woes, it might be worth giving this release candidate a try. Hopefully, with the release of this RC, the code should also now more readily filter through to TPVs in the coming weeks / months.

UKanDo 3.7.2: More nips and tucks

Posted on by Inara Pey

logoConnor Monaron issued a further updated to the UKanDo viewer on Thursday February 27th.

Version 2.7.2.27938 brings the viewer up to parity with the Lab’s 3.7.2 code base and with RLV 2.8.5.10 and offers a series of inventory-related TPV updates, some rebranding and fixes, and the ability to re-skin the viewer with the default LL viewer skin. Release notes for the update are available here.

Inventory Updates

Version 3.7.2.27938 now incorporates three additions to the inventory floater which are popular among several other TPVs:

  • A pair of Collapse and Expand buttons: the first of these will close all folders and sub-folders in your inventory floater; the second will open all folders and sub-folders in your inventory floater, displaying the full tree
  • An inventory search filter drop-down list: allows inventory searches to be filtered by criteria on the drop down (e.g. only search for Landmarks matching the search term)
  • An inventory Worn Items tab: displays everything your avatar is wearing, by folder.
The new (to UKanDo) inventory floater options: the Collapse and Expabnd buttons and the Worn items tab (l): the inventory search filters drop-down (r)
The new (to UKanDo) inventory floater options: the Collapse and Expand buttons and the Worn items tab (l): the inventory search filters drop-down (r)

UKanDo Preferences Tab Updates

The UKanDo tab in Preferences has also been overhauled, with the options rationalised. A new sub-tab is added: Chat – IMs, which pulls together the chat / IMs related options previously found in the Miscellaneous sub-tab into a tab of their own (chat range indicators for the mini-map, notifications alignments, MUpose* and OOC options). Similarly, the Group Land Rez option is moved from Miscellaneous to Avatar (under the new Inventory heading) and also appears in the Build sub-tab as well.

UKanDo 3.7.2 sees the UKanDo tab in Preferences re-worked to make finding options easier.
UKanDo 3.7.2 sees the UKanDo tab in Preferences re-worked to make finding options easier, including a new Chat – IM sub-tab

LL Default Skin

UKanDo users can now opt to re-skin their viewer with the default Lab viewer skin. This is reported as being a part of the UKanDo 3.7.2.27938 update, but appears to work with earlier releases as well (tested with 3.7.0). Be warned, the process does require some fiddling on the user’s part:

  • UKanDo must be shut down
  • The skin folder  must be downloaded from the UKanDo website download page as a ZIP archive
  • The user needs to locate the viewer  install location (e.g. for 64-bit Windows: C:\Program Files (x86)\UKanDoViewer) and then rename it (e.g. “skins_old”)
  • The downloaded skins folder then needs to be dragged from the ZIP archive and dropped into the viewer’s install location (e.g. for 64-bit Windows: C:\Program Files (x86)\UKanDoViewer)
  • UKcanDo can then be restarted, and will use the LL default skin.

The original UKanDo skin can be restored by following the steps above, making sure the original skin folder is renamed “skins”.

Feedback

Another small-ish update, aimed at keeping the UKanDo viewer on a par with LL code updates whilst also incorporating a few nips and tucks.

The option to change the viewer skin is a somewhat convoluted process, especially compared to those TPVs which allow you to select a skin style from within them (e.g. through a Preferences tab) and then applies the selected style with a simple re-start. Whether UKanDo will also move in that direction, remains to be seen; as it is the copying / renaming of folders following each update to the viewer could get a little tiresome for some users.

That niggle aside, a compact and useful update for UKanDo users.

Related Links

Viewer release summaries 2014: week 9

Posted on by Inara Pey

Updates for the week ending: March 2nd, 2014

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
  • By its nature, this summary will always be in arrears
  • The Viewer Round-up Page is updated as soon as I’m aware of any releases / changes to viewers & clients, and should be referred to for more up-to-date information
  • The Viewer Round-up Page also 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.

Official LL Viewers

  • Current Release updated on February 25 to version 3.7.2.286707 (formerly the HTTP RC) – core updates: DNS look ups changed; improvements to mesh uploads / downloads (download page, release notes)
  • Release channel cohorts (See my notes on manually installing RC viewer versions if you wish to install any release candidate(s) yourself):
    • “Project Interesting” RC updated on February 26th to version 3.7.3.287127 – core updates: more viewer-side control of which objects are loaded in memory at any given time; more aggressive scene caching; faster scene load when visiting a region never previously visited; expanded performance metrics (download and release notes)
    • Maintenance RC updated on February 27th to version 3.7.3.287263 – core updates: assorted MAINT fixes (download and release notes)
  • Project viewers:
    • Project Zipper viewer version 3.7.2.286810 released on February 25th – faster viewer installation (download and release notes)

LL Viewer Resources

Third-party Viewers

V3-style

  • UKanDo updated to version 3.7.2.27938 on February 27th – core updates: parity with LL code base through to 3.7.2; RLV updated to 2.8.5.10; added inventory Worn Items and inventory quick filters and Expand and Collapse folder buttons; re-work of Preferences>UKanDo Tabs; LL default skin download added; assorted fixes  (release notes)

V1-style

  • No updates

Mobile / Other Clients

  • No updates

Additional TPV Resources

Related Links

SL projects update week 9/3: viewer, Vivox and Fitted Mesh

Posted on by Inara Pey

Server Deployments: week 9 – recap

As always, please refer to the server deployment thread in the forums for the latest updates / changes.

On Tuesday February 25th, the Main channel was updated with the server maintenance package previously on all three RCs, which comprises the following:

  • Fix for BUG-5034 “If an EM restarts a region and then teleports out immediately, the EM will disconnect just after teleport”
  • Fixed a rare case in which e-mails read by LSL scripts immediately after rez or region change would sometimes be missing the message body
  • Fixed some crash modes.

On Wednesday February 26th, the BlueSteel and LeTigre Release Candidate channels were updated with an infrastructure update, with no functional changes. The Magnum RC received the same infrastructure update and had the server-side AIS v3 code is enabled. As noted in part 1 of this report, the new AIS code is designed to improve performance and reliability when changing outfits, but is reliant on new viewer code, which is currently available from the Lab in the Sunshine Project viewer (of which mor below), and will doubtless start appearing in TPVs soon.

While no details were given, the infrastructure updates deployed to the RC channels are apparently system changes to make simulators easier to manage.

TP Developer Meeting Video

A TPV developer meeting took place on February 28th. The core items discussed in the meeting are reported below, with timestamps in the relevant paragraphs indicating the point at they are discussed in the video embedded here. My thanks as always to North for the latter.

SL Viewer Updates

Release Candidates

  • The “Project Interesting” interest list RC  viewer updated to version 3.7.3.287127 on February 26th
  • The Maintenance RC viewer updates to version 3.7.3.287263 on February 27th.

[0:29] These updates put both of these viewers on a par with the current release viewer, and both are doing “well” in terms of low crash rates, but as Oz Linden said at the TPV Developer meeting on Friday February 28th, “it’s still early days”.

Upcoming Release Candidates

[0:43] The Google Breakpad viewer is expected to reappear as a release candidate “pretty soon”. The last version of this viewer had significant issues related to Windows XP, and so a “different tack” will be taken to handling XP and older versions of Windows with the next update, XP itself having a “truly horrific” crash rate for the viewer. However, and to ease any concerns,  the “new tack” doesn’t involve blocking Windows XP systems from accessing Second Life.

[2:33] The Breakpad update is described as being “important” for TPVs to pick-up and include in their own code, in order to ensure viewers are all reporting stats in the same manner.

[6:48] Both the Sunshine (AIS v3) project viewer and the Merchant Outbox project viewer are expected to move to release candidate status very shortly. These are described as being in the “last stages of the QA pipeline”, and so will be entering the viewer release channel,  once again increasing the number of RC viewers vying for promotion.

Project Zipper Viewer

[7:20] On Wednesday February 26th, the Lab issued the “Zipper” project viewer (version 3.7.2.286810), designed to speed-up viewer installation time (cutting it by roughly 50% in a clean install on my own PC) – from 35.6 seconds to  16.4 seconds. Most of this appears to be the result of compressing / combining files, and there have been questions raised on whether doing so might result in an actual performance hit.

It is anticipated that this viewer will also be shortly rebuilt as a release candidate viewer in the release channel.

Other Viewer Projects

  • [9:12] Group Bans – as I’ve noted in part 2 of this week’s report, the viewer-side code for Group Ban (lists) should be appearing as a project viewer in week 10, ready for the Group Ban functionally to be tested on Aditi
  •  [10:07] Oculus Rift – the Rift viewer is still with LL’s QA team.

Continue reading “SL projects update week 9/3: viewer, Vivox and Fitted Mesh” →

SL projects update week 9/2: group bans update

Posted on by Inara Pey

Group Bans, or Group Ban Lists as I’ve tended to refer to them, as some people appeared confused by the term “group bans” and have taken it to mean banning groups from parcels or regions, is nearing a status where it will be ready for testing on Aditi.

“I’ve gotten the backend almost ready for release (I’m waiting on some builds at the moment),” Baker Linden said of the server-side element of his work, while speaking at the Server Beta Meeting on Thursday February 27th. Baker is hoping that the viewer code will be appearing in a project viewer in the course of the next week.

Recap on Functionality

Baker Linden has been working on the ability to ban people from groups for some 10 months
Baker Linden has been working on the ability to ban people from groups for some 10 months

While discussing the project status, Baker gave a recap of the new functionality:

I’ve talked many previous times about group bans, and now that it’s finally boarding the release train, I’d like to just do a quick overview of what known issues are and what it can do:

    • Group Ban provides the ability to permanently prevent a resident from joining your group.  Currently, the limit will be set to 500 bans per group
  • By default, only Owners will have this ability set
  • Owners must then grant the ability to the roles they want to have manage the ban list
  • You can ban members from the “Members” tab of the group panel, and pre-emptively ban residents through the new “Banned Agents” tab
  • The “Roles” tab will allow you to grant the “Manage Ban List” ability to a role.  when doing this, keep in mind that allowing this ability will also automatically grand the “Eject Members from the Group” and “Remove Roles from Members” ability
  • You will NOT be allowed to disable the “Eject” and “Remove Roles” ability while “Manage Ban List” is allowed
  • You will also be able to (hopefully) batch up bans in groups of 100 at a time (through the “Banned Agents” tab). [It’s the] same as inviting residents; it’s the same code, I just refactored it so I could use it for bans too.

In the initial release, group members can only be banned from within the group floater (right-click on a name and click the Ban button), it will not be possible to right-click on a name in group chat and ban the individual; however, this may be added in the future, as it is considered a relatively straightforward addition.

Group Ban will introduce a new tab to the Groups floater, called "Banned Agents"
Group Ban will introduce a new tab to the Groups floater, called “Banned Agents”, allowing group owners and designated roles to ban people from joining a group

A FAQ has been produced, purely for the purposes of testing on Aditi, but which also helps further explain the group ban functionality. This can be found here, but do note that:

  • The instructions apply to the yet-to-be-released project viewer
  • The final functionality of group bans may vary from that described in the FAQ as a result of bugs or issues arising during testing.

In order to function correctly, the ban ability requires that the Eject and Remove Roles are enabled, as Baker explained above. To make this clear, when a group owner grants a role the ability to ban people from the group, a pop-up will be displayed reminding them that Eject and Remove Roles will also be granted. Similarly, when the ban ability is revoked, a message is displayed confirming that both Eject and Remove Roles have also been revoked.

Known Issues / Initial limitations

  • There may be an initial issue with the new capability during initial deployment as the code starts to reach Agni, when there is the “new” and “old” server-side code running on different channels. This may result in someone being able to re-join a group after being banned, simply because the ban was executed on a simulator which does not have the new code. Obviously, once the code is fully deployed to Agni, this will no longer be a problem
  • There is a risk of some “overlapping” bans may not be processed as anticipated. For example, if two people have the ban role, and one bans users A,B, and C and the other C, D, and E at the same time, “C” should be banned, but there is a slight chance this may not be the case
  • If two (or more) people have the ban ability, then their own view of the group member list will not be updated to reflect bans made by others until such time as they refresh the list
  • The list will cap-out at 500 bans. When that limit is reached, someone with the ban ability must remove names from the list in order for new names to be added, otherwise further ban attempts will fail.

Group Bans represents some 10 months of work for Baker Linden, including a large amount of code refactoring on both the server and viewer sides. The capability still won’t be deployed to the main grid for a little while longer, but progress has now reached a point where more widespread testing should be taking place on Aditi, most likely starting in week 10 (week commencing Monday March 3rd). Deployment to the main grid will most likely remain a combination of resolving any unforeseen issues during the more widespread testing on Aditi and on how it takes for the viewer code to progress from project viewer to release candidate to release viewer.