Linden Lab have released a new Viewer Project to sit alongside their exiting Mesh-enabled Alternative Viewer. This is the Search Project Viewer, which is promising to deliver a new and better Search experience in Viewer 2.
Given that Search has long been a contention where Viewer 2 is concerned – where it initially started out as a massive step backwards in so many respects – the fact that LL have moved it to a dedicated Viewer should be welcome news, in that it gives people the opportunity to properly test the new features, provide feedback and for LL to finally ensure that Search is providing what the user community wants and expects.
I’m not going to go into a long review of the new engine – Ciaran Laval has already done that, and I see no reason to repeat the work he’s done. Certainly the new Search looks very promising, although some of the more irritating problems with the engine remain – such as the number of steps you have to go through simply to be able to see the information you want to get to, regardless of the fact that the Search engine can finally now locate it.
What is interesting to note is that Linden Lab state in the blog post that:
New search will soon be available to you in the official SL Viewer and we will not be implementing it for the 1.23 Viewer. To be clear, you can still use the 1.23 Viewer, but search functionality will be impaired once new search is released into general availability, after the test period.
Specifically, searches using the ALL and GROUP tabs of the 1.23.x Search will be impaired. So, where does this leave existing 1.x-based Viewers? Again the blog post provides a part of the answer:
(We cannot speak to which Third-Party Viewers will adopt the new search technology.) All of our development efforts are focused on making SL Viewer with Basic and Advanced modes exceptional for all Residents–new and seasoned.
In other words, as far as the “official” version of Viewer 1, already frozen in development in many respects, this pretty much marks the end of the road, and it will by up to TPV developers themselves to overcome any functional impairments in search by adopting the new “search 2”. How easy / difficult this might be remains to be seen, but it would certainly seem to add to the burden 1.x TPV developers are having to carry in their attempts to keep things going.
Given that many are already producing Viewer 2 alternatives (Dolphin 2, Firestorm, Kokua, Kirstenlee’s S21, to name but four), this might push them towards making a full and final switch to Viewer 2-based development and allowing any 1.x Viewer offerings they have depreciate. This many not be a popular move among the wider user community should it happen, but the fact is – and Oz Linden has pointed out – there is a lot coming down the tracks in terms of new functionality within the Viewer that trying to maintain two code bases, or simply trying to backport functionality into the older code, may simply reach a point where it is no longer viable.
If you wish to try out the Project Search alternative Viewer, you can fins the downloads on the Alternative Viewer wiki page.
Viewer 2’s Basic Mode gains a new feature today – that of Voice.
While I don’t use Voice myself – I have nothing against it, I just move largely in the world of role -play in SL, and Voice can be illusion-shattering in that regard – I think it’s a pretty good option to have within Second Life, and adding it to the Basic Mode makes sense. To a point.
The problem is, a lot of things are “coming” to the Basic Mode (or have been indicated at coming) – currency, for example. To be fair, I’ve suggested some additions myself, although they appear to be fewer than those LL are contemplating. Which leads to a problem I’ve touched on before.
If LL keep adding to the Basic Mode, how long until it ceases being the “Basic Mode” and becomes “The Viewer”? The function of a Basic Mode, I thought, was to ease new users into the Second Life / Viewer experience. Ergo, it makes sense to keep the Basic Mode relatively simple and clean. While things like Voice are very useful to have, the fact remains that if things keep getting added to the Basic Mode, then it won’t be long before any advantages gained in introducing it are going to be washed away.
In discussing this with Rodvik a while ago, I pointed out the need to provide a better transitional experience between the Basic and Advanced modes of the Viewer. It’s something he apparently generally agreed with, although he also appeared to imply that Basic might be more to do with making Viewer development more iterative, and that at some point in the future, Basic may merge with Advanced – presumably because the code base has been overhauled and made somewhat more modular, making future Viewer maintenance a lot easier. If so, this throws the purpose of the Basic Mode into a whole different category than “simply” being a tool to help new users – and it’s future becomes somewhat more intriguing.
Personally, while I’m all in favour of making the Viewer a lot more modular (something I understand Bagman Linden (Jeff Petersen) is quite keen on) to the point of potentially making elements of the Viewer “optional” / “installable as required” where users are concerned, I still think that the Basic Mode holds a lot of potential where new users are concerned, providing LL address its current shortfalls without overloading it with features and providing they add the means to bridge the gap between it and the Advance Mode smoothly.
It’ll be interesting to see which direction they do opt to take.
Nalates Urriah reports that Linden Lab have confirmed there is a security exploit involving a flaw in the Ogg Vorbis library could lead to Viewer crash issues. It’s not thought that the exploit can either perform privilege-escalation or arbitrary code-execution on users’ systems.
The flaw has been known about since 2009, but the exploit is fairly recent. Ogg files are in widespread use, so this is not an issue specific to the Viewer code. Linden lab has responded to the situation by issuing a patch and an advisory for all TPVs to recompile their binaries for all TPV viewers.
At the time from writing, updating executables for Kirstenlee’s Viewer (S21 7a) and the Firestorm Previews have been released. Links for the Firestorm downloads (which do not appear to be available on the Phoenix website) are available as follows:
Note that all of the above three releases of Firestorm should be clean installations, not installed over any previous release (which should be removed first).
Other TPVs will doubtless follow, and users are advised to keep an eye on the various Viewer-related blogs and update as required.
Addendum May 16th
Phoenix have released an update that fixes this issue (and others). Find it here.
Kokua is the name of the new Viewer from the Imprudence team. It’s been in development for several months, and a “test release” or “Work-in-Progress release” has now been made available. Based on Snowstorm 2.4, Kokua represents the forth major TPV to be based on the Viewer 2, following Kirstenlee’s S20/S21 series, Dolphin 2 and Firestorm itself.
Given the version (0.1.0) on offer isn’t even an Alpha, it would be unfair to subject it to a full review; rather, here are some impressions after having taken it for a spin over a couple of hours.
Installation and Start-up
Installation was pretty much the norm for an SL Viewer, although running it might cause some surprises, at least on the Windows version, where it opens up a couple of unexpected terminal windows; one apparently monitoring the Viewer’s system calls, etc., and the other blank. Closing the latter will remove the blog display panel from the splash screen, but otherwise not impact the Viewer. Closing the other window – identifiable from the commands displayed – will also close the Viewer – it must remain open until you actively quit the Viewer (at which point it will close). Doubtless future releases will see these additional windows removed.
Hybrid Interface
Once logged-in it becomes evident that Kokua is something of a hybrid Viewer; while the layout of the UI is broadly Viewer 2, there are subtle differences. The most obvious of these at first glance is the menu bar, which is more Viewer 1.x in appearance than Viewer 2.x. Rather than the increasingly-familiar Me, Communicate, World, Build and Help options, Kokua presents us with File, Edit, View, World, Build and Help, together (as with Viewer 2) the optional Advanced and Develop menus.
Similarly, the toolbar at the bottom of the Viewer window presents additional buttons over Viewer 2’s default set (see below). Of particular note is the Sidebar button, which brings up a floating palette from which the various Sidebar tabs can be accessed. Anyone having used Kirstenlee’s S20 Viewer, will find this instantly familiar. However, there is a slight annoyance – close the Sidebar palette before you’ve closed any open Sidebar tab…and you cannot close the tab. You must re-open the Sidebar palette and click on the relevant button to close the tab.
One of the major frustrations with Viewer 2.x has always been in the area of typewritten communications which has exhibited various flaws, including much in the way of wasted space through the use of avatar icons in the actual chat / IM windows. While things have improved over successive releases of Viewer 2, Kokua sadly takes a step backwards.
The problem is that both the chat and IM window tabs take up an excessive amount of space when compared to Viewer 2 because both include a central “column”. In the case of IM tabs, this is used to display the Profile picture of the person with whom you are conversing and a series of Action buttons (Pay, Teleport, etc), as shown below; in the case of the Chat window, it displays a list of icons representing everyone in your immediate vicinity.
IM tabs (Left: Viewer 2.x; right: Kokua)
Truth be told, while not always ideal, Viewer 2’s use of icons at the top of IM tabs is a far better solution to providing access the options to pay, teleport, etc. Where the chat window is concerned, the list of avatar icons is…wasteful.
View (Camera) Controls
On a more positive note, a nice touch within Kokua is a revised View / Camera control palette which includes buttons for camera zoom and for entering Mouselook, as well as the more familiar control options. These are a very nice touch.
Performance and General Feedback
In terms of performance and use, Kokua sits right up there for me. My frame rate was hitting 50-55 fps when on my own, and dropping to around the mid-30s when interacting with a few others. This actually puts it top of the tree for me in comparison to the likes of Firestorm and even Phoenix 908/977. However, activating dynamic shadows did give me a massive performance hit; one far greater than with Firestorm, with my frame rate collapsing to around 7-8 fps.
Rezzing was also extremely fast on Kokua when compared specifically to Phoenix and Firestorm – both of which it beat hands-down when logging on to the same location with each Viewer and with a cleared cache. While it might be my eyes, Kokua also seems to render objects with a far greater sharpness than seems to be the case with Viewer 2, Firestorm or Phoenix.
When installed, Kokua leaves one of the bigger footprints on a hard disk – 137Mb. This compares to the 102Mb used by V2, the 129 by Klee’s S21 and the whooping 154Mb required by Firestorm. Memory usage for the Viewer equated to that for both Firestorm and Klee, with similar overall core usage on a multi-core (quad core) CPU, where three cores shared the load.
Conclusion
There is of course much that is missing from this release – hence the “test” and “WIP” warnings in the Imprudence blog; so those anticipating a Viewer comparable to the pre-Alpha of Firestorm should perhaps wait until the next release of Kokua comes along. Certianly, anyone requiring the Media Filter, RLVa, radar or a choice of skins would do well to wait.
People also shouldn’t expect things like web Profiles or Avatar Physics – these became available after the version of Snowstorm Kokua is currently based on, so it is frankly unfair to expect either, or critique the Imprudence team because they are “not there”. Indeed, those expecting more would do well to read the Imprudence blog post caveats relating to the release, namely:
This is a test build. It will likely have many bugs. It might break your avatar or eat your pets. Use it for testing purposes only.
This is not a finished product. The UI is not final. The feature set is not final. Nothing about it is final.
We need your feedback to improve the viewer.
However, that said, there are two elements of the current release that I would change were I involved in Kokua. These are:
The current chat / IM window / tab layout: this is really irritating in the amount of screen real estate required to adequately display conversations – and it is simply not necessary. The central “column” for images and the like really serves no purpose that cannot be better met through other means. If nothing else, those routinely using SL from a laptop may well find the amount of screen display lost to chat very annoying
The Sidebar tabs really need individual options to close them in addition to being able to do so from the Sidebar button palette; relying on the palette alone is not really convenient.
Other than that, this looks like a promising start for Kokua, and I look forward to taking future, more advanced, releases for a more thorough test drive.
Well, Enhanced Avatar Physics are finally formally released – and blogged about by Samuel Linden, aided by Amanda Linden (honestly, the bouncy bits are that big they require a double team effort?!).
The news isn’t exactly new; people have been blogging and filming the new undulating body parts and having mild fits of hysterics playing with the sliders for a while now.
And truth be told, the enhanced physics are fun and add another level of realism to SL (and without the angst associated with the way bewbs bounce in viewers like Phoenix).
However, we’ve come through nigh-on a month of almost deafening silence from Linden Lab while a myriad of things bork, bomb and basically bugger-up (OK, not quite so alliterative, but you get the point). So you can understand it when people take a tongue-in-cheek line of reportage on the subject, or indeed, mix a little acidity into their view on the news, as Marx Dudek did (sorry; hard to avoid that particular alliterative bit) on Twitter:
What I like best about SL jiggly bits: My breasts bounce with just the right amount of realism while I hover after another failed teleport.
Yes, bouncy bits are fun – but unless this announcement marks a renewal of the Lab actively communicating with the community, people are going to remain pretty unimpressed, even if those of us blessed with them can have bits that wiggle and jiggle and bounce and flounce.
Opinions relating to the Basic mode available in Viewer 2 are mixed. While finding it usable in my original review, several aspects left me concerned as to how well it might fill the role for which it appears to have been designed. I specifically questioned the fact that beyond things like basic movement, the view controls and communicating, it has very little in common with the Advanced mode – and there is no obvious continuity in the assistance available for those who opt to start with Basic and come to the point where they want to transition.
One Small Step for a Viewer; One Giant Leap for the User
In fairness, getting to grips with the Viewer at the best of times isn’t easy; while Torley has produced some outstanding videos, these aren’t always easy to locate. Worse, the So-called Quick Start Guide suffers from a combination of having the wrong emphasis in part and missing important and basic information (like actually modifying your avatar’s appearance, rather than simply changing clothes). Also, it’s fair to say the Quick Start Guide hasn’t been updated to reflect the arrival of additional and attractive functionality, thus putting it further out-of-synch with the Viewer.
Put all of this together – the more intense UI of the Advanced mode, a less-than-helpful Quick Start Guide, only the broadest elements of commonality between the Basic and Advanced modes of the Viewer, etc. – and it becomes clear that moving up from the Basic mode to the Advanced mode is not so much a matter of taking the next logical step as it is about taking a leap of faith that the effort is going to be worth it. This considerably undermines the usefulness of the Basic mode.
If the Basic mode is to prove worthwhile, work needs to be put into providing some level of continuity between the two modes of the Viewer to help those making the transition. Indeed, with a little forethought, re-working where and how people get help in the Advanced mode may well assist those leaping straight into it, opting to avoid the Basic mode altogether.
Such continuity / general assistance could be achieved first and foremost by incorporating the HOW TO button with an expanded number of pop-ups (providing overviews of, say, the Sidebar, the revised Toolbar, the menus and the Favourites bar). Doing this would immediately achieve two things:
It would provide needed continuity of approach to seeking help for those moving up to Advanced from Basic.
It offers an obvious place to find basic help and information for those leaping into the Advanced mode of the Viewer and bypassing the Basic mode altogether.
All the pop-ups associated with HOW TO (both Basic and Advanced) should additionally contain links to the Viewer Quick Start Guide, where more in-depth information would still reside. These links should display a pop-up informing the user the QSG will be opened in their external browser (although the Advanced mode should still retain QSG access from the Sidebar as an option).
To further increase the relevancy of the QSG, it should be re-formatted into two sections: BASIC and ADVANCED:
BASIC should provide additional information relevant to the Basic mode and which is not included in the HOW TO pop-ups (such as the more familiar WASD keys being available for movement, information on the various icons that appear on the right of the toolbar, etc.)
ADVANCED should provide more in-depth information available to Advanced mode users
Where any overlap occurs between the two modes, simple visual indicators should be used to indicate options those options only available to the Advanced mode.
Help, Don’t Hinder
It is fair to say that the current QSG is encumbered by several problems:
It is out-of-date
It lacks key information users will want to know – such as instructions on physically altering an avatar, as mentioned earlier
It contains a lot of what might be regarded as extraneous information. For example, while one understands LL’s desire to promote Premium Accounts, is it really necessary to have the latter third of the QSG read like a brochure for Linden Homes – especially as there is already an entire section of the Sidebar given over to this very topic?
It would therefore seem preferable that any re-vamp of the QSG should also focus on ensuring it is updated to reflect more recent version of the Viewer and on assisting the user more effectively, rather than engaging them in a sales pitch for Premium Accounts.
Obviously, a better alignment of the two modes of the Viewer and overhauling the QSG will not solve all the problems inherent in joining Second Life – there are many other aspects of getting into SL that also need to be addressed over an above the Viewer itself.
However, changes like these should help to ease people into using the viewer and encourage a greater tolerance towards it by presenting a more easy-to-follow route into getting help and understanding the UI. In short, it will do more to help users in gaining familiarity with either mode of the Viewer, rather than possibly hindering them.
As stands, as long as the disconnect between both modes of the Viewer remains, it is hard to see how the Basic mode can achieve any lasting positive impact on new users.
Inara Pey: Living in a Modemworld 