SL Projects update week 43 (2): server and viewer notes

Things are in something of a lull server-side in terms of deployments and projects at the moment, so the news from the Lab is a little light.

Server Deployment

With just the one deployment to the Main channel in week 43, the entire grid is currently running on the same server release.

Commenting on the released package at the Server Beta group meeting on Thursday 24th October, Maestro and Simon Linden provided further information on the performance issue fix which is aimed at the experimental interest list viewer (which has yet to formally appear, but can be self-compiled by those with access to the code repository).

“The bug was about avatars not loading for ~70 seconds when you visit an area with ten or so avatars nearby, Maestro explained. “And by ‘not loading’,  you wouldn’t even see name tags.”

“I think the problem was when those viewers used new methods to download or check the cache state of some data … it would over-load the network and thus the avatar updates were really slow,” Simon added, before continuing, “Since the current viewer doesn’t do that, they don’t have the bug. Clubs and large crowds are always a problem because when you arrive you just get a ton of data to fetch and load.”

Week 44 should see what Maestro described as a “minor maintenance release” for the server appearing next week, which includes “a few miscellaneous crash fixes”. At the time of writing it is not clear if this will be the only RC deployment or whether anything else might also pop-up when the deployment thread is published.

SL Viewer Updates

The “Sharestorm” release candidate, version 3.6.9.282535, which combined the updates from the Snowstorm contributions viewer featuring the request teleport functionality with the SLShare release candidate, was promoted to the de facto release viewer on October 23rd. This leaves just the Maintenance release candidate viewer 3.6.9.282553 sitting in a release cohort, which will be updated in week 44, once it has been rebuilt using the release viewer code base.

Group Ban List

Baker Linden’s Group ban list work remains on internal testing within the Lab (with Maestro and Caleb Linden volunteering as Baker’s guinea pigs). The project has also apparently been awaiting internal QA resources.  Baker hopes to have a detailed update on progress in week 44, but as he said at the Server Beta meeting, “I’d rather take the time to do it properly than rush it out the door and have it be worthless! :).”

Other Items

As reported in week 42, A problem had been noted following-on from the recent updates to prevent people from using recursive rezzing which means some engaging in combat have found combat vehicles in regions with short auto-return times can have their ordnance immediately returned when a weapon is fired, and any temp vehicles are unable to rez attachments, even when sat upon. Maestro confirmed that as a result of a feature request having been raised, Andrew Linden is now looking at introducing a special exception for temp-on-rez / auto-return timer inheritance when the rezzer is a vehicle.

SL project updates week 43 (1): Server releases, interest list

Simulator UG meeting, Tuesday Octber 22nd, 2013
Simulator UG meeting, Tuesday October 22nd, 2013

Server Deployments – Week 43

As always, please refer to the week’s forum deployment thread for the latest news and updates.

Second Life Server (Main Channel) – Tuesday October 22nd

The Main channel was updated with the server maintenance project that was previously on all three RC channels.  The package includes:

  • A fix for “Group member access to parcels fails when ‘Sell passes to’ is enabled”
  • Fixes for two region crossing issues:
    • “‘Ghost’ avatars and vehicles sometimes appear to an observer at the sim border”
    • “Vehicles which exit a region with a passenger are incorrectly auto-returned and become ‘ghost shapes’ in the physics engine”
  • Extremely high Avatar Render Weights reported to the server are now capped at 500,000
  • A performance issue fix for avatar loading speed in the experimental ‘viewer-interesting’ viewer.

Second Life RC BlueSteel, RC Magnum, and RC LeTigre – Wednesday October 23rd

There are no updates planned for the three RC channels, as a result, there was no rolling restart across the RCs.

SL Viewer Updates

The Google Breakpad RC was removed from the viewer release cohorts at the end of week 42.

Interest List Viewer

The interest list RC viewer is once again delayed.  Commenting on it at the Simulator User Group meeting on Tuesday October 22nd, Andrew Linden indicated the hoped-for schedule for its appearance is before the end of the month, but there is something of a low confidence level in the estimate.

Apparently, there is still a performance issue to be dealt with (whether this is the same issue Richard linden mentioned in discussing the interest list viewer at the TPV developer meeting on Friday October 18th is unclear). Also, it seems that the recent issues of objects steadfastly refusing the render in the interest list viewer without a relog  – thhought to have been resolved in week 42 – have also regressed into the viewer code with recent builds.

The issue of prims failing to render in the Interest List viewer, as demonstrated by Whirly Fizzle in the images above and once thought to have been solved, has apparently returned to haunt the code in recent builds, helping to further delay the appearance of the viewer as a release candidate.

Andrew also clarified that the definition of objects which are cacheable by the viewer has been revised such that it is now objects which have not changed outward appearance or transformed in the last two minutes, rather than the one minute Richard Linden indicated, so as to allow for temp-on-rez objects (otherwise additional logic would have been required to check on these). The changes to the definition also mean that some scripted objects which have certain script calls in them, but which do not change appearance as a result of the calls, can also now be cached by the viewer.

As an adjunct to the interest list viewer discussion, Andrew indicated his “before / after” video for scene loading has received the “Torley treatment”, and the results are “impressive”. This is for the changes already implemented server-side, and which should already be visible to people without the Interest List viewer. There’s no date as to when this video may make its public debut.

Other Items

LSL Control for Materials

There have been renewed enquiries for the introduction of scripted control for materials. This has been requested in the past, and was always considered “out-of-scope” for the initial release of materials. A (further?) JIRA has been raised on the topic (MATBUG-359), but is light on suggestion on what might be required, etc.

Those Lindens attending the meeting (Andrew, Kelly and Simon) could see the advantages of extending LSL to handle materials (and Brooke Linden has indicated she feels the JIRA is a valid request). However, how best to achieve this, and the time-frame in which it might be achieved (not just in terms of a technical approach, but also in terms of the Lab’s internal priorities and workload) are unclear at this point.

Both and Andrew and Kelly felt that requiring the normal / specular maps to be in the object contents might be a means by which to both enable and constrain the use of LSL manipulation of materials because of the lack of permissions associated with UUIDs  and concerns of misuse. While no promises were made as to whether the work would proceed, Simon Linden suggested a further step would be to lay out a clearer proposed API and the exact behaviour required for manipulating materials via script. Andrew also indicated he has a “few” LSL calls to add, so he’ll try to take a look at the materials system o see how hard it would be to give script access to it.

llGetObjectDetails() and keyframe animation states

Simon Linden indicated that there has been some talk within the Lab of adding some new parameters to llGetObjectDetails() which would return an object’s keyframe animation states, so it would be possible to get the step number, state (paused, looping, ping-pong, etc.). Again, if / when this might appear is unclear; Simon appeared to be putting the idea out for feedback from the meeting attendees.