Firestorm 4.3.1.31155: the wait is over

On November 17th, the Firestorm team made a beta release of their latest update to Firestorm in order to offer users access to the new Group Services updates for managing large groups. At the time, it was indicated that the “full” release would occur in early December.

Keeping to their word, the team released 4.3.1.31155 on December 3rd, which includes everything featured in the beta release, and a few more goodies besides.

Given I’ve already given a comprehensive review of the beta release, this article will be focused primarily on the updates made between it and 4.3.1.31155 – although there will be some overlap.

As always, please refer to the Firestorm release notes for full details on credits, etc., for code contributions to the viewer, and for details of known issues and problems (known issues carried over from the LL code can be found here).

Download and Installation

As noted in the last review, the download .EXE is big – 40MB, which is unsurprising given that Firestorm packs so much into it. Installation – at a least for Windows users – is where the first set of changes occur, and it is worth recapping on these for people who have not installed the beta release:

• A pop-up requesting whether or not the user wishes to have a Windows Start menu entry created for Firestorm during installation
• Addition of the version string and estimated installed size to the installer
• Addition of new OS detection code to warn if Windows Service Packs are not up-to-date and to prevent Firestorm being installed on Windows XP with
• Publisher data, Phoenix URLs and Firestorm icon for the Firestorm entry in the Windows uninstall list
• Automatic deletion of all previously installed skins to reduce issues arising from an unclean install
• Addition of a DETAILS button in the installer pop-up window to allow the installation to be reviewed.

Havok Sub-licence

As noted last time, Firestorm has now signed a Havok sub-licence agreement with Linden Lab. This means that Firestorm is now available in two flavours – one for SL and one for OpenSim grids, with the SL version having both the –loginURI capabilities and the Grid Manager functionality removed.

This change means that Firestorm is now able to access the new LL-supplied Havok libraries, allowing the viewer to immediately include the pathfinding navmesh visualisation tools (as covered in my review of the beta release), and which could allow Firestorm to switch over to using the official LL mesh uploader code in the future, should they so wish, rather than using the current HACD code for mesh uploads.

For those using OpenSim, Firestorm 4.3.1.31155 can be downloaded here, and I’ve included an update on the OpenSim-specific updates to the viewer at the end of this article.

One point to note is that it is possible to use the OpenSim version of Firestorm on SL – the only difference is the OpenSim flavour of the viewer will not be able to access the SL Havok libaries or use any functionality associated with them.

Updates from Phoenix

Further updates from Phoenix have been added to Firestorm 4.3.1 in addition to those found in the 4.3.0 beta:

Texture Comment Metadata

When opening any texture, this will display the uploader name with a link to their profile together with the date / time the texture was uploaded. If permissions are sufficient, it will also display the asset ID on the texture preview floater.

Progressive Draw Distance (PDD)

A popular Phoenix feature, when enabled, this causes Firestorm to use a progressive Draw Distance stepping after a teleport, to help improve rezzing times. The Firestorm version includes an option to cancel stepping in progress if Draw Distance is manually changed (Preferences > Firestorm > General).

More Phoenix-like default settings for Phoenix Mode

The following Phoenix-like behaviours have been added to Firestorm when running in the Phoenix mode (selected via the Firestorm log-in splash screen):

• “Resident” is not trimmed off legacy names
• L$ balance changes will be shown in nearby chat instead of toasts
• Received Items folder is shown as a normal Inventory folder
• Firestorm will now send accept/decline responses for inventory offers after the according button has been pressed and not if the item has been received at the receiver’s inventory already
• Group and IM notifications are now sent to the nearby chat console (v1-style) instead of toasts (v3-style)

Legacy Search

Firestorm 4.3.1.31155 re-introduces the V1-style “legacy” search capability for those who prefer it to the V2/V3 web-style search functionality.

The Legacy Search floater and its associated toolbar button shown in icon mode

Provided by Cinder Roxley, the legacy search option is currently available via a menu option (Content > Legacy Search) or via a dedicated toolbar button, and works for all search categories except Events, which will be added in a future update.

Documentation on the search function is available via the Firestorm website.

Phototools, Windlight and Snapshots Updates

The main Phototools floater & toolbar button, shown in icon mode

Phototools is a suite of floaters which bring together a range of controls, debug settings and options available within the viewer into a single, cohesive set of options aimed at the SL photographer and machinima artist. I’ve covered them in detail previously, and provided a further update in my last Firestorm review. With this release of Firestorm the Phototools floaters (Phototools and revised Camera floater) can be accessed via a menu option: World > Photo and Video.

Alongside of these comes a windlight update of some 100+ presets for water and sky developed by Phototools developer William “Paperwork Resident” Weaver.

These additional presets can be accessed either via the Fixed Sky / Water presets menu option (World > Environment Editor > Environment Settings) or via the Phototool floater (shown right). All of the Phototools presets have “Phototools” at the start of their name.

Also, the Flickr tab on the Firestorm snapshot floater includes Katharine Berry’s update which add the parcel name to the location option.

Please use the page numbers below to continue reading this article

Pages: 1 2

Firestorm 4.3.0: Cry “Havok!” and let slip the goodies of update

Firestorm 4.3.0 has arrived slightly earlier than expected, in the form of an initial beta release made as a result of the implementation of new Group Services code across the main grid.

While this is only a beta, and the associated Firestorm blog post gives fair notice that it may yet be somewhat wobbly while final work on getting it QA’d and ready for a formal release is ongoing, there is more than enough in the release to make it something people are liable to be hungry for. So here’s a preliminary review of the release as it stands today, with the caveat that things may change between now and the full release, which is currently scheduled for December.

Download and Installation

The download .EXE is big – 40MB, which is unsurprising given that Firestorm packs so much into it. I’ve been running pre-releases of this version for a while now, and the size has been consistent between them and while much bigger than other TPVs and the official viewer, it hasn’t grown overly much since the last release.

The installer is actually the place where the updates to the viewer begin for Windows users, as it now incorporates:

• A pop-up requesting whether or not the user wishes to have a Windows Start menu entry created for Firestorm during installation
• Addition of the version string and estimated installed size to the installer
• Addition of new OS detection code to warn if Windows Service Packs are not up-to-date and to prevent Firestorm being installed on Windows XP with
• Publisher data, Phoenix URLs and Firestorm icon for the Firestorm entry in the Windows uninstall list
• Automatic deletion of all previously installed skins to reduce issues arising from an unclean install
• Addition of a DETAILS button in the installer pop-up window to allow the installation to be reviewed.

Lab Updates

Version 4.3.0 of Firestorm sees the viewer merged-up the official Linden 3.4.1 code base and the inclusion of later updates which are just filtering through to the official viewer 3.4.2 code pipe. Together these mean that this release incorporates and number of LL updates, including:

• Recent updates and improvements to the viewer-side pathfinding code
• Memory leak and memory crash fixes
• Translation updates (together with further updates from members of the Firestorm team)
• Incorporation of the official LL spelling checker (contributed to LL by Kitty Barnett to LL) and the official Auto-replace function (contributed to LL by Kitty Barnett, Jonathan Yapp, Tankmaster Finesmith and LordGregGreg Back)
• Rendering fixes and optimisations
• Group Services (group management) update (from the LL 3.4.2 code branch) allowing groups with more than 10K members to be edited and updated
• Objects by multiple creators show creator details when viewed in inventory (Properties), rather than “unknown”

This release also incorporates the new LL maturity rating function which:

• Notifies a user when trying to enter a region without having set the required maturity level in the viewer and presents the option to change their maturity setting (subject to age verification)
• If applicable, sends a message to the person offering a teleport that the recipient is unable to access the region due to their maturity level.

Havok Sub-licence

Firestorm 4.3.0 sees the implementation of the Havok sub-licence agreement between the Firestorm team and Linden Lab. This means that this is the first version of Firestorm to be released without any support for OpenSim access. Both –loginURI capabilities and the Grid Manager functionality have been removed.

However, as Jessica Lyons has previously noted, development of the viewer will be forking, and OpenSim support will continue in the future via a version of Firestorm which excludes the code required to access the LL Havok libraries. How tailored the OpenSim version will be for use on those grids is not clear, and those who use Firestorm to access both SL and OpenSim grids should read Jessica’s comments on support in the future.

The Havok sub-licence agreement does mean that this release of Firestorm can access the new LL-supplied Havok libraries which in the first instance, enable TPV viewers to visualise and model the pathfinding navmesh.

The pathfinding navmesh can now be visualised in Firestorm 4.3.0

Group Services

The Group Services update was the main reason for pushing out a beta release of Firestorm  4.3.0.

This code allows for improved loading of membership lists of very large groups, together with improved reliability in editing such groups (i.e. assigning roles, removing people, etc.), by the group moderators. The server-side element of this code has been available on the RC channels for the last couple of weeks, and was deployed to the main release channel on Tuesday November 13th, making it available right across the main grid.

However, in order to be used, it requires additional viewer-side code. Without this additional code, the viewer will be unable to display membership lists for groups with more than 10K members (although any groups with fewer than 10K of members can still be edited using any viewer). Thus, the decision was taken by the Firestorm team to release 4.3.0 in a beta version so that users responsible for managing groups with very large members lists can continue to edit them.

Group Services update – the difference: On the left, an attempt to load a group with almost 20K of members in the current release of Firestorm 4.2.2. On the right, the same group loaded using the new Firestorm 4.3.0 beta.

In making this release, Firestorm joins Cool VL and Niran’s Viewer in being able to handle large groups alongside the official SL beta viewer. However, the remaining TPVs are likely to have updates to support the capability out in the near future (and the code will soon be available in the SL release viewer as well).

Please use the page numbers below to continue reading this review
top of page

Pages: 1 2 3

Firestorm Beta Release: Group Services and Havok sub-licence

As a result of the release of the Group Services project code to all of the main grid this week (see my SL Projects news report), The Firestorm team have released a beta version of their upcoming Firestorm viewer update.

The new Group Services code allows for improved loading of membership lists of very large groups, together with improved reliability in editing such groups (i.e. assigning roles, removing people, etc.), by the group moderators. however, in order to be used, it requires additional viewer-side code. Without this additional code, the viewer will be unable to display membership lists for groups with more than 10K members.

To overcome this, and to allow Firestorm users who manage very large groups, the Firestorm team have released a beta version of the Firestorm viewer which includes the necessary code – as well as a lot of other updates.

Group Services update – the difference: On the left, an attempt to load a group with almost 20K of members in the current release of Firestorm 4.2.2. On the right, the same group loaded using the new Firestorm 4.3.0 beta.

Announcing the release, Jessica Lyons, the project manager for Firestorm notes, that while this is not an official Firestorm release, it will be supported by the team but requests that only those who need to manage and edit groups with more than 10,000 members download and install this release. She comments:

NOTE:
– This is NOT an official release, but we will provide support for it.
– This has NOT been thoroughly tested by our Quality Assurance team.
– We can NOT make any promises regarding how stable or bug-free it is.
– This DOES have some really cool new stuff in it!

USE IT IF:
– You need to manage large groups inworld.
– You’re tired of seeing unknown alert messages in Phoenix.
– You’re feeling brave, you live on the cutting edge and you want to get an early look at what’s coming in December’s Official Release.

This release means that Firestorm joins Niran’s Viewer, Zen, and Cool VL viewer alongside the official beta viewer in enabling large group editing.

Havok Sub-licence

This beta also includes code to access LL’s new Havok libraries. This means that it will be able to view the pathfinding navmesh, but as a result of the sub-licence arrangement, it will not be able to access OpenSim grids.

Downloading and Installing

The beta viewer is available here for Windows, Mac and Linux. As usual, a completely clean install is recommended for the most stable results.

A full review of the new Firestorm release will be appearing on these pages in due course.

A Note on Phoenix

The blog post from Jessica includes a section directed at those still using the Phoenix viewer, in which she states:

Our developers and support staff have been extremely busy trying to balance their real working and personal lives while continuing their volunteer efforts to develop SL’s most popular viewer for you. Unfortunately, most of us cannot easily compile Phoenix anymore because of missing/expired libraries like Fmod, compiler changes we’ve had to make for Firestorm, OS upgrades (Win8), etc. To update Phoenix to current LL code now would be a very, very big task and, because we are already at our limit of what we can do, there are no plans to update Phoenix Viewer to support this new group code or handle the new notification system at this time. We are, after all, only human.

This is unlikely to make popular reading in some quarters. However, as Jessica notes, the team have striven to make Firestorm’s front-end as much like Phoenix / Viewer-1 as humanly possible. While it is not possible to revert menus, etc. fully to the Phoenix format, the skinning and broad approach to getting as much of the look and feel on Phoenix into Firestorm should go a long way towards easing people willing to make the conversion a lot easier.

This does not mean the end of the road for Phoenix, but with user number falling and Firestorm proving to be a much more stable and reliable viewer which is capable of embracing viewer changes being driven out of LL, it is understandable that the Firestorm team is sounding a warning note as to the future and continued enhancement of Phoenix.

Firestorm: SL, MOSES, OpenSim and the future

Logging-on to SL today, I notice from the Firestorm MOTD that Jessica Lyon brings word on Firestorm and what is going on with SL’s most stable and most popular viewer – and the viewer of choice for many OpenSim grids.

The team has been hard at work on the viewer while LL have been busy sorting out stability and crash issues on their own beta. As Jessica comment in her blog post, one of the reasons Firestorm is on a long release cycle is that until now, she has preferred to see the viewer go out with significant updates which users will want to have / see (both new capabilities and bug fixes), rather than pushing out much smaller, more incremental releases which might get on people’s nerves the their frequency. The next release will be no different in that regard, with a range of further fixes and well as a host of new features, including William Weaver’s marvellous Phototools, which I simply adore. William (Paperworks Resident in SL) has been working closely with Firestorm developer Ansariel Hiller to get the tools integrated into Firestorm. I’ve been able to use the integrated version ahead of the release, and love the work both Ansariel and William have put in on this.

Phototools, fully integrated into Firestorm in the next release, allows stunning images to be produced from within the viewer without necessarily relying on external processing through PhotoShop, etc. (image courtesy of William Weaver)

However, in the future, it seems things will be changing, as Jessica states:

We plan to make that updating process easier for you by setting up seamless behind-the-scenes updates you will hardly even notice, allowing us to provide more frequent updates and even hotfixes to improve your experience faster!

This sounds like the team will be implementing an automatic update process similar to that used by LL to update the official viewer. It will be interesting to see how this is implemented and how people respond to it. While it is likely most people won’t mind  / will welcome the move, some may prefer to keep the option turned off (if possible) so they can track what changes are being made to their viewer installation.

MOSES: collaboration with Firestorm

An intriguing part – for me at least – of Jessica’s news is that the team are liable to be working with Doug Maxwell and his MOSES team.This is interesting for me as I covered MOSES last year in an article in this blog, and also covered a major upgrade to the platform after meeting Doug at a presentation he gave on the platform. He’s looking to enhance OpenSim security for the MOSES grid, and it appears he’ll be working with the Firestorm team on security aspects affecting the viewer, which will in turn be fed back into the OpenSim community.

In terms of direct OpenSim support, Jessica has this to say:

While Second Life still remains the primary focus of our development efforts, we have begun working towards bringing Firestorm Viewer into better compatibility with the OpenSim Platform. It is important to point out where the extent of that effort ends, though. We are making Firestorm work better on the “base” OpenSim Platform, but we cannot fix problems that arise on specific OpenSim grids because of changes those particular grids have made to their OpenSim code. For those issues to be fixed, we will rely on those grids to provide us code contributions to address those issues.

This is a pragmatic and sensible approach and typifies the considered manner in which Jessica approaches projects.

To help support the OpenSim effort, Firestom had two regions on OSgrid donated to them for their use, one of which has been outfitted to serve as Firestorm’s OSgrid headquarters and which has been named, somewhat appropriately, Firestorm Island. Directions for visiting it can be found in Jessica’s post.

All-in-all, an interesting update.