SL project updates 16 12/1: server, viewer, Aditi inventory

The Trace; Inara Pey, March 2016, on Flickr The Traceblog post

Server Deployments

On Tuesday, March 22nd, the Main (SLS) channel was updated with the improved server maintenance project previously deployed to the three RC channels. This comprises server script fixes (not LSL changes) and internal improvements.

There are no planned deployments for the RC channels for week #1. However, there will be a new RC deployment in week #13 (week commencing Monday, March 28th). the Slow-down in updates remains due to ongoing infrastructure and OS updates occurring across the servers.

SL Viewer

Current Release Viewer

As noted in my last update, the most recent Maintenance RC was promoted to the de facto release viewer on Thursday, March 17th. What I didn’t mention then, and should have done, is that this viewer, version 4.0.2.312269, includes the Lab’s fix for issues of Calling Card duplication.

This means that anyone using as version of the official from this version forward should no longer have issues with calling cards being duplicated, although an initial deletion of cards may be required to clear away any current duplicates with the Calling Cards inventory folder (and any sub-folders within it).

There have been no further updates to the official viewers so far this week, leaving the list of RC cohorts and project viewers as:

  • Current RC cohorts:
    • HTTP updates and Vivox RC viewer, version 4.0.3.312684, dated March 18th
    • Quick Graphics RC viewer, version 4.0.2.312297, dated March 11th, providing the new Avatar Complexity options and graphics preset capabilities
  • Current project viewers:
    • Project Bento (avatar skeleton extensions) viewer, version 5.0.0.311861, dated March 2nd
    • Oculus Rift project viewer, version 3.7.18.295296, dated October 13, 2015
  • Obsolete platform viewer version 3.7.28.300847 dated May 8, 2015.

Aditi Inventory Syncing

The new process for syncing inventories between Agni (the main grid) and Aditi (the Beta grid) is now live.

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.

There does appear to be a possible issue with the syncing, however, with some reports that textures and snapshots unique to Aditi inventories may be getting deleted as a part of a merge between the two. Further investigation is being carried out to see if this is actually the case.

2 thoughts on “SL project updates 16 12/1: server, viewer, Aditi inventory

  1. Ai Austin

    Inara.. in tidying up the calling cards repeated entries… do you know how the folder structure is meant to be when its all corrected…

    Calling Cards
    Friends
    All


    i.e. even after removing repeats in each of the nested folders, I have THREE entries for each name…. in EACH of the three nested folders…

    Calling Cards
    Calling Cards/Friends
    Calling Cards/Friends/All

    Should any or all of these be removed? Would a simple tidy up process of removing everything under Calling cards be okay and let it repopulate the area on login?

    Like

    Reply
    1. Inara Pey Post author

      For the official viewer, I believe the easiest way to get rid of duplicates is to delete everything from the Calling Card folder and from within any sub-folders it contains (the sub-folders are generally system created, so you may not be able to delete them). A new Calling Card list & folder structure will be created on your next log-in, with duplication prevented from then on.

      It’s the same process with Firestorm, with the exception that when using only Firestorm, any regeneration of Calling Cards is suppressed, unless you log-in to SL with another v3-style viewer. So, if you work exclusively with Firestorm and do make use of Calling Cards, only delete all instances of those you’re not interested in.

      Like

      Reply

Have any thoughts?

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s