Breast physics are not new to the world of Third-Party Viewers (or Third-Pervy Viewers as I once saw them called in a forum post). First introduced with Emerald, they are now available in most TPVs.
Until now, however, they’ve not been available in the “official” Viewer; but all that is about to change. Yes, bouncing bewbs are coming to Viewer 2. And not only bouncing bewbs, but also physics to make bellies and butt do their own thing.
Whether this leads to a wider uptake of Viewer 2 remains to be seen; I’ve personally found the bouncing bewbs thing to be a nevermind situation – I’m not particularly fussed if someone out there has parts of me madly boinging up and down to aid their visual jollies in a TP, but at least here, as a clothing layer, I retain full control of what is seen. This alone means there should be less screaming from people in terms of sexist attitudes or degrading the female form, as we’ve had in the past.
At the end of the day, if bouncy bits are fun to have and further mimic what we get in real life (well, if not taken to extremes), then well done to LL for finally jumping on the band wagon!
In the meantime – and with grateful thanks to Opensource Obscure, here’s a fun little video marking the soon-to-arrive features, currently available in Snowstorm.
On the 16th March, Linden Lab pushed a new version of Viewer 2 into a Development release. Version 2.6.1.223988 has two modes associated with it: “Advanced” – the Viewer we are all now familiar with, and “Basic” – a version with a trimmed-down feature-set designed to get new users familiar with the Viewer and UI.
I downloaded a copy of the Viewer (thanks, Ann!), and took it for a spin. Here’s what I found.
Installation and Start-up
Installation is as you’d expect from a Second Life Viewer: simple and direct. Given this is a Development copy, it goes into its own folder, but be warned: the Viewer appears to use the same folders for caches, etc., as the Release version.
On starting the Viewer however, there is an immediate difference: the splash screen now has an additional button, which allows you to set the default mode of the Viewer – either BASIC or ADVANCED, with the former selected by default following installation.
The new Mode button
Toggling between the two modes is a little clumsy: you have to select the alternate mode, then quit the Viewer (you are prompted to do so) before manually re-starting. This shouldn’t be too much of an issue for those moving up from Basic to Advanced, but it would still be nice to see the re-start handled automatically: confirm your wish to quit and have the Viewer resume without you having to go find the icon and clicking on it once more.
The User Interface
Once the Viewer is started, things get interesting. For a start, there is no menu bar at the top of the screen, nor are there any options available to display one, or the Favourites bar by right-clicking up there. Instead, there is just the address bar and the media play / pause button and the volume control.
There is also no Sidebar.
The button bar at the bottom of the screen also demonstrates noticeable differences. The familiar chat box, Gesture and View buttons are there, everything else is somewhat different.
The Basic Mode Button bar
Replacing Speak (the Basic Mode does not support Voice), Move and Snapshot buttons, the new user has a range of function-specific buttons:
Destinations
Opens up a full-width window across the bottom of the UI, displaying all the major destination categories, thus:
The Destination window
Click on a category, and a new set of options is displayed, complete with a Browser-analogous “back” option to get back to preceding views. Clicking on an actual destination will teleport the user there – something that is potentially a little disconcerting the first time it happens, as there is no pop-up to warn the users as to what is about to happen; the screen simply blanks to the black teleport screen. Given there is no World Map or search function, the Destination button is pretty much the only way of getting around the Grid with the Basic mode.
My Avatar
Opens up a full-width window in much the same way as Destinations, but this one featuring a range of avatar looks, defined both in terms of ethnicity and dress style
The My Avatar window
Clicking on an avatar option will automatically drive the user’s appearance and clothing to change to the selected option – again, a very clean, easy way for new users to quickly change their look and style to something they are happier with. Given there is no way to edit appearance, or get to any form of Inventory, it is also the only way to change an avatar’s appearance.
People
Opens up a compact form of the People tab from the more familiar Viewer 2 sidebar. Most of the functionality here is the same as for the full Viewer, other than the options found under the Tools “cogwheel” icon. This has been simplified to have only the View Profile, Add Friend, IM, Teleport and Block, Report and Zoom In options.
Profile
Opens up the Viewer Browser to display the avatar’s profile.
How To
This is potentially the most useful button for new users, and is well-presented for what it does. As the name implies, it presents a series of what I’d call “cue cards” on how to perform basic tasks: walking, talking, starting an IM, flying, changing the user’s view, using the keyboard to change the view, and using the Destination and Avatar buttons.
Options can either be paged through using the intuitive “>” and “<” buttons, or by clicking on the top menu and selecting an option from the drop-down list.
Two of the How To button “cue cards”
In-world Interactions
In terms of in-world interactions, the Basic Mode of the Viewer functions pretty much as with the “full” Viewer, but with a reduced option set; as one might expect, there are no options to build or edit objects, for example. However, there are also some nice touches: left-click on the centre of another avatar, for example, and a blue dot is displayed. Release the mouse button and your avatar walks directly to them (although this can cause a few bumps and shoves if the route is not clear between the two avatars!).
Right-clicking on another avatar displays a simplified menu, comprising View Profile, Add Friend and IM, and the Block, Report and Zoom In options. Simply pointing at another avatar displays the familiar name pop-up and “information” symbol that in turn leads to their “mini-Profile” and IM / Profile / options buttons.
Similarly, right-clicking on an object provides a four-function menu comprising: Sit Here, Stand Up, Zoom In and Touch. The last displays any menu associated with the object (providing the menu is contained in the root prim, obviously).
One further thing that is glaringly absent from the Basic mode UI and in-world interactions, is that the user has no ability to either purchase Linden Dollars or make purchases. Given this is designed to be a basic introduction to Second Life, one can understand why such options have been left out. However, while “Shopping” itself is not included as a category in the Destination options, the new user isn’t going to travel far before they do encounter opportunities to buy things – and the fact that they can’t using the Basic mode could see it being abandoned before it has served its purpose.
Impressions and Thoughts
As a first-cut “introductory” Viewer, the Basic mode is not that bad; it offers what is essentially a point-and-click approach to finding your way around in-world – something that pundits have been crying out for – while at the same time presenting a relatively clean and easy-to-follow user interface that will help the new user gain familiarity with the basic functionality of the Viewer as a whole.
The Destinations button is particularly useful in getting new users out and about, again given there is now search or world map; while the avatar button makes it relatively easy to change looks – albeit it with shape as well.
However, while the How To button and “cue cards” have been well laid-out, one cannot help but think they would benefit from a few more items: how to jump, a quick explanation of left and right clicking on objects, etc., just for those that are nervous about simply diving in and click all over the place. Similar, a brief overview of common terms would not go amiss: what is a Profile? What is the “cogwheel” button? What does “Report” mean? And “Block”? “How do I unblock someone I blocked by mistake?”
Another concern is that while the Basic mode is very good as a first look, the step up to the “full” version of the Viewer is nevertheless huge. It would be useful if, on first detecting the mode has been changed, the Viewer itself could direct the use to the Quick Start Guide and offer the new user a smoother transition from Basic to Advanced modes. This would be invaluable, given the fact that core elements of functioning in Second Life – inventory, search – are completely absent from the Basic mode, and as such, liable to leave the user somewhat confused.
Finally, and given the recent RedZone situation, and the fact that devices like it are still very much in operation in-world, one would prefer to see the Viewer start-up in either Basic or Advanced modes with the media turned off – together with a How To “cue card” on how to turn it on. It would also be nice to see the Media Filter included as a part of the Basic Viewer, again with a simple “cue card” guide.
These points aside, the Basic mode is a good first step for users entering Second Life for the first time. Even the lack of any ability to buy things can be forgiven, despite my earlier reservations; it provides enough impetus for people to find their feet in SL and get the basics under their belt. Certainly, given this is only a first look, there doubtless can and will be opportunities to tweak it as people coming into SL are exposed to it, in order to ensure it does adequately meet the needs of new users.
Kudos to the team who have been working on it!
If you wish to have a look yourself, the Development version can be found here.
It went unannounced and pretty much unnoticed – except possibly by Boy Lane.
The end of the official Viewer 1.x moved a step closer mid-February, when both it and Snowglobe were removed from the official Viewer download page.
LL have apparently informed TPV developers that the date they officially stop supporting Viewer 1.x hasn’t been agreed as yet, but this move suggests it is drawing closer.
One year ago today Linden Lab finally launched Viewer 2. I say “finally” because the project was originally called “Viewer 2009”, and was running several months late to warrant that name; however, the more accurate definition might have been “prematurely”.
Reactions to the launch announcement were fairly mixed. Leaving aside the fact that generally, people don’t react well to change and all bar the freshest of new users were very, very grounded in Viewer 1.x – so Viewer 2 was going to have an uphill battle to start with, no matter what functionality it offered – it was fairly clear there were issues with the Viewer. Issues that went beyond people’s personal likes / dislikes in terms of UI; things simply didn’t work – and basic things at that. Worse, some decisions had been made concerning the interface that made common tasks a lot more obscure – such as the lack of any CREATE option in the initial Context menus, as well a terms – such as APPEARANCE – meaning different things depending on where you encountered them within the Viewer. There were other issues as well – basic usability issue that should have been more comprehensively considered prior to simply springing the Viewer on an unsuspecting audience, as I commented on at the time.
The biggest criticism concerning Viewer 2 – other than it apparently having been developed by people who spent very little time actively in-world – was no so much that it wasn’t ready for prime time (it was in fairness launched as a “beta”, and therefore was expected to have rough edges), but rather that for a time it appeared as if Linden Lab were not prepared to accept any form of criticism for the major faults within the Viewer, be they technical or with usability. For example, repeated complaints concerning the way the Sidebar both violently interfered with the world view and took up far too much screen real estate were ignored until well after Kristenlee Cinquetti’s S20 hybrid demonstrated just how easy it would be to make this feature both less intrusive and less jarring on the eye.
Beyond this there were security issues with the Viewer raised from day one relating to media usage which are – even now – entirely unresolved. And while it is true to say these vulnerabilities existed in Viewer 1.x – the situation with Viewer 2 is a lot worse, given the way the Viewer has been set-up to enable shared media and the like. Indeed, these issues are currently the focus of much concern among the user community because of the way they are being abused – and rightly so – and that LL apparently considered and dismissed them from the outset in their desire to push ahead with media sharing within the Viewer, has always been something of a bone of contention.
Indeed, such is the situation at the moment that these issues look set to overshadow any celebrations around the launch of Viewer 2. In some respects a shame because – to be fair – it cannot be denied that in many areas, the five iterations we’ve had with the Viewer since its launch have seen significant improvements made on many fronts, such that many early negative issues with the Viewer have (however grudgingly on the part of LL) now been eradicated.
Speaking as one who has taken the time to get to know Viewer 2 through its various iterations, I do appreciate the effort that has been put into it since the premature launch a year ago. However: and here’s the rub – it is still not a Viewer I will use full-time.
This is not because I refuse to learn the new interface – far from it, or that I simply “hate” the Sidebar. I’ve learned the essentials of using Viewer 2 by spending time with with it, with Kirstenlee’s S20 and S21 and with Firestorm; so actually finding my way around the Viewer isn’t an issue: I actually have no preference for pie menus over context menus (both work fine for me) or anything else of this ilk.
No, the reason I won’t use Viewer 2 is that compared to the likes of Kirstenlee’s hybrids and even the “pre-alpha” Firestorm, and despite the improvements made, it is still far too incongruous and intrusive; rather than form a part of my world-view, it remains something that sits between me and whatever I’m, and making its presence felt, rather than remaining largely invisible to me.
Oddly, this is something I don’t find so much with Viewer 2 TPVs like Kirstenlee’s and Firestorm, both of which – while resembling Viewer 2 – offer a flexibility in use that far exceeds anything seen within either Viewer 2 or Viewer 1.x. In this, the developers have shown themselves to be far more responsive to user feedback than Linden Lab has demonstrated in a very long time.
Beyond this, there is the question of information security. The Client Detection System farrago is not going to go away; and while it is true that the answer does not only reside in a technical solution – we need, as has been stated previously a policy to resolve these issues once and for all – the fact remains that it is through technical approach that people are going to feel more comfortable. As reported, one solution is already on its way. As such, the first Viewer 2 TPV that can offer the same options and capabilities is going to gain my support and adoption at least until Linden Lab demonstrate that user privacy is a genuine matter of concern for them, and provide similar technical capabilities as well as a decent policy on these matters.
Doubtless, there will be other issues along the way that will affect things like security and privacy. But as long as Linden Lab respond to them be either going entirely dark (rather than even give a simple, “We hear your concerns, and we are looking into things and will get back to you”), or by becoming somewhat hostile towards concerns (such as by threatening to revoke JIRA privileges), I will always sway towards a Viewer that, when combined with my own common sense, will help me minimise my exposure to situations where people opt to exploit the Viewer code for their own questionable ends.
And, I rather suspect, such matters will cut to the overall take-up of Viewer 2 compared to TPVs as Viewer 1.x code is wound down and deprecated.
In May of last year, I reported on the initial steps that would see the eventual loss of Viewer 1.23.x as we know it.
That the depreciation had started – and would take a goodly while to complete, admittedly – caused one Third Party Viewer creator to get a little out of his tree, threatening to AR me to Linden Lab for “spreading lies”, and also to submit a “defamation” report against me with WordPress!
Anyway…it now appears that the first major step to ending Viewer 1.23 from effectively working on the Main Grid will be taken some time in Quarter 2 of 2011 (although this has yet to be precisely confirmed by Linden Lab).
The news came to light in a Phoenix Viewer office hour on the 11th January (the transcript from which I missed at the time). To whit:
Linden Labs has announced that they will be blocking search, server-side, for the Viewer 1.x viewer, effectively making all Viewer 1.x useless for search, and effectively forcing users to move over to the Viewer 2x viewer (allowing Linden Labs to move forward with features that are not compatible with the 1.x viewers). That gives the Phoenix team 3 or 4 months to get Firestorm ready for delivery… [Addendum: To be clear… We were notified of the intention to turn off viewer 1.x search capability during a meeting between LL and approved Third Party Viewers. This information was provided to us as a means to help us prepare for what the future holds for existing 1.x viewers. Linden Lab has not officially announced this yet, and you can be sure that they WILL announce it well ahead of time and give everyone ample notice. We are told that the Lab will stop support for their 1.23 viewer before search in 1.x viewers is turned off….]
This announcement has been reported on at SLU, where it has been met with a mixed response. Elsewhere, the news has also meet with opposition – and one has to say that the concerns and critiques are somewhat justified.
However, is this really a bad thing? While it is true that Search in Viewer 2 is far from perfect, and still needs considerable work (not least shown by the fact that each new release of Viewer 2 seems to operate slightly differently with regards to search, and people have been commenting on this and getting frustrated about it in the official forums for a while) – the fact remains that Linden Lab cannot maintain two code bases indefinitely, and Viewer 2 already embeds a lot of functionality that Viewer 1.23 cannot support without more work than Linden Lab can afford to give, even were they so minded.
Ergo, things have to change, and as such, the end of Viewer 1.23 and its derivatives was and is only a matter of time. And let’s be fair: Viewer 2, while it still has warts, has come a considerable way in the last 12 months. While one could argue that in doing so, it could have benefited if, for part of that time it had remained in a more rigorous closed Beta testing environment in which perhaps more user feedback which was then acted upon, the Viewer would be now be enjoying a far greater degree of popularity among users than is currently the case; the point is now moot. Viewer 2.5 and the 2.5 Beta are a long way removed from the original, and time and effort has been invested by a lot of people both within and without Linden Lab – and they deserve thanks.
Again, the demise of 1.23 later this year shouldn’t be a surprise to anyone. The likes of the Phoenix and Imprudence teams have been beavering away with their own Viewer 2 based products, Firestorm and Kokua since around November of last year because of this very fact.
Of course, one could argue that “breaking” search in 1.23 is a lot different to “depreciating” the Viewer – but is it? The end result is the same.
While “breaking” – or more correctly – blocking search for 1.23 is perhaps a little unsubtle in some respects (rightly or wrongly, the perception(note the emphasis!) is that search is “working” in 1.23, and “not working in Viewer 2.x), it shouldn’t be seen as a negative. As some on the SLU thread point out, it clears the way for LL to focus down more thoroughly on Viewer 2 and its good and bad points.
Yes, Search in Viewer 2 still need work – but again, as many have pointed out to those raising a hoo-haw over this move: Search in Viewer 2 does work; just not in all cases. LL is fighting hard against people gaming the system – and in the areas where people complaining about it “not working”, it tends to be the most gaming goes on (such as with land and the like). In other areas, things are a lot better, and merchants and users alike are encountering fewer problems.
However, given that Search on Viewer 2 is still being worked upon, and may people do rely on Search in many ways, one hopes that the “turn off” date for Viewer 1.23’s access to search is not something that will be viewed as “stopping the train” if it is delayed. If we reach the date and it is widely acknowledged by the users who have to make use of it that Search in Viewer 2 still needs important work – LL will delay the switch-off.
Unless, of course, Firestorm and Kokua (and whoever else is going down this route) have rolled out and wooed all those still “anti” Viewer 2 on the grounds of its awkward UI – which is likely to be the case. Providing they do, I have a sneaking suspicion that many won’t even notice any Search issues. They’ll have a Viewer with a UI they like (aka one without a sidebar and with a better approach to chat windows / chicklets / toasties – whatever cute name you give them) – and so on, and won’t be worried about Search.
With the news of Esbee’s forthcoming departure since spreading, Viewer 2.5, recently promised by Frank (FJ Linden) Ambrose is rolled out a “Beta” to trumpeting by Q Linden.
Chief among the list of features in this iteration is the new web-based profile feature. I’ve already reported on this, and I like the fact that, in 1.23.x viewers at least, we get the best of both worlds – a web page Profile and the familiar in-world Profile window. Changes to one are automatically reflected in the other – neat.
However, in Viewer 2.5, it seems things are to be somewhat different: the web page Profile actually replaces the in-world Profile in the sidebar (clicking on Profile now apparently pops-up the built-in browser to display the web Profile). While this overcomes the somewhat ugly and limited Profile display found in the Viewer 2 sidebar, it’s not entirely ideal.
However, this isn’t the biggest issue with the new Profile option. People have already commented on the fact that it includes options to link to Facebook and Twitter – and people commenting on the release are also raising objections about the fact that others can click on the included buttons and add Profiles for SL avatars to their Facebook pages.
Me? I’m failing to see the problem. I’m sure there are those in SL who use Facebook, Twitter and LinkedIn who will find such options a delight and welcome addition. For those who don’t, I tend to say, “so what?” Why get all het up about it? I personally don’t use Facebook, so I won’t be linking anything from anyone to anywhere. I don’t even care if Joe Schmoe or Patty Pattacake out in Facebook land link my SL Profile to their Facebook pages because it doesn’t affect me in the slightest. There is nothing within my SL Profile that allows anyone to beat a path to my RL front door; so if Joe or Patty want to claim Inara as their friend – good for them. I’ve never been someone’s imaginary friend before – the experience might be fun.
And that’s assuming there are people out in Facebook land who are going to go clicky-happy when they happen to stumble upon SL avatar profiles – or worse, say nasty things about us! In sort, where this particular problem is concerned, people really should get over themselves. Now, had the new feature forced us all into Facebook land, then I’d understand (and be a part of) the outcry; as it stands, “mountain” and “molehill” are words that spring to mind.
What I do find telling about this release is that it has been pushed out the door by LL despite the fact this much-heralded feature has an irritating bug sitting in it – which is this: it doesn’t exactly work.
Those using Internet Explorer stand to be OK. But people using Chrome or Firefox or Safari, etc., are all reporting issues – specifically “SSL Handshake Failure”. This is due to the fact that the software requires a security certificate in order to function, and the only way to get that certificate until the Viewer is patched (2.5 Beta 2) is to run Internet Explorer and access a profile…
It’s not a major bug – but many people don’t use Internet Explorer. It’s not liked. Period. Linden Lab know this – just look at the kurfuffles surrounding the release of the “new” forum software, which originally only ran “properly” on Internet Explorer (and which today still doesn’t display all posts in a thread in browsers like Chrome…) users of other browsers weren’t exactly shy in giving vent to their frustrations – and rightly so. Given this problem was discovered before 2.5 Beta 1 was released, one has to ask why was the software still pushed out the door? Why the all-fired rush?
Would waiting just a day or two (or even a week) to get the patch sorted really have hurt that much?
I don’t use Viewer 2 – I’m a Phoenix / KLee Viewer user – so something like this doesn’t really affect me per se – and yet it does; simply because it is indicative that LL, rather than being focused on stability, usability and the like are still focused primarily on dates on the calendar and ticking boxes – something Philip R himself said back at SLCC they’d “gotten wrong” and would be “fixed”.
Inara Pey: Living in a Modemworld 