{"id":3492,"date":"2018-04-30T14:35:08","date_gmt":"2018-04-30T14:35:08","guid":{"rendered":"http:\/\/avastar.guru\/?page_id=3492"},"modified":"2018-04-30T14:35:08","modified_gmt":"2018-04-30T14:35:08","slug":"intro-2","status":"publish","type":"page","link":"https:\/\/avalab.org\/avastar\/292\/reference\/usermanual\/advanced\/devkits\/creators\/intro-2\/","title":{"rendered":"Intro for creators"},"content":{"rendered":"

<\/image> Developer kits Intro<\/h2>\n

This is a short introduction mainly aimed at Developer kit creators who are not familiar with Blender and Avastar but want to prepare their Developer kit so that it can be used most efficiently from within Blender\/Avastar.<\/p>\n

Before you even begin<\/h2>\n

So you are a developerkit creator and you want to make the usage of your Developerkit with Avastar as easy as possible. And now you are eager to learn how that can be done. Relax! You are at the good place. But before we get into the details, please take a minute and understand:<\/p>\n

\n
\n
Your Right<\/strong><\/p>\n

Of course you are allowed to include Rigs to your Developerkit, even if the rigs are based on the Avastar Rig (changed or unchanged)<\/p>\n<\/div>\n<\/div>\n

\n
Your Duty<\/strong><\/p>\n

You have to take care of your customers on your own. We take no responsibility for your distribution.<\/p>\n<\/div>\n<\/div>\n<\/div>\n

The big exception<\/strong><\/p>\n

When you distribute your Developerkit as a Collada file which can be uploaded to SL without errors, then we support your users if they step into issues!<\/p>\n

So we strongly recommend to use Collada files instead of blend files because Blender and Avastar change frequently, while the Collada format remained pretty stable over the years<\/div>\n

Please take the above seriously. We simply have no capacities to help out every single user on their issues with your Developerkit. So now you know, now we can step forward to…<\/p>\n

Purpose of the Developer kit Manager<\/h2>\n

The following chapter describes the Developer kit Manager from the point of view of an Attachment maker. If you are a Developer kit creator then you still should read through this chapter so you can better understand what your users (attachment makers) are dealing with.<\/p>\n

The problem<\/h4>\n

Developer kits basically are reference models of already existing Avatar creations. A Developer kit is typically used for creating additional content (attachments) for those Avatar creations. Hence a Developer kit must ensure that whatever attachment is created with it can also later be attached easily to the same Avatar in SL (or OpenSim).<\/p>\n

Developer kits are often distributed as Collada files, less often they are provided as Blend files and sometimes they are even provided with an Avastar Rig. However in all cases the attachment makers always must take care to import the correct Collada file into Blender using the correct import options, or they need to load the Developer kit blend file with the correct version of Avastar and possibly a specific version of Blender and take care to never overwrite the Developer kit itself. This is a very error prone approach. The Developer kit manager comes to the rescue…<\/p>\n

The Developer kit Manager<\/h4>\n
\n
\n

The Developer kit Manager takes as input an original Developer kit file (Collada or Blend) as it was distributed by the Developer kit Creator, then it converts the Developer kit into an Avastar Rig, which finally can be used with Avastar…<\/p>\n

Provided the Developer kit creator has taken care to obey some pretty straight forward rules:<\/p>\n