The Developer kit Manager is a convenience tool made for users who work with different Development kits. With this tool you first configure the locations and properties of your development kits in the Avastar Addon Preferences. then later you can quickly create new characters directly from your development kits and ready made for usage in Avastar.

Developerkit Manager

Note: We do not ship any third party developer kits!
You have to get the developer kits from their creators!

Sidenote: How to get the Avamesh Developer kit:

  • Open the Developer kit Manager.
  • Select Avamesh – Female

Note: The Avamesh is just a Demo model. Please use it for your own education. But you are also free to use it as a basis for your own projects, you can upload to SL and we encourage you to improve it as you like. We are happy when you share your improvements with us.

Below you find a brief overview for how to use this tool.

You find the Developer kits Manager in the Avastar Tool Shelf in its own Tool Panel.  Avastar ships with the Avamesh developer kit (this is our own kit). So on a fresh installation of Avastar you will only see one entry for Avamesh as shown in the image aside.

Your next step is to configure your developer kits. You open the configuration screen by Click on the Add/Edit Configuration button.



Here is a screen shot of the Developer kit Configuration panel in the Avastar Addon Preferences. Of course all fields are empty at the beginning. In the screen shot we have already added a new developer kit configuration and added it to the Configuration list by hitting the button Add/Replace Developer kit Preset (see image):

Usage Tips

The customization looks a bit complicated first. But you will quickly find out that most fields are self explaining. However there are a few points that may cause problems:

  • SL supports 2 Joint Types (POS and PIVOT) and unfortunately both types are used by different Developer kits. Sometimes it is even necessary to set the joint type of the imported rig differently from the joint type of the final Avastar character. You see the joint types are wrong when you get small deviations on shoulders and chest after importing your attachments to SL.
  • You want to transfer joints only when the Developer kit is a non human rig or when it is reportedly modified (Note: for A-Posed rigs you have to enable this option, see next line!)
  • When the imported rig only uses a different pose but has otherwise no joints edited (Belleza and TMP are examples for this) then you still have to Transfer Joints, but you also can use the Use Bind Pose option in that case.
  • When your imported rig has significant changes from the default SL Rig (significant joint edits) then be careful with the Use bind pose option.
  • Also when your imported rig is scaled up or down for tinies and giants, then please be very careful with using the bond pose option. It may give you a lot of trouble in those cases.


You can configure as many development kits as you like. the only restrictions are:

  1. We only support blend files and Collada files.
  2. We can only configure one armature per file. If a Developer kit comes with multiple armatures in one file then we can not handle this properly for now.
  3. We do not distribute Developer kits. You must get the kits from their creators. (Avamesh is our own demo developer kit)

When you are done then the Rig Importer changes its display as seen on the image aside. You now can click on the Buttons to get a ready made Developer kit model placed into the scene.