Firestorm: counting down to the next release

firestorm-logoThe Firestorm team are working towards  their next major release. This has been in the works for a while now, and will represent a significant step forward for the viewer, as it will bring it up to parity with  the Lab 3.7.26, and also includes a number of cherry-picked fixes and updates from the more recent maintenance fixes, etc..

This means the viewer will include updates such as the revised snapshot floater, as originally re-designed by Niran V Dean as a contribution to Linden Lab, together with additional effects filters; the new Avatar Hover Height capability, the latest updates for HTTP pipelining and fastpipe changes, plus the recent AIS v3 changes, and much, much more, including numerous updates and improvements made by the Firestorm team and  from other TPVs.

Preview Testers Wanted

Beta versions of the release have been undergoing assorted tests for the last several weeks. However, prior to it reaching a formal release status, the team want to expose it to more extensive testing among users. To this end, a call has been put out through the Firestorm blog requesting more people to consider joining their Preview group.

Things you can expect in Firestorm 4.7.0: the revised snapshot floater (as developed by Niran V Dean), complete with an expanded set of default filter effects
Things you can expect in Firestorm 4.7.0: the revised snapshot floater (as developed by Niran V Dean), complete with an expanded set of default filter effects

If you are a Firestorm user and have a good working knowledge of the viewer, do please read the blog post and consider joining the Preview group. However, do keep in mind the following guidelines:

  • You will be required to give feedback on any Preview release you receive. This includes being prepared to report them through the Preview group and raise bug reports on the Firestorm JIRA – if you’ve never filed a bug report before, you can find guidelines on the Firestorm wiki. There is also a Reporting Bugs class which may also help
  • Please, do not join the group simply to get your hands on shiny new versions of the viewer – not only will this defeat the object of trying to test the viewer and uncover any issues possibly missed during QA and beta testing, you could find yourself running a viewer than has bugs, etc., and for which you cannot get assistance through the normal Firestorm support channels
  • Please do not share any links you are given to Preview versions of the viewer to people outside of the Preview group. Again, this defeats the object of controlled testing, and it runs the risk that if there is a significant issue with the viewer, then it means limiting the impact of the issue is that much harder (if not impossible).
Things you can expect in Firestorm 4.7.0: Avatar Hover Height
Things you can expect in Firestorm 4.7.0: Avatar Hover Height

The Current Release Plan

As it stands, Firestorm hope to ramp-up to a formal release over the next few weeks as follows:

  • A further release to the Beta test group ready for the week commencing Monday, April 13th
  • If no significant issues with this release are found by the Beta testers, it will be released to the Preview group for wider testing
  • A further release is then likely to be made to the Beta and Preview groups for final testing and assessment.

Assuming nothing major is found to be a problem with the second preview release, a formal release of the viewer will then be made – potentially around three weeks (ish) from the date of this article.

Things you can expect in Firestorm 4.7.0: the Preferences floater has been completely overhauled and sub-tabs / options rationalised for easier use
Things you can expect in Firestorm 4.7.0: the Preferences floater has been completely overhauled and sub-tabs / options rationalised for easier use

It is possible that when it is made, the formal release will be classified as a “Public Beta”, rather than a “full” release. Part of the reason for this is that there are a number of further updates coming out of the Lab – such as the new Viewer-Managed Marketplace (VMM) functionality, once it has cleared its beta testing – and the Firestorm team will want to incorporate these updates as soon as they can into a follow-up release, allowing for the Lab’s own release schedule.

However, whether a “Public Beta” or a “full” release, I’ll of course be providing an overview / review of the viewer once it is available to everyone.

Could the Lab use Amazon AppStream to “replace” SL Go?

Sl Go proved itself very popular among SL users running low-end hardware
SL Go proved itself very popular among SL users running low-end hardware

On Thursday, April 2nd, it was announced that SL Go, the streaming service for accessing SL  provided by OnLive, is to shut-down on April 30th alongside OnLive’s other consumer services. The reason for this is because OnLive has sold the IP and patents associated with the services to Sony Computer Entertainment.

Since the news broke, there have been numerous calls made for Sony to maintain SL Go as a service, including  an on-line petition. However, as painful as it is, all such calls and petitions to  Sony are unlikely to succeed, as I explained in a recent blog post.

In that article, I also considered whether or not the Lab might invest time and effort in offering something that might fill the void. At the time, I thought the answer to this would most likely be “no”, as the Lab seem to have enough on its plate already with Second Life and its next generation platform.

But the more I think about it, the more I feel that the Lab should endeavour to offer some kind of “SL Go replacement”.

One potential means by which they might do so could be via Amazon AppStream.

Obviously, there are issues involved in providing such a service beyond the physical provisioning. Anything which requires some form of external hosting is going to incur costs, for example. However, the flip side to this is it’s fair to say the SL Go has demonstrated that if users believe they are getting a beneficial service, they are willing to pay for it, providing the price is not prohibitively high.

Certainly, there are a wide range of potential benefits to be had from such an endeavour, particularly if implemented through something like Amazon AppStream:

  • It offers an easily scaled means by which the Lab could provide an “SL streaming service” to users on low-end hardware and those on mobile devices – something long demanded by SL users
  • It could provide the means by which SL could be accessed through web browsers – again, a long-desired means of attracting new users to the platform who might otherwise be put off by having to download and install the viewer
  • It obviously means that those SL users on low-end systems can enjoy the full graphical richness of SL in the manner LL would like to see all users experience it
  • It could help those preferring to run older operating systems – such as Windows XP – to continue accessing SL even after they might otherwise be unable to even install the viewer
  • It might even help the Lab map and test options which might be beneficial for their nascent next generation platform.

While developing such a service might not necessarily be easy, the Lab isn’t entirely without any experience in this area. As I and many others have pointed out, in 2010 they did experimenting with streaming the viewer, using the Japanese company Gaikai (coincidentally purchased by Sony Computer Entertainment in 2012), which delivered the viewer to web browsers, as shown in the video below. If there is anything remaining of this work at the Lab, it might possible to put it to work through something like Amazon AppStream.

That said, there is a lot for the Lab to consider in attempting to fill the forthcoming void that will be left by SL Go. And while I would not be at all surprised to learn they are already doing so, they might still require some encouragement to take things beyond just considering options. Something which might encourage them, or at least demonstrate to them that there really could be a worthwhile demand for such a service, could be for users to politely speak up.

One way to do this might be to add your name to the existing petition – I would hope someone at the Lab is keeping an eye on it.

Another could well be to leave a positive and polite comment on the subject following this article, as (and all ego aside) I do know eyes at the Lab pass over this blog (just as they do many others).

There is no guarantee that Lab will move to provide some kind of “SL Go replacement”, but on the other hand, as someone once said, nothing ventured, nothing gained.

2015 viewer release summaries: week 14

Updates for the week ending: Sunday, April 5th, 2015

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 updated to version 3.7.26.299635 on March 24th (formerly the Avatar Hover Height viewer) download page, release notes, wiki page, AHH overview
  • Release channel cohorts (See my notes on manually installing RC viewer versions if you wish to install any release candidate(s) yourself):
    • HeatWave RC viewer version 3.7.27.300424, released on April 3rd – core updates: the same fixes and improvements as the Maintenance release, with an additional fix for a URI parsing issue (download and release notes)
    • Maintenance RC viewer updated to version .7.27.300323 on March 31 – core updates: multiple fixes and improvements (download and release notes)
    • Tools Update project viewer version 3.7.27.300242 updated on March 30th – core updates: builds Windows and Mac viewers using the new tool chain and autobuild process and also incorporates the revised viewer log-in screen (download and release notes)
  • Project viewers:
    • Attachment fixes project viewer (Project BigBird), version 3.7.27.300377, released on April 1 – core updates: a number of fixes for various attachment issues (download and release notes)
    • Avatar Layer limits project viewer updated to version 3.7.27.300098 – allows users towear up to 60 wearable layers (jackets, shirts, tattoo, alpha, etc.) in any combination  (download and release notes)

LL Viewer Resources

Third-party Viewers

V3-style

V1-style

  • Cool VL Viewer Stable branch updated to version 1.26.12.37, Experimental to version 1.26.13.6 and Legacy branch to 1.26.8.92, all on April 4th (release notes)

Mobile / Other Clients

  • No updates.

Additional TPV Resources

Related Links

Why SL Go won’t continue, and OnLive opted to sell

Farewell SL Go; one of OnLive's most successful services, but nevertheless one unlikely to be saved
Farewell SL Go; one of OnLive’s most successful services, but nevertheless one unlikely to be saved

Since the announcement that OnLive’s gaming services are to shut down at the end of April, there has been understandable upset from within the SL community (and from some OpenSim users as well, given Firestorm on SL Go can be used to access OpenSim grids).

Following the news, there were a plethora of requests made to Sony on social media that they continue to provision SL Go as a service and an on-line petition was started in the hope of achieving the same end. Unfortunately, these requests and the petition overlook one thing.

As OnLive made clear in their statements on the future of their gaming services, and as I attempted to point to in my original article on this news, Sony didn’t actually acquire OnLive’s services. They took the opportunity to purchase the IP and 140 patents the company held relating to cloud gaming and other “assets” (which would most likely appear to be the additional 135 patents related to cloud gaming  OnLive had pending), without actually buying OnLive’s services. So technically, there’s nothing for them to “continue” to offer SL Go users.

What’s more, as Dennis Harper, the SL Go Product Manager at OnLive, made clear in these pages, taking the IP and patents is akin to taking the heart and lungs of OnLive’s services; without them, a service like SL Go cannot easily be continued by someone else. At least, not without money changing hands and someone having the infrastructure by which they can deliver the service.

So, are Sony the Big Evil for doing this? did they gobble OnLive’s patents to stifle competition? Is this, as was dramatically stated in some quarters as the news broke, some kind of first shot in a forthcoming “VR battle” between corporations? Well …. No.

From the start, OnLive was well ahead of the curve, and even though we're reaching a point were the viability of cloud-based gaming can be demonstrated, it seems few are yet willing to take a gamble on taking-on the kind of services OnLive have offered
From the start, OnLive was well ahead of the curve, and even though we’re reaching a point were the viability of cloud-based gaming can be demonstrated, it seems few are yet willing to take a gamble on taking-on the kind of services OnLive have offered (image courtesy of OnLive)

The truth is that OnLive put itself on the market.

That this is the case can be found in another post on the company’s blog entitled, A Bright Future for Cloud Gaming At Sony. As well as containing useful historical information, the post underlines the specific issues the company’s management had been forced to face:

Since 2012, the company has dramatically improved its technology and business models such that all of its 5 services are gross margin positive, ranging from 43% to 86% margin … The company also was able to achieve conversion rates from free trial to paid of between 64-78% for its services. Despite these positive metrics, the lifetime value (TLV) of a subscriber was still less than the cost to acquire subscribers (CPA), but they were converging. While we knew we could not get to break-even on our own, we believed that there were many large companies who would be able to get there.

In other words, in order to get to a break-even point,  OnLive’s management felt the company needed to be offered-up for acquisition, albeit hopefully as a going concern.

Perhaps the first fully public hint that this was the case may have actually come in a blog post issued a couple of days ahead of Sony deal being announced. Of course, by the time the post appeared, the deal was undoubtedly cut and dried; nevertheless, The 2015 Case for Cloud Gaming and OnLive, could almost read as the company laying out its stall in order to attract a suitable investor / acquirer.

Despite the fact the Nvidia suggested OnLive themselves were helping to lift cloud gaming out of the Trough of Disillusionment towards its Plateau of Productivity, no-one was interested in acquiring the company as an operational concern when OnLive decided to seek outside assistance (image: Nvidia via OnLive)
Despite the fact the Nvidia suggested OnLive themselves were helping to lift cloud gaming out of the Trough of Disillusionment towards its Plateau of Productivity, no-one was interested in acquiring the company as an operational concern when OnLive decided to seek outside assistance (image: Nvidia via OnLive)

Unfortunately, despite all the positive indicators they could show, the Cloud Gaming hype cycle had bitten hard; no-one OnLive approached was willing to take them on as a going concern. Not even the fact that Nvidia had indicated the worst was behind the sector, and that OnLive itself was helping to push the technology up the Slope of Enlightenment, could encourage anyone to acquire the company outright. Thus the deal with Sony for the IP and patents sale was agreed.

Why didn’t Sony acquire OnLive as a whole? Because they already have their own cloud gaming service, PlayStation Now, which came out of a 12-month beta programme in January 2015. The OnLive patents understandably offer more value when put to work within PlayStation Now than Sony would be liable to find in buying-out OnLive as a whole, so they didn’t bother.

Interestingly, and entirely coincidentally, PlayStation Now has its own link to Second Life. It is built on the back of Gaikai, a Japanese streaming game provider acquired by Sony in 2012. Gaikai is the company Linden Lab worked with in an attempt to provide the means of streaming Second Life to web browser, a service which underwent a limited beta run in 2010, as the video below demonstrates.

But to draw things to a close; however “unjust” it might appear, all of this means that SL Go cannot really be saved. The patents which enabled it to function are gone, and the services upon which it runs are closing down. The only real options are for someone else to come along and offer a similar service of their own, or for LL to work with a partner to provide such as services, as they once attempted with Gaikai.

Both would seem unlikely; in the case of the former, SL perhaps represents too small a community of users to be worth catering for (and remember, SL Go came about in part as a result of rather unique circumstances). And while I tend to lean towards LL having an interest in cloud-based streaming, I don’t think that interest is with regards to Second Life, so I can’t see them getting directly involved in trying to provide a streaming solution for SL access. If nothing else, they’ve likely got enough on their plate already.

SL Go was a great and brave experiment. It is a shame that its days are drawing to a close; but OnLive, through their services as a whole, have proven what might be achieved. In that respect, they are right when they proclaim that cloud gaming has a bright future.

SL Go discontinued as OnLive sells patents

Even ideas around offering Sl Go as a Premium offering, while simple in concept, are potentially less-than-simple to implementUpdate, Friday, April 3rd: An on-line petition has been started to try to persuade Sony to keep SL Go running as a service.  In all honesty, the likelihood of this succeeding is less than slim, but if you would like to add your name to the petition, it can be found here.

On Thursday, April 2nd, it was announced that the SL Go streaming service supplied by OnLive has been discontinued.

The move is part of a wider shut-down of services that will take place on Thursday, April 30th, following a decision by the company to sell its portfolio of patents to Sony Computer Entertainment America.

An official announcement on OnLive’s SL Go website reads in full:

It is with great sadness we must announce that OnLive’s SL Go service will be coming to an end. Sony is acquiring important parts of OnLive, and their plans don’t include a continuation of the SL Go service. However, your service should continue uninterrupted until April 30, 2015. No further subscription fees will be charged, and you can continue to enjoy SL Go on all of your devices until that date.
In our year of SL Go service, we have become quite close to the Second Life® community. Thanks to your patronage and constructive feedback, SL Go became one of OnLive’s most successful services. We know how important SL Go is for many of you, and it saddens us to bring the service to a close. We extend our heartfelt gratitude to you for being a part of “SL Go by OnLive” and wish you all the best.
With warmest regards,
Everyone at OnLive
SL Go provided a means to access Second Life through Android devices, followed by the iPad - something SL users had been hoping to see for years
SL Go provided a means to access Second Life through Android devices, followed by the iPad – something SL users had been hoping to see for years

In a personal address sent out to those with whom he’s been in contact with over the course of the last year or more, OnLive’s Product Manager for SL Go Dennis Harper – someone whom I’ve come to regard as a friend both in-world and through our communications outside of the platform – said:

To my good friends and partners in Second Life,
 It breaks my heart to tell you that OnLive (OL2, Inc) has been acquired and will be closing down the game service, including SL Go.  The official press release is attached.
 SL Go Island will continue to exist for a while, but we have removed the Pay with L$ feature.
 The OnLive and SL Go services will continue to operate in full capacity until April 30.  All services will be free to anyone who has or creates an account.  All prices for the service have been set to $0.00, including SL Go.
 On a personal note; you all have been so supportive of SL Go.  You have my heartfelt thanks for all you have done.  I have made some good friends in SL and it greatly saddens me that this project is ending.  You all have accepted us n00bs into your community and mentored us on what Second Life really is.  I have learned so much!  My sincere thanks to all of you.

This is and unfortunate end, not just for SL Go, but also for everyone at OnLive, a company which had come through a lot to provide a unique on-line gaming service and which has tried to enter a very unique environment with SL Go, and has done so by providing a very successful approach to providing access to Second Life (and OpenSim) to people while on the move through their delivery to Android and iPad devices, and to those using older, lower-specification hardware.

SL Go has also allowed users to enjoy the full richness of Second Life on relatively low-end machines. Following a recent severe hardware failure on my primary PC, SL Go became my primary means of accessing SL for some 2 weeks while the "main" machine was repaired; above, I'm running it on a humble 2 GB win 7/32 Asus PC EE 1201N
SL Go has also allowed users to enjoy the full richness of Second Life on relatively low-end machines. Following a recent severe hardware failure on my primary PC, SL Go became my primary means of accessing SL for some 2 weeks while the “main” machine was repaired; above, I’m running it on a humble 2 GB win 7/32 Asus PC EE 1201N

I’ve been fortunate enough to be somewhat closely involved in SL Go, initially being offered the opportunity to help beta the product, and then in helping to report on and promote the service, and (hopefully) provide OnLive, through Dennis and his team with useful feedback, support and advice.

As such, I’d like to take this opportunity to offer Dennis, Jeff, Shae, Jersey, Robby and everyone else at OnLive involved in SL Go – including Jane Anderson in the US and Mark Bevan here in the UK,  my thanks and my heartfelt best wishes for the future. I do, however hope that we’ll continue to able to see one another in-world, at the very least.

In writing about the situation, in Ars Technica (linked to at the top of this article and in the links section below),  Kyle Orland notes:

Looking back, it seems OnLive was just a little bit too far ahead of the curve, both in terms of market readiness and the Internet infrastructure necessary for streaming games. As low-latency bandwidth continues to become cheaper and more accessible around the world, it seems likely someone will nail the correct combination of business model, game selection, and easy-to-use interface to become the industry’s answer to Netflix. That company will owe a debt to OnLive for getting the ball rolling and proving that streaming gaming was something that was worth trying in the first place.

I couldn’t agree more.

Related Links

Firestorm TTT: building

firestorm-logoIn the Firestorm Tool Tip Tuesday video for Tuesday March 31st, 2015, Jessica takes a look at the assorted tools and options Firestorm provides in order to assist people with in-world building. As with some of the other TTT video, various options described within the video are not exclusive to Firestorm, which makes the video a worthwhile watch by anyone wishing to get more to grips with building, manipulating prims, and so on; although admittedly, if you’re not using Firestorm, you’ll have to poke at your preferred viewer’s Preferences, etc., to see where the options might reside.

Starting with changing the default colour of the basic rezzed prim shapes, the default size, prim status (physical, phantom, etc), and the next owner permissions (a function now common to all viewers, including LL’s own), Jessica takes a rapid-fire run through many of the the more frequently used build options and tool additions.

The build sub-tabs on Firestorm, located under Preferences > Firestorm, present access to the majority of additional options and capabilities associated with building using the viewer
The build sub-tabs on Firestorm, located under Preferences > Firestorm, present access to the majority of additional options and capabilities associated with building using the viewer

This includes a look as assorted features within the build floater itself, many of which are, again, presented through other viewers as well, including the ever-popular prim alignment option (which, sadly, remains as something the Lab have refused to adopt, as they feel it does not fulfil enough potential use cases, despite the fact it actually achieves precisely what it sets out to do).

The video concludes with a look at the Z-drop and Z-take options, which respectively allow you to drop the contents of a folder into an in-world prim without needing to select and physically drag-and-drop them, and to take a number of in-world objects and place them within a root folder in your inventory – both of which are powerful and useful options, before finally providing an overview of one of the most useful building resources within Second Life: Builder’s Brewery. You can also find out more about BB through their website.

Getting to grips with building isn’t easy, and while this video isn’t intended as a beginning guide, for those who have paddled in the shallows of building, it offers some very useful pointers. Even those with a little more experience might also find it contains some interesting little tips!