“When I’m sixty-four”: discussing the 64-bit version(s) of Firestorm

firestorm-logoOn October 18th, Jessica Lyon poked me about an upcoming blog post she was preparing for Firestorm which would make mention of a 64-bit Windows build, offering me the opportunity to talk to her about it ahead of the announcement going public.

At the time, my schedule was such that I couldn’t get back to Jessica immediately, so by the time we did get things worked out, the official blog post announcing both the team’s immediate plans for their next release and the arrival of 64-bit flavour of the viewer had been published. However, this didn’t stop me from taking the opportunity to sit down with Jessica and members of the team at the Cheeky Tiramisu Café late one afternoon in order to find out more about the promised “Firestorm 64”.

Meeting with some of the team: Miro (centre-left), Lassie, Ed, Whirly, and Jessica.
Meeting with some of the team: Miro (centre-left), Lassie, Ed, Whirly, and Jessica.

64-bit versions of SL viewers have been in demand for a considerable period of time. There has been some degree of resistance to them in the past, although there are a number of developers and self-compilers who have produced their own 64-bit versions of one viewer or another. The resistance has been for many reasons; Windows viewers are already Large Address Aware, for example, allowing them to use the additional memory common to computers using the 64-bit version of the operating system, thus helping to negate one of the biggest reasons for developing a 64-bit build.

Given that 64-bit builds have been seen as potentially problematic in the past, I started by asking what had prompted the Firestorm team to decide to go ahead with one.

“Our Windows 64-bit code was developed by Nicky Dasmijn as a sort of side project she wanted to do to scratch an itch she had,” Jessica informed me. Nicky, who started-out contributing code to the project, is now the project’s Lead Developer. Sadly, she’s also a little camera-shy as well, and managed to successfully escape my conversation with the team, hence why her profile picture appears here.

Nicky Dasmijn - Firestorm's Lead Dev and Win 64-bit coder
Nicky Dasmijn – Firestorm’s Lead Dev and Win 64-bit coder

Jessica went on, “None of us were expecting her to drop the code into the repo when she did; but since she did, and since we had already decided to do a public beta, I figured, ‘Why not? Let’s get it out there in alpha form to see public reaction, and to see what the cost versus benefit might be’, neither of which we know for sure yet.”

I noted that when discussing 64-bit viewer builds at a recent Firestorm Q&A, there were concerns from the team about potential issues with maintenance, such as bugs and additional regressions, and for how it might negatively impact support were they ever to try for 64-bit viewer versions. I wondered what else had changed, other than Nicky working on the code herself, to persuade the team to push ahead on the 64-bit front.

“The expectation is that the 64-bit version won’t have different bugs than the 32-bit,” Jessica replied. “In fact the hope is that it may have better performance and fewer crashes, which if true, should actually take some load off our support team. But we don’t know for sure as we’ve only tested it on a dozen or so computers.”

Miro, Lassie and Ed
Miro, Lassie and Ed

I wondered if trying to offer a 64-bit version of a viewer might be the proverbial catch-22 / can of worms situation: the viewer needs to be put to public use in order to see what the response to it is like, but if it is put into public use, it’s going to be awfully hard to prevent it becoming an accepted and expected version of the viewer.

“Well, the feedback will determine whether we move forward with it, but I think chances are good,” Jessica said, before giving me a wry smile, “As for the can of worms; yes, we’ve opened it, and we’re not going to be able to get those worms back in it now. Folks are going to want it, many will want it even if there is no noticeable benefit.

“But other TPV’s are also working on 64-bit windows too, I spoke to Latif [Khalifa] from Singularity and found out he also has coded up Windows 64-bit for them. So to add another metaphor to the mix: the cat is out of the bag, and x64 for Windows is going to happen with or without us, and due to user demand it will likely become a standard presence going forward.”

Whirly, Jessica and Cinder
Whirly, Jessica and Cinder

Continue reading ““When I’m sixty-four”: discussing the 64-bit version(s) of Firestorm”

CtrlAltStudio: Bringing the UI to your Oculus Rift

CAS-logoStrachan Ofarrel (Dave Rowe in RL), has issued an update to the experimental version of his CtrlAltStudio viewer with Oculus Rift support. It’s an update those with the Rift SDK and headset are likely to find interesting, as it includes some initial work on bringing the viewer’s UI to the Rift.

Version 1.1.0.34332 (Alpha 4 release) of CtrlAltStudio appeared on Wednesday October 23rd, and Strachan was kind enough to poke me about it.

It’s important to note that this is only a first pass at things, so if you have a headset, keep in mind what you see of the UI may change as Strachan  tweaks things further. Commenting on the work, Strachan himself says:

I originally wasn’t intending to do any UI as I thought Linden Lab’s viewer with Rift support would have been released by now, but it hasn’t been and there’s a pressing need for at least some UI so I’ve added some as a stop-gap measure.

The viewer UI in Oculus Rift: preliminary work undertaken by Strachan Ofarrel in CtrlAltStudio (image courtesy of Strachan OFarrel / David Rowe) – click to enlarge

There are some limitations with this first pass in that the menu bars and toolbars are not yet displayed in Riftlook, and for those who prefer the Pie menu, right clicking on in-world objects will only display the context menu (no Pie). Even so, this is an impressive start to the work of enabling the UI, and does much to increase people’s ability to interact with the world when using the Oculus Rift.

In order to use UI elements effectively with the headset, Strachan recommends users:

  • Turn on Show User Interface In Mouselook and Enable Context Menus In Mouselook (both under Preferences > Move & View > View)
  • Consider enabling Show Chat In Bubbles Above Avatars (Preferences > Chat > General).

He notes that with the above settings enabled, shortcuts can be used to show / hide dialogue boxes (e.g. CTRL-I for showing / hiding inventory), which again significantly adds to the usability of the viewer when in Riftlook. He also reminds people to use the cursor to left-click interact with windows and right-click interact with in-world objects, and that cursor movement can be defined / refined in Preferences > Graphics > Display Output.

The Display Output options for when Using Oculus Rift: note the new depth slider and the options to define / refine camera / cursor movement
The Display Output options for when Using Oculus Rift: note the new depth slider and the options to define / refine camera / cursor movement

As well as adding preliminary UI capabilities to Riftlook, this release of the CtrlAltStudio Alpha version also brings with it a range of updates and fixes, including:

  • Some adjustment of the depth at which the Riftlook UI is displayed
  • Enabling the display of avatar toasts and floating text in Riftlook
  • Esc in third-person Riftlook will return you to Riftlook first-person (instead of having to exit then re-enter Riftlook)
  • Esc in flycam Riftlook with SpaceNavigator will return you to Riftlook first-person
  • Entering / leaving stereoscopic 3D display mode now recorded in the program log
  • Work-around added to get stereoscopic 3D working with AMD Radeon on Windows
  • Added “–riftlook” command line parameter that toggles into Riftlook after a successful login
  • Fixed OpenSim “4096 bug” that limited the range of hypergrid teleporting
  • Fix to ensure view remains in Mouselook when TPing or when an alert dialog pops up, if UI is turned on in Mouselook
  • And more: please refer to the release notes for this version for a complete list of updates, changes and fixes, together with the correct attributions for those contributed by others.

Sadly, I don’t have the Oculus Rift SDK, so can’t speak first-hand has to how things look. So if you do have a headset, why not pop over to the CtrlAltStudio website and download this version of the viewer and take it for a test run? Strachan would doubtless appreciate all constructive feedback received!

At the time of writing, the viewer is only available for Windows, but the Mac OSX  version is promised soon – so be sure to check back with the CtrlAltStudio website if you’re a Mac user.

Related Links

Lab confirms “SL mobile” beta programme

secondlife

Update October 26th: As noted in the comments, it appears that the new client may be using the OnLive streaming service / application. This has been reported in a recent comment on the forum thread linked to in the article, and also in a further thread on the subject.

Linden Lab has been issuing an e-mail to a limited group of users inviting them to sign-up to be a part of a beta test for a Second Life client for mobile devices.

The e-mail, which has been popping-up in user’s in-boxes for the last day or so, reads:

We’re looking for enthusiastic beta testers to evaluate a version of Second Life designed for mobile devices.

Sound interesting? Then simply…

  1. Visit  [link removed] to create a FREE account with <link removed to be safe>, then
  2. Visit  [link removed] to complete a 5-minute questionnaire

You have to finish both steps to be considered for the beta.

We’ll email those selected when the program begins and check in periodically over the next couple of months to get their feedback. 

This is your opportunity to be among the first to try a new mobile version of Second Life, and we hope you’ll help us to make it a great product with your input.

Thank you for your consideration!

Linden Lab

Some concern had been raised on the SL forums as to whether the e-mail was genuine or not. While some were able to confirm it was indeed genuine. However, just to be clear, I contacted Peter Gray, the Lab’s Director of Global Communications, and to ask whether the Lab would be prepared to point to any specific platforms they’re looking at (iOS, Android, Windows Mobile, etc). He replied saying:

The email you’re referencing did indeed come from Linden Lab. The originating address is related to the system used to send the messages out, and there was initially an unfortunate problem with links, which has since been resolved.

It’s too soon to share details about this service that would bring Second Life to mobile devices (as you can see, we’re beginning a limited beta test), but we’re hoping that with the help of some enthusiastic beta testers, things may progress to a point where we can share more information with the community at large soon.

Do note that the beta programme is via invitation only; there is no public sign-up page available – so don’t go looking for one! Also, not all of those responding to the e-mail will necessarily be selected to participate in the programme.

Lumiya for Android has been the ground-breaking mobile client for Second Life and OpenSim since its launch at the end of 2011
Lumiya for Android has been the ground-breaking mobile client for Second Life and OpenSim since its launch at the end of 2011

Getting SL onto a mobile device has been a much demanded option. As I reported in April 2012, Comverse had a stab at getting SL onto the iPhone back in 2008, complete with graphics. Back then, it required an intervening server in place and didn’t get too much further than an initial proof-of-concept.

However, mobile devices have come some way in terms of power and capbilities, although until now all moves in the mobile arena have been left to third-parties, with text-focused clients such as LittleSight and Mobile Grid Client on the Android platform, and Pocket Metaverse on iOS, and of course the incredible Lumiya for Android with its rich graphical capabilities and which I routinely cover in these pages.

It’ll be interesting to see exactly what the Lab have put together, and the code they’ve used – home-built, or perhaps using something like Unity3D? Time will tell!

SL project updates week 43 (1): Server releases, interest list

Simulator UG meeting, Tuesday Octber 22nd, 2013
Simulator UG meeting, Tuesday October 22nd, 2013

Server Deployments – Week 43

As always, please refer to the week’s forum deployment thread for the latest news and updates.

Second Life Server (Main Channel) – Tuesday October 22nd

The Main channel was updated with the server maintenance project that was previously on all three RC channels.  The package includes:

  • A fix for “Group member access to parcels fails when ‘Sell passes to’ is enabled”
  • Fixes for two region crossing issues:
    • “‘Ghost’ avatars and vehicles sometimes appear to an observer at the sim border”
    • “Vehicles which exit a region with a passenger are incorrectly auto-returned and become ‘ghost shapes’ in the physics engine”
  • Extremely high Avatar Render Weights reported to the server are now capped at 500,000
  • A performance issue fix for avatar loading speed in the experimental ‘viewer-interesting’ viewer.

Second Life RC BlueSteel, RC Magnum, and RC LeTigre – Wednesday October 23rd

There are no updates planned for the three RC channels, as a result, there was no rolling restart across the RCs.

SL Viewer Updates

The Google Breakpad RC was removed from the viewer release cohorts at the end of week 42.

Interest List Viewer

The interest list RC viewer is once again delayed.  Commenting on it at the Simulator User Group meeting on Tuesday October 22nd, Andrew Linden indicated the hoped-for schedule for its appearance is before the end of the month, but there is something of a low confidence level in the estimate.

Apparently, there is still a performance issue to be dealt with (whether this is the same issue Richard linden mentioned in discussing the interest list viewer at the TPV developer meeting on Friday October 18th is unclear). Also, it seems that the recent issues of objects steadfastly refusing the render in the interest list viewer without a relog  – thhought to have been resolved in week 42 – have also regressed into the viewer code with recent builds.

The issue of prims failing to render in the Interest List viewer, as demonstrated by Whirly Fizzle in the images above and once thought to have been solved, has apparently returned to haunt the code in recent builds, helping to further delay the appearance of the viewer as a release candidate.

Andrew also clarified that the definition of objects which are cacheable by the viewer has been revised such that it is now objects which have not changed outward appearance or transformed in the last two minutes, rather than the one minute Richard Linden indicated, so as to allow for temp-on-rez objects (otherwise additional logic would have been required to check on these). The changes to the definition also mean that some scripted objects which have certain script calls in them, but which do not change appearance as a result of the calls, can also now be cached by the viewer.

As an adjunct to the interest list viewer discussion, Andrew indicated his “before / after” video for scene loading has received the “Torley treatment”, and the results are “impressive”. This is for the changes already implemented server-side, and which should already be visible to people without the Interest List viewer. There’s no date as to when this video may make its public debut.

Other Items

LSL Control for Materials

There have been renewed enquiries for the introduction of scripted control for materials. This has been requested in the past, and was always considered “out-of-scope” for the initial release of materials. A (further?) JIRA has been raised on the topic (MATBUG-359), but is light on suggestion on what might be required, etc.

Those Lindens attending the meeting (Andrew, Kelly and Simon) could see the advantages of extending LSL to handle materials (and Brooke Linden has indicated she feels the JIRA is a valid request). However, how best to achieve this, and the time-frame in which it might be achieved (not just in terms of a technical approach, but also in terms of the Lab’s internal priorities and workload) are unclear at this point.

Both and Andrew and Kelly felt that requiring the normal / specular maps to be in the object contents might be a means by which to both enable and constrain the use of LSL manipulation of materials because of the lack of permissions associated with UUIDs  and concerns of misuse. While no promises were made as to whether the work would proceed, Simon Linden suggested a further step would be to lay out a clearer proposed API and the exact behaviour required for manipulating materials via script. Andrew also indicated he has a “few” LSL calls to add, so he’ll try to take a look at the materials system o see how hard it would be to give script access to it.

llGetObjectDetails() and keyframe animation states

Simon Linden indicated that there has been some talk within the Lab of adding some new parameters to llGetObjectDetails() which would return an object’s keyframe animation states, so it would be possible to get the step number, state (paused, looping, ping-pong, etc.). Again, if / when this might appear is unclear; Simon appeared to be putting the idea out for feedback from the meeting attendees.

UKanDo a whole lot more with 3.6.8

logoConnor Monaron released an updated UKanDo viewer on Saturday October 20th. Version 3.6.8.27869 brings the viewer up-to-date with the latest viewer release code from the Lab, including the “hot fix” to prevent crashes for those using the latest AMD Catalyst drivers (13.9, 13.10, and 13.11), and adds a lot of useful nips, tucks, tweaks and additions.

Download and Installation

The Windows installer remains unchanged at 28.7 MB in size, and installation was, as with the first version of the viewer I reviewed, smooth and without incident.  I ran a completely clean install out of curiosity, and the viewer again installed without a hitch, and AVG Pro didn’t hiccup over things like the voice plugin, etc.

Improved UI

One of the things I found a little hard with UKanDo last time around was the UI colours. The white-text-on-blue-buttons was not always easy to read (for me, at least on my 1440×900 monitor). I’ve no idea if the issue was widespread, or if Connor felt the same, but 3.6.8.27869 sees buttons with black text / icons by default (text turns white when the button is active), which I do find easier on the eyes.

Buttons and Placement

Version 3.6.8 brings with it a couple of new buttons – Quick Tools and Area Search (both of which are looked-at below), and sees UKanDo gain improved toolbar button alignment. As with some other TPVs buttons on the bottom bar can now be ranged to the left or right, and buttons to the left or right of the screen can now be ranged to the top or bottom – kudos, Connor!

Quick Tools

UKanDo Quick Tools
UKanDo Quick Tools

This release brings with it a Quick Tools floater (and associated toolbar button), which is similar to the “Quick Prefs” floaters found in other TPVs, providing rapid access to things like Draw Distance, Bandwidth, Max Avatars, Particle Count, the Windlight presets and so on. The list of options isn’t as extensive as some TPVs provide, but what is here is more than enough to allow users to make rapid-fire adjustments to core settings when necessary – such as when operating in a crowded environment.

Also with this release, and found in the Quick Tools, as well as in Preferences > UKanDo > Miscellaneous, is the ability to set Windlight cross-fading when moving between different Windlight environments / changing Windlight settings.

 Area Search

Another popular TPV capability is that of area search: being able to locate a specific object within a region using a range of criteria – object name, creator name, etc.  This makes its debut in UKanDo version 3.6.8.27869, and is likely to be a welcome addition among users. It can be accessed either via a dedicated menu button or via the UKanDo menu or by pressing ALT-A.

Area Search comes to UKanDo
Area Search comes to UKanDo

Context Menu Updates

A couple of the context menus in UKanDo get updates as well. The right-click avatar context menu sees options added to copy an avatar’s name, UUID or Profile SLurl to the clipboard. Additionally, and in the case of estate owners / managers / parcel owners, the avatar context menu includes options to Freeze / Unfreeze and Eject / Ban where appropriate.

Options to copy an avatar's name, UUID or profile SLurl can now be found of the right-click avatar context menu (l) and context menu in the Nearby tab of the people floater (r). In addition, both menus can offer estate owners / managers / parcel owners options to freeze / eject avatars
Options to copy an avatar’s name, UUID or profile SLurl can now be found of the right-click avatar context menu (l) and context menu in the Nearby tab of the people floater (r). In addition, both menus can offer estate owners / managers / parcel owners options to freeze / eject avatars

These options are also available in the right-click context menu within the Nearby tab of the People floater (with the freeze / ban options only appearing for estate owners / managers / parcel owners).

Other Additions, Tweaks and Touches

  • RLV is updated to 2.8.5.8
  • Toolbar Buttons floater New “Close” button
  • World Map New “Clear Selection” button
  • Help->UKanDo Support Group menu option will either open the group profile or, if you are a member of the group, start group chat
  • Allow Media to Auto-play is defaulted to off
  •  Play Sounds from Gestures is defaulted to off
  • Option to allow Chiclet bar and/or Notifications to be placed top or bottom right
  • Viewer gives audible warning when trying to shift-drag while in edit linked parts/select face mode & object remains locked in place
  • Plus more – see the release notes

Feedback

Version 3.6.8.27869 represents a tidy set of updates and tweaks to UKanDo. The addition of Area Search is liable to be popular, as is the arrival of a Quick Tools floater. I personally like the additional button ranging options (I like my toolbar buttons over to the right of the screen and out-of-the way), and the ban / eject additions to context menus may well prove useful to some!

Performance-wise, this version of UKanDo is right up there with the last, and faces-off very well compared to the SL release viewer upon which it is based. In my PC, with ALM enables, ambient occlusion and shadows (Sun/Moon + projectors) enabled, and a couple of others on my home region, I was again hitting an average FPS of around 68-70.

I did find one or two things at odds in my version compared to the release notes (RenderVolumeLODFactor is reported as defaulted to 4.00, but in my clean install, I found it set to 1.25), but these were very minor issues and easily fixed. One thing I would recommend, however is that the icon for the Quick Tools button is revised. It is currently the same as the icon used on the Preferences button, and when operating with the buttons in Icon Only mode, it could lead to confusion.

I’d still like to see the media filter added to UKanDo, just for the added comfort when wanting to fiddle with media on other land; having something like Will Weaver’s Phototools appear in UKanDo would also be a blast – but these are purely personal preferences. As it is, UKanDo is a perfectly useable viewer, and for those looking for something sitting between the SL viewer and TPVs with all the bells and whistles, it’s worth taking a look at.

Related Links

Viewer release summary 2013: week 42

This summary is published every Monday and is a list of SL viewer / client releases (official and TPV) made during the previous week. When reading it, please note:

  • It is based on my Viewer Round-up Page, a list of  all Second Life viewers and clients that are in popular use (and of which I am aware) and which are recognised as adhering to the TPV Policy
  • By its nature, this summary will always be in arrears
  • The Viewer Round-up Page is updated as soon as I’m aware of any releases / changes to viewers & clients, and should be referred to for more up-to-date information
  • The Viewer Round-up Page also includes comprehensive links to download pages, blog notes, release notes, etc., as well as links to any / all reviews of specific viewers / clients made within this blog.

Updates for the week ending: October 20th, 2013 (with extras)

Official LL Viewers

  • Current Release updated on October 16th to version 3.6.8.282367 – core updates: Catalyst RC viewer with a start-up crash on latest AMD Catalyst drivers: 13.9, 13.10, 13.11 (download page, release notes)
  • Release channel cohorts (See my notes on manually installing RC viewer versions if you wish to install any release candidate(s) yourself):
    • Maintenance RC release on October 18th,  version3.6.9.282553 – core updates: finer access control for estate/parcel owners; CHUI: toggle expanding Conversations by clicking on icon; GPU table update + more (download and release notes)
    • “ShareStorm” RC viewer released on October 18th, version  3.6.9.282535 – core updates:  combines SLShare functionality (formerly 3.6.8.282036) and Snowstorm contributions (request teleport feature, et al – formerly 3.6.8.281997)  – (download and release notes)
  • Project viewers:
    • None at present

LL Viewer Resources

Third-party Viewers

V3-style

  • Black Dragon updated on October 15th to version 2.3.3 Alpha  – core updates: Machinima Sidebar overhaul; greyscale and posterization post processing options (unfinished) – (release notes)
  • UKanDo viewer updated on October 21st to version 3.6.8.27869  – core updates: AMD Catalyst driver hot fix; RenderVolumeLOD defaults to 4; RLV updated to version 2.8.5.8; numerous fixes and additions (release notes)

V1-Style

  • Cool VL updated on October 19th to:
    • Stable version: 1.26.8.34
    • Experimental version: 1.26.9.34
    • Release notes (both) core update: major bug fix for the “.32” releases. please update if you are running either one)

Additional TPV Resources

Related Links