Get to grips with Firestorm’s Contact Sets with Jessica and TTT

firestorm-logoOn Tuesday, February 17th, the Firestorm team launched the latest in their Tool Tip Tuesday series, with Jessica taking a look at Contact Sets.

Contact Sets provide a way to organise your friends – and other people – into sets or categories, using your own criteria. Thus you can create sets of friends, colleagues, business contacts, and so on. They aren’t necessarily for everyone, but for those who are a member of different role-play groups or combat groups, etc., or who need to manage lists of customers or tenants, etc., and perhaps need a quick way of identifying people, they can be very useful.

By assigning a colour to a Contact Set you can, for example, make it easier to identify members of that group in your Friends list or on the mini-map, or through their name tag in-world – or even in group, IM and nearby chat. So identifying a customer or tenant in a crowd becomes very easy, helping to smooth any communications which take place, while spotting people on the mini-map is also made easier.

And if you have problems reading fancy text people sometimes use in their display names, Contact Sets lets you assign an alias to contacts who do, making it it easier for you to identify them without struggling to read their display name.

Contacts Sets allow you to organise your contacts in a wide variety of ways, making them a powerful tool when needed
Contacts Sets allow you to organise your contacts in a wide variety of ways, making them a powerful tool when needed

Contact lists can also be be shared across accounts. This means that if you use alts for a specific tasks (such as customer care) you can copy one or more Contact Sets from one account to another, making the management of your customers that much easier when using your various accounts.

However, the very power found in Contact Sets can make getting to grips with them a little bewildering – so if you’ve ever wondered what they are all about, but have fought shy of diving into them, Jessica’s introductory video should be just the ticket for you. In it she provides an uncomplicated overview of the major features in Contact Sets and demonstrates how to get started within using them.

Should you want to know more about Contact Sets after watching the video, then be sure to check the Firestorm class schedule for lessons on them, and further guidance can be found in the Firestorm wiki.

Firestorm 4.6.1 to be blocked from February 20th

firestorm-logoThe Firestorm team has formally announced the forthcoming blocking of version 4.6.1 of the popular third-party viewer. The move, which is part of Firestorm’s policy of only allowing three active  version of their viewer to access Second Life,

The plan is for this block to only affect Second Life, it should not prevent OpenSim users continuing with version 4.6.1 if they so wish. However, at the time this article was written, this was still being tested.

The Firestorm announcement on the blocking reads in full:

In keeping with our three-version rule, we will be applying a block to version 4.6.1 on Friday, February 20th. This block will only apply to logins for Second Life grid; OpenSim grid logins should still work. Versions 4.6.5, 4.6.7 and 4.6.9 will be the only officially supported versions, but we highly encourage all users to be on our latest release of 4.6.9.

Version 4.4.2 is still exempt from the rule due to Mac-specific issues. However, Linden Lab’s statistics from January 21st indicate that there are still around 8,000 people using this ancient, pre-fitted mesh version. Because of the volume of users who cannot see the world properly, it is harder and harder to justify allowing it to remain exempt. We will be blocking it as well before our next release.

If you are using version 4.6.1 please update as soon as possible to avoid problems logging in on the 20th.

Currently, it looks as though the next release for Firestorm should be around the end of March or early April; however, this is not an official date – the viewer is still being worked on. Therefore, eyes should be kept on the Firestorm blog for information on the next release.

Firestorm Tool Tip Tuesday: People panel and mini-map

firestorm-logoJessica is back with a further Firestorm Tool Tip Tuesday video, this one focusing on the People panel – notably the Nearby tab and mini-map functionality within Firestorm.

The Nearby Tab of the People panel is a quick and easy means of keeping an eye on what is going on around you, and the Firestorm team have, in response to requests for users, added a lot of additional functionality and options to it – so much so that getting to grips with it can be a trifle bewildering.

Jessica offers walk-through of a number of option and settings for the People Panel, including the display options, and how to configure it so that it displays the information you want. As the video indicates, all of what is referred to within the People panel is equally applicable to the Radar panel as well.

The Nearby tab in the People panel (shown here with the mini-map displayed as well), offers a wealth of options to users
The Nearby tab in the People panel (shown here with the mini-map displayed as well), offers a wealth of options to users

An overview of some of the mini-map options follows, noting how these can be linked to options within the People panel.

As the video demonstrates, there is a lot to cover with both panels, so much so that i places the video feels a little rushed (breathe, Jess, breathe! 😉 ), however, this doesn’t detract from the amount of information provided, and if you haven’t plumbed the depths of the People panel / radar, this video offers a great introduction. You can also find more information on the options available through both the Nearby tab on the People panel and the Radar panel by visiting the Firestorm wiki’s Radar page.

Firestorm Tool Tip: getting the most from Auto-Replace

firestorm-logoJessica Lyon was back on Tuesday, February 3rd with another Firestorm Tool Tip Tuesday video, and this one focuses on the use of the Auto-Replace function, and how it might well be more useful than people might appreciate.

As explained in the video, Auto-Replace can be found under Preferences > Chat > Text Input in Firestorm, and generally under chat in other viewer supporting the same Auto-Replace functionality. It is shipped with two lists: Spelling Corrections, which offers corrections for common spelling errors, and Abbreviations (which is the list I actually use and have customised myself).

The Auto-Replace function in Firestorm
The Auto-Replace function in Firestorm and the supplied lists

The Abbreviations list converts commonly used abbreviations such as bbl, afk, gtg, etc., into their long-hand equivalents (be back later, away from keyboard, got to go, etc.), just by typing-in the abbreviation followed by a space.

So far so good, nothing especially exciting there. But did you know, using Auto-Replace you can:

  • Create a custom greeting you can use when working as a greeter or host, or simply on meeting people?
  • Combine abbreviation entries to create statements?
  • Use abbreviations to display SLurls and URLs in chat without having to type them long-hand?
  • Export  / import your lists so you can share them with friends or easily copy them between the computers you use with SL?

If you didn’t – then this video is certainly for you, as Jessica reveals all!

Note that you can use Auto-Replace like this in any viewer that supports the same Auto-Replace functionality as found in Firestorm, including the official SL viewer.

Firestorm’s Tool Tip Tuesday

firestorm-logoFirestorm is renowned not only for being Second Life’s most popular viewer, but also for the degree of end-user support provided by the viewer team. With multiple language support groups, in-world classes, a wiki, an in-world support regions, and so on, Firestorm offer users a broad range of support options.

On Tuesday, January 27th, Firestorm added to all of this with a new feature on their You Tube channel,  entitled “Tool Tip Tuesday”.  In launching the feature, Firestorm Project Manager Jessica lyon describes it thus:

Firestorm has so many features and functions most folks don’t even know about that we decided to do a series of short videos showcasing a hidden or lesser-known feature once a week.

The first of the new videos is just over six minutes in length and provides tips on  getting more out of the camera, and short cuts which may help make using the camera easier. The tips include:

  • Use of the SHIFT and the CTRL/CMD keys with the mouse scroll wheel (if you have one!) to assist in camera movement / placement
  • Keyboard options to help with camera placement (e.g. CTRL-0, etc.)
  • Use of the main camera floaters (default and Phototools)
  • Saving and loading a sorted camera position (which may not be quite what you think it is!).

So why not take a look at the first video in the series and keep a note of Tip Tool Tuesday? Even if you don’t use Firestorm, you may be surprised by what you find.

Firestorm meeting: SL Go explored

firestorm-logoOn Sunday, December 21st, The Firestorm Team held a short-notice meeting which focused on Firestorm and SL Go. The special guest for the event was Dennis Harper, OnLive’s Product Manager for SL Go, who provided commentary on the background to SL Go and OnLive, and addressed audience questions.

Chakat Northspring was on-hand to record proceedings. As usual, the video is embedded here, and a transcript of the Q&A session is provided. However, in the interests of brevity, the first part of the meeting is provided a summary format, rather than a full transcript. Time stamps are provided for key topic areas, and for the Q&A session, for those who would like to listen to any point of interest within the video. Note that dates mentioned in the initial conversation reference 2012 and 2013, in actual fact, these should be 2013 and 2014, as reflected in the text.

A Summary of the initial Conversation

This initial conversation on SL Go, OnLive and the relationship with Firestorm lasted some 35 minutes, and is summarised here. Some questions were asked during the discussion on topics such as privacy and payment options. For ease of reference these have been moved to the Q&A section and placed with other questions on the same topic. Time stamps are provided to the relevant part of the video (below).

How Firestorm Got Involved with OnLive SL Go

  • Gary Lauder, OnLive's Lead Investor (and company chairman at the time), approached LL's former CEO, Rod Humble, about OnLive providing SL to users through their service (Image courtesy of LinkedIn)
    Gary Lauder, OnLive’s Lead Investor (and company chairman at the time), approached LL’s former CEO, Rod Humble, about OnLive providing SL to users through their service (Image courtesy of LinkedIn)

    [0: 03:57] The OnLive / Linden Lab partnership came about as a result of OnLive’s Lead Investor (and at the time, Chairman), Gary Lauder, indicating he believed SL would be a good match for OnLive and then initiating contact with Rod Humble at the Lab in May 2013 (see my article on the launch of SL Go)

  • [0:0515] Initial closed beta testing commenced in October 2013, while Dennis Harper joined in November 2013, charged with getting the product published and launched. The occurred in March 2014, using the SL viewer, offering to Mac and PC systems and Android tablets
  • [0:05:25] The initial metered pricing plan wasn’t popular with users. However, OnLive launched with it as they really didn’t know what to expect. Their service costs money to provide (servers, data centres, network, support), and SL users are a very different type of user compared to games users, spending up to 10 times longer active on the platform compared to someone playing a game. Metered payments were seen as a means of balancing use against cost
  • [0:06:48] As the reaction to metered payments was bad, OnLive revisited things and in April changed the pricing model to one of unlimited use of the service for US $9.95 (UK £6.95) a month – and the service started gaining traction, Then in October, the service launched on the iPad
  • [0:07:25] OnLive had always been aware of Firestorm and its large market share of the SL user base, and it was felt that offering Firestorm through SL Go would be a good way to bring the OnLive experience to a wider audience
  • [0: 08:24] Jessica Lyon was initially unsure of the, but was convinced when Dennis pointed-out that a large take-up of SL Go was among users on low-end computer systems, who were finding the service gave them renewed access to the platform, complete with a rich graphical experience. As many Firestorm users on such low-end systems complain that each new update of the viewer is pushing them further and further out of SL, she felt that having Firestorm on SL Go could include them once more

SL Go is a Service

[0:12:59] The launch of Firestorm on SL Go drew some negative feedback from Firestorm users (and from elsewhere). However, it is important for people to remember:

  • SL Go isn’t intended to be another viewer offering like a TPV. It is a service intended to meet very specific goals:
    • To provide people who are on older, lower-specification systems with a rich, immersive Second Life experience comparable to that enjoyed by someone using a much more capable computer
    • To provide those who wish to have the same rich, graphic SL experience as supplied by the viewer when accessing SL from their Android Tablet or iPad
  • [0: 12:25] Dennis Harper is the first to admit that the service isn’t for everyone, but for those who might have a need for it, it is available on a 7-day free trial basis, so people have nothing to lose in giving it a go.

SL Go and the Firestorm Take-up

[0:13:40] Dennis describes the take-up of SL Go following the addition of Firestorm as “scary” and being like “the hockey stick term” in the way that there was gradual take-up up until the Firestorm launch, which saw a large substantial increase in initial adoption, as Firestorm users gave SL Go a try under the 7-day free trial offer. He also notes that there is an affiliate programme available for those wishing to refer people to the service via blogs, websites, etc., and earn money via referrals to the service.

[0: 15:32] There was an initial issue with the system as a result of the way the texture cache was being handled.

  • The SL viewer uses a default 512 Mb cache, which users rarely adjust. Originally, on exiting the SL Go service, an entire user’s cache, together with their settings would be copied to a secure, encrypted store. Then, the next time the user logged-in to SL Go, the cache and their settings would be copied to the server they were assigned for their SL session, a process that didn’t take long
  • Firestorm, by default uses a 2Gb cache, and users often set it larger. This made the copy process a lot more protracted, with the result that if a Firestorm user opted to restart the viewer by logging out (which ends their SL Go session), on immediately relogging, they’d get an error
  • To avoid this, users now get a 2 Gb cache, which is automatically flushed at the end of each session, leaving only their inventory files and settings to be copied back to and from the secure store.

Continue reading “Firestorm meeting: SL Go explored”