Viewer Updates 2013-27

We seem to be coming to a crunch point in viewers. The Lab is changing things so quickly third party developers have a challenge keeping up. Henri Beauchamp does well with Cool VL Viewer, which is a viewer based on V3 code with a vintage V1 user interface.


Image by Kitty Barnett

Niran seems to have leapfrogged the Niran’s Viewer to having all the latest Linden features by jumping to a recent SL Viewer V3 model. Niran’s Viewer is now Nirans Black Dragon viewer. Niran’s features from previous versions are being added to the new SL V3 Viewer code in Black Dragon. Eventually Niran will have Black Dragon on a feature par with his previous versions.

So, both of those viewers have materials. Firestorm 4.4.1 doesn’t and Tonya Souther of the Firestorm Team explains why, in a blog post: Tracking LL’s big changes, and why the 4.4.2… well now that there is an emergency roll out… 4.4.3 version won’t either. 

Emergency Bug Fix

The 4.4.1 version has a bug. It is going to get recalled. Version 4.4.2 will be rolled out ASAP. This version will NOT need a clean install. You’ll see this new version arrive today or tomorrow. It seems this version has a bug that overloads the Linden’s stats server. Once the roll is available the 4.4.1 viewer will be blocked. Currently the 4.4.1 version cannot be downloaded.

There is a debate among viewer developers as to which is the best way to develop the viewer. Henri thinks he can maintain a V1 user interface, so far Siana Gearz thinks the same is true with Singularity. Tonya explains why they, the Firestorm team, believe that is not the best choice for Firestorm.

There are also egos involved. I do not know all the people involved well enough to have a definitive opinion about how has the largest ego or is most evolved with protecting theirs. You can make your own decisions on that call. I think I can tell who is doing ergo and who is being practical. I will say that Tonya and the FS Team have made the most popular viewer in SL-dom, but it is falling behind the Linden viewer.

Linden Viewers

The current main release viewer is version: 3.6.1-278007. This is the Materials and SSA capable viewer with fixes to 3.6.0. See the release notes.

The Beta Viewer is version: 3.6.2-278133. See release notes (277515).

Currently viewer information coming from the Lab for ‘users’ is a bit out of date and confusing. I think that is due to the new viewer pipeline coming out. We may see that clean up a bit this week (27).

Other Viewers

Catznip Viewer

Catznip Viewer R8 has SSA and Havok for Navmesh editing. This is also an RLV enabled viewer. Kitty Barnett keeps this viewer interesting.

If you don’t already know, Catznip is the development viewer for RLVa features. I think of this viewer as more of an insider’s viewer.

CtrlAltStudio Viewer

This is a new on the scene viewer. I covered it in: CtrlAltStudio Viewer. This one is developing 3D. It is based on Firestorm so it will lack Materials too. But, should have SSA.

Dolphin 3 Viewer

Dolphin Viewer 3 last released an update in March 2013. I haven’t heard anything from Lance Corrimal in some time. That is 3 months. It doesn’t mean the viewer is discontinued. But, without a release containing SSA upgrades this viewer will be unusable sometime early this month.

Exodus Viewer

The latest news from Exodus was Katharine taking over as lead developer. The last release viewer is dated August 2012.

Developers for this viewer and from Firestorm have been engaged in working with Linden Lab via open source in the development of Materials.

That has lead to little work being done on the Exodus viewer. That means it will soon no longer be useable in the SL grid.

Imprudence Viewer

This viewer is falling behind. I understand it is used on some OpenSim grids. While it work with SL, it is behind and AFAIK does not have SSA or Materials. The latest release I can find is 1.4.0 Beta 2 from, I think, 2011.

Kokua Viewer

Kokua Viewer 3.6.1-28990 was released June 29th. This is a multi-grid viewer that is my current favorite for OpenSim. It has Materials capability now. It does not have a Navmesh editor, which for most users is not a problem. You can still work with Navmesh, you just have to know what you are doing because you can’t see it. I am guessing SSA has been or will be added.

NaCl Viewer

I haven’t heard much of anything on this viewer since 2011. It is alive. Zwagoth Klaar and Chalice Yao are still developing it but this viewer is apparently for their personal use. We see code from it appear in other viewers.

Phoenix Viewer

The Phoenix viewer is no longer developed. This month it won’t be useable.

Restrained Love Viewer

Its last release is May 2013, RLV version I expect this viewer to update. Work from this developer appears in other viewers that provide RLV functionality. If I have it right this is Marine Kelly’s work. RLVa is an extended RLV. I’m not into the details of these features so I could have this worng. Sorry, if I do.


When I first came into SL in 2008 there were two viewers, as far as I knew: the SL Viewer and Nicholaz Edition Viewer. Actually there were more.

  1. Able Edition
  2. Dale Glass Edition
  3. Greenlife Emerald Viewer
  4. Henri Beauchamp Edition
  5. Imprudence    Marine Edition
  6. Meerkat
  7. METAbolt
  8. MonoVida Studio
  9. Nicholaz Edition
  10. Omvviewer
  11. omvviewer-light
  12. Rainbow Viewer / Cool Viewer*
  13. RealXtend Edition
  14. SLiteChat
  15. SL Viewer

*I’m pretty sure this was not Henri’s viewer.

About 2 of them are left. Some of the developers are still around and working with other teams.

With the arrival of the new viewer pipeline in a couple of weeks we may see some viewers dropping from the development cycle as the development pace increases more. Time will tell if Henri is right: development model is most important. Or Tonya is right: quality control and teamwork is more important along with having a V3 like and V1 like user interfaces.

Either way it appears that Firestorm’s effort to appeal to everyone and carry multiple user interfaces is creating challenges and slowing development. It is obvious that FS improvements and features have made adapting to the new Linden CHUI a problem.

The Firestorm Viewer team created the problem by getting ahead of Linden Lab’s development work. The Lab contributed to it by keeping the CHUI under wraps until they felt they were ready to release it. That is not a bad thing on either’s part. But, it has lead to problems and delays for Firestorm.

The FS team wants to get features out and improve the user’s experience. Their criteria and emphasis is different than the Lab’s. That can get them out front ahead of the Lab in some areas. This happened with Firestorm’s improved chat.

The Lab wants to develop features they can support moving forward and avoid wasting TPV Dev’s time with preliminary code that could drastically change. So, they took a year to build CHUI and I believe most of that time was without releasing codes to TPV Dev’s.

Both developers have reasonable criteria. And both have incentives and reasons to work alone. The Lab has made it clear there are ways and places where they are willing to work with TPV Dev’s and places where they are going to work in private. So, I expect CHUI is not the last time something will be a big problem for Firestorm or other TPV’s.

CHUI is an instance of FS having to back up and redo things because of something the Lab did. While the Lab isn’t deliberately ignoring what FS Team does, they simply don’t consider the code the FS team uses and is developing. The Lindens have their work and it is more than enough to deal with without having to keep track of a collection of TPV versions. It is not surprising there are conflicts in the viewer code. And that is not going to change.

Will the TPV Dev’s be able to keep up with the Lab? Time will tell. Will more viewer developers give up and stop development? Probably. But, I would bet there will always be TPV Dev’s doing their thing.

6 thoughts on “Viewer Updates 2013-27

  1. Pingback: Updating Firestorm | Virtual Bloke

  2. The Firestorm team has made it clear that during the current chaos of new and indeed desirable feature releases the official release will be ahead of them on those features. Firestorm endeavors to maintain a very feature rich and adaptable viewer in the face of very dynamic viewer code from LL. They will catch up in time. The one thing we do not want them to do is second guess what will be coming out of the Lab and stumble into a fishhook can of problems.

  3. In the beginning (back in 2007), the Cool VL Viewer was named “Cool SL Viewer” (the name was chosen and used months before LL made out their naming copyright policy): it sources were provided as a (large) collection of patches to apply to LL’s official viewer sources (you can still see this collection of patches for v1.25, which was the last, non-forked version, here: It was a Linux-only viewer (Nicholaz and others were providing Windows-only or MAC-only TPVs, so I felt like I needed to provide a Linux one to the community).

    Boy Lane proposed to make Windows builds of the Cool SL Viewer, which I gladly agreed to and all went smoothly for a while.
    Then she took on herself to rename her Windows builds into “Cool Viewer” and started bragging on forums how “her” viewer was so much better than every other TPV in the world. When I found out and demanded her to stop this little game (the “Cool Viewer” was still exactly the same viewer as the “Cool SL Viewer” and she had no right to rename it with such close a name and pretend it was “hers”), telling her to stop using “Cool Viewer” and do a proper fork (and starting from this point, I provided my own Windows builds of the Cool SL Viewer).
    Boy Lane then made the “Rainbow” viewer (which was reusing all Cool SL Viewer patches but for the v1.18 UI reversal ones, and had a couple other patches, borrowed from other viewers (such as Emerald) added).

    There is a difference between release builders (people compiling viewers made out by others for a given platform that the original maker can’t provide binaries for) “patch integrators” that reuse a collection of patches made by others, apply them to LL’s sources and publish the resulting viewer as “theirs”, and real coders, who do code the patches or modify (fork) LL’s original sources to make a new viewer.
    Boy Lane has been a release builder, then (starting with Rainbow), a patch integrator.
    I’m a coder..

  4. Thanks for the run-down on the viewers. For what it’s worth, I wouldn’t just describe Catznip as “an insider’s viewer,” though it’s certainly not as widely-used as it might be.

    I use it almost all the time. This is not simply because I make a lot of RLVa stuff but because I find Catznip a very fast, stable and economical viewer that looks and feels pretty much like V3 but has some very welcome (and well-thought-out) tweaks and adaptations. You get the impression (I do, anyway) that Kitty and Trinity sit down and think, “this particular feature is good but how can we make it really useful?” (for example, for ages Catznip’s implementation of outfits was the only one I found usable, and I think it’s still a lot more intuitive than the others on offer).

    I would recommend it to anyone. It’s not that I dislike Firestorm; it’s just that Firestorm has a gazillion features I never use, while almost everything I want is there in Catznip.

Leave a Reply

Your email address will not be published. Required fields are marked *