2018 SL project updates week 29/1: Simulator User Group

Abandale; Inara Pey, July 2018, on FlickrAbandaleblog post

Sever Deployments

Please refer to the server deployment thread for the latest updates.

  • There was no SLS main channel deployment or restart on Tuesday, July 17th, 2018, leaving regions on that channel running on server release 18#18.06.14.516450.
  • On Wednesday, July 18th, the release candidate channels should be as follows:
    • Bluesteel and LeTigre will remain on server release 18#18.07.03.517389 and will not be restarted.
    • Magnum should receive a new server maintenance package, 18#18.07.11.517746, comprising “internal fixes”.

The Main channel roll – which was to have included Animesh – was postponed, as Simon Linden explained at the Simulator User Group on Tuesday, July 17th:

We unfortunately held back this morning’s update with the Animesh roll. Late last week we found some code that is probably causing problems with the physics shapes of mesh bodies … not Animesh, but other normal mesh stuff …  Not using the correct physics shape. When building with mesh, there are a few ways to set that shape, and the Animesh code changes affected that code.

Simon Linden, SUG meeting, Tuesday, July 17th 2018.

It should be pointed out that in the context of Simon’s comments, “mesh bodies” means “in-world mesh objects, as worn mesh items doesn’t have a physics shape per se.

Deployment of the Animesh code to the SLS channel will therefore likely await the deployment of a fix for the issues encountered.

SL Viewer

There have been no Sl viewer updates / changes to mark the start of the week, leaving the pipelines as follows:

  • Current Release version 5.1.6.516459 and dated June 15, promoted June 21 – formerly the Pálinka Maintenance Release Candidate – No Change
  • Release channel cohorts:
    • Quinquina Maintenance RC viewer updated to version 5.1.7.517594, on July 12.
  • Project viewers:
  • Linux Spur viewer, version 5.0.9.329906, dated November 17, 2017 and promoted to release status 29 November – offered pending a Linux version of the Alex Ivy viewer code.
  • Obsolete platform viewer, version 3.7.28.300847, May 8, 2015 – provided for users on Windows XP and OS X versions below 10.7.

Attachment Loss / Ghosting on Teleport / Region Crossing

Some people are reporting loss / ghosting of attachments on teleporting. The problems sees to vary in the number of teleports taken before it is noticed, and tends to take the form of others noticing an avatar is missing parts, rather than the wearer (for whom everything still appears to be worn).

It’s not clear how widespread the issue is, although it seems it has been reported a lot through the Firestorm support groups. Mazidox Linden did confirm some attachment / region crossing testing was occurring on Aditi, but it’s not clear if this is in reference to this specific problem, or to with examining / improving region crossings in general.

Firestorm has a Refresh Attachments option (Advanced menu), however, addressing the issue from the viewer is seen as a less than optimal approach, a server-side fix being preferable.

Commenting on region crossings and attachments in general, Simon Linden said, “From what I can tell with my investigations so far, most attachment problems with region crossings come down to messaging failures, and then the viewer and region(s) get out of sync and don’t recover. ” He also noted that his own testing of “double” region crossings (e.g. cutting across the corner of a region while moving between two others) lead him to want to say “stop!” at the first, and not even attempt the second until the first hand-off have completed.

At this point I want to improve the code and communications so after a crossing, both regions and the viewer can agree that everyone is on the 2nd region with all attachments and vehicles and, when something goes wrong, try to recover … At both ends, viewer and region, it should be able to realize it’s been a few seconds and things are missing or not, and then re-try.

Simon Linden on investigating region crossing, Tuesday, July 17th, 2018

As an aside, one of the reasons the Lab is working on region crossings and attachment issues beside trying to make region crossings smoother and more predictable in general, is so that they might increase the limit on the number of attachments that can be simultaneously worn (currently 38). However, as Oz Linden noted at the Simulator User Group meeting, this won’t happen until such time as attachments can remain reliably … attached.

Advertisements

2018 SL project updates week 28/1: simulator user group / EEP

Aphantasia; Inara Pey, June 2018, on FlickrAphantasiablog post

Sever Deployments

Please refer to the server deployment thread for the latest updates.

  • There was no SLS main channel deployment on Tuesday, July 10th, 2018, leaving regions on that channel running on server release 18#18.06.14.516450. However, due to the “14 day rule”, region on the main channel were restarted.
  • On Wednesday, July 11th, the release candidate channels should receive server update package 18#18.07.03.517389, comprising “additional internal tweaks”.

Both of the RC updates will include changes to the Animesh code currently deployed to the RC to allow better logging of Animesh related activities.

SL Viewer

At the time of writing, there had been no SL viewer updates to mark the start of the week, leaving things as follows:

  • Current Release version 5.1.6.516459 and dated June 15, promoted June 21 – formerly the Pálinka Maintenance Release Candidate – No Change
  • Release channel cohorts:
    • Quinquina Maintenance RC viewer, version 5.1.7.516813, released on June 22.
  • Project viewers:
  • Linux Spur viewer, version 5.0.9.329906, dated November 17, 2017 and promoted to release status 29 November – offered pending a Linux version of the Alex Ivy viewer code.
  • Obsolete platform viewer, version 3.7.28.300847, May 8, 2015 – provided for users on Windows XP and OS X versions below 10.7.

Environment Enhancement Project (EEP)

This is the project to introduce a set of environmental enhancements. Rider Linden is now engaged in internal testing a viewer supporting the new EEP capabilities, together with the server-side support. During the July 10th, 2018 SUG meeting, he provided a brief summary as to how the basics of EEP will work:

You can create what are called settings objects in your inventory. These settings objects [they are not prim-like not can they be rezzed in-world] represent either a water, a sky or a complete day cycle. We are providing interfaces that will let you set the parameters for each of these types of settings. (Very similar to the existing WL editors).

[Then,] from the context menu for a setting object you can apply it either to yourself, the parcel you are in or the region you are in. (The last two if you have rights to do so; you may also open the editor and a button there will let you apply to region or parcel as well).

Scripted support for EEP will be provided for agents (avatars) in experiences, but as I’ve noted in previous EEP updates in these pages, this scripted support will not be part of the initial EEP release, but will be added later.

Will there is now the ability to present different windlights at pre-set altitudes (to to 1,000m, then 1,000m up to 2,000m and then 2,000m up to 3,000m and 3,000m+), this may be seen as a less flexible approach that can be achieved through some third-party viewers, which allow much closer altitude zoning of windlight settings (e.g. have a windlight from, say 22m to 500m, another from 500m to 1,000m, etc.). .

The bar at Holly Kai park exemplifies a potential limitation of EEP. The bar is built-in to the base of a rock plateau, and currently, it is possible to define a viewer-side windlight that applies purely to the bar’s interior (i.e. up to a height of 32 metres above the sea floor). Above that limit (“above ground” so to speak), the parcel uses the same daylight windlight as the rest of the region. EEP’s 1,000 metre altitude zoning effectively prevents this.

How big an issue this might be remains to be seen – but it is not unfair to say there is a reasonable number of regions scattered across the grid where EEPs altitude zoning could force a repositioning of different sky builds using local windlights, should it become the only means of applying localised windlight – which might not be initially popular.

In Brief

Retrieving Grid Statistics Page via llHTTPRequest (see BUG-216320): trying to retrieve grid statistics via a script results in a 499 error, although queries via web browsers will still succeed. No remedial work has been done on this.

JIRA Bug report fields issue (BUG-1074): the fields used in the Create form for a bug report do not use the same titles as the fields seen in a filed bug report, nor are they in the same order. This makes submitting a bug report confusing for anyone not used to the SL JIRA (they can’t even look at a filed report to easily see what they sound be entering in the fields of the submission form). This is something the Lab might fix following the deployment of an upcoming JIRA update.

2018 SL project updates week 27

The Vault – dare you enter? – blog post

Sever Deployments

Due to this week being July 4th week in the United States, there are no planned server deployments.

SL Viewer

At the time of writing, there had been no SL viewer updates to mark the start of the week, leaving things as follows:

  • Current Release version 5.1.6.516459 and dated June 15, promoted June 21 – formerly the Pálinka Maintenance Release Candidate – No Change
  • Release channel cohort:
    • Quinquina Maintenance RC viewer, version 5.1.7.516813, released on June 22.
  • Project viewers:
  • Linux Spur viewer, version 5.0.9.329906, dated November 17, 2017 and promoted to release status 29 November – offered pending a Linux version of the Alex Ivy viewer code.
  • Obsolete platform viewer, version 3.7.28.300847, May 8, 2015 – provided for users on Windows XP and OS X versions below 10.7.

Retrieving Grid Statistics Page via llHTTPRequest

There is a known LSL bug when trying to retrieve grid statistics via a script, which results in a 499 error – see BUG-216320. However, queries via web browsers will still succeed.

This Week

Project news will be in short supply, again due to it being 4th of July week.

 

2018 SL project updates 26/1: Simulator User Group meeting

Oboeru; Inara Pey, June 2018, on FlickrOboerublog post

The majority of the following notes come from the Simulator User Group meeting of Tuesday, June 19th, 2018.

Sever Deployments

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

  • On Tuesday, June 26th, the Main (SLS) channel was updated with server maintenance package 18#18.06.14.516450, previously deployed to the LeTigre and Magnum RC channels, comprising internal fixes and logging improvements.
  • On Wednesday, June 27th, the release candidate channels should be updated with server maintenance package 18#18.06.22.516968, which includes Animesh on a first-time deployment for LeTigre and Magnum (having been deployed to BlueSteel in week #25), and “new Main Channel code”.

Some SLS channel regions reported double restarts on Tuesday, June 26th, and these are being investigated by the Lab.

Animesh Deployment

Follow the Wednesday, June 27th, Animesh will be live on all the major RC channels – however, as previously noted in this updates, it is still in development, and not product-ready.

The Animesh project viewer, necessary for working with Animesh and rendering it correctly, can be obtained from the Alternate Viewers wiki page.

Animesh Resources

You can find further information on Animesh via the following resources.

SL Viewer

Recent updates:

  • The release viewer updated to version 5.1.6.516459 (dated June 15th) on June 21st, formerly the Pálinka Maintenance Release Candidate.
  • A new Maintenance RC viewer, version 5.1.7.516813 and code-named Quinquina, was released on June 22nd.
  • The Animesh project viewer updated to version 5.1.6.516525 on June 22nd, and again on June 25th to version 6.0.0.516979.

The other SL viewers in the current pipelines remain as:

  • Project viewers:
  • Linux Spur viewer, version 5.0.9.329906, dated November 17, 2017 and promoted to release status 29 November – offered pending a Linux version of the Alex Ivy viewer code.
  • Obsolete platform viewer, version 3.7.28.300847, May 8, 2015 – provided for users on Windows XP and OS X versions below 10.7.

Environment Enhancement Project (EEP)

The is still some confusion as to how EEP will work with different region / parcel windlight settings at altitude when compared to Firestorm’s parcel windlight capability. In short:

  • Firestorm allows the windlight within a parcel to be changed at any altitude using a command line construct in the About Land description floater.
    • However, this is purely a viewer-side change.
    • Anyone entering a region using a viewer that does not have the same windlight support will not automatically have the setting defined in About Land applied to their viewer.
  • EEP should ensure that windlight settings set by altitude will apply to everyone in a parcel, regardless of the viewer they are using.
    • However, windlight changes by altitude are limited to four heights: from ground level up wards; 1,000m and above; 2,000m and above; 3,000 and above.

Top Scripts and Region / Parcel Management

Some people are experiencing region performance issues  – notably around scripts, etc. It’s been suggested that making Top Scripts and Colliders visible to parcel holders within a region so they can see what in their parcel might be impacting performance has been suggested.

  • This isn’t a fresh request (see JIRA SVC-835), but it is one that hasn’t been discussed recently.
  • The concern was raised that allowing Top Scripts to be more widely visible could lead to harassment between parcel holders in a region.
  • There is also some concern that over-use of the capability could itself impact region performance, because Top Scripts is an intensive query to run.
  • Even so, it is something being take back to the Lab for further discussion, and is seen as “reasonable”, providing the ability to start / stop scripts isn’t included (griefing vector).

2018 SL project updates 24/1: Simulator User Group meeting

Italian Village of Ciampi, Italy; Inara Pey, May 2018, on FlickrItalian Village of Ciampi, Italyblog post

Server Deployments

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 12th 2018, leaving the channel running server maintenance package 18#18.05.25.515749, containing internal fixes and server-side support for the upcoming new Estate Management ban list management changes.
  • On Wednesday, June 13th, the three main RC channels – LeTigre, BlueSteel and Magnum – should be updated with a new server maintenance package, 18#18.05.30.516064, comprising:
    • Additional work to support localised Abuse Report categories.
    • Improvements to object updates as part of ongoing performance improvements.
    • Removal of the logging of a trivial message.
    • Internal fixes.
    • Note that the majority of this updated is the same as 18#18.05.30.515812, initially deployed on Wednesday, June 6th, and subsequently rolled-back.

The reason for the RC channel roll-backs was described by Simon Linden at the Simulator User Group meeting on Tuesday, June 12th:

We had some excitement last week as we rolled a new version out to the RC channels, discovered a crasher bug we didn’t catch in testing, and had to revert back to the main version. That was fixed real quick and we’ll get the updated server again tomorrow … It was basically “go to a region with a crowd”; I’m not sure of the exact frequency, but the new code was in sending attachment updates … it probably happened one in a million times. Put that on a few thousand regions and it becomes noticeable.

SL Viewer

The Pálinka Maintenance RC updated to version 5.1.6.516121 on Tuesday, June 12th, 2018.

At the time of writing, the remainder of the SL viewer pipelines are as follows:

  • Current Release version 5.1.5.515811, dated May 31, promoted June 1 – formerly the Love Me Render Release Candidate.
  • Release channel cohorts:
    • 2-bit Windows Unloop RC viewer, version 5.1.6.515965, dated June 5 – specifically for 32-bit Windows users caught in the 64-bit install loop (see here for more). Otherwise, the viewer is functionally identical to release version 5.1.5.515811.
  • Project viewers:
  • Linux Spur viewer, version 5.0.9.329906, dated November 17, 2017 and promoted to release status 29 November – offered pending a Linux version of the Alex Ivy viewer code.
  • Obsolete platform viewer, version 3.7.28.300847, May 8, 2015 – provided for users on Windows XP and OS X versions below 10.7.

Other Items

Client-Side Scripting Discussion

During the Simulator User Group meeting, the discussion turned towards client-side scripting support. This is something the Lab looked at several years ago, with Babbage Linden working on a possible C# implementation. Tis could enable things like scriptable UI elements, eliminating the need for HUDs, etc.

There are practical benefit to such an approach – be it with C# or something like Python; but there are also risk with the potential for exploiting the capability, as Simon Linden pointed out:

There’s also a really ugly trust issue with viewer-side code … do you trust someone so you’ll install their code, with the potential they might look into your inventory and such … we could probably sandbox an interpreter, but yes that kind of thing would have to be locked down, or it is definitely scary if it can read/write files … also preventing a viewer interpreter from loading outside modules … which of course are very useful, but can do scary things.

Also during the meeting, Oz Linden didn’t rule out the possibility of looking at the project again at some point in the future. However, it is important to note that currently, there is nothing on the SL roadmap with regards to this kind of work – or anything like it – at this point in time.

 

2018 SL project updates 23/2: server and viewer mini-update

Butterfly Beach; Inara Pey, May 2018, on FlickrButterfly Beachblog post

Server Deployments

the RC deployment made on Wednesday, June 6th (version 18#18.05.30.515812) was rolled by on Thursday, June 7th, leave the main grid running server release 18#18.05.25.515749.

As I was unavailable for the Server Beta meeting, I am unaware of whether or not an explanation for the roll-back was given.

SL Viewer

The following viewers have been updated in week #23:

  • The Pálinka Maintenance RC viewer – to version 5.1.6.515927 on Thursday, June 7th.
  • The 360-degree snapshot project viewer – to version 5.1.6.515934 on Wednesday, June 6th.

Both of these updates are to maintain parity with the de facto release viewer (at the time of writing version 5.1.5.515811, formerly the love Me Render RC viewer, promoted on June 1st, 2018).

As noted in my report here, the Unloop RC viewer, version 5.1.6.515965 was released for 32-bit Windows users only, and to specifically help those caught by the “64-bit Windows install loop” created during the initial promotion of the Love Me Render viewer to release status, which left both 64-bit and 32-bit Windows users only able to download the 64-bit version – see here for more.

The remaining viewers in the current LL pipeline remain as:

  • Current Release version 5.1.5.515811, dated May 31, promoted June 1 – formerly the Love Me Render Release Candidate – NEW
  • Project viewers:
  • Linux Spur viewer, version 5.0.9.329906, dated November 17, 2017 and promoted to release status 29 November – offered pending a Linux version of the Alex Ivy viewer code.
  • Obsolete platform viewer, version 3.7.28.300847, May 8, 2015 – provided for users on Windows XP and OS X versions below 10.7.