Category: Viewers

Viewer 3 new UI: first looks

Posted on by Inara Pey

The first phase of the new UI has arrived as a Development Viewer release (3.2.1 (243328)). So what do we have in store?

No Modes

Well, actually, quite a lot, and it’s obvious right from the login screen, where the absence of the BASIC and ADVANCED modes is clear.

No mode options!

Once logged-in, more differences make themselves immediately felt:

  • The top of the UI has been revised so that the Navigation and Favourites bars have been combined, with a slider between the two allowing you to adjust their sizes relative to one another
  • There is a new button up on the Menu Bar I’ll return to shortly
  • There are no Sidebar tabs visible on the right of the screen
  • There is no chat bar at the bottom of the screen
  • There are two sets of buttons visible: one on the left, featuring icons only (by default), and one at the centre bottom of the screen, featuring text and icons (by default).
The default UI on logging-in

If you want to type, you can either click the CHAT button on the bottom toolbar, select NEARBY CHAT from the COMMUNICATE menu (as per previous versions of the Viewer) or, in a move that follows V1 behaviour, tap ENTER. All three options will display the chat bar in its own repositionable floater.

Buttons, Buttons, Buttons

As there are a lot of them, let’s start with the buttons – most of which should be perfectly obvious.

On the left of the screen, we have by default, seven buttons. These are: Avatar, Appearance, Inventory, Search, Places Map, Nearby Voice and Mini-map. All of these will be familiar to V2/V3 users. They perform the same functions as in earlier releases of the Viewer; although in the case of Appearance, Inventory and Places, rather than opening them in the Sidebar, the buttons open the Appearance (outfit), Inventory and Places panels in their own floaters.

I have to admit, Mini-map had me fooled for a moment – the button’s icon suggests it is something to do with Voice.

Only Avatar is a new button here, lifted directly out of the BASIC mode. Clicking it opens up  floater than enables you to pick an entire avatar look – shape, skin, clothes, etc. Four types of avatar are provided with the development release: human, animal, robot and vehicle. One suspects further choices (such as other races) will be added in time.

At the bottom of the UI is the more familiar toolbar with the following options: Chat, Speak, Destinations, People, Profile, View, Move and How To.

Of these, Chat enables the chat floater, as described above, while Speak, View and Move do exactly what they did in previous releases of the Viewer. People and Profile display the People and Profile panels from the Sidebar, now in their own floaters, leaving Destinations and How To.

Both of these will be familiar to those who have tried the BASIC mode: Destinations displays a mini Destination Guide floater, with destinations split into categories: What’s Hot Now, Chat, Newcomer, popular Places, and so on.

Destinations Floater
How To

How To is something I’d speculated / hoped would be carried over from the BASIC mode as a part of the merge. I was a big fan of How To when it made its debut in the BASIC mode, as it is a simple, easy to use “cue-card” system for obtaining help, especially for those new to SL. If I’m honest, it is something I banged on at Rodvik about back when it first appeared, I was that enthusiastic about it, so I’m really pleased it has come up into the revised UI.

True, I’d personally like to see the range of topics it covers increased (without going completely overboard), but perhaps further topics will be added over time.

Within How To, the GET LIVE HELP option is new – it wasn’t in the BASIC mode. At first my oldbie heart soared on seeing it, as it seemed to herald the return of the long-gone and sadly lamented Live Help as used to be in Viewer 1.x.

Sadly, this is not the case. Selecting the option displays this message:

“Need help?

“Click the button below to teleport to a Help location where a Second Life guide is available to assist you between the hours of 10am – 6pm PST.”

Beneath it is a TELEPORT button, which in turn opens the Places floater, from which you should, in theory, be able to teleport to a suitable help location. Quite what or where this help location is and who staffs it (one assumes resident volunteers) is unknown. I’m not sure if it is because I tried the option after 18:00 SLT or simply that the function isn’t working as yet – but Places came up a blank, leaving me nowhere to teleport.

So, back to the buttons…

Looking at the layout, one might end up thinking that all LL have actually done is swapped a set of ugly tabs and screen-hogging slidey Sidebar and replaced them with a set of buttons on the left of the screen.

And one would be entirely wrong. Why? Because these buttons are movable buttons. Not only that, they are customisable (to a degree). For example, right-click on any of the sets of buttons and a prop-up displays a menu with the options CHOOSE BUTTONS, ICONS AND LABELS and ICONS ONLY.

The latter two options allow you to switch between displaying the buttons with icons only (as is the case by default with the buttons on the left side of the screen) or with an icon and text (as is the case with the buttons on the bottom of the screen). But it is when you select CHOOSE BUTTONS that things start to get interesting, because this displays a Button Toolbox floater (which can also be accessed via CTRL-T or the TOOLBARS option of the ME menu).

Button Toolbox

This contains all the buttons available to you within the UI. Any buttons that you haven’t yet used are highlighted for easy identification. Note here, as well, that there are a few new buttons to play with, notably ABOUT LAND, PICKS AND PREFERENCES (yes, you can now have one-click access to the Viewer Preferences!).

To add a button to your UI simply position the mouse pointer over it, click and hold the LEFT mouse button and drag the button from the toolbox.

As you do this, you’ll notice the border on three sides of the Viewer turns blue, indicating you can position the button either on the left, bottom or right side of the screen. Nor does it end there.

You can also move buttons between locations (left side, right side and bottom of the screen) using the same method: simply left-click and hold over each button you wish to move in turn, and drag it to your preferred location. Thus, it is perfectly possible to have all your buttons placed at the bottom of the screen a-la V1, or you can split your buttons between the bottom and right of the screen, a-la a “traditional” V2 style.

You choose where the buttons go

Continue reading “Viewer 3 new UI: first looks” →

Viewer UI: Rhett gives a little more information

Posted on by Inara Pey

Tateru Nino carries some news relating to the initial changes to the official Viewer UI, obtained courtesy of Rhett Linden.

Rhett’s revelations, while interesting reading, are not entirely earth-shattering, and don’t actually go that much beyond what Rod Humble himself has already said concerning the Viewer, and what some of us were speculating as a result.

In a nutshell, Rhett has confirmed:

  • The Sidebar is to go. This is something that wasn’t hard to guess at, given Rod himself said as much at SLCC 2011
  • There is to be a more flexible approach to the UI in general, that will allow users to, “Arrange the UI to fit the way they use Second Life.  This is important because it moves us toward a model more like most creative software“

This latter point more than likely refers to things like the “Customise Toolbars” and the “FUI” (which people have taken to mean “Flexible User Interface”), both of which are mentioned in passing / hinted at in the SL Helpfile wiki pages (although no specific information is available on either right now). Certainly, the release notes for the merge (see below) point in this direction as well.

What is worthy of note is that Rhett confirms that the initial code for the UI changes, which should also see the arrival of things like click-to-move and the new camera palette (again as revealed by Rod Humble, this time talking on the SL Universe forum), was merged into the Development Viewer code today – although TPV developers had been expecting as much, going on comments passed elsewhere during the day.

For those planning on trying out the latest development Viewer, be aware that the release notes state:

  • The Viewer floater camera views and presets do not work
  • The Nearby Voice panel does not update to a new call or from nearby voice info once opened
  • Viewer crashes when updating UI size in preferences
  • The Speak button is activated when dragging and dropping between toolbars and/or moving back to the toolbox
  • Viewer crash when moving the speak button from one toolbar to another when there is an active call request
  • Teleport history doesn’t display visited locations
  • Viewer crash when double-clicking the mini-map in People > Nearby
  • Notification and conversation chiclets overlap
  • WASD controls don’t move avatar while move floater is in focus
  • Closing voice controls while a group or p2p call also closes the group call / IM window
  • Viewer crash after teleport
  • Hitting back in the ‘Create Group’ panel or ‘Blocked’ panel requires multiple clicks for action to occur.

Singularity Viewer gets mesh rendering

Posted on by Inara Pey

An experimental release of the popular V1-based Singularity Viewer was made today – version 1.6.0 (0). According to the blog post accompanying the release, it has been four months in development, and most of the changes are under-the-hood, with the team acknowledging they still have a lot of work to do in some areas. However – the exciting news for Singularity user (and for those who prefer using V1-style Viewers as a whole) is that the release includes mesh rendering.

Currently the release is only available for Windows users – and requires systems running SSE2. Work is underway on a release for Linux, which is listed as “It’ll be here soon!”. However, Mac users may have a longer wait in store, as the download page states: “There are serious bugs affecting OS X in current codebase and also present in Linden V3 codebase. So far there is no known solution“.

So, how does this Windows release look and handle?

Installation and First Run

Given this is an experimental release, it is recommended that previous versions of Singularity are removed prior to installing 1.6.0. (0), or that you install it in an entirely separate folder hierarchy. I opted for the second option, and following the download and scan of the regularly sized .EXE file (22Mb), installed the new release into a folder I called “Singularity-Mesh”.

Starting the Viewer brought with it a surprise: up popped the “new” V3 login screen from LL with the Destination Guide, etc. This is the first time I’ve seen this login screen appear in a V1-based Viewer and as such, the Singularity team deserve double kudos; both for being the first, and for actively using the screen. It’s a massively useful feature for both old and new SL users  – particularly when you want to get to a noted event fast (as I’ve done myself several times even if it has meant using V3 in preference to Firestorm).

Singularity uses the “new” LL login screen

Once logged-in, you’re presented with the familiar (or in my case nowadays – not so familiar!) V1 UI in Singularity’s stylish charcoal grey / black. Don’t expect any obvious updates or changes here in terms of menu options and Preferences options; again, as the release notes state, most of the changes with this release are under-the-hood.

However, one change that is obvious (for those that use it) is with the Grid Manager (accessed via the login screen or via PREFERNCES -> GRIDS). In most V1 Viewers including older versions of Singularity, opening the Grid Manager would display the full information relating to the grid you are / will be logged-in to (below left).

Grid Manager changes: old (left) and new (right) – but no GET GRID INFO button

With Singularity 1.6.0. (0), a cleaner, summary page is displayed (above right). To access detailed information for a specific grid, one needs to lick on the ADVANCED tab, near the top of the floater.

This is regarded as an experimental Grid Manager, which includes megaregion support for OpenSim. However, it is missing a critical element: there is no GET GRID INFO button in either the ADD or the AdVANCED tabs. Thus, there is currently no way to fetch information relating to a grid (login page URI, etc.) on the basis of the grid name and URL. Instead, all additional information has to be manually typed-in (assuming you have it to hand).

This is something of a major oversight for those of us who do jump between grids – particularly given the button was present on earlier Singularity releases. Hopefully it will be back in an update.

Mesh Rendering

However, it is mesh that will be tweaking most people’s interest, and in this area, the Viewer is flawless in its ability to render mesh objects. A nice touch is that “Prim Equivalence” and “PE” have been abandoned in the Edit menu floater when viewing mesh objects, and replaced with a simple “Cost”. This should cause less confusion for users who still get caught between “Prims” and “Prim Equivalency” and also allow the Viewer code to easily be tweaked to read “Impact” once LL’s “Land Impact” approach becomes widely adopted.

There is no mesh upload tool at present, but apparently work on an uploader for V1 Viewers is underway on several fronts.

Other Noteworthy Bits

As those familiar with Singularity know, it includes much of the functionality found within Phoenix and other V1 TPVs. Radar, client-side AO, media filters, quick preferences, command line support (“/dd” for draw distance, etc), some shield options, and so on, so I’m not going to delve into these. However, a few things are worthy of note in terms of the “haves” and “have nots”:

  • RLVais updated to the latest release. When using the Viewer, remember:
    • RLVa is turned on by default in Singularity, so there’s not need to go hunting for a Preferences or menu option to enable it, and no need to then log out / log back in
    • To disable RLVa, enable the ADVANCED menu, then click on RESTRAINEDLOVE API. A message will be displayed informing you RLVa will be disabled following a restart. Use the same procedure to re-enable
  • There is no support for MOAP, multiple clothing layers and region Windlight settings, but these are being worked on
  •  Other updates include:
    • Renderer updated to move from mixed-pipeline to shader-only pipeline on capable hardware, analogous to V3
    • Editor support for more LSL/OSSL functions
    • Additional Windlight presets
    • A texture fetch and bake bug fix
    • Improvements to the notecard editor
    • V3-style media browser

Performance

Overall, performance good, although obviously slightly down on the non-mesh version. On my usual test machine (Q6600 quad-core Intel at 2.4Ghz, Windows 7 32-bit with all service packs, 3Gb RAM, nVidia GE9800 GT with 1Gb RAM), Singularity 1.6.0 (0) clocked an average of 23-25fps on a sim with 4 others, compared with 36-38 fps on 1.5.10 (2) – graphics set to ULTRA on both as usual, and Draw distance set to 256m.

Enabling shadows did, unsurprisingly, cause a huge fall-off in FPS – down to an average of 4-5fps. I also had issues with some mesh objects which had Shininess enabled rendering as plain white objects with shadows active; something I’ve not encountered with other Viewers.

Overall, the new release performed very well, and easily matched anything other mesh-enabled V1 Viewers could achieve.

Singularity 1.6.0 (0) and Other Grids

As mentioned above, the experimental Grid Manager floater has an issue in that it lacks a GET GRID INFO button. However, once you’ve set-up accessing another grid, Singularity 1.6.0 (0) seems to work as smoothly as Imprudence. I skipped around InWorldz quite happily with in and dipped a toe into a couple of OpenSim grids without mishap. Frame rates in InWorldz matched those for Second Life, although the Viewer suffered the same issue I’ve had with others in relation to InWorldz – crashing on attempting to log out (this happens for me with Imprudence on InWorldz as well).

Opinion

A long-awaited and tidy update. Feature changes may appear small – but getting mesh rendering active is no trivial matter, and there are apparently in excess of 68,000 new lines of code within this release to enable it and take care of the other under-the-hood fixes and updates!

The release should go down well with Singularity users, the “experimental” tags not withstanding. Given Singularity also includes much that makes Phoenix popular it could prove to be a viable alternative for Phoenix users who want to get to see mesh now, but who don’t yet wish to make the jump to Firestorm or a V3 TPV.

Related Links

Kirstens Viewer: looking to Crowdfunder

Posted on by Inara Pey

Coming on top of yesterday’s tweet, there is good news for those who wish to see Kirsten’s Viewer continue.

Kirstenlee Cinquetti has announced that, following the outpouring of support for the Viewer, the team are going to try and obtain funding by going the Crowdfunder route.

In announcing the approach, Kirstenlee blogs:

Many of you have asked and wondered what the future would hold for the Viewer, well here is the answer..

After lots and lots of thought and quite a bit of behind the scenes activity we are going to go Crowdfunder!

The upshot of the whole deal is this, a target has been set to fund the entire project and it’s continued development for a period of one whole year. What happens remains to be seen, I can however reveal a few details of what does happen if we hit the target, and more critically what can occur if we exceed the funding target. If we seal the deal, almost instantly the binaries will become available for download the project will become active again and an updated and early build of S22 will become live.

If the funding target is achieved, it means that the binaries will be released once more, and work will immediately continue, with a list of juicy enhancements coming down the line over time:

  • Programmable camera positions
  • Enhanced photo making features
  • “Radical changes” to the user interface
  • Enhancements in the area of post processing and 3D vision

If the required funding level is exceeded, then the team will look into other aspects of Viewer development, such has obtaining a KDU licence, funding other developers, etc.

For those helping to fund the project, a special area of the Viewer’s website will be set up, providing preview access to builds and features, and where funders can vote on proposed new features and enhancements, etc. Rewards for funders will be based on their level of funding.

The project’s Crowdfunder page is now open. Using Crowdfunder is pretty much a win/win situation for all involved: if the target is reached, the project will go ahead; if the funding target isn’t reached, then money promised to the project will be refunded. So there’s no reason not to get involved!

Kirsten’s Viewer: announcement expected

Posted on by Inara Pey

At the start of September came news that Kirsten’s Viewer was effectively frozen as a result of Kirstenlee Cinquetti having to withdraw from the project in order to be better placed to care for partner Dawny Daviau.

While this news came a cause for regret, coupled with warm support for both Kirstenlee and Dawny, Hamlet Au put forward an intriguing idea to the community as to how the Viewer might survive. This resulted in a massive outpouring of further support for the Viewer, as evidenced in the KV blog, which prompted Jabba Aabye to post sincere thanks to all who had come forward, hinting that something may well be forthcoming, as he referred to the Viewer thus:

But there might be some light on the horizon. Tho it is not official yet, there is some hope growing it will work out and benefit all of us.

Not long after that post was made, I heard a rumour  – and I emphasise the word rumour – that there had been a further code commit for Kirsten’s Viewer. A check on the Kirsten’s Viewer SorceForge page revealed that, on the day Jabba made the announcement, a subversion of the Viewer code  – No. 1060 – was in fact committed. A total of 13 files were submitted to the SVN repository – most of which appear related to the forthcoming Direct Delivery mechanism / Inventory changes.

Obviously, the above is not indicative that there is about to be a further release of the Viewer; the commit could simply be related to placing work-in-progress into the repository pending the project being unfrozen at an unspecified point in the future.

However, earlier today, the following was sent out today via the Viewer’s Twitter account:

Given the upbeat tone of the Tweet (note the smiley), it would seem that some very welcome news may be in the offing where Kirsten’s Viewer is concerned, and the commit of the 22nd September may yet find its way into another release of the Viewer. Here’s to keeping fingers crossed that the forthcoming announcement carries some very good news.

Firestorm – an update on updates

Posted on by Inara Pey

firestorm-logoOn the 4th October, the Phoenix Hour was on-air and had a sort-of celebration for it’s first birthday, having first aired in 2010, and moved home in the interim. A belated happy birthday from me to Phalen, Jess and all the team who work on the show.

Support Groups

Jessica kicked-off the meat of the show with a warning about “unofficial” in-world Support Groups for Phoenix/Firestorm.There are a number of such Groups operating in-world, some of which have proven to be problematic for Phoenix and Firestorm users who have joined them in the mistaken belief that they are a part of the Phoenix / Firestorm team. In order to help people avoid similar issues in the future, Jessica reiterated that “official” support teams will always have either herself (Jessica Lyon) or Ed Merryman as a Founder and / or in the Ownership. As such, when looking to gain “official” support, users should only join these Groups.

Phalen Fairchild (l) and Jessica Lyon filming The Phoenix Hour

Firestorm Update

V1 Functionality

Firestorm has surpassed Linden Lab’s Viewer 2(/3) usage hours, which demonstrates the Viewer has a very strong uptake. However, adoption among existing Phoenix users remains an issue of concern. To overcome this, the team will be carrying out further work on the Phoenix mode log-in option for Firestorm:

  • The toolbar at the bottom of the screen will receive further work, possibly to include text rather than icons in the buttons to help make it look more like Phoenix
  • Phoenix / V1 chat bar behaviour is to be included in the mode:
    • V1 Auto-hiding of the chat bar will be included (Preferences option), so that when ENTER is hit, the chat bar will slide off to the left of the screen (rather than behind the toolbar buttons, as with V1 behaviour); pressing ENTER again will display the chat bat once more
    • Similarly, pressing ESC will hide the chat bar and allow the WASD keys to be used for avatar movement, a-la V1 behaviour. Pressing Enter will display the chat bar once more for text entry
    • A major source of complaint from V1 users coming into Firestorm has been the use of chiclets in the V2 code. The team are looking into an option for users to replace the chiclets with V1 style dialogue boxes if they wish. Firestorm does currently display script menus in the top right and also V1-style notices appearing in the lower right-hand corner – although they do not currently stay open – and the team are looking to enhance this

A further issue with adoption from V1 has been identified with the menu bar – which is clearly very different in V3 Viewers from V1.To assist people in transitioning to the new menu system, the team have started looking at ways in which the V1 style menus can temporarily displayed in Firestorm for a period of around 30 seconds at a time.

The idea behind this is not to replace the V3 menu system, but to help people orient themselves with the new menus – the capability can be used to quickly find & use options under the V1 menu system (such as uploading an image) – once an option has been used, the menu bar will revert to V3 style. In this way, people can find much-used options without frustration, while learning the new menu system at their own pace. While details are yet to be finalised, the capability will most likely be enabled through a button on Firestorm’s menu bar.

As Jessica stated in the show, the Team are trying to provide means by which V1 users find it easier to orient themselves to using Firestorm without impacting the team’s ability to keep pace with V3 developments coming out of Linden Lab. To achieve this the team must balance changes within the Viewer’s functionality with the ability to merge such changes with the code base coming out of the Lab.

Jessica also indicated that not all of the above changes will be implemented in the next Firestorm release, although the chat bar changes will be there (and gave the impression things like hiding the chat bar may be common to all three of the Viewer’s log-in modes).

General Updates

Away from V1 adoption issues, Jessica reported that:

  • Spell check is finished and will be in the next Firestorm release, there are just a couple of bugs to iron out
  • Mouselook has been updated (notably for combat users) to include:
    • The ability to see beacons in Mouselook
    • Mouselook zoom – press and hold the right mouse button and use the mouse scroll wheel to zoom in / out
    • The ability to display local chat and IM history
  • The current “chat echo” behaviour that sees anything typed into the chat bar being repeated in the Local Chat window (if open) and vice-versa, has been fixed, allowing different comments to be typed into each of the chat entry bars
  • Nicky Dasmijn has been working on the mesh uploader, and it looks very much as if this will be in the next release of Firestorm – there was some doubt as to whether it would be finished in time for the next release when Jessica last mentioned it in The Phoenix Hour
Mesh uploads coming to Firestorm (image from Viewer 3 for representative purposes)
  • Similarly, the inventory “jump” issue has been fixed by Kitty Barnett and will also be in the next Firestorm release
  • Notecard find & replace will be included, together with a number of fixes to the text editor, including, it would appear, the cursor placement issue
  • Radar is to made available as a floater in its own right, rather than as a part of the Nearby People Sidebar tab / floater – work has just started on this, so it may not be in the next release
  • Anti-spam controls are to be included in Firestorm – but it is unclear if these will be in the next release or not
  • There are a number of AO bug fixes, although at the time of the show (4th October), the issue of the AO turning itself off when you log-in was still unresolved

Code Contributions

Jessica raised the issue that Phoenix / Firestorm is in some ways viewed as the “giant” in Viewer development and as being somehow untouchable – which is far from the case. While the team does have an extensive support network for users, the development side is actually quite small (thirteen developers in total, only some of whom are able to commit large amounts of time to the project).

Therefore, rather than being large and untouchable, the team actually welcomes contributions from other developers that can be incorporated into the Viewer. Such contributions don’t have to by major new features or bug fixes, as Jessica stated:

“You may think that you’re not worthy, or you’re not good enough – but you are. Trust me. Even the littlest, smallest contributions you can provide are sometimes really big impact things Even just a typo that you find in the interface … and you can fix that easily and submit it to us … The thing is, I can put Aaron on a typo, and he’s going to spend 15-20 minutes on that typo; but that 15 minutes of Aaron’s time can be spent on really complicated things, and I’d rather keep him on the more [high] impact stuff, the complicated things that only he can do, than to put him onto something small. But if you can supply us [with] a patch, we can right-click, commit, give you credit for it and suddenly it’s fixed and it hasn’t taken us any time at all.”

Jessica then went on to outline the contributions that have come from a number of people – and other Viewers – that have helped to improve Firestorm, culminating in a further statement that Firestorm would not be where it is today without the efforts of a lot of contributors outside of the core team, “So if you have something in your Viewer that  improves your experience, I bet you it’s going to improve someone else’s. Send us a patch”.

Patches can be submitted via the Phoenix JIRA – you will require an account. There is also a mailing list available for developers and compilers to join. Note that this is not for asking questions on using the Viewer or for making suggestions for future features, etc – all of these should be handled through the usual support channels. The mailing list is purely for those actively engaged in Firestorm development, or who to assist in developing the Viewer (so it could be used to confirm whether or not someone is already working on fixing a particular bug or not, for example). Full credit for all patches / code used are given.

New Classes for Firestorm

There are new classes for Firestorm covering subjects such as troubleshooting, creating and using Contact Sets. Notification on these classes are provided through the  Phoenix / Firestorm Support Groups.

When Will the Release be Made?

There are a number of things still to be sorted as core issues prior to the next release of Firestorm.

  • As previously indicated, there are a number of issues inherited from Linden Lab within the code, and for which the team are still awaiting fixes from the Lab
  • Jessica would personally like to see the issues of settings reverting and the Viewer locking up as “not responding” periodically for some to be fixed prior to the next release

As such, there is still not given date for the next release – too much depends upon Linden Lab in many respects.

A further issue for the team are the recently announced changes to the Viewer UI that are to be forthcoming from Linden Lab.  At the time the show was recorded, little was known as to when these changes would start to be implemented by Linden Lab (or, in fact, what they would be), and Jessica was of the opinion that the team would likely release Firestorm prior to merging it with any UI updates coming out of LL.

However, given that some of these are now apparently due by the end of October (merging the Basic & Advanced modes, click-to-walk functionality, etc.), as indicated by Rodvik Linden speaking over on the SLU Forums, plans for Firestorm may have again been changed. As such, there is liable to be a further update on the release status for Firestorm at the next Phoenix Hour to take this particular matter into account, once more is known on LL’s plans.

Jessica was also unable to commit to supplying a date for the release of Phoenix with Mesh support. This has dependencies other than mesh (such as a complete update of the RLV system), which the team would like to see completed priority to making a further Phoenix release.

Finally, both Firestorm and Phoenix are also waiting on LL fixing the mesh-related OpenGL  issues and graphics issues that are currently being investigated by Runitai Linden.

The next Phoenix Hour is schedules for 14:00 SLT on Tuesday 18th October.