Archive for June, 2009

Updated Imprudence 1.1.0 Installer for Windows

If you’re a Windows user who had used the 1.1.0 RCs, you may be seeing these errors when you run Imprudence 1.1.0:

  • The ordinal 67 could not be located in the dynamic link library zlib1.dll
  • The procedure entry point gst_rtp_buffer_calc_header_len could not be located in the dynamic link library libgstrtp.dll
  • The procedure entry point gst_rtp_buffer_payload_type could not be located in the dynamic link library libgstrtp.dll

If you’re having those or similar errors, you should re-download the Windows installer for Imprudence 1.1.0! There were some old DLLs left by the RCs which were causing trouble. The new installer should get rid of them.

Imprudence 1.1.0 (Final) Released

It has been a long time coming, but Imprudence 1.1.0 is finally here!

This final release of 1.1.0 fixes several issues that were present in Release Candidate 2, as well as a few miscellaneous tweaks and additions. Most notably:

  • The pie menus have been reorganized again, in response to the user feedback we received. Check out our wiki page about the pie menus for the details!
  • The music and video subsystems have been vastly improved, eliminating many of the hiccups, freezes, and crashes that occurred in the release candidates. It’s still not perfect, but it’s a lot better!
  • Confirmation dialogs have been added for several actions, to help avoid accidently triggering them: Restore to Last Position, Teleport Home, Toggle Fullscreen, Take Off All Clothes, and Mute (avatar / object).

Be sure to check out the full release notes to see all the other stuff we changed and fixed in this version!

Good news for Mac users: this release comes with a Mac version! We have only prepared the Intel-only version so far, but if there is enough demand, we can offer a Universal version without music or video support. Leave a comment here or in the forums to let us know if you need a Universal version.

Regardless of which platform you’re on, you may experience some issues with audio, music, and video support. Please continue to report issues in the forums — but, as I explained in my post a few days ago, McCabe and I won’t be working on audio, music, or video issues anymore, except for the most serious and widespread issues. We have each spent dozens of hours per week for 3-4 months just to get things working as well as they do now, and we’re eager to move on.

Now, without further ado, the links:


What’s Going On With Imprudence?

Things have been quiet on the Imprudence front lately, I’ll admit. So, you might be wondering: What’s going on with Imprudence?


McCabe and I got pretty exhausted working on cross-platform GStreamer and OpenAL support, which has been a long and frustrating campaign, much longer and more stressful than we had anticipated. The end always seemed just a little bit further, so we let it drag on way too long, and it wore us out and used up a lot of time that could have been spent on other improvements.

So, we’ve been on vacation on and off for the past month or two, resting up and recharging. But we’re gearing up again now, and getting back to work. But we won’t be working on sound, music, or video issues anymore, except when critical issues (widespread crashing or freezing) demand it. Fixes for less critical sound/music/video issues will have to come from other community members.

We plan to release 1.1 this weekend, and then move on to 1.2.

Moving Right Along

So, if we’re not going to be hammering on GStreamer and OpenAL, what will we be working on? Fun and interesting (to us) things! UI improvements, new features, and other things that make the viewer generally more awesome. In other words, the stuff we started this project for.

Here are a few things (but not the only things) planned for 1.2 and beyond:

  • Updating to SL 1.22 core. Imprudence has been based on the Second Life Viewer version 1.21 source for nearly all of its history. For Imprudence 1.2, we’ll be changing bases to SL 1.22. (We’ll be changing to 1.23 some time after LL has made a full release of that. But, we’ll probably borrow specific, known-good changes from the 1.23 RCs in the meantime.)
  • Restrained Life support. Imprudence 1.2 will feature support for the Restrained Life API, most popularly used in SL bondage gear, but also in a variety of other useful devices. However, we will not be using the official Restrained Life Viewer patches due to licensing issues. Instead, we will be using Kitty Barnett’s RLVa (Restrained Life Viewer Alternative), which is licensed under the GPL.
  • Account / Grid Management. We’re planning to add better support for third party (OpenSim) grids in Imprudence 1.2. This will be similar in functionality to the Hippo Viewer’s grid manager feature, but with better usability and an added account manager feature, so that you can just select an account from a drop-down list on the login screen.
  • Object Import and Export. This probably won’t be done in time for 1.2, but we’re in planning stages for an object import and export feature, i.e. saving and loading prims to/from your computer. The tool will respect object permissions. You will only be able to export objects you have rights to. We recognize the risk of someone modifying the code to disable permissions checks, but believe that the legitimate uses and benefit to content creators — content backup, transferring to and from offline build tools, migrating content to and from OpenSim, etc. — far outweigh the illegitimate uses and potential harm. There are already numerous tools that allow illegitimate copying of SL content, so content thieves won’t gain much. The lives of builders, on the other hand, will be a great deal easier.

Project Evaluation

It’s hard to believe, but two days ago, June 1, marked the 9-month anniversary of the announcement of the Imprudence Viewer Project. We’ve made some significant steps towards better usability in that time, but there’s still so much further to go.

Over the next few weeks, McCabe and I will be evaluating various aspects of the project itself (policies and workflows and such), seeing what has worked, what hasn’t, and what needs to be improved. Things we’ll be evaluating include stuff like the effectiveness of the forums as a channel for bug reports, whether an active mailing list would be worthwhile, how we should deal with the ChangeLog (manually maintaining it is a significant timesink and flow-breaker), and how to encourage more involvement from other developers and designers in the community. We’ll also be trying to establish design guidelines for the viewer, a general development strategy, and a proper roadmap!

So… that’s what’s going on with Imprudence!