I would Like to see standard sizes implemented into Avastar , via shape keys . also maybe a high poly avastar model for normals creation and better weight painting
Kitsune Lassiter
on February 25, 2015 at 8:16 pm
I also would like to see a streamlined pipeline for fitted mesh clothing. I do hate making different sizes for them and it would be nice if that could be simplified.
elenewell
on February 28, 2015 at 2:12 am
Considering how SL chose to implement fitted, it really has to be understood that there are concessions to be made and that you need to live with “good enough” when it comes to fitted. There are many reasons why fitted will never be perfect and may not be able to have one size that fits all. You might, however, be able to do fewer than five sizes. The middle ground has more ability to fit than anything in the extreme at the large or very thin. If an avatar decides to have huge boobs and a tiny, little butt, that throws a whole other wrench in things. So just as designers reluctantly accepted the five standard sizes to make creating clothes easier, so will the need to find what works for fitted. And the rest will have to be custom jobs if you desire to do them for your customers. IMHO.
StockMaster
on February 25, 2015 at 8:09 pm
I believe one of the things that are missing in avastar is a way to help streamline the pipeline production of clothing items into secondlife.
Be it with the Fittedmesh, but also the 5 standard sizes.
Any tools, process, tricks that woulc speed and help increse the quality of the items imported would be much apreciated by creators.
By the same extent, helpers/tool tips to prevent huge meshes to be imported as rigged and impact negativly the behaviour of SL could be interesting. By this i mean, “mesh optimier” filter that would warn the user of wrong scale/too many or excessive poly count. Etc.
Merry
on February 26, 2015 at 2:33 am
I second this! Especially anything that encourages optimization. I keep seeing clothes that look like they’ve just been sculpted in dynatopo and uploaded directly (that’s got to cost a bundle!). Also, while it’s probably outside the scope of Avastar maybe some mention of using normal and spec mapping to imply more detail would help people realize they don’t really need to sculpt in every seam and wrinkle. Heheh, that’s just a dream though.
tonka
on February 26, 2015 at 7:47 am
I second Merry’s comment! 🙂
elenewell
on February 28, 2015 at 2:05 am
Those things may be out of the scope of Avastar, but what we have found is that sometimes people are resistant to being given the suggestion to optimize in terms or polycount, retopo, use of normal and other maps, and sometimes they aren’t. You DO actually have to sculpt or model in every seam and wrinkle for your high poly version to have details to bake into a lower, retopo’d model. This implies more work to optimize, which in fact, it is, but that is what is necessary. Not all are willing to hear or do anything about it, or have trouble learning how to. It’s a very complicated thing, so no easy fix.
elenewell
on February 28, 2015 at 2:01 am
Can you explain what you mean? At what point does the workflow we have set up not work and need more information? And what information do you see is needed? I see some of the suggestions for an optimizer. Those are good suggestions, but I do not think you mean those by the need to streamline the pipeline, do you?
I would Like to see standard sizes implemented into Avastar , via shape keys . also maybe a high poly avastar model for normals creation and better weight painting
I also would like to see a streamlined pipeline for fitted mesh clothing. I do hate making different sizes for them and it would be nice if that could be simplified.
Considering how SL chose to implement fitted, it really has to be understood that there are concessions to be made and that you need to live with “good enough” when it comes to fitted. There are many reasons why fitted will never be perfect and may not be able to have one size that fits all. You might, however, be able to do fewer than five sizes. The middle ground has more ability to fit than anything in the extreme at the large or very thin. If an avatar decides to have huge boobs and a tiny, little butt, that throws a whole other wrench in things. So just as designers reluctantly accepted the five standard sizes to make creating clothes easier, so will the need to find what works for fitted. And the rest will have to be custom jobs if you desire to do them for your customers. IMHO.
I believe one of the things that are missing in avastar is a way to help streamline the pipeline production of clothing items into secondlife.
Be it with the Fittedmesh, but also the 5 standard sizes.
Any tools, process, tricks that woulc speed and help increse the quality of the items imported would be much apreciated by creators.
By the same extent, helpers/tool tips to prevent huge meshes to be imported as rigged and impact negativly the behaviour of SL could be interesting. By this i mean, “mesh optimier” filter that would warn the user of wrong scale/too many or excessive poly count. Etc.
I second this! Especially anything that encourages optimization. I keep seeing clothes that look like they’ve just been sculpted in dynatopo and uploaded directly (that’s got to cost a bundle!). Also, while it’s probably outside the scope of Avastar maybe some mention of using normal and spec mapping to imply more detail would help people realize they don’t really need to sculpt in every seam and wrinkle. Heheh, that’s just a dream though.
I second Merry’s comment! 🙂
Those things may be out of the scope of Avastar, but what we have found is that sometimes people are resistant to being given the suggestion to optimize in terms or polycount, retopo, use of normal and other maps, and sometimes they aren’t. You DO actually have to sculpt or model in every seam and wrinkle for your high poly version to have details to bake into a lower, retopo’d model. This implies more work to optimize, which in fact, it is, but that is what is necessary. Not all are willing to hear or do anything about it, or have trouble learning how to. It’s a very complicated thing, so no easy fix.
Can you explain what you mean? At what point does the workflow we have set up not work and need more information? And what information do you see is needed? I see some of the suggestions for an optimizer. Those are good suggestions, but I do not think you mean those by the need to streamline the pipeline, do you?