May be the solution here is so close then you imagine: Presets! Like the empties have some preseted shapes, bones could have it too.<br>Presets! But more than that: another thing is in development (almost in our hands) to we have our own RIG presets is Etch a Ton. I think it will save more time then ever and anything! Presets Rig Libraries. 'Cause you can set your arm rig, for example, with your favorite shapes controls and bone deforms ONCE, and easily apply to a new character! Only needs to set right the bones weight and may be shape keys deform corrections.<br>
Everyone here wants to see a better Blender, for sure. Thats why I thing is valid your concern. Questions like that makes us think about the way we can blend and it doesn't need to be the same like the biggers,[emotion=on] but it could be better. I have a dream [big pause]... and all that free speeches from the blender nation and the amazing organization and moderation from the lidership will make 2.50 come true!!<br>
Thank you all! Thank you!!! For president, vote MangoJambo!!! lol<br><br><br clear="all"><br>Moraes Junior - aka mangojambo<br>3D Artist Animator<br>
<br><br><div class="gmail_quote">2009/3/30 joe <span dir="ltr"><<a href="mailto:joeedh@gmail.com">joeedh@gmail.com</a>></span><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Bone shapes are not a time problem, which any serious rigger will tell<br>
you. Rigging isn't magically easier just because you can have<br>
object/bones mixed, either. Rigging is an inherently difficult<br>
problem, but the workarounds related to mixed objects/bones tend to be<br>
fairly easy, and not that slow to do.<br>
<div class="im"><br>
<br>
On Mon, Mar 30, 2009 at 6:23 AM, David Bryant <<a href="mailto:aceone@bellsouth.net">aceone@bellsouth.net</a>> wrote:<br>
> When you are working in a pro studio enviroment, time is money so any time<br>
> you save is time to meet your deadline and less money squandered on paid but<br>
> lost manhours.So, most pro rig rig controls use simple controls (boxes,<br>
> circles,crosses,spheres). Secondly, non armature controls makes the rig<br>
> "cleaner" for the animator to be able pose effectively.The less you have to<br>
> "hide"on a rig represents less package computation thus faster graphical<br>
> response.In Blender, you have to designate which shape you would like the<br>
> bone to take by calling forth an object, cause the bone to draw the object<br>
> (which has to already exist somewhere in your .blend file) and hide the<br>
> object that the bone is going to look like (that has to exist but is doing<br>
> nothing but existing)and use the bone that looks tlike the original object<br>
> anyway.<br>
<br>
</div>This really isn't a problem in practice. Rigs in other apps have<br>
"hidden" portions too; all production rigs do. Besides, whether you<br>
use objects or bones, it's the same computational complexity, I don't<br>
get this idea of it being more responsive.<br>
<div class="im"><br>
><br>
> Imagine 6 characters with complex rigs with bones that look like something<br>
> they're representing with the original objects just "exisiting" in the<br>
> .blend file when all that had to be done is to be able to use the original<br>
> object anyway.You have objects in your files doing nothing but they have to<br>
> be there "hiding" because if they didn't exist you would have no icons<br>
> because the bones would have nothing to "look like".<br>
<br>
</div>Again, this is not a problem in practice. It's also something that'd<br>
be better solved by allowing use of the empty shapes with bones. It's<br>
definitely not a time sink in any way.<br>
<div class="im"><br>
><br>
> Other packages don't have pose mode either.So there are no objects that<br>
> can't be used in their versions of the action editor.Try using the action<br>
> editor and try to adjust timing with an empty or non bone in concert with<br>
> your rig (using bones)in pose mode.You simply can't because it's not an<br>
> intergrated part of your rig.So, now you have to use workarounds that take<br>
> more time.That's why you need bone heirarchy with objects in Blender.<br>
<br>
</div>Well, this does work in 2.5.<br>
<div class="im"><br>
> If you're a hobbyist, you have all day to do these things.If you make your<br>
> money by rigging and animating, and have to meet deadlines, every step saved<br>
> is a plus.The less you have to "hide" on a rig, is less you have to remember<br>
> to keep track of and in a pro setting, the less the animator has to tamper<br>
> with to break your rigs.<br>
<br>
</div>This isn't true. As I've said many times, these problems you're<br>
discussing don't exist. I'm a fair rigger myself, and I have plenty<br>
of experience with this. And the time you spend solving these<br>
problems is like 1% of total rig time. Besides, you always have to<br>
hide something, all good rigs work that way, in all apps.<br>
<br>
And animators should *never* tamper with rigs, ever. That's why you<br>
hire TDs. Rigging is simply too complicated for casual tampering with<br>
it. If something breaks, you have your TD fix it. You should never<br>
expect your animators too, unless their doubling as TDs.<br>
<font color="#888888"><br>
Joe<br>
</font><div><div></div><div class="h5">_______________________________________________<br>
Bf-funboard mailing list<br>
<a href="mailto:Bf-funboard@blender.org">Bf-funboard@blender.org</a><br>
<a href="http://lists.blender.org/mailman/listinfo/bf-funboard" target="_blank">http://lists.blender.org/mailman/listinfo/bf-funboard</a><br>
</div></div></blockquote></div><br>