Category: SL Viewer

So, yesterday mesh arrived (except for folk on the BlueSteel RC channel, who still appear to be waiting for mesh to be rolled-out), and  – as I predicted in my report on the roll-out, Viewer “3” jumped very quickly from Beta to the main Viewer download channel.

For those hoping Viewer “3” was bringing with it some radical departure from Viewer 2 (and I did actually hear and read speculation from some who had not actually taken a look at the new version while it was in Beta), sorry folks, that was never the aim.

Elevating the Viewer from 2.x to 3.x was never about bringing out a whole new Viewer (or even radically improving what was there already), but simply about marking the arrival of mesh. In fact, other than a muted blog post in the In-World section of the official blog (actually promoted to Featured News as I wrote this article) and a couple of Tweets, it’s actually been the only sign from Linden Lab that mesh has rolled out. While I appreciate (very sincerely) that LL included a link to this very blog in their announcement, I’m nevertheless somewhat baffled at the low-key approach.

So what does “Viewer 3” bring us.

Well, pretty much what Viewer 2.8 had, with some bug fixes and, of course, the inclusion of various mesh features.

Performance-wise, I’ve personally found it to be reasonably comparable to the likes of Firestorm on my main PC. The frame rate for a reasonably busy sim (i.e. more than a handful of avatars) comes in at around 32-37fps. On a sim where I’m just one my own or with one or two others, this bangs up to 45-48fps. It doesn’t rock the way Viewer 2.7 did for me, but these figures give a pretty smooth performance.

With shadows enabled, things aren’t so good. I crash to around 5-8fps with just one or two on the same sim. Any more than that and the frame rate bottoms-out at around 2-3. This is pretty chronic compared to Firestorm with shadows enabled, and a lot worse even than some earlier iterations of Viewer 2.

The usual annoyances remain: lack of location co-ordinates in the navigation bar, overly clunky movement / camera control pop-ups, frustratingly confusing toasties, etc. (although in fairness, all Viewers based on the V2 code have this), absolutely crappy IM / chat windows (please, please, LL, take a leaf out of the Firestorm book), yadda, yadda.

As previously mentioned, the update includes an option to allow region / sim owners to allow / disable mesh on a sim. IMPORTANT UPDATE: please see the end of this article of the latest status of this option.

The can be found bby clicking on the WORLD menu option, then navigating to PLACE PROFILE -> ESTATE / REGION, as shown above, and then clicking on the REGION tab. The option should be available for  estate managers. However, at present the option still has a bug that means it will fault back to ALLOW on clicking APPLY. Ciaran Laval has raised a JIRA on this: VWR-26727, which has been moved to SH-2341 – please make sure you WATCH it.

When it comes to uploading mesh objects, the option can be found in the BUILD menu, alongside the other upload options.

A couple of things to bear in mind here:

• You’ll have to have completed the Mesh Upload Status tutorial and have Payment Information On File to upload mesh objects
• It would appear that if the land is set to a Group with object entry / rezzing is restricted to that group, you may find the mesh upload option is not displayed unless you are a member of that Group (this was certainly my experience, testing on both my own land and a sim belonging to a friend whose Group I’m not a member of).

I ran a couple of upload tests without incident (although the meshes were not that complicated, and I didn’t play with the defaults that much, as they’d already been optimised for SL). I gather others have found problems.

Other than this, there is little more to say about Viewer “3”. Others have experienced crash and frame rate issues, but in using it for some 3 hours, with plenty of teleports, etc., I didn’t encounter any technical issues. usability issues, yes; but not technical. Again, the official Viewer, in whatever version number it sits under, has a long, long way to go before it reaches the level of convenient use offered by the likes of Firestorm – at least where the non-mesh aspects are concerned.

Update 25th August, 2011

In a comment on the revised JIRA, Charlar Linden states:

Charlar Linden updated SH-2341:Status: Expected Behavior  (was: Open)   Resolution: Not Applicable – thanks – this flag would have no effect, and is being removed soon.

So it would appear the option to disable mesh is not intended to be a part of the Viewer.

Some may count this post as premature, but given we’re now into July, and what is coming down the road, I’m getting my goodbyes in early.

Viewer 1 has been with us since Second Life opened its doors. Over the years, it has seen features added, tools moved around, the capability for API elements to be introduced (perhaps the most widely-used being Marine Kelley’s Restrained Love Viewer); the code has been open-sourced, allowing a raft of famous (and not a few infamous) Viewers to come into use: the OnRez Viewer, Cool Viewer, Rainbow Viewer, Meerkat, Imprudence, Phoenix and of course the “Devil incarnate” itself: Emerald (and that’s without mentioning the various “blackhat” Viewers).

Many changes to the Viewer were welcome (remember the introduction of the first skin option? of Windlight?), many were being decried and striking fear in the hearts of some even before they rolled out (remember the hoo-haw in some camps over the arrival of Voice?); others were met with much facepalming and LL’s apparent failure to grasp how people used their viewer (remember the consternation when the chat windows all changed and “communicate” turned up?). Some of the criticism aimed at the Viewer and LL was justified; a lot of it wasn’t. But through it all, Viewer 1.x, in all its many guises has remained a perennial favourite among Second Life users. Not even the demise of the official 1.x series of Viewer did much to put a dent in this: people simply switched over to V1-based TPVs in preference to going over the Viewer 2.

Now all of that is about to change. In truth, the writing has been on the wall for V1-based Viewers for the last 12 months or so: ever since Linden Lab depreciated all versions of their Viewer prior to 1.23.5 and then turned off Snowglobe work in favour of Snowstorm for Viewer 2.x.

From this month, however, even those using V1 TPVs are going to have to consider where they are going to move to next. As LL remind us (via retweets of this announcement, at least through @SecondLife), mesh commences its roll-out this month, starting with, I understand, the Blue Steel Release Channel prior to the remaining Release Channels & the rest of the main grid being mesh-enabled by the end of August.

The key issue here is that V1-based TPVs apparently will not be able to render mesh objects in-world, nor will they be able to upload mesh imports even if they follow LL’s “registration” requirements.

Ergo, if people want to see mesh objects, they are going to have to move to a V2-based viewer. What’s more, unless the TPV developers have persuaded LL otherwise, it is possible those wanting to upload mesh imports will be forced to use Viewer 2 for this purpose, given LL were looking to ring-fence this capability (whether this is still the case is unclear – like much else around mesh).

Nor does the bad news for Viewer 1 end there; Oz Linden is on record as saying that developers of such Viewers are facing an uphill battle: “[A]ny Viewer that isn’t being actively maintained is going to start having fairly serious problems over the next months. We’re making a lot of changes… if viewers don’t keep up, things will break.” 

The fact is, it will become harder and harder for TPV devs to try and maintain Viewer 1 code. Kirstenlee Cinquetti saw the writing on the wall over a year ago, and has moved over entirely to the development of the outstanding S21 Viewer. Announcements made at the end of last year concerning the future of the Viewer 1 Search prompted Phoenix and Imprudence to start down the road to developing a V2-based Viewer each. While Imprudence are still putting effort into their V1-based 1.4 Viewer, it is evident that their longer-term aim is not merge this work into their V2 Kokua Viewer, while Phoenix already have the outstanding Firestorm available. Individual TPV developers are also transitioning: Lance Corrimal hasn’t done anything significant with his V1-based Viewer since the end of April, while his V2-based Viewer comes on in leaps and bounds.

It is going to take a while for mesh to really make its presence felt – assuming, again, that the roll-out goes smoothly and without any major updates; it’s also possible that some TPV developers will look to try and backport the Search 2 functionality into their offerings in the hope of keeping things alive. So it’s possible that some may try to cling to Viewer 1 for a little longer; but while it may be seen as an unpopular statement in some quarters, the era of Viewer 1 really is now drawing to a close.

I don’t say that with any sense of superiority (I am an unabashed V2-based Viewer convert – Firestorm and Kirstenlee’s S21); I started out with Viewer 1 (version 1.14 or 1.15), and personally have no problems with it. But, sad to say, we all come to a time where, for better or worse (depending on one’s own feelings), we must move with the tide.

And the tide is now assuredly flowing to Viewer 2’s shore.