Virtual Progress
Written on May 18, 2008 by Katherine W. Prawl
Since my last post here, a lot has been accomplished.
Last time I wrote, I was downloading the OpenSim server software to my external hard disk via SVN. That went well, but I have to admit that the instructions for compiling and running it on MacOS 1.5 were so daunting that I deferred that until after I’d tried out the binary under WindowsXP.
It worked! I installed and ran the binary version of the open source server on WinXP, which was installed on a virtual machine running in Parallels Desktop for Mac on my early 2006 20″ Intel Core Duo iMac, and while I couldn’t do much except look around with the camera tools (since I had not configured any of the other servers — asset, inventory and avatar databases), it was quite a thrill to know that I could have my own little world running on even a laptop unconnected to the internet if I wished. (The reason I use an external disk for my virtual machines is so I can access them using my husband’s 17″ MacBook Pro or any other Mac with Parallels Desktop installed.) I logged in using a copy of the SecondLife viewer, just editing the target definition in the shortcut’s general properties window, and using the default login ID and password of “Test User” and “Password”. The target I specified in Properties, of course, was the localhost URI, http://127.0.0.1 plus the designated port, in this case “:9000″.
Other VW Developments
In an already-running OpenSim grid (OpenLife), a week or two ago I met the person who started that system, Sakai OpenLife (OL name). It was interesting chatting with him, and he gave me a tip I’ve followed up on for porting content among VWs. He said many people have had good luck with Second Inventory, an application that creates a backup on your own hard disk of objects, textures, bodyparts, etc. as long as you have full permissions for those assets. I discovered that there is a multi-avatar version available, so while it’s a bit pricey (29 Euros, vs 14 Euros for the single-avatar version), I went ahead and bought it. It does indeed work as promised, although it is a bit slow to copy a large inventory since the “folder copy” function isn’t yet enabled and items must be backed up and restored one at a time. Folder actions are promised for the next version, though.
I ran a few tests, and I was able to back up and “restore” copies of simple and linked objects from both my primary and alt accounts in SecondLife to accounts in Open Life and OS Grid. It isn’t perfect; embedded scripts don’t always make it, and when they do they must be recompiled since not all LSL functions are available in the OpenSim VWs yet, and animations also don’t seem to come across when embedded in an object. Presumably those might be uploaded and added to objects if one has the .bvh files for them, though. My coffee mugs came through with their handles and “coffee” intact and didn’t require relinking, but the “drink” animation and script aren’t there, and the little “ring” piece used for the rim of the cup wasn’t linked. I just threw away the rings since they aren’t critical, and copied the particle steam script I used in SL, recompiled it and added it to the “steam” prim, but I haven’t done anything about the animation yet.
Interestingly, once I had the backups made, I could restore inventory items from my SL alt account as well as my main account to either SecondLife or another VW with impunity. The owner’s name didn’t make any difference to the software. When an asset is “restored” to an inventory, whether it came from that account or not, the owners name becomes that of the account that it’s being restored to, not the source inventory owner’s. There is certainly some potential for mischief here, especially since I was also able to “back up” some full-permission assets that I did not create, and when they were restored my avatar’s name showed up as the creator.
Copyrights and DMCA Issues
The ability to “rebrand” items that I owned full permission copies of, but had not created, made me wonder what the attitude of some of the content creators in SecondLife were toward these brave new virtual worlds. Would I be able to legally use copies of fulll-perms textures I’d bought in SecondLife in other worlds? I sent that question to one of the texture store owners I’ve patronized extensively, LilyBeth Filth, owner of Textures-R-Us. Predictably, she said, “No.” Here’s a direct quote from her IM, which I think explains her reasoning and the problem very well:
Hi, Our User License does not allow customers to use them in any other virtual world including SL open source clients. The reason for this is because they would be uploaded in your name and not that of the creator. In time people will share these textures with friends (as they always have) and before we know it people are selling work created by the original artist but uploaded by other people and it creates a nightmare of a DMCA issue. We create & sell textures for SL only. Sorry. LillyBeth 2008/5/17
So, it sounds like there could well be a whole new round of rights issues to hash out, even when the dream of a mostly seamless metaverse becomes a reality. The technology is not the only thing that needs to be mastered.
If you enjoyed this post Subscribe to our feed


July 17th, 2008 at 5:37 am
Great article.
Just a couple of actualizations, at the moment the Folder backup in Second Inventory is working already since some versions and the Opensim embedded Script upload was implemented since the 1.2.0.3, S.I. runs very fast
Regarding the textures part, I would like to remind that full perms Textures can be locally saved and so, re-uploaded in sl also with the regular second life client. When a customer buy a texture set, he agrees with the license with the one they are delivered, if he infringes that license it can’t be considered a Second Inventory’s exploit and neither an sl one, but rather his choice.
In Second Inventory we denied exportation of items that aren’t full perms, emulating the standard client’s behavior. Unfortunately we can’t check the license or the agreements between seller/buyer unless they are not technically readable.
Best regards