• 10Feb

    Mera poses the challenge: Tell us what you like most about Second Life.

    Dolmere wrote in his response to the challenge:

    I still remember Mera exclaiming something like “I love this place. It’s good to know that the skills I have spent my life learning are appreciated somewhere”.

    That reflects much of the appeal of Second Life to me: the sense of efficacy and satisfaction that I derive from it. The things that I love are things that matter in Second Life. And I love what things matter in Second Life.

    Continue reading »

  • 10Feb
    Uncategorized 1 Comment

    Mera demands: Tell us what you like most about Second Life.

    Oooh, that’s a toughie. Well, after thinking it over for a while, I decided that what I like most about Second Life is…

    Jacek looking rather blingy


    Hoo-ha-ha! Just kidding, gentle reader! The thing that I actually like the most about Second Life is…

    Jacek still looking exactly the same about of blingy.


    Ah-ha-ha! I kill me with my own humor! I am truly slain with laughing!

    Tune in again later for less silliness!


  • 06Feb

    If I were to name two locations in Second Life to show a new Resident, what would they be?

    Well, if I’m going to be giving a newbie the ultra-premium tour de luxe of Second Life, that newbie is probably a clever one, bursting with raw creative will!! I want to expose that Resident to the amazing possibilities in Second Life, and get them started on the path to supreme excellence!

    Continue reading »

  • 03Feb

    What a super idea! I’ve got the YAYZERAMA HANDS too now!!

    Features like this (and other cool things, too!) could be added to the viewer client, ‘specially now that it’s open source, but so many features require just a little bit of help from the server to do it properly.

    For example, right now there’s no good way for the sim to remember “This prim has a saturation of 0.5 on all its sides” and tell that to everybody that comes by, so there isn’t any way to share the desaturated goodness with anyone else! (Maybe you could store some cryptic data in the prim’s name or description for other special viewers to notice, but that would be a dirty, dirty hack. Yuck!)

    Sure, we could tug on the Linden programmers’ shirt tails every time there’s a new client-side feature we’d like the sim to store a little bit of data for. But, even if they were just twiddling their thumbs all day and waiting for something to do, there would never be enough time to add something for every feature that someone thinks up. (Plus they’d have to do a grid-wide update every 15 minutes.)

    A better way would be to give each prim a little pocket where it can hold some arbitrary data to give to viewers that see it. There would be a hard limit on the size of the data (maybe 1k, or 5k), and it would be completely up to the viewer software to decide what to do with it. And of course, scripts would have to be able to read and write this data!

    Ideally, objects and prims in SL should be sent as XML, kinda like this:

        name="My Awesome Prim"
        description="The best prim ever made."
        texture_uuid="top: [uuid], bottom: [uuid]"
        contents="[first_item_uuid], [second_item_uuid]"
        size="8m 2m 2m"
        awesomeness="23.5" />

    Then the scripts could do something like this:

    if( llGetAttribute( "shape" ) == "torus" )
        llSetAttribute( "awesomeness", "infinity" );

    Or if we had a decent scripting language, like ruby, it would be like this:

    if self.shape == "torus"
      self.awesomeness = "infinity"

    And if you had a special viewer client that was programmed to understand the “awesomeness” attribute, the client could do something cool like write “This prim is so awesome!!” on your screen with a big squiggly arrow pointing to it.

    That would be awesome.

    P.S. If you’re worried that this would contribute to sim load because of the increased amount of data being sent, remember that textures are the #1 cause of teen pregnancy sim lag. Plus, the sim could enforce a data size for the prim declaration, by dropping out some nonstandard attributes if it gets too big.

    P.P.S. Yeah, I know this could be a big ol’ security hole. What isn’t? ‘specially if you’re using a custom viewer client provided by some homeless person down the street.


   Next Entries »

Recent Comments

  • The feet and hand control bones can be used for inverse kine...
  • thanks! It's woahking! However I have a problem...someho...
  • it is very nice.i can easly understood for animation work.th...
  • I just want to thank you very much!...
  • Sorry, the exporter only works with Blender 2.49 and earlier...