SL project updates 24/3: TPV Developer meeting

Le Sixième Sens, Les Reves Perdus; Inara Pey, June 2017, on Flickr Les Reves Perdusblog 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.

Advertisements

One thought on “SL project updates 24/3: TPV Developer meeting

  1. About the 8180

    The way we work it when the object is owned by another:

    a) Object Owner puts the object and contained script(s) on group Share and full perms
    b) Owner gives the Experience scripter(s) Edit rights on their stuff
    c) Scripter can then edit the script(s) in-situ and compile it/them
    d) Scripter can make a backup (for themselves) of in-situ script edits using copypasta to nc or irl
    e) To replace a script (or add new script) then scripter sets full-perms to own script and drops it in the Owner’s object. The script ownership is transferred to the object owner, in situ editing is then also possible as above
    f) Scripts are set to full perms to make it simple, as when Modify perms are set then copypasta is always possible negating any No Transfer/Copy perms
    g) As the scripter has Edit rights on Owner’s stuff then scripter can drag/copy the object (to make a inworld backup and/or testing) with Owner retaining ownership of the copy

    Like

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