{"id":2824,"date":"2017-12-27T20:59:19","date_gmt":"2017-12-27T20:59:19","guid":{"rendered":"http:\/\/avastar.online\/?page_id=2824"},"modified":"2017-12-27T20:59:19","modified_gmt":"2017-12-27T20:59:19","slug":"manager","status":"publish","type":"page","link":"https:\/\/avalab.org\/avastar\/279\/avastar-2\/reference\/advanced\/devkits\/users\/manager\/","title":{"rendered":"Manage Developer kits"},"content":{"rendered":"<h1><image src=\"\/avastar\/279\/wp-content\/uploads\/2019\/07\/approve_logo_250.png\" style=\"width:120px;vertical-align:middle;margin-left:0px;margin-right:10px;\"><\/image> Manage Developer kits<\/h1>\n<div class='three_fourth et_column_last'>\n\t\t\t\t\t\n\t\t\t\t<\/div><div class='clear'><\/div>\n<div class=\"row-fluid\">\n<div class=\"rhcol span11\">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.<\/div>\n<div class=\"rhcol span1\"><a class=\"mamap\" href=\"\/wp-content\/uploads\/2018\/08\/panel_devkit_manager.png\" target=\"_blank\"><img decoding=\"async\" alt=\"\" src=\"\/wp-content\/uploads\/2018\/08\/panel_devkit_manager.png\" \/><\/a><\/div>\n<\/div>\n<div style=\"min-height:200px;\"><iframe id=\"ytplayer\" type=\"text\/html\" width=\"100%\" src=\"https:\/\/www.youtube.com\/embed\/BHU7898ywK8?autoplay=1&t=29\" frameborder=\"0\"><\/iframe><\/div>\n<p><strong><div class=\"symple-box  black center \" style=\"text-align:left;\"> <span style=\"color: #ff99cc;\">Note: We do not ship any third party developer kits!<\/span><br \/>\n<span style=\"color: #ff99cc;\">You have to get the developer kits from their creators!<\/span><\/div><\/strong><\/p>\n<p><strong><div class=\"symple-box  tolightblue center \" style=\"text-align:left;\"> <\/strong><strong>Sidenote: How to get the Avamesh Developer kit:<br \/>\n<\/strong><\/p>\n<ul>\n<li><strong>Open the Developer kit Manager.<\/strong><\/li>\n<li><strong>Select <em>Avamesh &#8211; Female<\/em><\/strong><\/li>\n<\/ul>\n<p><strong><\/div><\/strong><\/p>\n<p>Below you find a brief overview for how to use this tool.<\/p>\n<div class=\"row-fluid\">\n<div class=\"span6 rhcol\">\n<p>You find the <span style=\"color: #ff6600;\">Developer kit Manager<\/span> in the Avastar Tool Shelf in its own Tool Panel. (The image has a wrong name, please apologize). Avastar ships with the Avamesh development kit. So on a fresh installation of Avastar you will only see one entry for Avamesh as shown in the image aside.<\/p>\n<p>Your next step is to open the Avastar Preferences panel and configure your developer kits.<\/p>\n<\/div>\n<p><a href=\"https:\/\/avalab.org\/avastar\/279\/wp-content\/uploads\/2018\/08\/Image557.png\"><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter size-full wp-image-3856\" src=\"https:\/\/avalab.org\/avastar\/279\/wp-content\/uploads\/2018\/08\/Image557.png\" alt=\"\" width=\"244\" height=\"376\" srcset=\"https:\/\/avalab.org\/avastar\/279\/wp-content\/uploads\/2018\/08\/Image557.png 244w, https:\/\/avalab.org\/avastar\/279\/wp-content\/uploads\/2018\/08\/Image557-195x300.png 195w\" sizes=\"auto, (max-width: 244px) 100vw, 244px\" \/><\/a><\/p>\n<div class=\"span6 rhcol\"><\/div>\n<\/div>\n<p>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 development kit configuration and added it to the Configuration list by hitting the button <em><span style=\"color: #ff6600;\">Add\/Replace Developer kit Preset<\/span><\/em> (see image):<\/p>\n<p><a href=\"https:\/\/avalab.org\/avastar\/279\/wp-content\/uploads\/2017\/12\/Image558.png\"><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter wp-image-2935 size-full\" src=\"https:\/\/avalab.org\/avastar\/279\/wp-content\/uploads\/2017\/12\/Image558.png\" alt=\"\" width=\"660\" height=\"465\" srcset=\"https:\/\/avalab.org\/avastar\/279\/wp-content\/uploads\/2017\/12\/Image558.png 660w, https:\/\/avalab.org\/avastar\/279\/wp-content\/uploads\/2017\/12\/Image558-300x211.png 300w\" sizes=\"auto, (max-width: 660px) 100vw, 660px\" \/><\/a><\/p>\n<h3>Usage Tips<\/h3>\n<p>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:<\/p>\n<ul>\n<li>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.<\/li>\n<li>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!)<\/li>\n<li>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<em><span style=\"color: #ff6600;\"> Use Bind Pose<\/span> <\/em>option in that case.<\/li>\n<li>When your imported rig has significant changes from the default SL Rig (significant joint edits) then be carefull with the Use bind pose option.<\/li>\n<li>Also when your imported rig is scaled up or down for tinies and giants, then please be very carefull with using the bond pose option. It may give you a lot of trouble in those cases.<\/li>\n<\/ul>\n<div class=\"row-fluid\">\n<div class=\"span6 rhcol\">\n<p>You can configure as many development kits as you like. the only restrictions are:<\/p>\n<ol>\n<li>We only support blend files and collada files<\/li>\n<li>We can only configure one kit per file. If your Developer kit comes with multiple armatures in one file then we can not handle this properly for now.<\/li>\n<\/ol>\n<p>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 Avastar character that uses the Developer kit meshes.<\/p>\n<\/div>\n<div class=\"span6 rhcol\">\n<p><a href=\"https:\/\/avalab.org\/avastar\/279\/wp-content\/uploads\/2017\/12\/Image559.png\"><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter size-full wp-image-2760\" src=\"https:\/\/avalab.org\/avastar\/279\/wp-content\/uploads\/2017\/12\/Image559.png\" alt=\"\" width=\"229\" height=\"422\" srcset=\"https:\/\/avalab.org\/avastar\/279\/wp-content\/uploads\/2017\/12\/Image559.png 229w, https:\/\/avalab.org\/avastar\/279\/wp-content\/uploads\/2017\/12\/Image559-163x300.png 163w\" sizes=\"auto, (max-width: 229px) 100vw, 229px\" \/><\/a><\/p>\n<\/div>\n<\/div>\n<p>&nbsp;<\/p>\n\n","protected":false},"excerpt":{"rendered":"<p>Manage Developer kits 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 [&hellip;]<\/p>\n","protected":false},"author":2,"featured_media":0,"parent":5193,"menu_order":2,"comment_status":"closed","ping_status":"closed","template":"","meta":{"_et_pb_use_builder":"","_et_pb_old_content":"","_et_gb_content_width":"","footnotes":""},"categories":[6],"tags":[],"class_list":["post-2824","page","type-page","status-publish","hentry","category-reference"],"_links":{"self":[{"href":"https:\/\/avalab.org\/avastar\/279\/wp-json\/wp\/v2\/pages\/2824","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/avalab.org\/avastar\/279\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/avalab.org\/avastar\/279\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/avalab.org\/avastar\/279\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/avalab.org\/avastar\/279\/wp-json\/wp\/v2\/comments?post=2824"}],"version-history":[{"count":0,"href":"https:\/\/avalab.org\/avastar\/279\/wp-json\/wp\/v2\/pages\/2824\/revisions"}],"up":[{"embeddable":true,"href":"https:\/\/avalab.org\/avastar\/279\/wp-json\/wp\/v2\/pages\/5193"}],"wp:attachment":[{"href":"https:\/\/avalab.org\/avastar\/279\/wp-json\/wp\/v2\/media?parent=2824"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/avalab.org\/avastar\/279\/wp-json\/wp\/v2\/categories?post=2824"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/avalab.org\/avastar\/279\/wp-json\/wp\/v2\/tags?post=2824"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}