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”

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”

Firestorm at three: party, kitties, pendants!

firestorm-logoJune 2013 saw Second Life celebrate its tenth anniversary as a publicly accessible grid. Now September marks the anniversary of SL’s (and OpenSim’s?) most popular viewer as Firestorm turns three.

Anyone who takes time out of their lives to sit down and work on a viewer, providing code and capabilities to enhance our times in-world, and the support so often needed by users, is an unsung hero of Second Life and virtual worlds. It’s no easy task, as I’m sure everyone at Firestorm and other TPVs – even at the Lab – can attest; get one thing wrong and you’re liable to get chased up the nearest tree by a group of users who, if not actively bearing pitchforks, tend to have pretty barbed tongues!

In this, it’s easy to forget that every TPV, including Firestorm, is built, maintained and managed by volunteers. They don’t get paid for their efforts; they don’t consider themselves to have any better grasp of Second Life and virtual worlds than the rest of us – they, like most people, just want to have fun and at the same time they want to make SL more fun for the rest of us. I think that sometimes, in calling for this feature or that feature in a viewer and then getting the hump when it doesn’t appear, we all lose sight of that simple fact.

Join the Party!

So it’s good when an opportunity comes around which lets us celebrate the work that goes into a viewer to take the time to say “thank you” to the folks behind the work. Firestorm users will have just such an opportunity to do so on Tuesday September 3rd, as the Firestorm team throw a Firestorm Third Birthday party at the Phoenix Firestorm support island. The kick-off time is 13:00 SLT, and there is an open invitation from the team to their users to come along and join the fun (well, region limits allowing!).

If you do want to attend, please keep in mind:

  • It is only the one region, so headcount will be limited. Sadly, with over 200,000 users, the team can’t host a party for everyone. However, people are liable to be coming and going throughout the celebrations, so if you don’t get in the first time – keep trying
  • As the party is liable to be very popular, please go along as script-light as possible; it’ll help the region, it’ll help others and it’ll help you. Detach anything you can do without when dancing / chatting – HUDs, scripted attachments, etc.

The Firestorm Kustom Kitty and a Special Pendant

firestorm-firekitty-adTo further mark Firestorm’s third birthday, Jessica and the team have joined forces with KittyCatS to develop a special, limited edition non-breedable custom Firestorm Kitty. The offer is limited to one per avatar, and the kitties are No Transfer. The kitty is fully functional & rumoured to be the cat that dined on the Phoenix. Whether this is true our not, the folks at Firestorm aren’t saying!

The collectables will be available from 09:00 SLT on September 3rd through until 09:00 SLT on September 10th, via vendors in the following locations:

zuri_s_firestorm_pendant_gift
The Firestorm pendant (see left)

Note that If demand is high, you may experience delivery problems. If a vendor faisl to deliver, please follow these instructions to initiate a re-delivery.

In addition, Zuri Rayna has produced a beautiful limited edition Firestorm 3rd anniversary pendant. This is available from the Phoenix Firestorm Support island until midnight SLT on the 3rd September  – and it is stunning!

So Happy Birthday, Firestorm, and many thanks to Jessica, Ed and the rest of the developers, testers, helpers and the support volunteers at Firestorm. Here’s to many more birthdays and celebrations!

Related Links

Firestorm meeting 10th August, 2013 – video and transcript

firestorm-logoOn Saturday 10th August, 2013, the Firestorm team hosted a question-and-answer session so they could outline the current status of the Firestorm viewer, the issues the team are facing, and outline plans for the future, as well as address questions from the audience.

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 10th August, 2013 – video and transcript”

Calling all Firestorm users: get ready for an emergency update

firestorm-logoUpdate July 2nd: version 4.4.2 has been released by the Firestorm team, and Firestorm 4.4.1 has been blocked from accessing Second Life. If you have previously installed Firestorm 4.4.1, you can install 4.4.2 without needing a clean install. If you are updating from Firestorm 4.4.0 or earlier, a clean install is strongly recommended. The downloads can be found on the Firstorm website.

Firestorm 4.4.1 was release on June 27th. However, it will shortly be superseded with Firestorm 4.4.2.

The reason for this is explained in a new Firestorm blog post, but the short version is that due to a slight mishap, some additional logging capabilities which had been enabled during the beta release of 4.4.1 and which were intended to help Linden Lab gather information for the forthcoming release of Server-side Baking / Appearance were not removed from the viewer when it moved to release status.

As a result, the system the Lab uses to gether data on viewers is now being completely overwhelmed by the amount of data Firestorm 4.4.1 is sending to it. Although it has taken a few days for the problem to be identified and the Firestorm tem notified, the result is that they are now taking some emergency corrective action:

  • With immeidate effect, version 4.4.1.34164 of Firestorm has been removed from the Firrestorm download page
  • A new version for Firestorm is being prepared for release. This version – 4.4.2 – will be no different to 4.4.1 other than the removal of the additional statistics logging code
  • When the new version is released, and to ensure the LL service is no longer inundated with excess data, Firestorm release 4.4.1.34164 will be blocked from accessing Second Life.

It is therefore essential for everyone who has updated to Firestorm 4.4.1 keep an eye on the Firestorm blog an update to Firestorm 4.4.2 when it becomes available. This should not require a clean install (as was the case with 4.4.1) – but please double-check with any associated blog post which is forthcoming when the release is made.

Again, it is essential that all users of Firestorm 4.4.1 update to Firestorm 4.4.2 as soon as it becomes available.

Related Links