Tag: SL Viewer

SL project updates 16 11/2: server / viewer / Aditi

Posted on by Inara Pey

The Mill; Inara Pey, March 2016, on FlickrThe Mill – blog post

Server Deployments Week 11 – Recap

There was no planned Main (SLS) channel deployment / restart for the week. On Wednesday, March 16th, the three RC channels were updated with an improved server maintenance project comprising script fixes and internal improvements. The lack of recent deployments remains down to ongoing infrastructure updates occurring across the Lab’s simulator servers.

SL Viewer

On Thursday, March 17th, the Maintenance RC viewer, version 4.0.2.312269, was updated to the de facto release viewer. This viewer does have an issue with invisiprims, which the viewer renders as solid  objects with invalid textures, rather than leaving them transparent, as intended, whether or not ALM is enabled (ALM having previously “broken” invisiprims) – see BUG-11562.

On Friday, March 18th, the HTTP / Vivox viewer was updated to version 4.0.3.312684, which I assume is a rebuild based on the new release viewer, potentially marking this viewer as the next-in-line for promotion (subject to updates with the Quick Graphics RC).

Aditi Inventory Syncing

The new process for syncing users’ Aditi inventory with their Agni inventory has not gone live as anticipated. however, all things being equal, it will be deployed in week #12. This means that, going forward, a user’s Aditi inventory will no longer be overwritten when they change their password and log-in to Aditi, nor will a password change be required to trigger an Aditi inventory sync.

Instead, anyone logging-in to Aditi will automatically have their inventory copied from Agni to Aditi a part of a new process (run at about 06:00 SLT each day). This will happen each time a persona logs in to Aditi, unless their inventory is already flagged for copying, and instead of overwriting a person’s existing Aditi inventory, the incoming Agni inventory will be merged with their existing Aditi inventory, with checks to avoid unnecessary duplication of items each time this occurs and to ensure thing like Trash contents and COF aren’t copied as well.

Other Items

Created Agents for SL?

Lucia Nightfire filed an interesting feature request, proposing the use of created agents in SL. A created agent is essentially the same as regular avatar or bot, but without an internet connection to the server. Created agents have an object-style inventory, and can attach things in a similar manner to regular avatars. Such an approach could allow the development of pets, breedables, ridables, NPC’s, monsters, game enemies, all without the associated cost and complexity of using other means of achieving the same result. See BUG-11368 for more.

What’s now interesting is that the request has been accepted by the Lab. This doesn’t mean it definitely will happen, but it means they are at least interested in considering the potential of the idea.

SL project updates 16 11/1: server / viewer

Posted on by Inara Pey

Suomi - Finland; Inara Pey, March 2016, on FlickrSuomi – Finland – blog post

Server Deployments

There is no planned Main (SLS) channel deployment / restart planned for the week. On Wednesday, March 16th, the three RC channels should be updated with an improved server maintenance project comprising script fixes and internal improvements.

The lack of recent deployments remains down to ongoing infrastructure updates occurring across the Lab’s simulator servers.

SL Viewer

It is anticipated that an RC viewer – mostly likely either the current Maintenance RC or the HTTP / Vivox RC will be promoted to the de facto viewer this week. However, at the time of writing, the list of official viewers still stood at:

  • Current Release version: 4.0.1.310054, dated January 15th – formerly the Maintenance RC viewer
  • Release channel cohorts:
    • Quick Graphics RC viewer, version 4.0.2.312297, dated March 11th
    • Maintenance RC viewer, version 4.0.2.312269, dated March 10th
    • HTTP updates and Vivox RC viewer, version 4.0.2.312094, dated March 9th
  • Project viewers:
  • Obsolete platforms viewer, version 3.7.28.300847, dated May 8, 2015

 

SL project updates 16 10/1: SL viewer, Aditi inventory, PaleoQuest issues

Posted on by Inara Pey

Asphyxiation Point; Inara Pey, February 2016, on Flickr Asphyxiation Point – blog post

Server Deployments

There are no planned deployments / restarts for week #10.

SL  Viewer

The HTTP  / Vivox RC viewer updated to version 4.0.2.311980 on Friday March 4th. This release sees the CURL updated to 7.47.0, together with 10 further fixes and updates over the previous release, included HTTP fixes and fixes with issues within the viewer such as avatar bake fails, viewer crashes, notifications problems, and music stream failures.

The current Maintenance RC viewer updated on Wednesday, March 2nd to version 4.0.2.311770.

As noted in my last Project Bento update, the Bento project viewer updated to version 5.0.0.311861, also on Wednesday, March 2nd, and includes a new version of the Bento skeleton with additional bone sets and other revisions.

Aditi Inventory Syncing

Coyot Linden as he once looked (I need to update my images of him!)
Coyot Linden as he once looked (I need to update my images of him!)

As reported by Coyot Linden at the Simulator User Group meeting on Tuesday, March 8th, the new process for syncing users’ Aditi (Beta grid) inventories with their Agni (main grid) inventories is in the final stages of QA testing, and should be deployed either later this week or early in week #11.

I’ve covered on this subject a number of times since it was first noted as being in the works in December 2015, but in short.

  • Once in place, the new process will not require users to change their SL passwords in order to trigger their Agni inventory being copied over to Aditi. Instead, anyone logging-in to Aditi will automatically have their inventory copied from Agni to Aditi a part of a new process (run at about 06:00 SLT each day)
  • This will happen each time a persona logs in to Aditi, unless their inventory is already flagged for copying.
  • Instead of overwriting a person’s existing Aditi inventory, the incoming Agni inventory will be merged with their existing Aditi inventory – so items unique to a user’s Aditi inventory will no longer be lost as a result of their Agni inventory overwriting the Aditi inventory

In addition:

  • The process will not duplicate items previously copied to Aditi from Agni; however, if an item is renamed or moved to another inventory folder on Agni, it will be copied to Aditi
  • If an item is deleted from inventory on Aditi, but exists in inventory on Agni, it will be copied to Aditi the next time the process runs for that user
  • Inventory and folder links will also be copied from Agni to Aditi
  • Trash and the Current Outfits folder will be excluded from the copy process (the latter to prevent avatars on Aditi ending up wearing multiple outfits).

Other Items

PaleoQuest Banning Issues

PaleoQuest, the Lab’s dino-related quest game which features Experience Keys and which opened in July 2015, has always had some fairly strict rules on what is and isn’t allowed. However, these rules appear to have been recently updated, with the result that a number of users  have found themselves banned (or in receipt of a ban warning) where no infringements have taken place (see here, here, and here for examples).

One major cause of recent bans seems to be that the game is confusing HUDs worn by a user when trying to enter the game (or even in the middle of playing the game), with an attempt to wear a “fraudulent” game HUD, resulting in the wearer gaining an immediate ban, together with the following notice:

YOU ARE WEARING AN OBJECT THAT IS TRYING, WITHOUT SUCCESS, TO PASS ITSELF OFF AS A GENUINE PALEOQUEST HUD. THIS BEHAVIOUR IS ASSOCIATED WITH FRAUDULENT ATTEMPTS TO OBTAIN REWARDS IN THE GAME AND IS NOT TOLERATED. YOU HAVE BEEN BANNED FROM PALEOQUEST.

The problem with the bans has been further exacerbated by some who have raised support tickets having their bans reversed with a note that the system will be adjusted, while others appear to have had their tickets summarily closed.

As a result of this, and other issues encountered with the ban system during what is effectively “normal” game play, a bug report as been raised (BUG-11533). Should you find yourself banned from the game or in receipt of ban warnings whilst engaged in “legal” game play, you might want to add the specifics of your situation to the JIRA, and don’t forget to append information about your viewer / system from Help > About (+ viewer logs, if you have them).

SL project updates 16 9/1: server deployments; SL viewer, misc news

Posted on by Inara Pey
Casabalanca: Rick's Café Américain - "Of all the gin joints, in all the towns, in all the world, she walks into mine."
Casablanca: Rick’s Café Américain – “Of all the gin joints, in all the towns, in all the world, she walks into mine.” – blog post

Server Deployments

The Main (SLS) channel was updated on Tuesday, March 1st, with the server maintenance package deployed to the three RC channel is week #8. This comprises a server crash fix and “minor internal improvements.”

The server deployment thread lists any RC deployments for the week as “TBD”. however, speaking at the Simulator User Group meeting on Tuesday, March 1st, Simon Linden indicated it is unlikely there will be any RC deployment until week #10 (week commencing Monday, March 7th 2016). These will apparently have an update that addresses a means by which a simulator can be intentionally crashed.

SL Viewer

Currently, the official viewer from LL remain unchanged from the end of last week:

  • Current Release version: 4.0.1.310054, January 15 – formerly the Maintenance RC viewer download page, release notes
  • Release candidate viewers:
    • Maintenance RC viewer version 4.0.2.311655, dated February 26th
    • HTTP updates and Vivox RC viewer version 4.0.2.311302, dated February 22nd
    • Quick Graphics RC viewer version 4.0.2.311103, dated February 17th
  • Project viewers:
    • Project Bento (avatar skeleton extensions) version 5.0.0.310099, dated January 20th
    • Oculus Rift project viewer version 3.7.18.295296, dated October 13th, 2015
  • Obsolete platform viewer version 3.7.28.300847 dated May 8th, 2015.

OpenSSL Update

As noted in my last TPVD meeting notes, the Lab were awaiting an update to OpenSSL. This has now been released and there is minimal impact for SL. This therefore should require any fast-tracked update to the viewer.

Grid-wide Experiences

The simulator user group meeting saw a general discussion about allowing broader access to the Experience Keys database (the KVP) without land owners necessarily having to grant permission to specific Experiences.

The idea here is that there are applications which rely on persistent data or utilise grid-wide data exchange (e.g. a teleport network, a vending system network, etc.), and applications which require script settings survive the script reset. Currently, the way to achieve this is to use external data stores (see BUG-11499 for one example).

Some feel that if there were a way to dissociate the KVP database from things like avatar influences, then it could be used for such applications, removing the need for external data stores and the rick of those data stores vanishing / not being available. However, this is not something the Lab is particularly keen on, for a number of reasons. For example, it could result in their servers storing a lot of data and carrying a lot of database quires and updates, something that might not scale terribly well with volumes and associated storage space cost. Nor would it necessarily safeguard the data any better (if the Experience owner downgrades to Basic or ceases paying their Premium subscription, the data will be lost).

During the discussion Oz indicated that the Lab has no plans to make grid wide experiences available any time soon, due to concerns about how “certain internal features” would scale.

SL project updates 16 8/1: server deployments; SL viewer

Posted on by Inara Pey

The Yorkshire Moors; Inara Pey, February 2016, on Flickr The Yorkshire Moors – blog post

Server Deployments

There was no scheduled Main (SLS) deployment on Tuesday, February 23rd. On Wednesday, February 24th, all three RC channel should all receive the same new server maintenance package, comprising a server crash fix and “minor internal improvements.”

It is likely the server deployments will remain at a slower pace over the next few weeks as the Lab focuses on internal infrastructure changes.

SL Viewer

On Monday, February 22nd the HTTP / Vivox RC viewer updated to version 4.0.2.311302. The see the additions of the following fixes:

  • MAINT-5295 Extra setopt in PUT case for llcore::http forces PUT to POST
  • MAINT-5625 [Project Azumarill] Selected Objects Show Land Impact of 0
  • MAINT-5628 [Project Azumarill] When posting to Flickr, Upload button does not grey out when upload is in progress, clicking Upload more than once results in all images failing to post
  • MAINT-5629 Viewer Makes Request for SRV Records on Login
  • MAINT-5676 Azumarill repeatedly requests weight of selected objects in edit mode
  • MAINT-5978 Convert the Vivox state machine over to a coroutine implementation
  • MAINT-6071 Reference to a UUID used after iterator is lost.
  • MAINT-6086 Crash when removing non added Vivox session.

The remaining RC and project viewers remain unchanged from week #7:

  • Quick Graphics RC viewer, version 4.0.2.311103 dated February 17th Avatar Complexity options and the new graphics preset capabilities
  • Maintenance RC viewer,  4.0.2.310545 dated February 2nd – 38 updates. fixes and tweaks
  • Project Bento (avatar skeleton extensions), version 5.0.0.310099 dated 20th
  • Oculus Rift project viewer, version 3.7.18.295296 dated October 13th, 2015
  • Obsolete platform viewer version 3.7.28.300847, dated May 8, 2015 – provided for users on Windows XP and OS X versions below 10.7.

This all leaves the release viewer unchanged: version 4.0.1.310054, dated January 15th.

SL project updates 16 7/1: server and viewer

Posted on by Inara Pey

Sorrow; Inara Pey, February 2016, on Flickr Sorrow – blog post

Server Deployments

There are no server deployments planned for this week, and no planned restarts for any of the channels.

There is an RC deployment planned for week #8 (week commencing Monday, February 22nd), details of which are still TBA.

As there have not been any rolling restarts, and won’t be any across the entire grid until around week #9, the advice is that if your region is behaving abnormally, file a support ticket to have it restarted. The Lab’s support team are aware that there are no scheduled restarts at present, so they should process requests OK.

SL Viewer

With Monday having been a holiday in the United States (Presidents’ Day), there was no meeting at the Lab to discuss viewer promotions.  This leaves the current list of Lab viewer unchanged from the end of week #6:

  • Current Release version: 4.0.1.310054, January 15 – formerly the Maintenance RC viewer download page, release notes
  • RC viewers:
    • HTTP updates and Vivox RC viewer updated to version 4.0.2.310660 on February 4 – combines the Project Azumarill RC and Vivox Voice RC updates into a single viewer  (download and release notes)
    • Maintenance RC viewer version 4.0.2.310545 released on February 2 – 38 updates. fixes and tweaks for memory leaks; viewer crashes; UI, permissions and mesh uploader bugs; visual muting issues, autopilot issues and duplicated calling cards (download and release notes)
    • Quick Graphics RC viewer updated to version 4.0.2.310127 on January 20 – provides the new Avatar Complexity options and the new graphics preset capabilities for setting, saving and restoring graphic settings for use in difference environments / circumstances (download and release notes)
  • Project viewers:
    • Project Bento (avatar skeleton extensions) version 5.0.0.310099 released on January 20 – adds 90+ bones to the existing avatar skeleton (download and release notes)
    • Oculus Rift project viewer updated to version 3.7.18.295296 on October 13, 2015 – Oculus Rift DK2 support (download and release notes)
  • Obsolete platform viewer version 3.7.28.300847 dated May 8, 2015 – provided for users on Windows XP and OS X versions below 10.7 (download and release notes).

As noted in my recent TPVD meeting report, further updates are expected to the HTTP / Vivox RC viewer and the Quick Graphics RC viewer, but these may not appear this week.

Region Crossings – Grey Box Issue

There have been increasing reports of region crossing issues, including the return of the “grey box” attachment issue which was originally seen in 2013 when crossing from a BlueSteel RC to any other region. This would see any passenger(s) sitting on a vehicle surrounded by (or even replaced by) a grey prim, and left with no choice but to relog, leaving the prim behind, attached to the vehicle.

Caitlyn recently got caught by the "grey box" issue as we were sailing on the north side of Blake Sea. If you encounter the problem, please file a JIRA with as much information as possible (see below)
Caitlyn recently got caught by the “grey box” issue as we were sailing on the north side of Blake Sea. If you encounter the problem, please file a JIRA with as much information as possible (see below)

At the time of the problem first appearing, Kelly Linden described it thus:

Every agent has a ‘task’ representation on the server that is the same as a prim. The bug is in sending the linked set w/ avatars to the other region: avatars after the first are losing the special avatar treatment and getting passed as a regular linked prim. So that prim is what the server thinks all avatars look like.

Simon then added:

The region crossing code basically un-sits avatars from an object, sends both the avatars and object to the next region [as separate sets of data], which puts them back together. In this case, the 2nd avatar doesn’t get detached properly and things go south from there. So the 2nd avatar gets sent over bundled up with the object … which it’s not designed to do.

It had been thought this issue had been dealt with via a fix for (non-public) BUG-3547. However, if it is resurfacing, the problem now is to pin it down in a reproducible manner, if indeed it is returning. Should you encounter it, please make sure you file a JIRA providing as much information as possible, including your viewer log files, the regions you were crossing between when it happened yo you (or your passengers), the date and time, details of the vehicle you were using, etc.