2016 SL project updates 48/2: TPVD meeting; SVC-7532 roll-back for guns

Rosemoor, Jadeite; Inara Pey, December 2016, on Flickr Rosemoor, Jadeiteblog post

The majority of the notes in this update are taken from the abbreviated TPV Developer meeting held on Friday, December 2nd. The video of that meeting is embedded at the end of this update. My thanks as always to North for recording and providing it.

Server Deployments – Recap

As always, please refer to the server deployment thread for any updates.

  • There was no deployment of a server maintenance package to the Main (SLS) channel on Tuesday, November 29th, leaving it running on the same build as week #47 – 16# However, the channel did undergo a rolling restart in order to update all private regions on it to the new land impact allowances – see my expanded report for more.
  • On Wednesday, November 30th, all three RC channels received a new server maintenance package, comprising internal simulator changes. This deployment also saw all private regions on the three RC channels updated with the new land impact allowances.

No Change Window

[01:51] The Christmas and New Year 2016/17 No Change window has been confirmed as running from Friday, December 16th 2016 through to Monday, January 2nd, 2017. There will be no planned server deployments or major viewer releases during this time frame.

SL Viewer

Project Bento RC

[00:23] On Thursday, December 1st, the Bento RC viewer updated to version, which primarily includes a further fix for a rendering bug related to bad skin weights in some mesh avatars, which hadn’t been entirely fixed with the last update.

Unless something completely unexpected crops up in the next few days, and providing the RC performs well, this viewer could be promoted to release status early in week #49 (week commencing Monday, December 5th). Should this happen, it is likely that Firestorm will issue their own Bento update roughly a week later.

Maintenance RC

[09:46] A new Maintenance RC arrived in the release channel on Tuesday, November 30th. Version includes some 42 fixes and improvements including the following:

Abuse Reporting:

  • When you’re trying to file an abuse report and you crash – the floater will stay open and all information we were able to save will persist.
  • There is a new toolbar button: “Report Abuse”


  • Appearance floater will now remember your last selected tab across logins. You like your Outfit Gallery? Enjoy! You don’t like it? Enjoy something you prefer …

Pay floater:

  • You can now add an optional payment message when you send money, and it accepts UTF8 (via Ansariel Hiller).

360 Snapshot Project Viewer

[29:07] Issues have emerged with the latest version of the 360 snapshot project viewer (, dated November 23rd) and the back-end web viewer, with people reporting:

  • Images captured using the latest version of the viewer will not load into older versions of the web viewer (pages remain suck on the gear cogs).
  • Images captured using any version of the viewer will not load into the latest version of the web viewer (which also uses a different folder hierarchy for the location of ZIP files).
  • The Lab indicates that some of these issues can be corrected by adjusting the image resolution in the snapshot floater to take pictures at a lower resolution.

[13:27] Right now, effort is being directed towards the 64-bit viewer’s media handling, it is therefore unlikely further work will be carried out on the snapshots viewer until 2017.

64-bit Viewer

[10:35] The Lab has successfully built 64-bit versions of the viewer that launch, but is “wrestling” with assorted issues in the new build pipeline. Discussions on the build process are largely taking place on the open-source development e-mail list, but the related wiki information will be updated to reflect the updates, and the use of a new configuration repository for setting all the correct build switches, etc., once the Lab is more confident with the build process. The target for a project viewer remains Real Soon NowTM.

[12:50] The 64-bit viewer will also include the changes to the viewer update process and how the process is managed. These will appear in the 64-bit version after the initial release has been made.

Viewer Release Notes

[10:09] A relatively new feature introduced to the official viewer, and which is now finding its way into version 4.x TPVs is that when opening a newly installed version of the viewer for the first time, the release notes are displayed in a  pop-up, to help encourage users read about what has changed.

Voice Updates

[12:40] There are still bugs to be addressed in the next set of SL Voice updates, and the Lab wants to have these addressed before the updates are released at a project viewer.

SVC-7532 Roll-Back

[14:03] After all the investigations into the recent llTakeControl issues, include the “Horizons gun issue“, which was recently fixed, the Lab has looked more closely at the overall issue of weapons breakage in general, which was introduced as a result of SVC-7532. The conclusion drawn is that the “fix” for the issue should not have been implemented, and the issue as reported in that JIRA should have been marked as “expected behaviour”.

As a result, the Lab will be reverting the change. This means that TPVs should not need to offer a menu / preference toggle to allow users to switch between behaviour modes when using weapons depending upon how the weapon  has been scripted.  However, this does mean that touching things in Mouselook may not work if you are under the control of an attachment using llTakeControl.

The change to revert SVC-7532 will most likely go into an update yo the new Maintenance RC viewer.

Other Items

Proprietary Licensing

[18:30] There is an issue with proprietary licensing, apparently related to music and MP3 decoding and issues around it successor, AAC, and possible patent infringement. The discussion has been going on elsewhere, and I’m currently not au fait with the problems.

Community Gateways

[22:34] The updated registration API for new users, which features the latest avatars, etc., was made available to those in the Community Gateway programme in August / September (London City was one of the first in the programme to implement the updated API). Firestorm is dealing with some issues in updating their own landing pages to point to the new API.

Last 2016 TPV Developer Meeting

This was apparently the last TPV Developer meeting for 2016 – although one has been appearing on the calendar for December 16th.

8 thoughts on “2016 SL project updates 48/2: TPVD meeting; SVC-7532 roll-back for guns

  1. I am trying to make sense of the current status of the 360 snapshot project viewer. Does that mean that the new version can generate snapshots, but there is currently no way to view them, as both the earlier version and the updated version snapshots cannot display in the latest version of the web code.

    It seems that it would be best to revert to the Oct 26th 2016 version and original web support code… but that viewer now will not run… it insist you have a mandatory update.

    Maybe I read this wrong and there is some combination that will work currently?


    1. “Does that mean that the new version can generate snapshots, but there is currently no way to view them, as both the earlier version and the updated version snapshots cannot display in the latest version of the web code.”

      That appears to be the case. Attempting to use the new web server code tends to generate a 404 error, whether ZIP files (from any version of the viewer) are located in the “new” old “old” repository folders (“demo/shots” and “shots”). Attempting to load shots captured using the latest version of the viewer using the older version of the web server fails to display them (the gear cogs appear on-screen, nothing more). Although, according Oz’s comments at the meeting, some have apparently got things to work by tweaking the image resolution in the snapshot floater, as noted in the report.


      1. Unfortunately I tried each resolution (512×512, 1024×1024 and 2028×2048) creating .zip files and the trying to view those with the original web viewer code. None of those work.

        If the ORIGINAL version of the 360 viewer was allowed to run and not blocked to a mandatory upgrade, the we would have this functionality back.


  2. Using the second version of the 360 snapshot project viewer from http://wiki.secondlife.com/wiki/Release_Notes/Second_Life_Project_360_Snapshot/ and the web support package from http://wiki.secondlife.com/wiki/360_Snapshots (link to https://bitbucket.org/callum_linden/360-snapshot-web-viewer/get/tip.zip) as at 5-Dec-2016 loaded onto our Apache web server, I was able to generate and view snapshots in Mozilla Firefox browser at resolutions of 1024×1024 and 2048x2048m but the 512×512 resolution snapshot showed the same image on each of the 6 box sides rather than choosing the size different images.

    http://www.aiai.ed.ac.uk/~ai/360b/demo/?shot=shots/360snap-512.zip (does not work properly)

    The previous multiple thumbnail viewer given by the menu.html example is not in the new web code framework, but a similar example inline.html is there. This needs a bit of modification to work a sit uses web site base specific embedded URLs.

    These need to be made to point to the snapshot .zip files in a suitable location that is relative to the inline.html web page.

    I.e. change zipFilePath: “/demo/shots/default.zip”,
    to zipFilePath: “./shots/default.zip”,

    Examples are shown at
    (order shown is default, 360snap-512, 360snap-1024, 360snap-2048)

    N.B. The “360b” and “360b/demo” test directories indicated above will be maintained once a fully working 360 snapshot setup is in place.


    1. Thanks for this. Whirly and I have been working purely from a localhost perspective with the latest web back-end tip (“…f97ab8f57dcf”) without success, although I’ve not tried different resolutions since the meeting – I’m not sure if Whirly has.


    1. …Which is curious in of itself.

      With earlier versions (viewer and web back-end), I was using my default snapshot set-up without any need to change resolution. I’ll try 1024×1204 with localhost later today if time permits, or at least during the week.


Comments are closed.