user_mobilelogo

RSS SL

Second Life Community - All Activity
  1. I guess people are preparing, because I see two 512s on the land page right now.
  2. Funny you should say that. I first bought the Legacy Male body in order to make a teenage boy avatar. At the time, I was still using the old TMP Male body, and I wasn't happy with how that scaled down. I was able to make a roughly 13 year old looking avatar pretty reasonably well using the Legacy Male body and a different head.
  3. Thank you and yes, I agree. I didn't take the RL laws into consideration, but did read the SL TOS beforehand and concluded I can share images of other residents. Under the Second Life TOS (Section 2.5) and SL Policy (Section 1.3), any resident who displays content in a publicly accessible area automatically grants all other users a "Snapshot and Machinima Content License." This is a non-exclusive, worldwide license that allows you to photograph or film their content and share those images in any media (including outside of SL), provided you follow the official Snapshot and Machinima Policy. Essentially, by being out in public, residents agree to be part of the community’s snapshots. The other artists in the gallery, where some of my pictures are now on display, sell copies of their work. That’s just not why I started taking these photos, and my blog isn’t commercial as well. Aside from the rules, it simply doesn’t feel right to benefit from images of other people’s appearances, which I see as beautiful works of art in their own right.
  4. This sounds pretty sensible to me… although I wonder if Firestorm actually rolls its own caching, it being a notoriously tricky thing to get right across operating systems and storage technologies. That tempts one to play around with size of cache (more is not always better anyway, and there may not be the expected penalty to shrink it as far as it can go). Long before SSDs, I'd routinely set the viewer cache to a RAM disk; loading over a fast network into an empty cache wasn't that much worse than fetching content from a poorly performing HDD cache. Don't think I'd recommend that now, but I would definitely try a drastically reduced cache to see if those 3-4 hours shrunk accordingly or (as I think just as likely) extended indefinitely with a truly tiny cache.
  5. Pfft, how dare you stereotype us like that Scylla, we are far more complex and nuanced than you give us credit for. Now, throw in some nachos and topless waitresses and you might be on to something.