Shnurui Troughton

No, but if you download the original SL UV Head map layout, you'll find a pair of inverted lash paths in the top right corner, approximately 8x24 map squares in shape. It's demarked by a thick black line with small lines feathered out from it.

It is true. Pre pipeline, aka, raw, images are kept in .png/.tga format. They are converted into jpg-2k, now, before being sent to the viewer. Before the pipeline upgrade for ogl encoding they were shipped in png/tga. The server compresses the multiple images when installed on an object into jpg-2k, which is the first jpg encoding to actually enable alpha.

One of two options. One, make separate mesh clothing work the way it always has, with the addition of an image fetch for the print. I could see that causing hems and seams in the wrong spot. Two, png encryption actually being read, like it already is on every other object. As far as I know there are two types of png encryption. Color slide and alpha layer. An alpha layer encryption has a print, a typographical layer, a shiny layer, then an alpha layer, all in the same file.

I'm confused. I was "quoted" but my statement, "BOM isn't going to be the only option until it's third party." wasn't. Nothing is the "only option" until it's released into the wild webs and everyone uses it. Second confusion: Creators are marketers? Some of us aren't rich and famous, even enough to fix known problems with our stuff, (like bellies that go cubist because of bad maths. Seriously, I think a small paid vacation could help with that.) Third confusion: Creators are supposed to find all their own bugs, even on demo and freebies? Maybe follow the creator's (s') bug reporting issue instead of crying over a haypenny or quincent on the shop page? Fourth confusion: Is clothing for mesh bodies sold as only models?

Sl "programming"

I'm confused as to why people think new tools make people stop making new things. The only thing with OLD mesh bodies is you won't be able to use OLD skins and clothing, unless they were forced onto the OLD, SYSTEM DEFAULT uv mapping. Even with the new arm and leg channels, the system default mapping isn't the end all, be all.

Not going to be "the only option" any time soon. Bom has to be third party released, first.

Unfortunately, you forgot to tell that to linden labs, back in the 90s, when they decided "material" would be used as a physics property in their engine. This includes, glass, rubber, stone, flesh, cloth, and yes, water. Feel free to look at the singular: material sl wiki page. This is not implemented in B.O.M. while, as a suggestion to add to B.O.M. keeps it on topic, it is only being considered.

Except there are actually two things wrong with your statement. Material, SINGULAR, is for the physics control. Yes that would let us have bouncy hair and clothing without extra "bones." Materials, PLURAL, can be done in the channels, giving clothing ridges at the seams and specular spikes. There's a reason you switch to "alpha blending" mode for worn items.

Nope. They define the physics of an object. Yes, I'll admit i was wrong from my phone, without access to http://wiki.secondlife.com/wiki/Material . Enjoy your ignorance. Ok, so I missed a word. The PRIMARY purpose is to USE the skin and clothing ATTACHMENT POINTS. This page calls them "Channels."

There seems to be a lot of confusion as to what terms belong where. Yes, B.O.M. or, Bakes On Mesh, is a nifty tool. The PRIMARY PURPOSE is for people with Mesh bodies to use OLD CLOTHING AND SKINS. That stuff you have floating around in your inventory that may or may not have cost you actual money. Skins are a set of 3-4 textures, if you include the hair. Clothing is also 1-4 textures, if you're just using the regular old stuff. Textures are detailed images giving an area a look, such as clothing, tattoos and cosmetics. Materials are also known as *Faces, or *Zones. They define where the above textures mete up with. Yes, it would be nice if the uploader was fixed so that creators could label and forget in their tool of choice, (lower_body, upper_body, etc.) and have the B.O.M. auto assign the default basic beta version textures to the right zones*. Yes, it would be extremely wonderful if there were some sort of Data Core that could be placed on an animesh to allow B.O.M. to work on single layer animesh items. But as someone noted, the heads haven't been replaced or even really taken a vacation to get fresh eyes on the problem. They're doing great work, don't need to harsh their groove.

Right. You don't apply a uv. You apply a texture and the UV aligns and orientates the texture. Please read slower. Which is it? Materials, which become "faces" inside Secondlife, affect access to uv mapping or lips have to be carefully painted?

Materials affect layout and positioning. UV affects texture orientation and alignment. You can use the same uv on multiple materials, but they won't show up unless they're set to. Simple example: Cosmetic masks and face skin masks use the uv that includes hair, teeth, and tongue. Yet, applying a mascara or lipstick uv doesn't change the face, except in earlier designs that had the slider values. Even then, they didn't affect the teeth or the back of the head, even though some maps "paint" those areas. This was before layers were available.

Not entirely accurate, but close enough. Things that aren't changed, won't change. If you have a model that hasn't been updated since 2002, like a prim rabbit, it will work how it did in 2003. BOM won't even be visible to end users, unless the models are unlocked. The applier tools that were available in 2001 will be available for all makers. You'll just apply custom maps to the correct skin zones, unless the object isn't linked to BOM.

That is the reason the default avatar has one toe and no separate toe nail objects. For us creators to produce a completely onion free avatar, it either has to the ultra simple, like a rag doll rabbit (Boid's nest) or mechanical. Anything with separate toe nails will need the nails alpha layered out. Anything with separate toes will need to be layered, even for socks. Ha ha hilarious. See Cathy's post: Tldr version: Unique User IDs are unique to each user. They should not be accessible when they aren't in the current user's inventory. My skins and tartans that are not in the default library, should, not be visible in a HUD, without the transfer of that texture, into the HUD or inventory of the EU. The only way his transfer HUD should work is if he drops a copy or transfer texture into it.

Sean, one of us is confused with what you're interpreting. I want people to be able to move my non mesh textures onto their mesh bodies. I know I will never recoup the lost lindens from the shift to mesh, but BOM gives me a chance to start making more, hopefully more attractive textures. What we don't want us texture ripping, which on a high enough resolution screen is impossible to completely prevent. What we do want is for those that buy our textures, to be able to use those textures. No, we don't want uuid(s) shared, if that even works.

That was a response to Hilary Querrien, I asked what layer her nails were on. That was Exactly why I made the response to Hillary Querrien. If you have a problem with the way Hillary Querrien's avatar is working, maybe you should help her.

I don't understand. Are your nails not part of your skin layer?

Exactly what I said. When the original model, aka Ruth, was designed, built, and released, linden labs cheated us, and them, out of having a left and right arm map. The two arms in the SLUV are the inner and outer arm, on both sides of the model. There is no left and right on the original arm of the original model. There is no left and right on the original foot of the same model. This was not corrected in 2.0 This is only correctable by mesh designers, but does not allow for use with the bakes on system.

That comes from the fact that the original maps did not detail the toes in a good manor and the hands were cheated into one arm, on one side. Depending on your mesh model, the feet and hands may have been remapped.

I'm slightly confused on the uuid bakes on issue. To clarify: There isn't a way to assign an uuid to a slot (head/torso/eye/aux etc) using existing data/lsl? Wasn't there a clothing script that did just this?

Soon. It will be released Soon. The status is good, beta is working well. So far the only "problem" is having to wear each item in order to link it to the corresponding layer. And the lack of Isolated body parts. Serious Confused look. Are you talking about wearable pets, maybe weapons, and shields? How is it unscrupulous to use unused fields for unknown items? It's under Edit>TEXTURES, click the Texture Field. Look at the Select Texture window. Right below that is the Bake Radial.

Yes the ears had two large areas dedicated to the ears. No, this does not work with large ears as those two small(relatively large) areas are 1.) Attached to the head and 2.) Force the back of the ears into a weird perspective that is fine for hidden eat backs, but very destructive for visible eat backs. In order to use the internal animal ear on the standard sluv, you completely warp the back of it. You can spoof that to the top of the head, but that causes the same problem we have with the arms.

"What are the(aux) gong to be used for?" I can't speak for every NHC avatar creator, but, as of today, I plan on setting the ears to 1, the tails to 2, and wings to 3. 3, could also possibly be the hinter of non winged hexapods. This includes centuars, and the like. This could evolve as I finish remapping the current uv maps, but this is the way I suggest, and will more than likely use.

Imo, alpha cuts are for noc(not original content) that isn't made with or by the original. Onion avatars don't need alpha cuts for the onion layers, do they?