On Tuesday June 24th, the Main channel was updated with the inventory / AIS v3 project, previously deployed to BlueSteel, which requires the current release viewer. See the release notes for more
On Wednesday June 25th, the three RC channels were updated as follows:
BlueSteel and LeTigre received a new server maintenance project with the new LSL functions to view and modify materials (see my notes) – release notes
Magnum remains on the Experience Tools project, but should additionally receive the inventory / AISv3 update deployed to the Main channel – release notes
Group Chat
Simon Linden is again working on improving group chat, with further tests being carried out during the Server Beta meeting on Thursday June 26th. Currently, the emphasis is on further improving reliability when engaged in group chat and moving between regions (either via teleport or directly by crossing between regions). A couple of people reported their chat windows appeared to freeze a lot less when switching between group chat sessions or following a teleport. Whether this was actually the case or a placebo effect is unclear, as Simon indicated he couldn’t see why it might be any different at this point in proceedings.
Other Items
Magnum llAttachToAvatarTemp Bug
An odd bug has been discovered on Magnum, which may be related to the Experience Tools code. It is defined in BUG-6438, “Objects attached via llAttachToAvatarTemp to object owner detach when script is removed from prim inventory”.
Essentially, using a script in an object which uses llAttachToAvatarTemp to attach an item to attach itself to the creator of the object, and which uses llRemoveInventory(llGetScriptName()) to remove the script from the object, results in the object itself detaching and being deleted. If the object is used by someone other than its creator, it will attach and the script will be correctly removed without detaching the object as well. It’s not clear if this happens with objects with multiple scripts in them or not, as it has only been tested against objects with the temp attach script in them.
Investigations are continuing into a fix, but in the meantime, it is believed that the Magnum code won’t be moving to the Main channel in week 27.
ALM and Viewer Log Spamming
There is a viewer rendering issue, which can make itself particularly known when using the LSL functions for materials, where the face of an object will not be rendered, and the viewer will receive a lot of log spam (see BUG-6187). While things got sidetracked so he couldn’t expand on things, Maestro Linden did indicated at the Server Beta meeting that the issue is continuing to be looked at.
On Tuesday June 24th, the Main channel was updated with the inventory / AIS v3 project, previously deployed to BlueSteel, which requires the current release viewer. See the release notes for more.
Release Candidate Channels
On Wednesday June 25th, the three RC channels should be updated as follows:
BlueSteel and LeTigre should receive a new server maintenance project with the new LSL functions to view and modify materials (see my notes) – release notes
Magnum remains on the Experience Tools project, but should additionally receive the inventory / AISv3 update deployed to the Main channel – release notes
SL Viewer Updates
The release viewer updated on Monday June 23rd to version 3.7.10.291134 (formerly the SL Share 2 RC – ability to upload Tweets and snapshots to Twitter and / or snapshots to Flickr).
The regular Monday Content Creation User Group meetings came to an end on Monday June 23rd. Also at the meeting, as he has been for the past few weeks, doubtless getting up-to-speed with things as a part of his new role in heading-up the SL development team, Oz Linden indicated content creation issues could in future be raised at either the Simulator User Group meeting (which generally has a strong cross-over of attendees with the Content Creation UG meeting) or the Open Development meeting.
Commenting on the change to the meeting, Nyx said:
I’m moving on to other projects and haven’t been able to keep up with the details of content creation tasks as well as I used to be able to … I’ll still be inworld from time to time, and will be helping Oz whenever any avatar issues come up or with any other pieces where I can assist of course.
Whether this can be taken to mean Nyx is moving on to the new platform project is open to speculation. However, that the Content Creation meeting has now ended as an entity in its own right should not be seen as any indication that the Lab is starting to raise the drawbridge. Meetings over the pass few months have, for the most part, had a low attendance (with occasional sharp rises), and opportunities remain to discuss issues in other venues.
Experience Tools
Thanks to my getting a bullet point in the wrong place in my overview of Experience Tools, the article gave the impression that whitelisting experiences on mainland would only be possible with grid-wide experiences. This has been corrected. Experiences can be run at the parcel level on the mainland.
Updates for the week ending: Sunday June 22nd, 2014
This summary is published every Monday and is a list of SL viewer / client releases (official and TPV) made during the previous week. When reading it, please note:
It is based on my Current Viewer Releases Page, a list of all Second Life viewers and clients that are in popular use (and of which I am aware), and which are recognised as adhering to the TPV Policy. This page includes comprehensive links to download pages, blog notes, release notes, etc., as well as links to any / all reviews of specific viewers / clients made within this blog
By its nature, this summary presented here will always be in arrears, please refer to the Current Viewer Release Page for more up-to-date information
Official LL Viewers
Current Release version: 3.7.9.290582 June 16th (formerly the MemShine RC – combining the MemPlugs memory leak fixes and sunshine AIS v3
SL Share 2 RC viewer updated to version 3.7.10.291134 on June 19th – ability to upload Tweets and snapshots to Twitter and / or snapshots to Flickr (download and release notes)
Snowstorm viewer prompted to RC and updated to version 3.7.10.291042 on June 19th – numerous code contributions including STORM-1831 Obtain LSL syntax table from simulator so that it is always up to date; STORM-1966 Block installation on old and unpatched versions of Windows and STORM-68 Allow setting of default permissions on creation of objects, clothing, scripts, notecards, etc. (download and release notes)
Project viewers:
Group Ban project viewer version 3.7.8.290887 released on June 17th – allows certain group members to ban avatar from a group or from joining a group When an existing group member is banned, they are also automatically ejected from the group (download and release notes)
Black Dragon updated to version 2.3.9.9(A) on June 17th – core updates: please refer to the change log
Restrained Love Viewer updated to version 2.9 on June 18th – core updates: new RLV camera commands (release notes)
V1-style
Cool VL viewer updated on June 21st – Stable release to version 1.26.12.4 and Legacy version 1.26.8.62 – core updates: please refer to the release notes
On Tuesday June 17th, the Main (SLS) channel was updated with the group ban project server code – release notes
One Wednesday June 18th, the RC channels were updates follows:
LeTigre received a new anti-griefing measure – release notes
Magnum remained on the Experience Tools project, but also received the group ban server code and the anti-girefing measure – release notes.
BlueSteel remain on the Sunshine / AIS v3 project, and the but also received the group ban server code and the anti-griefing measure, the viewer for which was promoted to the de factorelease viewer on Monday June 16 – release notes.
There has been some interest voiced at both the Simulator UG meeting and the Server Beta UG meeting, in the “anti-griefing measure” deployed to the three RCs this week. Commenting on this at the Server Beta meeting on Thursday June 19th, Maestro Linden said, ” I think I’ll be able to discuss the change next week,” (after it has been deployed to the Main channel as well). ” But right now, some people would unfortunately use the information as a how-to-grief instructional.”
Upcoming Deployments
The LSL functions for materials may be set to arrive on an RC in week 25. This depends on how this week’s RCs continue to perform, but assuming the anti-griefing measure on LeTigre is promoted to the Main channel, then that RC would theoretically be available for the LSL functions for materials, assuming no significant bugs are filed against it as a result of Aditi testing.
TPV Developer Meeting
A TPV developer meeting took place on Friday June 20th. The core items discussed in the meeting are reported below, with timestamps in the relevant paragraphs indicating the point at they are discussed in the video embedded here.
As has been noted elsewhere, the meeting was attended by Ebbe Linden, who took an impromptu Q&A session at the end of the meeting. This commences at around the 51:00 mark in the video. While this report does not cover that Q&A session, information on his comments about the Lab’s in-development new virtual world platform can be found in Ebbe confirms: “we’re working on a ‘next generation’ platform” (with audio).
My thanks, as always, to North for the video.
SL Viewer Updates
[0:01:18] The SL Share 2 viewer, providing Flickr and Twitter upload support and the snapshot filtering capabilities for both and for snapshot uploads to Facebook was updated to version 3.7.10.291134 on Thursday June 19th, bringing it to parity with the current release viewer code base
The Snowstorm viewer, released as a project viewer on June 12th was updated to version 3.7.10.291042 on June 19th, bringing it to parity with the current release viewer code base, and issued as a release candidate viewer. This has had a significant bug reported against it, which is currently being fixed. As such, it is unlikely that this RC will be in the running for promotion until after it has been refreshed with the fix and the updated version has been in the viewer release channel sufficiently long enough for the Lab to obtain meaningful statistics on its performance.
Avatar System Clothing Layers
[0:4:00] BUG-6258, “Popularity of Mesh Attachments Facilitates Need For More Alpha Layers” is a request to raise the number of alpha layers which can be concurrently worn (at the moment this is 5).
Rather than increasing the number of an individual layer which can be worn (such as alphas), the Lab is considering setting a global limit – so as with attachments, an avatar can wear as many clothing layers in any combination, up to the global limit (with attachments, this is set to 38).
The Lab is still investigating this approach in terms of feasibility and what the upper limit for clothing layers might be for an avatar. Until they do make a final determination on the issue, they have requested TPVs do not arbitrarily add to the existing layer limits, as there is a risk that anything the Lab does do on this front may conflict with alternatives put in place by TPVs.
SL Experience Tools
[0:07:10] The major technical announcement of the TPV meeting was that the long-awaiting Experience Tools will be entering a beta test phase in the very near future. You can catch-up on this in my initial Experience Tools overview.
Z-offset Height Adjustment Proposal
[0:39:06] One of the issues with the introduction of Server-side baking is that it broke the “Z-offset” capability common to many third-party viewers. This allowed the vertical height of an avatar above the ground to be adjusted, such that sits and kneels don’t leave the avatar apparently floating in the air, and which allow those with very tall / giant avatars or very small / petite avatars and those wearing full body mesh to similarly adjust their vertical placement relative to the ground / floor.
In response to the issue being raised as a bug report (see SUN-38, “As users of kneel/lay/sit animations and tiny/giant avatars, we need a way to change the body size in SSB sims”), the Lab, via Nyx Linden, introduced the hover feature, which allows an avatar’s standing height to be adjusted to some degree via an appearance slider.
Jessica Lyon demonstrates part of the avatar height offset issue: when seated using her preferred sitting pose, her avatar floats above a chair, and she has no means of adjusting the height so that she appears to be sitting in the chair
However, as a solution, it has a number of limitations (your shape has to be modifiable, it won’t work in cases where you are trying to adjust your avatar’s default sitting / kneeling pose height to prevent floating, as the hover option requires the avatar to stand in the default shape edit pose, etc).
In order to try to revisit the problem and possibly gain a more thorough solution, Zi Ree from the Firestorm team has written a proposal document entitled Height offset Proposal.
This clearly explains the issues in not having a more flexible approach to adjusting height offset, and also offers a couple of suggestions on what might be done to improve things. This was presented to the Lab at the TPV Developer meeting, together with a concise demonstration by Jessica Lyon of some of the issues.
Obviously the Lab hasn’t at this point committed itself to tackling the matter, but those from the Lab at the meeting were appreciative that the proposal has been written and the issues / possible approaches clearly laid out. There has been an agreement to look into further, and there might be some feedback at the next TPV Developer meeting (scheduled for July 18).
Cocoa Issues
[0:48:20] The Lab continues to work on the Cocoa issues affecting Mac users and there is some good news from them and Firestorm:
The Lab has a fix for the ALT-cam bug, which is expected to be in the next Maintenance RC viewer
Firestorm has a fix for the issue of severe typing lag when in a location with several other avatars (see: FIRE-12172). If successful, this is likely to be contributed to the Lab, and once in a Firestorm release, may see version 4.4.2 of that viewer blocked.
Update Wednesday July 9th: Dolphin Linden also attended the Simulator User Group meeting on Tuesday July 8th, where he further discussed the Experience Keys (Tools) project. As that discussion covered some of the information given here, I have provided a further update on the additional information provided by Dolphin at that meeting, to serve as a companion piece to this report. Please do ensure you read that article as a follow-up to this one.
During the TPV Developer Meeting on Friday JUne 20th, Linden Lab gave advanced notice to third-party viewer developers that the long-awaited Experience Tools project will be entering a beta phase in the near future – possibly within the next month.
Dolphin Linden is one of the people working on the Experience Tools / Keys
The notice came via Troy and Dolphin Linden, two of the key players from the Lab working on the project, who between them gave an overview of what it is and how it should work, and answered questions from TPV developers.
There has been considerable interest in this project at Simulator User Group and Server Beta User Group meetings over the last several months, particularly as mention of the tools has been made in various RC deployment release notes, and the fact that they are currently on the Magnum RC. However, until the June 20th meeting, the Lab has remained tight-lipped on the matter.
The notes which follow were taken from an audio recording I made of the meeting, and the salient extracts from that audio are included at the end of this article (see also North’s video recording of the meeting). I’ll have a summary of the TPV Dev meeting itself available soon.
What Are Experience Keys?
Experience Tools is essentially a new means of providing a set of “blanket” permissions against a range of actions which might be taken on an avatar participating in a defined activity (e.g. allowing the avatar to be animated, teleported, have items attached, etc., in accordance with the requirements of the activity). The idea is that rather than having to constantly give permission for objects, etc., to act on your avatar while participating in an immersive activity, you give a single OK at the start of your participation, and then no longer be distracted by additional dialogue requests. The permissions within the Experience Tools comprise:
PERMISSION_TAKE_CONTROLS
PERMISSION_TRIGGER_ANIMATION
PERMISSION_ATTACH
PERMISSION_TRACK_CAMERA
PERMISSION_CONTROL_CAMERA
PERMISSION_TELEPORT
Note that permissions such as DEBIT (i.e. take money from your L$ account) are explicitly excludedfrom the Experience Tools, and must still go the normal route of requesting permission from the user.
What is an “Experience”?
An “experience” in this context can be almost any immersive / interactive environment within SL where the user needs to provide permissions for objects, etc., to interact with their avatar. A list of examples of experiences might include:
A game or puzzle or hunt or quest which requires the use of a HUD and / or which requires certain items are attached to an avatar
An amusement park where every ride requires the user gives explicit permissions to every ride they take
A tour of an art or historical installation which utilises multiple teleports and / or the use of HUDs.
As noted above, within an experience, the user only needs to give permission to scripts and objects to interact with their avatar once, when they agree to participate in the experience.
Linden Realms, launched back in late 2011, was something of a precursor to Experience Tools, inasmuch as by entering a Linden Realm game area, players gave implicit permission for certain actions to be carried out on their avatars – HUD attachment, teleporting – without the need to explicitly allow each activity within the game. The difference between it and Experience Tools, is that with the latter, users must still explicitly give that initial permission for objects, etc., within the experience to interact with their avatar.
Linden Realms, launched in 2011, was something of a precursor of what has evolved into Experience Tools / Keys
During the initial deployment, experiences using the Experience Tools will be restricted to running at the region / estate level for private islands / estates and parcel level for mainland. They will require white listing by the land owner in order to run. However, it is possible that the capabilities will be extended in the future to allow grid-wide experiences to be created (e.g. a grid-wide hunt involving multiple regions / mainland parcels). When / if implemented, this will mean:
Private estates / regions with access restrictions will have an additional level of access which will allow anyone participating in a grid-wide experience running on that estate / region to access it. However, should they revoke the experience permissions while on such an estate / region, they will be teleported away in accordance with the estate’s / region’s access controls
If a user opts not to take part in a grid-wide experience at one location, their refusal to do so applies to all locations running the same experience (so they do not have to keep refusing to participate when travelling around the grid).
See How it Will Work, below, for further information on allowing / refusing experiences and revoking permissions.
On June 16th, Marine Kelley recently updated her Restrained Love viewer to version 2.9. It introduces a new series of camera control options, offering a range of potential opportunities for those wishing to create puzzles, mazes, immersive quests, etc., as well as being applicable to the general use of RLV!
Marine provides the details on the updates, but here in brief is a summary of the key additions, together with an image I’ve borrowed from her blog:
@camdistmin and @camdistmax force the camera to stay within a range (0= Mouselook any value above 0 actively prevents Mouselook being engaged)
@camdrawmin and @camdrawmax simulate fog / blindfolds by obscuring the world around the avatar (not around the camera, as with the windlight settings)
@camdrawalphamin and @camdrawalphamax indicate the closest and farthest opacities of fog defined by @camdrawmin and @camdrawmax
@camdrawcolor sets the color of the fog defined by the above (black is the default)
@camunlock prevents the camera from being panned, orbited, etc. away from the avatar – so can prevent someone from peer through walls, etc.
@camavdist specifies the maximum distance beyond which avatars look like shadows (think ssing people in a mist or heavy fog)
@camtextures renders the world grey, other than avatars and Linden water. Marine notes that bump mapping and shininess remain untouched, as even someone blindfolded or in heavy fog can still feel their way around
@shownametags hides the radar, name tags, and prevents doing things to an avatar through the context – useful for games involving trying to find someone without them being betrayed by their name tag.
There are three additional camera presets added as well (left, right, top), to allow some additional camera options when @camunlock is active. There is also a new debug setting, RestrainedLoveCamDistNbGradients, to go with the camera options, as well.
RLV 2.9 adds some interesting scripted controls for the camera which could have a range of uses, such as locking the camera to the avatar and controlling how far the user can see (image: Marine Kelley)
Again, please refer to the RLV 2.9 release notes for full details of these, and the other updates with this release.
The new camera options, as noted, could have a range of potential uses, and demonstrate (once again) that RLV isn’t just about “teh bondages” – it’s an extremely flexible extension to her viewer (note that they are only applicable to her RLV viewer at this time). Those wishing to find out more about it and who may not have taken a look at it previously, can find more information both on Marine’s blog and on the RLV API wiki page.
Inara Pey: Living in a Modemworld 