[opensource-dev] Open Development project: extendingavatar wearables
Dzonatas Sol
dzonatas at gmail.com
Thu Mar 25 08:12:19 PDT 2010
Kitty wrote:
> If someone sells a full-top + high pants combination they wouldn't have to
> struggle with defining which shirt layer goes on top of which other one by
> messing with numbers - since those will still result in conflicts with what
> it's being worn in combination with - but you just leave it up to the user.
> If they want the bottom of the top tucked into the pants then they just
> arrange the top under the pants. Or vice versa.
>
> It also solves the issue where you're limited to what the creator felt like
> providing you with and working with clothing items is much more natural than
> working with clothing layers that only clumsily map to what they represent.
>
This is where I think a outfit list should be hierarchal to allows
someone to wear multiple outfit (lists).
For example, let's say this outfit list is already being "worn":
Outfit "Worn":
* Upper-body
** Shirt
** Undershirt
* Lower-body
** Underpants
** lower-tattoos
Here is another outfit list (as Kitty suggested):
Outfit "Kitty's":
* Upper-body
** full-top
* Lower-body
** high-pants
If we take Kitty's outfit and 'add to' the worn outfit (with default
order), we get:
Outfit "Worn":
* Outfit "Kitty's":
** Upper-body
*** full-top
** Lower-body
*** high-pants
* Upper-body
** Shirt
** Undershirt
* Lower-body
** Underpants
** lower-tattoos
No priority numbers had to be given in the above lists to see that
layers near the top of the list appear as the outer-most layers to bake.
With the lists above, *both* the creator of the outfit and the wearer of
the outfit have full flexibility to change the priority of the layers,
with mod or no-mod. Keywords, like "Upper-body" slots, can appear
anywhere in the hierarchies multiple times.
With the list hierarchy like above, the program that bakes the layers
only needs to start at the bottom of the list to bake the first layer,
and step up the list to bake the next layer, until it reaches the top.
The keywords like "lower-body" and "upper-body" only denote where (or
how) the textures (in sub-lists from that keyword) are baked onto the
avatar.
More information about the opensource-dev
mailing list