METAbolt updates to 0.9.71.0

Metabolt-logoMETAbolt is a lightweight text-based client for Second Life and OpenSim offering a range of features and capabilities. At the start of the year, there had been concerns that due to the long delay between updates (the last being August 2013), work on the client had stopped.

However, as I reported in February, this was not the case, but rather CasperTech were stepping-in to take over the project, as was announced on the METAbolt website at the time.

While it has taken a while for things to move forward since then, the initial interim updates from CasperTech have now started to appear.

The updated METAbolt log-in / splash screen highlighting the fact CasperTech are now maintaining it (Feb 2014)
The updated METAbolt log-in / splash screen highlighting the fact CasperTech are now maintaining it (Feb 2014)

The first of these was to update METAbolt from release 0.9.69.0 (Beta) to version 0.9.70.0 (release notes) on June 13th. As an interim update, this release did not bring with it new features or capabilities, but focused more on bug fixes and under-the-hood updates:

  • Bug fixes from CasperTech and contributed by users – for which CasperTach pass on thanks
  • The removal of x64 support – the viewer is now 32-bit focused and installs into C:\Program Files (x86) by default. The reason given for this is, “If METAbolt uses over 4gb of memory, it’s really not doing its job as a lightweight text client. Let’s use faster 32-bit pointers instead!”
  • Initial work on providing Mono support for Linux and Mac compatibility, although as the release notes state, it will be a while yet before this is complete

As this release resulted in an issue with METAbolt plugins, June 14th saw the release of version 0.9.71.0 (release notes) which, as well as fixing the plugins problem, also added a digital signature to the installer to prevent any security warnings from popping up on download.

Both of the releases present METAbolt as an installer .EXE, rather than packaging them as a ZIP file containing the installer and support files, as with previous versions. A little more work is required on cleaning-up some elements, as the installer does still refer to “METAbolt (64 bit)” and defaults to naming the installation folder “METAbolt (64 bit)” under Program Files (x86). However, this is purely a cosmetic thing, and not something that interferes with using the client.

The latest releases mostly contain under-the-hood updates and bug fixes. However a major code refactor for METAbolt is underway
The latest releases mostly contain under-the-hood updates and bug fixes. However a major code refactor for METAbolt is underway

Given the focus with these updates is on under-the-hood changes, the look and feel ofMETAbolt remains largely unchanged from earlier recent releases, other than the revised log-in / splash screen. Which is not to say additional work isn’t already underway.Tom Mettam, now leading the METAbolt project indicates that there is a major code refactor underway; as a part of this, CasperTech apparently plan to offer “bounties” for people willing to assist with the work. Those interested are advised to keep and eye on the Issues section of the METAbolt GitHub tracker for more information.

While I have not covered every release of METAbolt through this blog, those unfamiliar with the client may want to read my initial review, mush of which still appears to be relevant, and check the METAbolt category of this blog for those updates I do have.

Related links

Advertisements

3 thoughts on “METAbolt updates to 0.9.71.0

  1. While it is great to see progress with Metabolt I was unable to successfully install the update when I tried last night. I had to except the installer with my antivirus just to start it, then it gave an illegal operation error and hung up. I had to reboot the machine to continue.
    As far as I can see there is no way to report this or any other problem to Caspertech.

    Like

    1. UPDATE: I was able to install Metabolt after uninstalling the 64bit version already on my machine.
      On first start it prompted for a further update to 0.9.71. This installer failed to close properly but a kick from Task Manager and everything seems okay (it may have worked better if I had not followed the dumb blonde route and just clicked through without closing the underlying dialog).

      Like

      1. Hmm… had no problems myself. 0.9.69 was installed under C:\Program Files and 0.9.71 went directly to C:\Program Files (x86) without a hint of getting sniffy. Also no issues with AV warnings (but then I’m one of the lucky few who almost never see any such warnings with clients or viewers). Hadn’t looked into issue reporting, so that’s interesting to note.

        Like

Have any thoughts?

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

This site uses Akismet to reduce spam. Learn how your comment data is processed.