Firestorm meeting and Q&A, October 12th: video and transcript

firestorm-logoOn Saturday October 12th 2013, the Firestorm team hosted another informal question-and-answer session. While the meeting was recorded, the Firestorm team are aware that many of their users have hearing difficulties, and / or prefer to read text. It is because of this that this transcript has been provided. When reading it, please remember:

  • This is not a word-for-word transcript of the entire meeting. While all quotes given are as they are spoken in the video, to assist in readability and maintain the flow of conversation, not all asides, jokes, interruptions, etc., have been included in the text presented here
  • If there are any sizeable gaps in comments from a speaker which resulted from asides, questions to other etc,, these are indicated by the use of “…”
  • Timestamps are provided as guidance should anyone wish to hear the comments in full from any speaker on the video
  • Questions were asked in chat while speakers were talking. This inevitably meant that replies to questions would lag well behind when they were originally asked. Therefore, to provide context between questions and answers, questions in the transcript are time stamped at the point at which each is addressed by a member of the Firestorm team, either in voice or via chat.

Please note: This transcript is provided for informational purposes only. As such, questions on technical issues relating to Firestorm and  / or project-specific questions cannot be answered here unless one of the Firestorm team drops by.

The TL;DR Summary

The numbers in braces are timestamps which refer to the section of this transcript where more details can be read, and to the section of the video recording where the relevant comments can be heard.

  • Current status for Firestorm, and potential time frames for the next release: end of October – unlikely; early December – possibly; early 2014 – if early December is missed, due to no change windows) [0:00:44-0:02:33]
  • Status with regards to LL’s viewer projects:
    • SSA updates (AISv3) – unlikely to make it into the next release and why [0:02:33-0:03:42]
    • SLShare (sharing with Facebook accounts) – possibly in next release, but low priority [0:03:42-0:04:22]
    • Group ban list – what it is and hopefully in the next release [0:04:22-0:06:30]
    • Interest list updates – unlikely to be in the next release and why [0:06:30-0:08:08]
    • Chat history capabilities from CHUI [0:18:50]
  • The hoped-for refactoring of the Preferences floater will not be in the next release [1:02:09]
  • What will be in the next release:
    • Materials, support for new particle capabilities, export features [0:08:08]
    •  Firestorm will include export capabilities, the majority of which have been in development in-house for a while, but which will include Singularity’s .DAE export capability. All export options will respect the SL permission system, so you will only be able to export things which are wholly your creation [0:09:57-0:16:14]
    • Linden Lab have introduced new particle capabilities, including a ribbon particle capability and a new means of dealing with particle griefing by right-clicking on particles to mute their source. These abilities will be in the next release of Firestorm [0:16:42-0:17:39]
  •  Firestorm may be getting a means for IM encryption in the future which will be more secure than OTR. This has arisen out of Firestorm being used as the default viewer for MOSES, the US Army’s Military Open Simulator Enterprise Strategy [0:23:50-0:28:50]
  • Firestorm is unlikely to gain 64-bit builds in the near future. So far, few advantages have been shown to exist with 64-bit builds compared to 32-bit builds utilising LAA, and 64-bit builds could present added complexity in trying to manage the project [0:33:28-0:41:39]
  • Firestorm and TPVs are experiencing much improved co-operation with the Lab, although striking a balance between openness and managing complex projects is hard to achieve and this leads to compromises [0:48:16-0:58:21]
  • The remainder of the meeting was more in the way of an open Q&A session covering a range of topics, and the transcript should be referred to for further details.

With thanks to North for the video.

Continue reading “Firestorm meeting and Q&A, October 12th: video and transcript”

Cocoa updates impact OS X 10.6 users

Update October 5th: The downgrade to viewer 3.6.4.280048 for those on OS X 10.6 has been made optional rather than mandatory, as the latest de facto release viewer (3.6.7.281793) contains fixes which address some of the issues users on OS X 10.6 were encountering. Those still encountering issues may wish to revert back to 3,6,4,280048.

Recent Cocoa updates to the Mac version of the viewer have led to problems for those running Mac OS X 10.6. Because of this, the Lab has opted to roll users on that version of the operating system back to an earlier release of the viewer – specifically version 3.6.4.280048 (August 20).

Commenting on the problems at the Open-source Dev meeting on Monday September 30th, Oz Linden said:

We found some obnoxious problems with the newer releases for users still on OSX 10.6. We’re working on getting them fixed … but in the mean time we decided that 10.6 users would be better off on the older version. We’ll be watching how many users it would affect, I’m sure.  Newer versions of OSX have significantly better crash rates, so if a user can upgrade, they definitely should.

Affected users should be automatically “rolled back” (so to speak) to this viewer release via the viewer update system. However, if you’re running OS X 10.6, experiencing issues and are running a later version of the viewer, you can manually download it here.

Lette Ponnier: “The three hours that can change your SL”

Letter Ponnier, one of the core support staff on the Firestorm viewer, runs her own blog, which often focuses on Second Life, the user’s experience and more. Obviously, as a member of the Firestorm team, many of her posts are Firestorm-centric – but this doesn’t make them any less a worthwhile read. When it comes to understanding SL and the viewer in general, Letter has much to say that is very much worth taking the time to read.

In a recent post, she covered The Three Hours That Can Change Your Second Life. As many know, the Firestorm team run regular classes throughout the week focusing on many aspects of Firestorm and getting to grips with it. In her blog post, Lette points to four lessons the team run, three of which could lead to anyone, regardless of their viewer preference, to enjoy their SL experience a lot more and gain a deeper understanding of the intricacies of the viewer and Second Life.

These classes are:

  • Preferences 2 – covering the Graphics and Network & cache tabs – which is definitely of use to anyone using SL, regardless of viewer
  • Lag – a mini-class which explains the major types of lag and dispels many of the myths surrounding lag – once again useful for anyone who has ever felt their SL is suffering as a result of “lag”
  • Basic Troubleshooting – which may be useful to anyone who experiences issues and problem, again regardless of their viewer
  • Reporting Bugs, Requesting Features – which is more Firestorm-centric, but can still be useful for those using any viewer which has a JIRA-based bug reporting system.

Details on when these lessons are held can be found on the Firestorm wiki.

As well as the blog post, which provides an overview of each of the classes, Lette has provided an audio recording for those who can multi-task and wish to listen while doing over things. You can find the recording at Vocaroo.

If you are at all interested in making your SL experience more enjoyable and / or in getting to grips with your viewer, I recommend three things – take a read of Lette’s post or listen to the audio, read Lette’s blog (you’ll also find a link in my blogroll, right), and try popping along to the Firestorm lessons.

Related Links

With thanks to Lette Ponnier.

Firestorm meeting 14th September, 2013 – video and transcript

firestorm-logoOn Saturday 14th September 2013, the Firestorm team hosted another informal question-and-answer session. While the meeting was recorded, the Firestorm team are aware that many of their users have hearing difficulties, and / or prefer to read text. It is because of this that this transcript has been provided. When reading it, please remember:

  • This is not a word-for-word transcript of the entire meeting. While all quotes given are as they are spoken in the video, to assist in readability and maintain the flow of conversation, not all asides, jokes, interruptions, etc., have been included in the text presented here
  • If there are any sizeable gaps in comments from a speaker which resulted from asides, questions to other etc,, these are indicated by the use of “…”
  • Timestamps are provided as guidance should anyone wish to hear the comments in full from any speaker on the video
  • Questions were asked in chat while speakers were talking. This inevitably meant that replies to questions would lag well behind when they were originally asked. Therefore, to provide context between questions and answers, questions in the transcript are time stamped at the point at which each is addressed by a member of the Firestorm team
  • Some questions were asked and answered purely in text. These have been excluded for one of two reasons. Either a) they lacked context with the voice conversation, or b) the seating arrangements in the auditorium meant there were some questions or answers which didn’t appear in my local chat window.

Please note: This transcript is provided for informational purposes only. As such, questions on technical issues relating to Firestorm and  / or project-specific questions cannot be answered here unless one of the Firestorm team drops by.

Video courtesy of Northspring

Continue reading “Firestorm meeting 14th September, 2013 – video and transcript”

Facebook support coming to the SL viewer

Eagle-eyed (or given his avatar, should that be owl-eyed? :)) Daniel Voyager spotted a pointer that a degree of Facebook support is coming to the SL viewer for those who already have a Facebook account.

The new capability is called Second Life Share, which is being aimed at the viewer 3.6.6  code base (although it isn#t a part of the latest Materials RC viewer, 3.6.6.280797 released on September 11th).

When it does appear, the capability will be opt-in, an important point to remember. Nothing happens vis-a-vis the viewer and Facebook unless you want it to happen (and you have a Facebook account). It will apparently consist of a new viewer floater, itself comprising a number of tabs:

  • Account Tab: will allow those with a Facebook account to connect their SL account to it for the purposes of posting from SL to Facebook
  • Check-in tab: will allow someone to share the SLurl for their current in-world location via Facebook, together with a short comment on the location and a map image if they wish
  • Status tab:  will allow someone to share a text comment with friends via Facebook
  • Photo tab: will allow someone to upload a snapshot to their FB account. As with the current Profile Feed option in the snapshot floater, the resolution of the image can be selected at upload (minimum 800×600), and an optional SLurl / comment can be included with the image.

Details on the capabilities are outlined in Viewerhelp on the wiki, which also references a new Knowledge Base entry, Second Life Share. Unfortunately, clicking the link generates a 404 error, and a search of the Knowledge Base at the time of writing did not yield and further relevant results. I’ve included the link here in anticipation of the issue being fixed by LL.

Whether the title of the new functionality is “Second Life Share” is indicative that it may be extended to include other social media options remains to be seen. It will also be interesting to see what it might mean for the future of the snapshot floater – if anything at all – if this is the case.

I’ll follow-up on this post once the new functionality is visible.

SL viewer gets “request teleport” feature and group eject confirmation

A new SL project viewer was released on September 3rd. The Snowstorm Project viewer 3.6.5.280476, brings with it a number of issue fixes, and includes two capabilities new to the viewer:

  • A “request teleport” feature (STORM-1838) contributed by Jonathan Yap, which allows users to request a teleport form another user (currently with caveats – see below)
  • A group eject confirmation pop-up (STORM-1952), submitted by Cinder Roxley, which some may be familiar with from using TPVs such as Firestorm.

Request Teleport

The new request teleport capability, which I first reported on back in week 4, requires both viewers to be using the code for it to work (so for the time being it is limited to the project viewer). Where this is the case:

  • Select the person to whom you wish to teleport (from your Friends list or Nearby list, etc.), and select Request Teleport
  • Enter a message in the pop-up, if required, and click OK.
Select the person to whom you wish to teleport (from your Friends list or Nearby list, etc.), and select Request Teleport. Enter a message in the pop-up, if required, and click
Request teleport: making a request

At the “other end” the recipient of the request will receive the request as an initial pop-up notification and within CHUI:

Receiving a teleport request - pop-up and CHUI message
Receiving a teleport request – pop-up and CHUI message

The recipient can than either accept the request, sending a teleport offer, or reject it, in which case no message is sent.

The teleport offer is again displayed in the requester’s viewer as both as an initial pop-up notification (below) and within CHUI.

Receiving the teleport offer
Receiving the teleport offer

Note again, that the system will only work where both viewers are running the new code (e.g. the Snowstorm project viewer for the time being). If someone on a viewer with the capability to someone using a viewer which does not have the teleport request code, the request will not be received / displayed.

Group Eject Confirmation

The group eject confirmation sees the official viewer get a new pop-up asking for confirmation when ejecting someone from a group, in order to help with issues where the wrong name is selected and ejected.

The new gtoup eject confirmation pop-up for the official viewer
The new group eject confirmation pop-up for the official viewer

Again, as noted above, the release notes for the viewer provide a full list of updates in the viewer.