The main reason for the warning is as a result of the recent Adobe security breach which resulted in the details of some 152 million Adobe users accounts – almost four times the amount admitted to by Adobe for incidents in October.
The blog post from the Lab carries the title Keep Your Account Secure – Never Reuse Passwords, and reads:
A recent security breach at Adobe gave hackers access to private information for users of Adobe sites and services. This included Adobe passwords, email addresses, and password hints. Second Life has not been compromised, but, this is a good reminder that it’s important to never use the same password for Second Life that you use elsewhere.
If you have reused your Second Life password on other services, particularly if you used it for an Adobe service, you should change it immediately.
After every large breach, fraudsters search for users who reuse their passwords on other sites, so if you use the same password for Second Life and other services, your Second Life account could be at risk if one of those other services suffers a security breach.
Anyone who has used their Second Life password with other on-line services may wish to consider taking the advice and changing their passwords as a precaution and for peace of mind.
The major topic of conversation during the course of the week has been the Lab’s announcement that they have released a new project viewer which can be used to make suitably rigged mesh garments deform to match an avatars shape as it is adjusted using the viewer Edit Shape sliders. It does so by using a modified version of the avatar skeleton and collision bones, as I was able to preview just before the project viewer was launched.
Rigged mesh deforming to changes to the pectoral sliders in the Fitted Mesh project viewer
Since the Lab’s announcement, the response from various sections of the community have been mixed. Some have welcomed the new with open arms; some have questioned the overall flexibility of the solution compared to others, some have regretted the “loss” of the deformer and some have reacted in outright hostility towards the Lab.
In terms of the technical aspects of the solution, Karl Stiefvater (Qarl Fizz), who coded the mesh deformer, took time out to leave a comment on STORM-1716, the JIRA for that project, which reads:
Several people have asked me – this seems like the best place to answer.
LL’s assessment here is mostly good. In almost all situations, the simplest solution is the best one – and collision bones are indeed MUCH simpler than the mesh deformer. As I see it, collision bones have two downsides: 1) they are substantially harder to use for the person creating the garment and 2) probably don’t track as well to the avatar shape.
In the end, the evaluation must be made by the content creators who use the tool.
I will reiterate that the two-year delay and refusal to communicate are unacceptable.
Avatar collision bones (image courtesy of Gaia Clary)
This would seem to be a reasonable assessment. The use of collision bones is technically easier and, as noted elsewhere, is less reliant upon a large amount of code being added to the viewer which then needs to be managed and maintained as the viewer evolves, but it does have some drawbacks.
Commenting further on the subject in the Metareality podcast on Friday November 22nd, Karl added:
It [the avatar skeleton] already had a bunch of these bones in it for collisions. I have never, ever notices that someone shoots a bullet at me, and my avatar is fat, it actually hits me as if I were fat … It’s incredible that they put that kind of detail into it ten years ago. But, OK, they did. So my feeling – just to head-off any drama – is that it’s a nice solution. It is definitely a simpler solution, which is preferred in all software engineering, and probably all of life.
He went on to reiterate the fact that a downside of the approach is that it can making creating and rigging mesh garments harder, although as William Reed Seal-Foss observed:
Well, speaking from an artistic standpoint … and knowing how to rig, that’s already not fun, and it’ll make it more not fun, but it’s not going to be like you have to learn to do something new.
Pressed on the matter, Karl reconfirmed that while the Fitted Mesh approach may have weaknesses, he does feel that it is a good solution, noting, “Obviously, I’m invested with the one that we did, but this is good. This is good,” before also noting that as a technically simpler approach, Fitted Mesh is likely to hold-up better over time when compared to the deformer.
This still leaves the question as to whether personality may have played a part in the Lab’s decision. In the podcast, Kimberley asks Karl outright if he believes this to be the case, and he indicates that he believes so, stating, “I heard back from two different people inside the lab that told me that Linden Lab would never accept my code.” One would very much hope that matters weren’t influenced on the basis of personality; but the fact that the Lab previously rejected code from Karl for reasons which appeared tenuous at the time, would seem to be point to there being an issue of some description.
The debate over the pros and cons of each system will doubtless carry on in some quarters, as will the theories as to why one was selected over the other. In the meantime, feedback on the Fitted Mesh viewer is being generated and the Lab is working on updates. In terms of the technical aspects / limitations of the system, it remains to be seen how they may impact things. As it is, the approach has arguably been used to good effect by the likes of Redgrave and other designers and has proven popular among consumers. Hopefully the same will prove to be the case as this solution proceeds through to a release status and as it is adopted by third-party viewers.
Most people are already aware that Linden Lab are working to integrate the Oculus Rift headset, and are also probably aware that at the start of 2013, Simon Linden did some initial work in enabling the Leap Motion controller to work with Second Life with very basic movement / action controls.
Simon’s work was not a part of any official project, but acted as a proof-of-concept as to what might be achieved using Leap Motion as an alternative means of avatar control to the keyboard / mouse, and he made the code available for anyone wishing to make use of it.
Since then, other have looked into the use of Leap Motion, with perhaps Draxtor Despres being the most noticeable of late, after he recently produced a video showing his work in SL / Leap Motion connectivity through the use of the GameWAVE software application which can be obtained from the Leap Motion Airspace online app store.
Now it looks as if Leap Motion integration into Second Life may become part of a combined project featuring Linden Lab, third-party viewer and open-source developers and Leap Motion themselves.
A surprise guest at the Third-party Developer meeting on Friday November 22nd was a representative from Leap Motion. However, as he was unable to speak due to voice issues, Oz spoke on his behalf, revealing that the company is very interested in having their controller “well-integrated” into the viewer.
“So they have been very gracious and provided us with some controllers to play with,” Oz informed those attending the meeting. “And they’re prepared to provide consulting and help for people who want to do it.”
As the Lab is already running a number of viewer-related projects (not all of which have yet been revealed), they are hoping the open-source / TPV developers will be willing to work on the project in order to get code contributed and integrated into the viewer.
It is hoped that the Leap Motion device can be “well-integrated” into the SL viewer (image courtesy of leapmotion.com)
Whether the work will build on Simon’s initial proof-of-concept or form a totally separate project is currently unclear at this point, but at least the Lab have the code should it prove useful in giving the work an initial boost.
There is no official timescale for the project as yet, however developers who are interested in being involved are encouraged to contact both Oz Linden at the usual e-mail address, and the Leap Motion rep.
Some confusion occurred recently after some SL users started reporting they were receiving requests from Linden Lab for tax information, specifically to fill-out IRS form W9, Request for Taxpayer Information. The news of the e-mails sparked a discussion on the SL Universe forums, where opinions as to the cause of the e-mails was somewhat split, with some concerned as to why this should be happening and what it might mean, and others seeing it as a matter of routine.
On Tuesday 19th November, Linden Lab moved to try to clarify matters, issuing a blog post entitled Required Tax Documentation, which reads in full:
The Internal Revenue Service (IRS) requires Linden Lab to collect and retain Form W-9 (for U.S. residents) and Form W-8BEN (for non-U.S. residents) at certain transaction volumes. If you reach the transaction threshold and we do not have your completed and signed W-9 or W-8BEN on file, we are required to withhold funds from your account (at the current rate of 28% of your gross amounts received). Additionally, for U.S. residents with 200 or more transactions with a total amount in excess of $20,000 in a calendar year, we are required to file a Form 1099-K with the IRS reporting those transactions for that year.
If you are required to submit a W-9 or W-8BEN form to us, we will email you before the end of the year with instructions on how to do so. Please follow the instructions to complete and submit the required Form W-9 or W-8BEN within thirty (30) days of receipt. You will only need to complete this paperwork once unless your information changes from year-to-year. If you do not receive an email from Linden Lab, we do not need you to complete these forms.
While the blog post is welcome, some confusion and concerns remain.
One key area of confusion is exactly what constitutes a “transaction” – is it related solely to cashing-out from Second Life, or is it based on the number of user-to-user transaction through the LindeX (i.e. the number of L$ sales a person makes per amount of L$ they offer on the LindeX? Or is it somewhere in between?
A potential cause for concern is that many people cash-out via PayPal, and are also required to fill-out the requisite forms mentioned by Linden Lab, so there is an understandable level of worry as to the risk of double reporting. While this is not strictly Linden Lab’s issue, it is nevertheless a genuine cause for concern.
It has been suggested that one way to clear-up some of the confusion and concern might be for additional explanation to be given through the likes of a Knowledgebase article linked to the entry on account balances and withdrawals. Another alternative might be through an official wiki article dealing with tax liabilities as a whole, much as there are similar entries dealing with matters such as European VAT.
Linden Lab has issued a reminder / warning to users about buying and selling Linden Dollars and taking the appropriate precautions to prevent being scammed.
Second Life users do tend to be targeted by scammers periodically, so the reminder is timely as we approach what is for many the end-of-year holiday season, with both Christmas / winterfest and New Year looming.
The blog post reads in full:
As with any online service, Second Life users are targeted by scammers from time to time. One type of scam we’ve seen recently are websites that promise huge discounts on L$ sales and even offer to buy L$.
Often, these sites use these “too good to be true” discounts to lure you into entering your credit card information, which they then steal. Sometimes, they will use trusted payment systems, but sell you fraudulently obtained L$. When these fraudulent L$ are recovered by Linden Lab, you may then struggle to recover your payment from the anonymous strangers that sold them to you.
Not only does using these sites put your credit card information at risk, but it also constitutes a violation of the Terms of Service. Remember, you can buy L$ only on the LindeX or from an authorized L$ reseller; you can sell L$ only on the LindeX.
The good news is, keeping your credit card and your Second Life account safe is easy:
Remember that the only place to sell your L$ is the LindeX, the official exchange operated by Linden Lab
Be wary of any offer (which may be made via IM or direct message) that sounds too good to be true. If the site isn’t an authorized L$ reseller, ignore it.
There are currently 47 authorised L$ resellers available for the purchase of L$, including the likes of CasperTech, VirWox, ZoHa Islands, AnsheX, DXexchange, CrossWorlds, PodeX and others which will be familiar to SL users. Many will accept payments in a range of currencies via a range of credit / debit cards as well as accepting payments via PayPal, as such there would appear to be little reason to trust non-authorised sites for the purchase of L$.
Project Viewer 3.6.11.283899 is aimed squarely at resolving the thorny and oft-critiqued issue of making mesh clothing fit a wide variety of avatar shapes, as the blog post itself notes, reading in part:
Since the introduction of Mesh to Second Life, creators have faced challenges fitting Mesh garments to the Second Life avatar. Because mesh objects are not resizable in as many ways as the avatar itself is, it has been difficult for mesh garment creators to provide garments that adapt to the shape of the avatar in the way that the image-based clothing layers do. While many creators have made heroic efforts to provide products in a range of sizes, and some have collaborated to define a set of standard sizes that work reasonably well for much of the user population, many have found that mesh garments just don’t work well enough for their avatars. Mesh garments also don’t move with the body parts affected by avatar physics.
Users have developed two approaches to address these problems:
Rigging garments to the “collision bones” of the avatar skeleton (often marketed as “Liquid Mesh”). This works in current Viewers for some body parts, but there are some avatar shape parameters that do not have corresponding collision bones, so garments do not adapt to fit everywhere on the body.
The “Mesh Deformer” project added code to the Viewer to dynamically compute how to modify each garment shape by looking at how the vertices of the avatar were changed from that of the female and male base shapes.
The Linden Lab development team has studied both approaches, and compared their effectiveness, maintainability, and performance. Neither approach completely eliminates the occasional need for an alpha clothing layer to prevent small parts of the avatar skin from appearing through garments, but both work quite well at resizing garments so that they fit the avatar and move naturally with it. While the collision bones method requires the creator to do some additional rigging, we have decided that because it leverages more of the existing avatar shape system it is likely to be the more maintainable solution and to perform better for a wider range of users.
While the two current approaches to fitting mesh clothing are mentioned in the blog post (“Liquid Mesh” and the mesh deformer), it’s worth pointing out that the “Liquid Mesh” solution is actually based on an idea first demonstrated by RedPoly Inventor as far back as June 2012 – and it turns out that his approach is the one that the Lab, via Oz Linden, acknowledge as the one that first got them “started down the path of using collision bones to do this.”
At the time Liquid Mesh first appeared, there were concerns as to its impact on the market and the potential for content breakage should it prove popular only for something like the mesh deformer to eventually arrive in Second Life, prompting calls earlier in 2013 for the approach to be blocked by preventing mesh rigged to non-standard collision bones from being uploaded. At the time, the Lab remained silent on the matter, although many did blog on the potential pros and cons about the approach, including myself. Strawberry Singh not only blogged, but produced a video showing her testing a pair of boots she’d purchased which utilised the capability.
Prior to the launch of the Fitted Mesh project viewer, I was fortunate enough to be given the opportunity to preview it, and get to try out some sample clothing to see how it works. I don’t pretend this is a comprehensive review of the viewer, the new collision bones or skeleton; nor is it intended to compare / contrast the Lab’s approach to other methods. It is purely intended to provide an overview of the viewer and how suitably rigged mesh garments are handled.
The New Bones
As noted in the LL blog post, the project viewers includes an additional set of collision bones alongside the familiar set of bones. These are:
BUTT *
LEFT_PEC *
RIGHT_PEC *
LEFT_HANDLE
RIGHT_HANDLE
* These bones are affected by avatar physics.
All of these bones, and the original avatar bones, now affect mesh clothing when the avatar shape sliders (Edit Shape) are manipulated, thus giving mesh clothing which is rigged to the avatar skeleton the ability to adjust with the avatar shape as the sliders are adjusted, thus leading to a better “fit” for the clothing.
Content creators are invited to begin experimenting with creating garments rigged to the new skeleton. To assist creators in this, a Rigged Fitted Mesh wiki page is under construction, which includes information on the existing / new collision bones, links to the male and female .fbx, .ma and .dae files, and basic instructions on getting started with creating fitted mesh, including a link to downloading the avatar skeletons and to additional external resources.
Do be aware that this wiki page is a work-in-progress, as is the viewer, and liable to both update and change.
The Viewer and a Quick Series of Tests
There are a number of important things to note before going too much further. The first is highlighted in the Lab’s blog post, and is this:
At this time, the new skeleton should be considered provisional and subject to change; we do not yet recommend selling or buying garments rigged to it. Since we may find reasons to improve it during this testing process, and any change to the collision bones will likely break garments rigged before the change, we want to make sure that we have a set of bones that we can all live with into the indefinite future before it is widely used.
The second is that as with RedPoly’s original approach and Liquid Mesh, the approach will not entirely eliminate the need for alpha layers – but then again, it’s unlikely the mesh deformer would have entirely eliminated them, either.
The third is that the viewer obviously will not work with either unrigged mesh or rigged mesh which does not make use of the new collision bones (or additional bones intended to work with the appropriate sliders).
As the test clothing passed to me was for male avatars, and presented some of the usual problems when used with a female shape (and given I have very few mesh garments in my inventory, unrigged, rigged, liquid or otherwise), Oz kindly popped over and gave an initial demonstration. As he was already wearing a mesh jacket, he quickly played with the sliders to give himself a more portly shape – with the result that his mesh jacket (as expected) no longer fitted. However, when he swapped to the rigged t-shirt in the pack, it more-or-less fitted off-the-bat.
Oz, looking more portly than his usual self, demonstrates the new project viewer and collision bones. His mesh jacket (l) which is not rigged to the new bones, fails to adjust to his altered size. The t-shirt which has been rigged to the bones, however, does (r)
Following-on from their reminder / warning about purchasing L$, the Lab has issued a warning about keeping SL passwords secure.
Inara Pey: Living in a Modemworld 