{"id":725,"date":"2015-10-18T11:28:52","date_gmt":"2015-10-18T11:28:52","guid":{"rendered":"http:\/\/avastar.online\/?page_id=725"},"modified":"2022-07-31T12:45:03","modified_gmt":"2022-07-31T12:45:03","slug":"rig-converter","status":"publish","type":"page","link":"https:\/\/avalab.org\/avastar\/300\/reference\/usermanual\/advanced\/devkits\/users\/rig-converter\/","title":{"rendered":"The Rig Converter"},"content":{"rendered":"

<\/image> Development Kits and the Rig Converter tool<\/h2>\n
\n
\n

Some creators of full mesh bodies provide Mesh Development Kits<\/span><\/em>. These kits typically contain Reference Meshes<\/em><\/span> and reference weight maps for the developing of body attachments (clothes).<\/p>\n

This document explains how you can use the Avastar Rig Converter to get a development kit imported into Avastar.<\/p>\n<\/div>\n

\n

<\/p>\n<\/div>\n<\/div>\n

Important: This document is a last resort when the Developerkit Manager fails!
\n<\/strong>We strictly recommend that you use the Avastar Developerkit Manager instead of using the Rig Conversion tool. Please read on only when the Developerkit manager fails for any reason. In that case please also report to us how the Developerkit Manager failed.<\/p>\n

\n\t\t\t\t\t

Disclaimer<\/h3>\n

If you are a Developer kit User<\/strong><\/p>\n

Whenever you run into an issue with a developer kit integration, we must strictly recommend you to ask the kit creator for help. It is important that the creator has kept their distributed working files up-to-date for use with Avastar. You may wish to suggest to the creator that they can contact us for help if they are not able to help you.<\/p>\n

If you are a Developer kit Creator<\/strong><\/p>\n

We provide help with getting your kit to work with Avastar if – and only if – you send us a copy of your developer kit for inspection. Also we only check Developerkits which also provide Collada files. Otherwise we won’t be able to help you or your customers with any issue resulting from the usage of your developer kit.<\/p><\/div><\/div>\n

Ok, so lets get started<\/h3>\n

Lets assume you got the Developer kit in some readable form, such as .obj (Wavefront) or .dae (Collada) file, .fbx file or even as ready made blend file. The models may already be rigged, or not, this does not matter, we also can work with simple unrigged mesh models. In general you will proceed as follows:<\/p>\n

Try first with the Developerkit Manager<\/h4>\n

Really! We tell this often to remind you that the Developerkit Manager is the way to go. Anything else is meant to be a workaround (please report any failure to us!)<\/p>\n

The Developerkit Manager should make the import of a Developerkit a snap when<\/p>\n