Firestorm is (SL) Go – and across multiple grids!

SL go logoImportant note: The SL Go service is to be shut down on April 30th, 2015. For more information, please read this report.

On Tuesday, December 16th, 2014, OnLive, the providers of the Second Life streaming service, SL Go, announced a new addition to the SL Go service: The Firestorm Viewer.

The announcement follows several months of collaboration between the Firestorm Team, lead by Jessica Lyon, and the folk at OnLive, lead by Dennis Harper, the results of which now mean that with immediate effect, SL Go now provides a choice of TWO viewers to subscribers and users:

  • The existing SL viewer – which OnLive are referring to as “SLV” – can be used from any Mac computer, PC, and from Android devices and iPads to access Second Life
  • AND The Firestorm viewer, initially available for Mac computers and PCs, which can be used to access Second Life and OpenSim grids.

SL Go’s pricing options remain the same whichever viewer you opt to use, and you can swap between them at any time you like, should you wish. Simply make your choice from the SL Go selection screen.

SL Go users access the service via PC or Mac now have a choice of viewer: the SL Viewer (SLV, as OnLive refer to it) or Firestorm
SL Go users accessing the service via PC or Mac now have a choice of viewer: the SL Viewer (SLV, as OnLive refer to it) or Firestorm (image via OnLive)

Since its launch in March 2014, which I covered in-depth at the time, the SL Go service has proven to be very popular with people who are using low-end systems which traditionally have problems when trying to run the viewer locally. Because the viewer is streamed from OnLive’s dedicated servers,  it’s the servers that do all the heavy processing, delivering a fast, smooth service to users, thus helping to give a new lease of life to older hardware.

Of course, because SL Go is streamed, it means that – like the SL viewer offered by OnLive – certain functionality within the Firestorm offering has either been removed for security reasons (such as the Develop menu, and no access to debug settings and content cannot be uploaded), or has been disabled (such as the option to save snapshots to a hard drive – as that would effectively mean saving them to the OnLive server).

Firestorm viewer on SL Go from OnLive - click for full-size
Firestorm viewer on SL Go from OnLive (click for full-size)

The big benefit in using Firestorm through SL Go is that – with the noted exceptions due to security issues, etc., – it brings the richness of Second Life’s most popular third-party viewer to those on older systems who have perhaps felt themselves to be increasingly edged out of Second Life, something Firestorm Project Manager Jessica Lyon commented on when discussing the release with me.

“I’m really happy about this,” Jessica said. “For years folk on lower-end systems have seen significant improvements to Second Life, particularly with how the world looks, pass them by because their systems are unable to run them. We’ve even heard from many that they simply cannot use Firestorm or any other viewer and as being pushed out of SL completely.

“This release of Firestorm through OnLive, together with the existing SL viewer, hopefully gives those people a new way to enjoy Second Life. I really hope this works for them!”

I can personally attest to that. In 2010, I purchased an Asus PC EEE 1201N notebook, which has found running a viewer like Firestorm increasingly heavy going. With Firestorm through SL, with all the bells and whistles turned-up, I’m averaging around 60 fps!

Firestorm on SL Go from OnLive: almost 60 fps on a Asus PC EEE 1201N notebook with all the bells and whistles active! (this image replaces an earlier version, after I realised I'd uploaded the wrong screen cap - one with shadows disabled)
Firestorm on SL Go from OnLive: almost 60 fps on a Asus PC EEE 1201N notebook with all the bells and whistles active! (this image replaces an earlier version, after I realised I’d uploaded the wrong screen cap – one with shadows disabled)

That SL Go does bring a new lease of life to older hardware can be seen in the fact that since the launch of the service in March, 2014, the largest take-up among users has been by those using the service through the OnLive PC and Mac clients. But those who want Firestorm on their mobile devices need not fear – it will be coming in 2015.  This is something Jessica is also looking forward to.

“A could of years ago we fooled a great many people with our April Fool’s joke of a Firestorm Mobile client,” Jessica said. “The excitement over the announcement, and the outcry when it turned out to be just and April Fool’s joke, was overwhelming. The great news is – and no joke this time! – that OnLive will be making this capability real very soon!”

And it doesn’t end there. One capability that Firestorm brings to OnLive and SL Go  users is the ability to log into other grids as well as Second Life. The version of the viewer supplied to OnLive is the OpenSim version, which means it is complete with the grid manager and start-up grid selection drop-down, allowing you to log into all your favourite grids – as I did, logging-in to Kitely and Fallingwater at the Seanchai Library.

Use Firestorm on SL Go and any PC / Mac / laptop to access your favourite OpenSim grids (click to enlarge)
Use Firestorm on SL Go and any PC / Mac / laptop to access your favourite OpenSim grids (click to enlarge)

Thus, with a single subscription to OnLive, you gain access to the entire metaverse from any low-end PC or Mac in your home.

“We’re happy to be able to empower SL Go users with more choice. They’ve told us they want a choice of viewers, so offering the popular Firestorm viewer was a natural next step.” said Rick Sanchez, VP of Product and Marketing at OnLive, at the launch of the new offering.

I’ll have a more in-depth look at Firestorm on SL Go available shortly.

Viewer release summaries: week 50

Updates for the week ending: Sunday December 14th, 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.22.297128 (no change) –  release notes
  • Release channel cohorts (See my notes on manually installing RC viewer versions if you wish to install any release candidate(s) yourself):
    • Maintenance viewer RC updated to version 3.7.23.297296 on December 10 – core updates: a broad range of fixes for for voice, rendering, avatar distortion, inventory, sounds, the viewer UI, and more, plus a series of fixes for avatar attachments (download and release notes)
    • HTTP Pipelining RC viewer updated to version 3.7.23.297272 on December 10 – core updates: reduced pipelined texture and mesh fetching timeout so that stalled connections fail quickly allowing earlier retry. Timeout value changed from 150 seconds to 60 seconds (download and release notes)
  • Project viewers:
    • No updates.

LL Viewer Resources

Third-party Viewers

V3-style

  • CtrlAltStudio Oculus Alpha updated to version 1.2.2.41224 on December 12th – core updates: a new Mac build and parity with the Oculus Rift SDK 0.4.4 (release notes)
  • Firestorm updated to version 4.6.9.42969 on December 10th with a hotfix release (4.6.9.42974) on December 11th – core updates: many new features and updates, fixes and improvements (change log).

V1-style

  • Cool VL Viewer stable branch updated to version 1.26.12.25 and Cool VL viewer legacy branch updated to version 1.26.8.83, both on December 13th (release notes).

Mobile / Other Clients

  • LightSight updated to version 1.6.0.5 on December 13 – core updates: unknown, no details given.

Additional TPV Resources

Related Links

CtrlAltStudio provides Oculus SDK 0.4.4 support and Mac build

CAS-logoOn December 4th, Oculus VR released the latest software version for the Oculus Rift, version 0.4.4. A beta release, it includes an number of bug fixes and improvements, while retaining  experimental support for Linux.

As a result of this update, Strachan Ofarrel (aka Dave Rowe in the physical world) released an updated version of the Alpha version of his CtrlAltStudio viewer on Friday, December 12th. Version 1.2.2.41224 Alpha 5 brings with it not only support for the SDK update but also, courtesy of Mac viewer developer Cinder Roxley, a Mac build as well.

As usual with the Alpha version of the viewer, this release is installed into its own directory / folder, and so can be installed alongside the current release version of the CtrlAltStudio Viewer. A clean install is not required if you have been running previous alpha versions.

Core updates in this release comprise:

  • Updated to Rift SDK 0.4.4. This fixes the overdone vignette (fading to black) around the Rift barrel image’ edges edges.
  • Updated position of notification messages and script dialogue boxes so that they’re visible and usable in Riftlook.
  • Modified Start+Back key behaviour on Xbox controller if Rift display is configured: if you’re not in Riftlook then you enter Riftlook the same as before; however if you’re already in Riftlook then it zeros sensors the same as Ctrl+Spacebar (instead of exiting Riftlook). To exit Riftlook with the Xbox controller, press the yellow ‘Y’ button.
  • Updates for Mac OSX build.

Hints and Tips

Also, don’t forget that each set of release notes for the Alpha version of the viewer includes a set of hints and tips for getting the best results when using the viewer with the Rift.  These include tips from Strachan and also discoveries made by other users, and are being added to over time. They include, but are not limited to:

  • If you have good frame rates, including while turning, set your Rift display to 75Hz: Control Panel > Display > Screen Resolution > Advanced Settings > Monitor
  • If you’re experiencing judder while turning then try to try disabling one or more of the “Dynamic prediction” … “Pixel overdrive” Oculus Rift options, consider configuring your Rift display to 60Hz, and possibly try enabling triple buffering in your display driver
  • Setting your Rift to be your primary monitor may also reduce judder [Estelle Pienaar]
  • If you have a stereoscopic 3D system, you may need to disable stereoscopic 3D display in order to stop the Rift’s display rate being reduced from 75Hz to 60Hz. [Estelle Pienaar]
  • If you have an Nvidia graphics card, adding an entry for the viewer in the Nvidia Control Panel 3D Settings and setting the preferred refresh rate to unlimited may let your Rift run at 75Hz without needing to make it your primary monitor [Phoenix]
  • If using Windows 7 and you’re experiencing juddering, try turning off Windows 7’s Aero. [Phoenix]
With floating text you may want to adjust the distance the floating text fades at so that distant text is not so annoying in Riftlook - one of the tips from Strachan
With floating text you may want to adjust the distance the floating text fades at so that distant text is not so annoying in Riftlook – one of the tips from Strachan

 Related Links

Firestorm 4.6.9.42974 hotfix released

firestorm-logoAs indicated in my update to the Firestorm 4.6.9.42969 release review in this blog, a couple of issues have been found within that release, which may affect some Firestorm users.

As a result, the Firestorm team have released a hotfix update to the viewer, which includes fixes for those issues and offers three more the team has also implemented.

The blog post on the fixes reads in full:

After releasing 4.6.9.42969 we discovered a few bugs that affect just enough users to warrant a hotfix update. However, if none of the issues addressed in this hotfix affect you personally there is no need for you to update to it.

The issues are listed below.

We have replaced the 42969 links with the new version 42974 on our download pages.

As per the blog post, unless one of the issues addressed by the fixes above affect you, there is no need to update your version of Firestorm. None of the fixes should directly impact on the elements of the viewer included in my 4.6.9.42969 review.

Firestorm 4.6.9: a Christmas feast of features and fixes!

firestorm-logoUpdate Thursday, December 11th: There will be a hotfix update for Firestorm, which will likely be made available on Friday, December 12th. This is to correct a couple of issues related to voice and RLV/a discovered with the 4.6.9.42969 release, and will likely add some additional fixes as well. I’ll have a further report available once the update is available.

On Wednesday, December 10th, the Firestorm team announced the release Firestorm 4.6.9.42969.

This is a hefty update which brings with it a lot of new functionality, together with bugs fixes and assorted improvements and updates.

As always, the complete list of changes, together with all attributions,  can be found in the release notes / change log, and I refer readers to that document for specifics on all contributors, FIRE JIRA links, etc. The following is intended as an overview of some of the more major / interesting changes, updates and  fixes to be found in the release.

The Before We Begin Notes

For best results when installing this release:

Firestorm Blocking

Note that as a result of the Firestorm team’s policy to keep only 3 versions running, version 4.6.1 will be blocked, most likely early in the new year. The advice from the team is that If you are on 4.6.1, to please update now. Version 4.4.2 will continue to remain for Mac users until all the major Cocoa Mac bugs have been resolved. However, if you are not a Mac user, then there really isn’t any reason for you not to have updated, and the team again ask that you update as well

Lab Updates

This release sees Firestorm remain on a parity with the Lab’s 3.7.8 code-base. However, a number of updates and fixes have been cherry-picked from upstream (such as the group ban functionality – see below), particularly bug fixes and stability improvements – please refer to the change log for details.

Building and Scripting Updates

The new buttons for cycling through objects in a linkset
The new buttons for cycling through objects in a linkset

Some additional updates and tweaks have been made to assist builders and scripters:

  • There are two new buttons located in close proximity to the Edit Linked check box.
    These buttons cycle forward or backward through a selected linkset, in the same way as the existing keyboard short cuts. note the buttons will only be active when Edit Linked is checked
  • The issue of the script editor failing to open scripts in copied objects (see VWR-27512), which has affected v2 and v3 viewers, is corrected with this release of Firestorm, and the fix has been contributed to Linden Lab for inclusion in the official viewer code
  • The build toolbar button should no longer be disabled when it shouldn’t be.

Communications Updates

Firestorm 4.6.9 brings with it a large number of features, updates and improvements to communications. These include, but are not limited to, the following.

Audio / Voice

  • Parcel media and audio now have a separate auto-play option (Preferences > Sound & Media > General > Allow audio to auto-play/Allow media to auto-play). Parcel audio should now auto-play correctly on logging-in
  • A reset voice button has been added to Preferences to help with fixing voice issues (Preferences > Sound & Media > Voice Settings)
The new voice reset button to help fix voice issues
The new voice reset button to help fix voice issues
  • You can now “zoom in” on a speaker using voice to hear them more clearly (Comm > Nearby Voice > Right click a name >Zoom in)
  • Voice level icons in the radar are now independent from other voice level icons
  • Sounds used for opening scrip dialogues can now be customised (Preferences > Sound & Media > UI Sounds 2 > Script Dialog)
  • The viewer now automatically adds http:/ to the music URL in the parcel audio panel.

Auto-response Updates

With Firestorm 4.6.9, auto-response messages are now localised. There is also a new option for an item of inventory to be automatically sent with your auto-response messages, when set. The selected item must be COPY / TRANSFER in order for this capability to work, and will be sent when one of the following is set:

  • Busy / do not disturb
  • Away
  • Autorespond
  • Autorespond to non-friends.

To set an item of inventory to be sent with auto-response messages, drag and drop a suitable item from your inventory and into Preferences > Privacy > Autoresponse > Autoresponse Item.

Firestorm 4.6.9 allows you to send an inventory item when auto-responding into incoming IMs. The item must be COPY / TRANSFER in order for this to work
Firestorm 4.6.9 allows you to send an inventory item when auto-responding into incoming IMs. The item must be COPY / TRANSFER in order for this to work

In addition, this release fixes getting an IM from yourself to yourself saying “Autoresponse sent” if somebody answers from an off-line IM via email. Also, having both “Autorespond to non friends” and “Only friends and group can call me or IM me” set no longer results in you getting two new IM sound alerts for every non-friend IM plus the non-friend receives your auto-response twice for each IM sent.

Contacts List

The Contacts List floater has been revamped to match the look of the nearby chat and IM session floater, for a smoother and unique appearance. In addition, an option to pay someone directly from your Contacts List has been added to the right-click context menu (Comm > Contacts > Right click a name > Pay).

New to Firestorm 4.6.9 as well is the ability to choose which name columns should be displayed in the Contacts List. You can now choose between choose between user name, display name, full name, or a combination of these, and you can now display full names in your Contacts List as “Username (Display name)“. Finally, a option has also been added to hide the permissions columns (whether those in your Contacts List can see when you’re on-line, map you, etc.). 

All of these options can be found under Preferences > Firestorm > General.

The Contact List display options in Preferences
The Contact List display options in Preferences

Continue reading “Firestorm 4.6.9: a Christmas feast of features and fixes!”

SL project updates week 50/1: server, viewer, misc

Black Basalt Beach; Inara Pey, August 2013, on FlickrBlack Basalt Beach, August 2013 (Flickr) – blog post

Server Deployments – Week 50

As always, please refer to the server deployment thread in the forums for the most recent news and updates.

On Tuesday, December 9th, the Main (SLS) channel was updated with the server maintenance package deployed to the three RC channels in week #49. This update comprises:

  • A fix for BUG-7515 “Restarting region turns off ‘block parcel fly over’”
  • A fix for BUG-4949 (non-public) “Cannot manage block list with certain object names”
  • A fix for BUG-7850 “Experience tools: ‘Script trying to teleport other avatars!’ script error” appears incorrectly
  • A fix for BUG-6789 “Spelling mistake in llGodLikeRezObject”
  • Minor server change to help configure the texture and mesh CDN.

On Wednesday, December 10th, all three RC channels should receive a new server maintenance package comprising:

  • A fix for BUG-7595 “Allowed & Blocked experiences persist with parcel owner change after purchase or abandoning”
  • A fix for (non-public) BUG-7036 “Experience based scripts in attached child prims reference their operation by region position instead of root position like non-experience based scripts”
  • A fix for (non-public) BUG-7048 “llGetExperienceDetails() returns 4 for state and “operation not permitted” for state message while over mainland parcels that have the experience allowed”
  • A fix for BUG-6757 “Different error code returned for an Experience that is not permitted to run on a parcel / region OR a user clicked No on the permission request dialog”
  • Additional internal Experience Key fixes
  • To find experiences with all unicode names you have to leave the search field blank and page through all results

SL Viewer

No further updates to any of the SL viewers (release, RC or project) since my last viewer release summary. Please refer to my Current Viewer Releases page for the current status of SL and TPV viewers.

However, as I noted in a separate report, the most recent AMD update to their Catalyst™ drivers, version 14.12 does not resolve the problem of failing to display rigged meshes unless the viewer’s hardware skinning is disabled. I’ve also been informed that this issues also extends to the most recently AMD / Nvidia Omega driver update.

Experience Keys / Tools

the RC deploy due on Wednesday, December 10th, sees a number of fixes and updates for the Experience Keys / Tools project. Again, commenting on the status of the project at the simulator User Group meeting on Tuesday, December 9th, Simon Linden said:

 We’re getting close on that … there are some last-minute things to take care of, and we’re being extra careful that we have the systems in place to handle the key-value storage usage.    How much load that will create is some interesting guesswork, but it’s better to be over-prepared.

However, with the holiday season now fast approach, and with it no change windows for server and viewer updates popping-up, it may be that the project doesn’t make it to a deployment beyond its current beta status until the new year.

Once Experience tools are deployed, the Lab will seek to address issues through the Simulator User Group meetings. However, if there is sufficient demand in terms of issues raise for discuss, etc., during the Simulator UG meetings so a to warrant a separate meeting, they will look into doing so.

Group Chat

Commenting on his recent group chat work, Simon had this to say:

There’s another chat server update this week.   It’s pretty minor, but you shouldn’t see the problem where it gets way behind and then starts delivering ancient (more than 5 minutes old) messages.  I’m still chasing the main bug but this should make the recovery faster and less confusing. The new code is on only one of the server cluster machines but will go to more this week, assuming we don’t see new problems.   So far it’s looking good.

He went on to comment that, while a complete overhaul of the group chat system is unlikely, simply because it is unlikely to result in a significant enough improvement in things, despite recent improvements. “the servers still spend more work updating your chat member lists than it does sending messages. That’s just not right.” So it would seem further tweaking of things will continue in 2015.

Tuesday, December 16th will be the last Simulator User Group meeting for 2014.