{"id":4411,"date":"2018-09-30T19:42:57","date_gmt":"2018-09-30T19:42:57","guid":{"rendered":"http:\/\/avastar.guru\/?page_id=4411"},"modified":"2018-09-30T19:42:57","modified_gmt":"2018-09-30T19:42:57","slug":"bind-pose","status":"publish","type":"page","link":"https:\/\/avalab.org\/avastar\/292\/avastar-workflows\/bind-pose\/","title":{"rendered":"Bind Pose"},"content":{"rendered":"

<\/image> Working with Bind Poses<\/h2>\n
\n
\n

In previous Avastar releases we always needed to eventually use the T-posed Character when we were creating models and attachments with human shapes. We did so to keep compatible to the SL\u00a0 T-Pose rig (experts may remember the Alter to Restpose Option that we provided for this purpose).<\/p>\n<\/div>\n

\"\"<\/a><\/div>\n<\/div>\n
\n
\n

In Avastar-2 we are no longer forced to handle the T Pose. Instead of that you can now work in any Restpose (technically named: Bind Pose). Avastar can now calculate the necessary extra data that is needed by the SL Importer to handle these Rigs properly.<\/p>\n

Besides supporting arbitrary Bind poses we also added a few extra functions so that you can create your custom rigs more efficiently…<\/p>\n<\/div>\n

\n

\u00a0\"\"<\/a><\/p>\n<\/div>\n<\/div>\n

Bind poses and Developer kits<\/h2>\n
\n
\n
\n\t\t\t\t\t
If you are working with Developer kits then you actually can not freely decide which Restpose (T-Pose, A-Pose, …) you want to use. In fact the pose used by the developerkit must be used by you as well.<\/p>\n

If you try to enforce to use a restpose different from a Developer kit, you always will end up with mismatched clothes!<\/strong><\/div><\/div>\n\n<\/div>\n

\n
\"\"<\/a>

A Develoepr Kit using an A-Posed upper body Rig.<\/p><\/div>\n<\/div>\n<\/div>\n

Some Rules of thumb<\/h3>\n