Tag: Firestorm News

On Monday November 18th, Firestorm will commence blocking older versions of the viewer from accessing Second Life.

This is a move that has been coming for some time, and has been announced on a number of occasions through the Firestorm blog, through Firestorm user meetings and Q&A sessions, and which has been repeated through various blogs, including mine.

As it is, there are a good number of users still running versions of Firestorm that pre-date the introduction of Server-side Appearance (“avatar baking”) and some which even pre-date mesh rendering. Not only does running such versions lessen the user experience and increase the workload Firestorm support volunteers have in trying to assist people on older versions of the viewer.

Nor are the Firestorm team doing this entirely off their own backs. For obvious reasons, the Lab would like to see more users benefiting from the broad range of improvements which have already been rolled-out to SL (and those still being deployed in terms of further viewer-side updates), including SSA, interest list updates, improvements to the rendering pipe, improvements to viewer / server communications, and so on, all of which should improve the user experience, even for those on older hardware.

Given that Firestorm does have the lion’s user of active users, just under 65,000 of whom are still logging-in to Second Life on versions of the viewer pre-dating the more recent SL updates such as SSA, the easiest way to encourage them to update is to block older versions of the viewer.

This being the case, once the block comes into force, it means only users on Firestorm 4.4.0 through to the current version(s) will be able to access Second Life. As such, from November 18th, the following versions of Firestorm will be blocked from Second Life (numbers of people still using each version given in brackets):

• 4.3.1.31155 (40,451)
• 4.2.2.29837 (14,120)
• 4.2.1.29803 (60)
• 4.1.1.28744 (3334)
• 4.0.1.27000 Beta (4585)
• 3.3.0.24882 maintenance release (606)
• 3.3.0.24880 hotfix release (571)
• 3.2.2.24336 (881)
• 3.2.1.24179 (166)

For those who feel they may be unable to run later versions of Firestorm, the recommendation is to give a later version a go and to contact Firestorm support teams for assistance or try the Firestorm troubleshooting wiki pages, as issues encountered may be fixable. For those who have genuine issues in trying to run later versions of Firestorm, Linden Lab’s Third-party Viewer Directory offers a list of self-certified alternative viewers you might want to try.

For further information, please refer to the Firestorm blog announcement.

Please note: I cannot address technical questions relating to Firestorm through this blog. Please contact the Firestorm support groups if you have specific technical questions.

Related Links

• Old FS Version Block to Begin – Firestorm
• Firestorm coverage in this blog

On 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”.

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.

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.”

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.”

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