Tag: TPVD meetings 2017

Yamagata – blog post

The majority of the notes in this update are taken from the TPV Developer meeting held on Friday, August  25th 2017. The video of that meeting is embedded at the end of this update, my thanks as always to North for recording and providing it. Timestamps in the text below will open the video in a separate window at the relevant point for those wishing to listen to the discussions.

Server Deployments Week #34 – Recap

Please refer to the deployment notice for the week for latest updates and news.

• On Tuesday, August 22nd, the  Main (SLS) channel was updated with server maintenance package, 17#17.08.11.328159, comprising internal fixes and the following feature requests:
  • BUG-5398: llGetObjectDetails() constants OBJECT_SELECTED & OBJECT_SAT_UPON. This sees the addition of two new parameters:
    • OBJECT_SELECTION_COUNT – returns how many agents are selecting any link in a linkset
    • OBJECT_SITTER_COUNT – returns how many agents are sitting on any links in a linkset.
  • BUG-9666: llGetObjectDetails() constants OBJECT_REZ_TIME, OBJECT_CREATION_TIME and OBJECT_RETURN_TIME.
  • BUG-134057 OBJECT_CREATION_TIME output precision possibly clamped – this sees a shift to 6-digit precision.
• On Wednesday, August 23rd, the three RC channels all received a new server maintenance package, 17#17.08.11.328152 comprising the MIME type changes for HTTP.

SL Viewer

[2:35] The Maintenance RC viewer, version  5.0.7.328060 and dated August 9th was promotion as the de facto release viewer on Wednesday, August 23rd.  A new Maintenance viewer is expected to appear around the middle of week #35 (commencing Monday, August 28th).

[1:23] The Alex Ivy 64-bit viewer failed a QA test as a result of issues being introducing in refectoring how the SL Luncher code (used to determine whether the 32-bit or 64-bit version of the viewer should be installed on Windows systems). The issues aren’t serious, so it is hoped this viewer will appear some time in week #35.

[10:50] A further delay in promoting this version of the viewer, which currently remains at version 5.1.0.507412, is that accurate crash reporting data isn’t being gathers, due to issues with the back-end crash analyser, which are in the process of being addressed.  This problem isn’t uinque to the 64-bit build, but does seem to impact it the most.

[2:13] The Voice viewer, currently version 5.0.7.327253, dated June 21st, has been updated for parity with the release viewer, but has yet to pass QA testing at the time of writing.

This leaves the overall pipeline as follows:

• Current Release version 5.0.7.328060, dated August 9, promoted August 23 – formerly the Maintenance RC
• Release channel cohorts (please see my notes on manually installing RC viewer versions if you wish to install any release candidate(s) yourself):
  • Alex Ivy 64- bit viewer version 5.1.0.507412, dated July 21
  • Voice RC viewer, version 5.0.7.327253 dated June 23
    
• Project viewers:
  • 360-degree snapshot viewer version 5.1.0.506743, dated June 29 – hands-on overview
• 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.

[2:50] It is likely the the Lab will, at some point in the future, move to block some of the older and more outdated versions of the official viewer from accessing Second Life.

Texture Memory Increase and Cache Improvements

[13:58] The 64-bit viewer build will see an increase in the texture memory size, although this isn’t part of the current Alex Ivy build. This work includes:

• [14:23] Changes to texture caching, including some re-organising and optimisation, and improvements to  statistics gathering to assist in understanding how well it is performing.
• [15:25] Changes to format of the stored texture data, using the post-decoding raw data, rather than the JPEG2000 data, which should “significantly” improve the amount of textures which can be loaded per second by the viewer, when visited a location previously cached.
• [16:18] An expansion of the cache version guards so that if a TPV changes versions of their texture decoding software (e.g. KDU) or change from 32- to 64-bit, the cache will get wiped, and force the start of a new one (this is something Firestorm already does).
• An increase in cache size.

Further changes will follow from these, including possibly changing how the static VFS cache is handled, but this work has yet to be fully characterised.

BUG-10515: Unable to Rez Due To Invalid Mesh Data

[24:42] The have been increased report of mesh rezzing failures with the message “Unable to rez object because its mesh date is invalid.” It has been noted across different objects, but multiple reports have been made for it occurring with the Maitreya Lara 4.1 body.

The problems seem to occur randomly on different simulators, and the Lab has had problems getting the issue to reproduce, as often a simulator restart may clear it, so Grumpity Linden is seeking reports of the problem which can be made as they occur (object, region name, date / time, etc.), so that an attempt to reproduce the error can be be made and log files immediately gathered before any restart takes place (and/or log files are lost).

Other Items

[3:32] Infrastructure work:  the events of Tuesday, August 22nd (see April Linden’s blog post) became an accidental way of testing some of the new infrastructure changes (in this case, the log-in servers) the Lab is implementing, and will continue to implement over the next several months. This encompasses Second Life and the Lab’s various web properties related to it. This includes further operating system updates as well as various component updates.

[24:09] Part of this work involves inventory, although whether it will lead to user-visible improvements to inventory handling is unclear at this point.

[4:19] Place Pages: this have received a number of fixes recently, for those who wish to use them (see here for general information on Place Pages if you are unfamiliar with them).

[5:32] Estate Tool ban list improvements: The lab did some initial work to improve ban lists at the estate / region level a while ago, but the intended work to improvement to overall layout for the lists, etc., has been delayed do to work on dealing with viewer crashes, etc. However, work will be resuming before the end of the year, and possibly sooner. However, this work is unlikely to see an increase in the number held by the ban list, but will focus on usability improvements.

[28:44]  McAfee Total Protection Issue: This is a problem being experienced by some users on TPVs (e.g. Alchemy and Firestorm) where the viewer is being flagged by McAfee Total Protection. This might be down to a code signing issue, however, to assist in further investigations, the problem needs to be reproduced and reported using the LL viewer.

[33:35] BUG-6925, HUDs and Attachments randomly detaching on region crossings / teleports: This has been investigated and determined to most likely be the result of a race condition, but a fixed has yet to be implemented.

[39:56-end] General discussion on documentation (e.g Axon animation; Objectllsd) and avatar physics calculations.

 

Whimberly – blog post

The majority of the notes in this update are taken from the TPV Developer meeting held on Friday, August  11th 2017. The video of that meeting is embedded at the end of this update, my thanks as always to North for recording and providing it. Timestamps in the text below will open the video in a separate window at the relevant point for those wishing to listen to the discussions.

Server Deployments Week #32 – Recap

Please refer to the deployment notice for the week for latest updates and news.

• On Tuesday, August 8th, the Main (SLS) channel was updated with a new server maintenance package (#17.07.27.327933), comprising “additional internal fixes”,
• The scheduled deployment to the RC channels for Wednesday, August 9th has been cancelled due to a back-end data issue which meant the region channel names weren’t being set correctly, so they didn’t start.

SL Viewer

[00:54] The Maintenance RC viewer was updated on Wednesday, August 9th to version 5.0.7.328060. This is currently the most likely candidate for promotion to de facto release status. The rest of the LL viewer pipeline remains as at the start of the week:

• Current Release version 5.0.6.326593, released on May 26, promoted June 20 – formerly the AssetHTTP RC viewer – overview – download and release notes
• Release channel cohorts:
  • Alex Ivy 64-bit viewer version 5.1.0.507412, dated July 21st.
  • Voice RC viewer, version 5.0.7.327253 dated June 23rd.
    
• Project viewers:
  • 360-degree snapshot viewer version 5.1.0.506743, dated June 29th – hands-on overview
• Obsolete platform viewer version 3.7.28.300847, dated May 8th, 2015 – provided for users on Windows XP and OS X versions below 10.7.

[01:15-01:40 and 4:51-5:33] It is hoped the Alex Ivy 64-bit viewer will be updated in the early part on week #33 (commencing Monday, August 14th). Currently, the viewer is still showing an elevated crash rate for some, for reasons yet to be determined. In the meantime, the Lab is adding further code that will hopefully capture more crash information.

[01:56 and 06:49] The 360-degree snapshot viewer is currently on hold due to people being on vacation at the Lab. This may be a slightly extended delay while resources are diverted to the 64-bit viewer and CEF work.

[14:22-14:34] The Voice viewer is also suffering a high crash rate, also for unknown reasons.

[14:35-14:46] One of the next viewer projects for the Lab is a major re-vamping of the crash reporting and analysis system, which will hopefully make it easier to trace down probable causes for viewer crashes.

llHttpRequest Issues

[02:15-04:21] The least couple of weeks have seen server-side issues with llHttpRequest. Some of this has been due to low-level library changes that were inherited in updating the simulator code to some of the new components, including the OS itself. Other issues were the result of changes the Lab made at around the same time.

Most of these issues have now been rectified, although there is still some incompatibility issues still to be sorted. There is one further significant update related to this which will be going out on Aditi (the Beta grid), which will be put to the test with the intention of seeing if anything else breaks. A blog post / forum notice will precede this.

Simulator Infrastructure Updates

[08:52-09:28] The Lab is going to be carrying out a lot of simulator infrastructure work over the next two quarters. Efforts will be made to make user-visible updates during this work, but most of the work will be transparent to users, and may result in some performance improvements.

Other Items

[08:18-08:46] Group notice failures: No work has been put into looking at why some group notices are being dropped. This is currently seen as a lower priority than dealing with issues which can crash simulators.

[10:29-11:37] Dynamic mirrors (again): (see STORM-2055). The Lab has no plans to work on this at all, but Oz offered a *possible* compromise:

If an open-source developer implements mirrors that work, and are acceptable from a performance point of view, without unreasonable restrictions on where you can put them and what you can put them on, I at least will be happy to consider the contribution. But I don’t believe that’s possible, and I am assured by graphics developers who know a great deal more about rendering than I do, that it isn’t possible; and that’s why we’re not doing in. So, if you have a miracle worker out there who wants to do a contribution to the viewer – go for it! But since I’d like to get other work done, I’m not going to devote our developers to doing it.

[13:37-14:01] EEP – Environment Enhancement Project: a re-iteration of this project see the outline Google doc or my overview for more) will allow for things like phases of the Moon.

[18:20-18:32] Viewer UI Region / Estate ban list improvements: this work is still pending a developer resource.

[19:10-24:12] Abuse of Setting Home:  it has been reported that griefers are able to circumvent being kicked out of a region (TP Home) by moderators if they have home set to that region. The alternative to this is to ban them from the land – but this requires the rights to do so. There are also alleged means to bypass estate bans if the home position is set to the banned region – which should not be possible. If there is a bug allowing this to happen, it needs to be reported with repro steps.

PacMan Stars and Black Stars: the issue of “Pacman stars” (irregularly shaped stars) has been fixed via a contribution by Drake Aconis (Sovereign Engineer). However, the issue of stars appearing as black dots in some daylight windlight settings has yet to be fixed. This may be looked at as a part of the EEP.

 

Follow Your Bliss – blog post

The majority of the notes in this update are taken from the TPV Developer meeting held on Friday, July 28th 2017. The video of that meeting is embedded at the end of this update, my thanks as always to North for recording and providing it. Timestamps in the text below will open the video in a separate window at the relevant point for those wishing to listen to the discussions.

Server Deployments Week #30 – Recap

Please refer to the deployment notice for the week for latest updates and news.

Main (SLS) Channel

There was no deployment / re-start of the Main (SLS) channel on Tuesday, July 25th, the Main (SLS), which remains on server maintenance package #17.07.11.327548. This update included a fix to allow DJ boards to work, however, any scripts which have not been updated to meet the new requirements may not work. for details, please refer to this forum thread.

RC  Channels

The deployment to the RC channels did not go as planned, after it was discovered the release had a creeping crash bug that could not be reproduced on Aditi, but would be a bad experience for all regions on the RCs. A roll-back was therefore performed, leaving all three RCs on the same server maintenance package as the Main (SLS) channel (#17.07.11.327548).

SL Viewer

[0:10-3:33] The Maintenance RC viewer updated to version 5.0.7.327940 on Friday, July 28th. This update includes two crash fixes, and an update for a pull request fix, which Oz has asked third-party viewers to include as soon as possible. Essentially, some of the very low-level code in the log-in process has a very aggressive approach to retries if it encounters log in delays, and this needs rectifying.

This only became apparent when a main network cable in the Lab’s data centre was severed (by a backhoe!). This shifted log-in attempts to an alternative network connection where the combination of high user numbers and this aggressive retry loop in the code resulted in what was essentially a denial of service attack which overwhelmed the log-in servers. Given the depth of the code in the viewer, it is believed it is present in the vast majority (if not all) viewers. This also means the Maintenance viewer will get promoted relatively soon.

[3:59-5:16] The Alex Ivy 64-bit viewer still has an elevated crash rate and the Lab is making changes to obtain better data on the crashes. The 32-bit version of the viewer in particular is suffering “really high” crash rates.

The remaining viewers in the pipelines remain unchanged:

• Current Release version 5.0.6.326593, released on May 26, promoted June 20 – formerly the AssetHTTP RC viewer – overview – download and release notes
• Release channel cohorts (please see my notes on manually installing RC viewer versions if you wish to install any release candidate(s) yourself):
  • Alex Ivy 64-bit viewer version 5.1.0.507412, dated July 21
  • Voice RC viewer, version 5.0.7.327253 dated June 23
    
• Project viewers:
  • 360-degree snapshot viewer version 5.1.0.506743, dated June 29 – hands-on overview
• 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.

Web Property, Attachments and ToS Issues

[5:48-7:01] Some users have been experiencing some or all of the following issues during the week:

• Inability to access various LL web properties (e.g. their own dashboard, the JIRA system, etc). As of the TPV Developer meeting, all web services were believed to be back up and running, although the Lab weren’t sure as a to the cause of the issues.
• Attachment failures – either on attach or with scripts. These are still being investigated, and a definitive cause has not yet been found.
• The Terms of Service update, which officially comes into force on Monday, July 31st but which currently requires acceptance by users, has been causing log-in issues for some. Again, the cause isn’t as yet known.

Other Items

Parcel Sounds

[7:55-13:12] There is a discussion on parcel sounds (from objects and avatars). In short: parcel sounds can be restricted from within a parcel going out, but not for sounds from other parcels coming in. As parcel privacy is two-way, this has caused some confusion for some users. The Lab is hesitant to change the scope of the setting (e.g. make it apply to both sounds leaving and entering a parcel), they are possibly amenable to changing the setting to sounds are restricted to parcels by default, or receiving a code contribution / feature request to separately stop sounds entering a parcel.

Sansar Public Beta

[17:58-18:50] During the meeting, Oz Linden indicated that the Sansar public Creator Beta will be launching on Monday, July 31st / during the week commencing Monday, July 31st.

However, during the week of July 24th through 28th, the Lab hosted a series of meetings involving staff, those of us fortunate enough to be in Sansar and creators and bloggers from Second Life who have not been a part of the Creator Preview in which it was indicated the company wasn’t ready to provide a date for the public Beta, other than it being “soon”.

We’ll obviously find out what is happening on Monday, but either way, I’ll have at least one article on Sansar and Second Life coming out quite soon which will delve into the meat of the meetings – so to speak!

Lab’s Second Life Development Summit

[18:00-18:42] Week 31 (commencing Monday, July 31st) marks the next Second Life summit in which Lab staff directly involved in running and maintaining SL (developer, product team, operations, etc), get together to plan out the next several months of work and projects for the platform.

In Brief

[19:51-20:36]  Further Estate Tool Improvements: the work to improve the Region / Estate floater in the viewer to make it easier to manage ban lists, etc., is still in-hand at the Lab, it’s just been delayed due to other work being carried out / completed.

[21:26-22:57] Premium “Goodies”: Grumpity Linden indicated there are some “awesome goodies” in the pipeline for Premium members, which sparked a lot of text-based suggestions.

[22:57-25:46] Group notices being dropped: there are issues around group notices being received by users in certain groups. The Lab has made adjustments to handling the UDP packets which handle group notices to try to improve things, but the issue of dropped notices is hard to reproduce, and therefore hard to diagnose and fix.

[26:51] Place Pages: have been updated to include events.

 

Stony Hill Vineyard – blog post

Friday, July 7th saw a truncated TPV Developer meeting take place in lieu of the planned meeting for Friday, June 30th. As always, the video of the meeting is embedded at the end of this report, and my thanks to North for recording and providing it. Timestamps in the text below refer to that video, and will run the video from that point in a separate browser tab.

SL Viewers

[3:30] The Alex Ivy 64-bit release candidate viewer (version 5.1.0.507006 at the time of writing) is due to be updated in week #28 (commencing Monday, July 10th). The viewer is liable to receive further updates prior to any promotion to release status, as the Lab further refines the Windows SL Launcher.

As previously noted in these pages, the launcher is designed to detect which version of the viewer a Windows system can run. If it detects the system can run the 64-bit version of the viewer, it downloads and installs that, if not, it defaults to downloading the 32-bit version. An upcoming update to the viewer will include a debug setting to override this and force one or other version to be downloaded and installed (obviously, this will not work trying to run the 64-bit viewer on 32-bit Windows, but will allow the 32 viewer to be run on 64-bit Windows).

Crash rates for the viewer are elevated, but the Lab suspects this is down to the number of 32-bit versions being run.

[5:35] This leaves the current viewer pipelines as:

• Current Release version 5.0.6.326593, released on May 26th, promoted June 20th – formerly the AssetHTTP RC viewer – overview
• Release channel cohorts:
  • Maintenance RC viewer version 5.0.7.327250 dated June 22nd
  • Voice RC viewer, version 5.0.7.327253 dated June 23rd
    
• Project viewers:
  • 360-degree snapshot viewer version 5.1.0.506743 dated on June 29th – overview
• Obsolete platform viewer version 3.7.28.300847 dated May 8th, 2015 – provided for users on Windows XP and OS X versions below 10.7.

The 360 snapshot viewer should be updated with some fixes “soon”.

Server Updates

[6:05] The simulator version using the new Linux operating system update, currently deployed to the Magnum RC channel (server version 17#17.06.29.327400) should be promoted to the Main (SLS) channel on Tuesday, July 11th.

[12:07] This simulator version also includes the fix for DJ boards (see BUG-10073). Some people may need to update their board scripts.

JIRA Temporarily Closed to Comments

The Second Life JIRA has been temporarily closed to comments, because: idiots. Or to allow the Lab to explain it:

Recently, our bug reporting system (Jira) was hit with some spam reports and inappropriate comments, including offensive language and attempts at impersonating Lindens. The Jira system can email bug reporters when new comments are added to their reports, and so unfortunately the inappropriate comments also ended up in some Residents’ inboxes.

We have cleaned up these messages, and continue to investigate ways to prevent this kind of spam in the future. We appreciate your understanding as we work to manage an open forum and mitigate incidents like this.

In the short-term, we have disabled some commenting features to prevent this from recurring. This means that you will not be able to comment on Jiras created by other Residents. We apologize for this inconvenience as we look into long-term solutions to help prevent this type of event from occurring.

Other Items

• The next Firestorm release is liable to be in September
• [8:51] The Lab is looking at turning off the remaining UDP messaging for asset delivery on the servers in February 2018, although this is TBC. This means that viewers not running the latest HTTP updates will not be able to receive any asset data.
• [17:41] The next scheduled TPV Developer meeting is Friday, July 28th

 

Les Reves Perdus – blog post

The majority of the notes in this update are taken from the TPV Developer meeting held on Friday, June 16th, 2017. The video of that meeting is embedded at the end of this update, my thanks as always to North for recording and providing it. Timestamps in the text below will open the video in a separate window at the relevant point for those wishing to listen to the discussions. Note that the timestamps may not be in chronological order, reflecting the fact that some topics were discussed more than once during the course of the meeting.

Server Deployments, Week 24 – Recap

As always, please refer to the server deployment thread for the latest information.

There was no deployment to the main (SLS) channel on Tuesday, June 13th. Nor, as the channel was updated in week #23, was there a restart.

On Wednesday, June 14th, two of the server RC channels were be updated as follows:

• LeTigre received a new server maintenance package (#17.06.12.327066), comprising additional internal logging and features and improvements to region start
• BlueSteel received a new server maintenance package (17#17.06.13.327122) containing internal fixes

[15:20] The Magnum RC was initially updated with a newer version of the new operating system update (#17.06.12.327060), which included a fix for BUG-100737 “Shoutcast receivers unable to relay on RC Magnum” (see part 1 of this report for more on this issue). However, this deployment had to be subsequently rolled-back as the corrective intent of the BUG-100737 didn’t work as expected. This update will likely be re-deployed to Magnum ion week #25 (commencing Monday, June 19th).

SL Viewer Pipelines

Asset HTTP Viewer

[1:39] The Asset HTTP viewer should be promoted to release status at the start of week #25 (week commencing Monday, June 19th). The promotion has been delayed while the viewer goes through a complete regression test (something the Lab does every X number of viewer releases).  This viewer sees delivery of all remaining asset types (wearables, gestures, animations, sounds, etc) over HTTP via the CDN.

[11:39] This viewer should hopefully see faster first-time playback of sounds and animations, as these will be obtained via the CDN, which should be faster than being obtained through the simulator. It also means obtaining assets should also be a lot more reliable when you’re in a busy region, because – again – the assets are not coming via the simulator, but through a CDN node.

The Lab will – several months hence from now – remove the server-side UDP messaging support for these asset types. This will in turn mean that any viewers not updated to the HTTP support at the time the messaging is removed from the simulator will no longer be able to receive these asset types.

Maintenance RC Viewer

[5:25] The Maintenance RC viewer updated on Thursday, June 15th to version 5.0.6.327125. This includes an update to prevent the viewer crashing if it receives a UDP message from the simulator that it doesn’t recognise, by having the viewer ignore all unrecognised messages.

Voice RC Viewer

[5:04] The Voice RC viewer has been updated, but the update has a high crash rate and so the update is unlikely to see the light of day.

Alex Ivy 64-bit Project Viewer

[2:23] The next version of the 64-bit project viewer is completing testing. This includes the new Windows SL Launcher and updater, together with a 64-bit version of the Havok sub-libraries. As noted in my last TPV Developer meeting update, the launcher is essentially a 32-bit executable that checks a Windows system to see if it is 32-bit or 64-bit, and then endeavours to download the correct version (32- or 64-bit) of the viewer if an update is available, install it and then launch it. SL Launcher is only required for Windows as the Mac version of the viewer will only be provided in 64-bit once the Alex Ivy viewer reaches release status.

A follow-up build for RC release has apparently been built, and this should appear soon after the project update, and work has commenced on updating the wiki build instructions for building the viewer to match the 64-bit build process.

[38:26] The wiki instructions are being updates to reflect the requirements of the 64-bit build, so care should be taken when following them for other builds.

360-degree Snapshot Project Viewer

[6:21] The 360-snapshot viewer is now up-to-date and includes code to generate a 360 equirectangular images and their metadata, which can then be uploaded to suitable websites supporting 360-images. The update will appear once it has cleared the Lab’s QA testing.

There is still further work to be done on this viewer – the UI is going to be updated to allow integrated uploads of 360-images to SL Place Pages (and this may be done for Flickr, etc), and SL Place Pages will be updated to accept 360-degree images from the viewer.

TP Throttle

[13:28] The Lab is still looking at throttling the speed at which teleport requests can be re-tried when trying to access a busy region. An initial change is currently on the LeTigre RC, and further changes are liable to be made. As previously noted, these updates shouldn’t impact manual teleports, but may affect teleport HUDs which are scripted to repeatedly re-try teleports in rapid succession until one is  successful (requiring the scripts running them to be modified so they don’t exceed the throttle).

This change is being made because a high incidence of failed teleport requests hitting a busy region places an additional load on the region’s simulator, adversely affecting performance for those already in the region.

Other Items

Uploading Meshes Rigged to Attachment Points

[17:48] This subject came up at the Content Creation User Group meeting as a part of the discussion on animating weapons to follow hands. There was some confusion on whether mesh objects rigged to attachment points could be uploaded, after it was reported that the LL viewer supported it, and Firestorm didn’t (see FIRE-21000 – which now has a fix).  While there is a server-side validation error which can cause some issues when uploading meshes (fix in progress) which might cause upload problems, it is believed that the current behaviour here should be that new objects rigged to attachment points should be blocked from upload, but existing items rigged to attachment points previously uploaded to SL will still work.

Supplemental Animations and Animation Priorities

[24:17] The question was asked if there was any historic reason for not being able to change the priority of an animation post upload (see SVC-8094). It is thought this might be because the priority is set within the animation asset, which cannot be edited. However, it is hoped the forthcoming server-side supplemental animation updates will help eliminate some of the conflicts created by priority clashes.

Providing a Means to Compile Experience Scripts in the User’s Inventory

[35:21] Some people working collaboratively on experiences are finding it problematic when having to update scripts used by the experience, but which are contained in another user’s objects for that experience, as it requires a lot of swapping and changing, rather than simply editing the script in question (see BUG-8180).

While the Lab understands these difficulties, it was a conscious decision to have experience management work as it does, and while at some point in the future they might revisit things, doing so isn’t on the short-term roadmap.

Resetting Scripts in No-Mod Objects

[36:47] This is a request the Lab is unlikely to implement, because it would violate the expectations of the script authors.

Chess Wonderland – blog post

The majority of the notes in this update are taken from the TPV Developer meeting held on Friday, June 2nd, 2017. The video of that meeting is embedded at the end of this update, my thanks as always to North for recording and providing it. Timestamps in the text below will open the video in a separate window at the relevant point for those wishing to listen to the discussions.

Server Deployment – Recap

• On Tuesday, May 23rd, the Main (SLS) channel was updated with a server maintenance package (#17.05.22.326523), containing a fix for BUG-100704, “[Server] If Anyone Can visit is selected after Allow Group was set only group members can enter”, related to the parcel overrides update.
• On Wednesday, May 31st, the RC channels were updated as follows:
  • BlueSteel and LeTigre received the same server maintenance package (#17.05.26.326655), comprising “Tweaks to help with capability loss”.
  • Magnum received a server maintenance package (#17.05.26.326659) for the simulator operating system update, which does not contain and functionality changes.

SL Viewer

[0:20] The Voice RC cohort updated to version 5.0.6.326589 on Wednesday, May 31st.

[0:31] The Asset HTTP viewer is doing reasonably well in its latest RC update (version 5.0.6.326593, dated May 26th), and this might be the next viewer to gain promotion to release status.

[28:22] Once the asset HTTP viewer has been promoted, the Lab plan to develop a schedule for removing simulator support for the old UDP messaging the HTTP updates have replaced. The actual removal of the messaging paths might not occur until 2018.

Maintenance RC

[0:40] A new Maintenance viewer was released as a RC cohort on Thursday, June 1st, 2017. Version 5.0.6.326731 includes a range of bugfixes and updates, including further updates to Trash management:

• Fix for number of items in Trash calculation
• Trash is full floater wasn’t showing in some conditions when it should have been. It will do as it should now.
• Fix for when Trash version gets out of synch
• A delete warning will now show up once every session to cut down on accidents
• Trash purge message will include number of items deleted.

Alex Ivy (64-bit viewer)

[0:55] A new update for the 64-bit viewer will be appearing soon, it will include the new viewer update code, to help ensure the correct version of the viewer (32-bit or 64-bit) is delivered to the user.  Additional changes to the server-side viewer update manager (the code which tells the viewer there is a newer version available) have delayed this update from appearing sooner.

[2:10] When this version of the viewer is issued, it is anticipated that work will commence on building and QAing a Release Candidate version of the viewer. At this point the Lab will also start work on updating the SL wiki instructions for building the viewer.

[5:35] The Lab’s reocmmendation is that if Windows users are using the 32-bit version of the viewer on a 64-bit system, they should swap to a 64-bit version of the viewer for a less crash-prone experience.

[6:16] A caveat to this is 64-bit systems using the Intel HD and Intel HD4000 GPU chipsets. These systems cannot run the 64-bit version of the viewer and require the 32-bit version.

360-degree Viewer

[3:43] An update to the 360-snapshot viewer is expected soon, pending the fix for an issue with the Mac OS X build.

When the update appears, it will not require any post-processing of a ZIP file (as is currently the case). Instead, it should produce an equirectangular image with all the necessary metadata required for displaying on sites which support 360-degree images.

OTR and Chat Text Encryption

[7:14-18:56] Questions have again been raised on the use of end-to-end encryption of IM conversations by TPVs. This was a thing several years ago, largely derived out of misplaced fears that LL staff where reading people’s IM conversations willy-nilly. However, as it used viewer code never intended for that purpose, it was “broken” when the underpinning code was updated / removed.

At the time the encryption was used, it was problematic for the Lab, as it interfered with things like verifying abuse reports by checking IM logs (if the conversation is encrypted, LL cannot verify what was said, and so cannot take any action, even if warranted), and could also be an issue assisting in other types of necessary investigation (e.g. possible fraud / money laundering acts).

The circumstances under which someone from LL can view IM files are strictly limited and controlled, both in terms of who can view them, when then can view them and how much of them can be viewed. As such, there is no risk in IM logs just being casually read at the Lab. Given this, and the issues it can cause, use of any form of encrypted IM exchange would likely be frowned upon or be regarded as a “normal” function of SL (and so wouldn’t be safeguarded from potential “breakage” during future changes to the viewer). Instead, those feeling they need secure communications with other are encouraged to use other means of doing so.

Shoutcast / Streaming Scripts Issues

[23:30-26:33] The Magnum channel RC has resulted in breakages to scripts used by various streaming service DJ boards (see BUG-10073). The issue has been diagnosed, and a means to allow these services to keep operating is being developed. However, when deployed it will mean that the scripts themselves will also need to be revised, and it will not be backwards compatible with systems that are not updated by their creators, which will remain broken. As the change causing the issue is integral to the HTTP updates being made to improve SL’s performance, it will not be rolled back.

Griefing Following Ban

[30:02-35:39] Some estate managers are finding themselves specifically targeted for griefing after banning someone from their land (identified by the griefer as ban notifications carry the banner’s name). In some cases the griefing can extend to groups associated with the land. One solution is to use a bot for banning purposes, however, the request has been made for better anonymity for those carrying out the ban. A JIRA has been requested, providing the fullest possible description of the issue, what happens, and how, and what is believed to be needed to counter it.

General

• [19:17] BUG-40824, “Missing Offline Group Notice (Unreliable Delivery)” is still proving a problem for some. The Lab haven’t looked at the issue recently, but will get back to it.
• [21:25] Local and group chat has been lagging – again, it’s been noted, but no specifics on possible causes.
• [21:49] Increasing limits (physics, etc) – currently the focus is on the simulator OS update, which includes, software tools and libraries. Once this work has been completed, the Lab hopes to look at all the limits and see what can be adjusted, either directly or with some up-front work.