{"id":286,"date":"2015-10-10T20:25:45","date_gmt":"2015-10-10T20:25:45","guid":{"rendered":"http:\/\/avastar.online\/?page_id=286"},"modified":"2015-10-10T20:25:45","modified_gmt":"2015-10-10T20:25:45","slug":"collada-avastar","status":"publish","type":"page","link":"https:\/\/avalab.org\/avastar\/279\/help\/io\/collada-avastar\/","title":{"rendered":"Collada Avastar"},"content":{"rendered":"<div class=\"row-fluid\">\n<div class=\"rhcol span10\">\n<h3><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> Export as Collada<\/h3>\n<\/div>\n<div class=\"rhcol span2\"><a class=\"mamap\" href=\"\/wp-content\/uploads\/2015\/10\/map_collada1_panel.png\" target=\"_blank\"><img decoding=\"async\" alt=\"\" src=\"\/wp-content\/uploads\/2015\/10\/map_collada1_panel.png\" \/><\/a><\/div>\n<\/div>\n<div class=\"row-fluid\">\n<div class=\"rhcol span7\">\n<p>The Collada exporter exports your Mesh character or mesh attachment to a form that is recognizable by the target System (SL, OpenSim or any compatible online world). You find the Mesh Exporter in the Blender Export menu.<\/p>\n<p>The Exporter opens with a file selection window where you can select the file to where you want to export, or you can type in a new filename.<\/p>\n<p><strong><span style=\"color: #3366ff;\">Note:<\/span><\/strong> If you prefer to see the Collada exporter in the Tool Shelf, then you can customize the Avastar Add-on Preferences.<\/p>\n<\/div>\n<div class=\"rhcol span5\"><a href=\"https:\/\/avalab.org\/avastar\/279\/wp-content\/uploads\/2015\/10\/Image355-1.png\"><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter size-full wp-image-1507\" src=\"https:\/\/avalab.org\/avastar\/279\/wp-content\/uploads\/2015\/10\/Image355-1.png\" alt=\"Image355\" width=\"412\" height=\"286\" srcset=\"https:\/\/avalab.org\/avastar\/279\/wp-content\/uploads\/2015\/10\/Image355-1.png 412w, https:\/\/avalab.org\/avastar\/279\/wp-content\/uploads\/2015\/10\/Image355-1-300x208.png 300w\" sizes=\"auto, (max-width: 412px) 100vw, 412px\" \/><\/a><\/div>\n<\/div>\n<div class=\"row-fluid\">\n<div class=\"rhcol span10\">\n<h3>The Export option Panel<\/h3>\n<\/div>\n<div class=\"rhcol span2\"><a class=\"mamap\" href=\"\/wp-content\/uploads\/2015\/10\/map_collada2_panel.png\" target=\"_blank\"><img decoding=\"async\" alt=\"\" src=\"\/wp-content\/uploads\/2015\/10\/map_collada2_panel.png\" \/><\/a><\/div>\n<\/div>\n<div class=\"row-fluid\">\n<div class=\"rhcol span7\">\n<p><strong><span style=\"color: #99ccff;\"><span style=\"color: #3366ff;\">Hint:<\/span> <\/span><\/strong>You usually can keep the default settings and just click on the &#8220;Collada(Avastar)(.dae)&#8221; button in the upper right corner of the Window (see zoom icon in this chapter title).<\/p>\n<p>A File Selector will pop up. Here you can navigate to your export directory and then export your file as a Collada file (using the file extension &#8220;.dae&#8221;)<\/p>\n<\/div>\n<div class=\"rhcol span5\">\n<p><a href=\"https:\/\/avalab.org\/avastar\/279\/wp-content\/uploads\/2015\/10\/Image356.png\"><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter wp-image-1510 size-full\" src=\"https:\/\/avalab.org\/avastar\/279\/wp-content\/uploads\/2015\/10\/Image356.png\" width=\"236\" height=\"165\" \/><\/a><\/p>\n<\/div>\n<\/div>\n<div class=\"row-fluid\">\n<div class=\"rhcol span7\">\n<p><span style=\"color: #0000ff;\"><strong>Tip:<\/strong> <\/span>If you intend to use your exported mesh for Animesh then please note that Animesh currently does not support the Appearance sliders. Your mesh will always shows as when you enable the white Stickman preset in the <a href=\"https:\/\/avastar.guru\/help\/toolshelf\/appearance-sliders\/\">Avastar Appearance slider<\/a> panel.<\/p>\n<\/div>\n<div class=\"rhcol span5\">\n<p><a href=\"http:\/\/avastar.guru\/wp-content\/uploads\/2015\/10\/Image379.png\"><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter size-full wp-image-1627\" src=\"http:\/\/avastar.guru\/wp-content\/uploads\/2015\/10\/Image379.png\" alt=\"\" width=\"227\" height=\"82\" \/><\/a><\/p>\n<\/div>\n<\/div>\n<h3>The Export option Sub-panels<\/h3>\n<p>The Exporter provides a couple of export options for special cases. Please use these options with care.<\/p>\n<div class=\"symple-toggle state-closed \"><h3 class=\"symple-toggle-trigger \">Modifiers<\/h3><div class=\"symple-toggle-container symple-clearfix\">\n<div class=\"row-fluid\">\n<div class=\"rhcol span7\">\n<p>By default Avastar applies all mesh changing Modifiers except the <span style=\"color: #ff6600;\"><em>Armature Modifiers<\/em><\/span> to the exported meshes. However, some modifiers offer 2 sets of options, one option set is for rendering, the other option set is for the Viewport. We offer 3 options here:<\/p>\n<\/div>\n<div class=\"rhcol span5\"><a href=\"https:\/\/avalab.org\/avastar\/279\/wp-content\/uploads\/2015\/10\/modifier_export.jpg\"><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter wp-image-302 size-full\" src=\"https:\/\/avalab.org\/avastar\/279\/wp-content\/uploads\/2015\/10\/modifier_export.jpg\" alt=\"modifier_export\" width=\"187\" height=\"101\" \/><\/a><\/div>\n<\/div>\n<div class=\"row-fluid\">\n<div class=\"rhcol span12\">\n<ul>\n<li><em>Apply according to the <strong>View Settings<\/strong><\/em> (the 3D Preview settings)<\/li>\n<li><em>Apply according to the <strong>Render Settings<\/strong><\/em> (the settings for Blender&#8217;s own Renderer)<\/li>\n<li><em>Don&#8217;t apply modifiers and only export the base mesh<br \/>\n<\/em><\/li>\n<\/ul>\n<p>The exporter by default applies the <strong><em>View settings<\/em><\/strong>. These settings are very closely related to the Blender Render System. In most cases you can actually just use the defaults. We will get back to this when we talk about how to use (or not use) Modifiers.<\/p>\n<\/div>\n<\/div>\n<h3>Side note: The Armature Modifier<\/h3>\n<div class=\"row-fluid\">\n<div class=\"rhcol span7\">\n<p>Armature Modifiers define the relation between your meshes and your Skeleton (Armature). Avastar never applies the Armature Modifiers when exporting because the mesh would be transformed to static non rigged Meshes. This is almost never what you want.<\/p>\n<p><strong><span style=\"color: #3366ff;\">For the curious:<\/span> <\/strong>You find the Armature modifier in the Modifier Stack (see image). Remind: Armature modifiers are always defined in the mesh modifier stack. Armatures them self have no Armature modifier.<\/p>\n<p>We will get to armature Modifiers in the &#8220;<a title=\"Create an attachment\" href=\"http:\/\/blog.machinimatrix.org\/avastar\/reference\/create-an-attachment\/\">Create an Attachment<\/a>&#8221; tutorial.<\/p>\n<\/div>\n<div class=\"rhcol span5\">\n<div id=\"attachment_303\" style=\"width: 310px\" class=\"wp-caption aligncenter\"><a href=\"https:\/\/avalab.org\/avastar\/279\/wp-content\/uploads\/2015\/10\/modifiers.png\"><img loading=\"lazy\" decoding=\"async\" aria-describedby=\"caption-attachment-303\" class=\"wp-image-303 size-medium\" src=\"http:\/\/avastar.online\/wp-content\/uploads\/2015\/10\/modifiers-300x268.png\" alt=\"modifiers\" width=\"300\" height=\"268\" srcset=\"https:\/\/avalab.org\/avastar\/279\/wp-content\/uploads\/2015\/10\/modifiers-300x268.png 300w, https:\/\/avalab.org\/avastar\/279\/wp-content\/uploads\/2015\/10\/modifiers.png 314w\" sizes=\"auto, (max-width: 300px) 100vw, 300px\" \/><\/a><p id=\"caption-attachment-303\" class=\"wp-caption-text\">Hint: You want to display the modifier in edit mode and adjust edit cage to modifier result<\/p><\/div>\n<\/div>\n<\/div>\n<\/div><\/div>\n<div class=\"symple-toggle state-closed \"><h3 class=\"symple-toggle-trigger \">Textures export (advanced)<\/h3><div class=\"symple-toggle-container symple-clearfix\">\n<div class=\"row-fluid\">\n<div class=\"rhcol span7\">You can export images along with your models. In that case Avastar stores the images as files on your disk and adds a reference to the Collada file. The SL Importer knows how to read and import these images for static meshes.<br \/>\n<span style=\"color: #3366ff;\"><strong>Note:<\/strong> <\/span>But for rigged meshes the images are not recognized.<\/div>\n<div class=\"rhcol span5\"><a href=\"https:\/\/avalab.org\/avastar\/279\/wp-content\/uploads\/2015\/10\/texture_export.jpg\"><img loading=\"lazy\" decoding=\"async\" class=\"size-full wp-image-304 aligncenter\" src=\"https:\/\/avalab.org\/avastar\/279\/wp-content\/uploads\/2015\/10\/texture_export.jpg\" alt=\"texture_export\" width=\"187\" height=\"171\" \/><\/a><\/div>\n<\/div>\n<div class=\"row-fluid\">\n<div class=\"rhcol span7\">\n<ul>\n<li><strong><span style=\"color: #ff6600;\">UV Textures &amp; Material Textures<\/span>: <\/strong>Blender supports Material based textures and UV textures (which are directly assigned to polygons). Normally you want to export only the UV textures. In rare cases it is more desirable to export the material based textures instead. But beware, Blender does not export the render results, but only the source images!<\/li>\n<li><span style=\"color: #ff6600;\"><strong>Image Type:<\/strong> <\/span> The image format is typically predefined in the Blender Render settings. However we found it convenient to offer an immediate setting in the Exporter. By default the exporter applies the image type only to generated images.<\/li>\n<li><span style=\"color: #ff6600;\"><strong>Use &#8216;Image format&#8217; for all images:<\/strong><\/span> If you set this option, then Blender will use the selected image format for all exported images. If you disable the option, then only the generated images are affected.<\/li>\n<\/ul>\n<\/div>\n<div class=\"rhcol span5\">\n<ul>\n<li><strong><span style=\"color: #ff6600;\">Use RGBA:<\/span> <\/strong>Blender can export the Alpha channel for images. Normally you set this in the render settings where you can specify to use either RGB or RGBA for image exports. If the selected export format supports Alpha then enabling RGBA here will export images with Alpha channel even if the render settings are set to RGB and vice versa.<\/li>\n<\/ul>\n<\/div>\n<\/div>\n<p><span style=\"color: #3366ff;\"><strong>Hint: <\/strong><\/span>You may want to NOT use RGBA because of the Alpha glitch. However this is not a general advice. There are many situations where using Alpha images is even recommended (when you want to create an Alpha mask).<\/p>\n<p><span style=\"color: #3366ff;\"><strong>Hint:<\/strong> <\/span>If the format of the exported image(es) does not support an Alpha channel then the &#8220;Use RGBA&#8221; option is simply ignored.<\/p>\n<\/div><\/div>\n<div class=\"symple-toggle state-closed \"><h3 class=\"symple-toggle-trigger \">Advanced options<\/h3><div class=\"symple-toggle-container symple-clearfix\">\n<div class=\"row-fluid\">\n<div class=\"rhcol span7\">\n<p>The Advanced Options are related to special scenarios. You should normally keep all options set as they are. This makes sure that your exports are well suited for SL. However in some situations you will have to get back here and set the options according to the descriptions below.<\/p>\n<p><span style=\"color: #ff6600;\"><strong>Warning: <\/strong><\/span>You must really know what you do when you set an advanced option. Handle with care!<\/p>\n<\/div>\n<div class=\"rhcol span5\">\n<p><a href=\"https:\/\/avalab.org\/avastar\/279\/wp-content\/uploads\/2019\/02\/Image059.png\"><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter wp-image-4881 size-full\" src=\"https:\/\/avalab.org\/avastar\/279\/wp-content\/uploads\/2019\/02\/Image059.png\" alt=\"\" width=\"238\" height=\"680\" srcset=\"https:\/\/avalab.org\/avastar\/279\/wp-content\/uploads\/2019\/02\/Image059.png 238w, https:\/\/avalab.org\/avastar\/279\/wp-content\/uploads\/2019\/02\/Image059-105x300.png 105w\" sizes=\"auto, (max-width: 238px) 100vw, 238px\" \/><\/a><\/p>\n<\/div>\n<\/div>\n<div class=\"row-fluid\">\n<div class=\"rhcol span7\">\n<p><strong><span style=\"color: #ff6600;\">Use Bind Pose:<\/span><\/strong> The Use Bind Pose option is largely documented in the <a href=\"\/workflows\/bind-pose\/\">Bind Pose Workflow<\/a><br \/>\nYou normaly set this option in the Appearance Sliders. We added it here only for convenience.<\/p>\n<\/div>\n<div class=\"rhcol span5\">\n<p><a href=\"https:\/\/avalab.org\/avastar\/279\/wp-content\/uploads\/2019\/02\/Image734.png\"><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter wp-image-4882 size-full\" src=\"https:\/\/avalab.org\/avastar\/279\/wp-content\/uploads\/2019\/02\/Image734.png\" alt=\"\" width=\"238\" height=\"106\" \/><\/a><\/p>\n<\/div>\n<\/div>\n<p>Following options are only available when the Use Bind Pose option is enabled:<\/p>\n<ul>\n<li><strong>Export Visual(new in Avastar-2.6): <\/strong>Avastar tries to minimize the number of translation components in joint offsets to achieve the best possible (the easiest) rig configuration. Normally you want to keep this option enabled. If you find that this option does not work for you,m then please send us a note, so we can improve the feature.<\/li>\n<li><strong>with Reset Animation (new in Avastar-2.6):<\/strong> Avastar generates a 0-priority single frame animation of the current Restpose. This animation can later be used in SL together with an animation reset script (see below)<\/li>\n<li><strong>with Reset Script(new in Avastar 2.6):<\/strong> Avastar generates an LSL Script ready for usage in SL. In SL you copy this script together with the Reset Animation (see above) into your model&#8217;s inventory. You need this especially when you are not exporting in white stickman mode (see <a href=\"\/fragment\/toolshelf\/appearance-sliders\/\">Appearance sliders<\/a>)<\/li>\n<\/ul>\n<div class=\"row-fluid\">\n<div class=\"rhcol span7\"><span style=\"color: #ff6600;\"><strong>Apply Armature Scale:<\/strong><\/span> If you have <strong><em>scaled your Armature in Object Mode<\/em> <\/strong>for making a tiny or a giant you should not apply the scale to the armature because then the entire Avastar Animation system may no longer work. But the Object Scale must be applied when you export the mesh.<\/div>\n<div class=\"rhcol span5\">Otherwise the target online world does not recognize the scaling and the giant shrinks back (or the tiny grows back) to normal size. The apply Armature Scale option ensures that the Object scale is applied in the exported Armature.<\/div>\n<\/div>\n<div class=\"row-fluid\">\n<div class=\"rhcol span7\"><span style=\"color: #ff6600;\"><strong>Apply Rotation &amp; Scale:<\/strong><\/span> If you have <strong><em>Scaled or rotated your Objects in Object Mode<\/em><\/strong> then this Scale&amp;Rotation should be applied to all objects of an export to avoid unexpected scaling and rotation issues within the target system. However this is all so often simply forgotten and sometimes even unknown.<\/div>\n<div class=\"rhcol span5\">Hence we have added an automatic apply Rotation&amp;Scale to the exporter. This setting does not affect the original objects.<\/div>\n<\/div>\n<div class=\"row-fluid\">\n<div class=\"rhcol span7\"><span style=\"color: #ff6600;\"><strong>Weld Edge Normals:<\/strong><\/span> When two separate objects share a boundary line, then you typically see a boundary seam in the object texture. This happens because the vertex normals differ even if the adjacent objects share the same vertex locations.<\/div>\n<div class=\"rhcol span5\">The exporter recalculates the vertex normals at the adjacent boundaries of the selected objects.<\/div>\n<\/div>\n<div class=\"row-fluid\">\n<div class=\"rhcol span7\"><span style=\"color: #ff6600;\"><strong>Weld to all visible: <\/strong><\/span>Sometimes you want to only export one part but still want the vertex normals be fixed.<\/div>\n<div class=\"rhcol span5\">This option lets the exporter take all visible objects into account when calculating the vertex normals at object boundaries.<\/div>\n<\/div>\n<h3>Bone Filters<\/h3>\n<div class=\"row-fluid\">\n<div class=\"rhcol span7\">\n<p><strong><span style=\"color: #ff6600;\">Export with Joints:<\/span><\/strong> When you have edited the Armature to adjust the Rig to your special character (Alien, creature, pet&#8230;) then you normally want to keep your edited Armature when you export your Meshes.<\/p>\n<p><strong><span style=\"color: #3366ff;\">Hint:<\/span> <\/strong>You want this option disabled only when your rig is so complex that Avastar can not calculate the Neutral Rig for your situation. In that case please set the sliders to SL Neutral and never touch the sliders again.<\/p>\n<\/div>\n<div class=\"rhcol span5\">\n<p><strong><span style=\"color: #3366ff;\">Disabled:<\/span><\/strong> Export the Rig visually as it is. Note: You must make sure that the Appearance Sliders are reset to the SL Neutral Shape (White Stickman Icon). Otherwise Avastar rejects the exports.<\/p>\n<p><span style=\"color: #3366ff;\"><strong>Enabled:<\/strong><\/span> Calculate the neutral skeleton from the current rig settings (temporary set Sliders to Neutral SL Settings) but apply the current Slider settings as bind pose. Pleased refer to the Bind Pose document for further explanations.<\/p>\n<\/div>\n<\/div>\n<div class=\"row-fluid\">\n<div class=\"rhcol span7\">\n<p><span style=\"color: #ff6600;\"><strong>Only Weighted Bones:<\/strong><\/span> Avastar can export all deform bones of the Rig. However in most cases it is enough to only export the deform Bones which are actually used (weighted to meshes)<\/p>\n<p><strong><span style=\"color: #3366ff;\">Hint:<\/span> <\/strong>You want to enable this option in most cases.<\/p>\n<\/div>\n<div class=\"rhcol span5\"><strong><span style=\"color: #3366ff;\">Disabled:<\/span> <\/strong>Export all deform Bones unconditionally<br \/>\n<strong><span style=\"color: #3366ff;\">Enabled:<\/span> <\/strong>Export only those bones which are actually used (have weights for meshes)<\/div>\n<\/div>\n<div class=\"row-fluid\">\n<div class=\"rhcol span7\">\n<p><strong><span style=\"color: #ff6600;\">Only Deform Bones:<\/span><\/strong> Avastar has many control bones (mainly for IK-animation, targetless Animation and attachment points) Avastar can export all Bones of the rig, or only the Deform bones<\/p>\n<p><strong><span style=\"color: #3366ff;\">Hint:<\/span> <\/strong>You want to enable this option in most cases.<\/p>\n<\/div>\n<div class=\"rhcol span5\"><strong><span style=\"color: #3366ff;\">Disabled:<\/span> <\/strong>Export all Bones in the Rig unconditionally<br \/>\n<strong><span style=\"color: #3366ff;\">Enabled:<\/span><\/strong> Export only deform Bones<\/div>\n<\/div>\n<div class=\"row-fluid\">\n<div class=\"rhcol span7\">\n<p><strong><span style=\"color: #ff6600;\">Include Parent Hierarchy:<\/span><\/strong> Ensures that all parent bones of exported bones are also exported, even if they have no weights defined.<\/p>\n<p>Details: When you enable the above bone filters then it can happen that not all bones of a Bone chain are exported. This becomes a problem when one or more of the not exported bones have Joint edits defined. Those definitions would then get lost during export.<\/p>\n<p><strong><span style=\"color: #3366ff;\">Hint:<\/span> <\/strong>You want to enable this option in most cases.<\/p>\n<\/div>\n<div class=\"rhcol span5\"><strong><span style=\"color: #3366ff;\">Disabled:<\/span> <\/strong>Do nothing<br \/>\n<strong><span style=\"color: #3366ff;\">Enabled:<\/span><\/strong> Take care that all parent bones of exported Bones are also exported.<\/div>\n<\/div>\n<div class=\"row-fluid\">\n<div class=\"rhcol span7\">\n<p><strong><span style=\"color: #ff6600;\">Export Bone Roll:<\/span><\/strong> Export Bone Roll using the Blender Collada Scheme.<\/p>\n<p><strong><span style=\"color: #3366ff;\">Hint:<\/span> <\/strong>This is only useful when you want to later import back the Dae file to Blender.<\/p>\n<\/div>\n<div class=\"rhcol span5\"><strong><span style=\"color: #3366ff;\">Disabled:<\/span> <\/strong>Do nothing<br \/>\n<strong><span style=\"color: #3366ff;\">Enabled:<\/span><\/strong> Export the Bone roll according to Blender&#8217;s Collada Scheme<\/div>\n<\/div>\n<div class=\"row-fluid\">\n<div class=\"rhcol span7\">\n<p><strong><span style=\"color: #ff6600;\">Export Bone layers:<\/span><\/strong> Export Bone Layer Data using the Blender Collada Scheme.<\/p>\n<p><strong><span style=\"color: #3366ff;\">Hint:<\/span> <\/strong>This is only useful when you want to later import back the Dae file to Blender.<\/p>\n<\/div>\n<div class=\"rhcol span5\"><strong><span style=\"color: #3366ff;\">Disabled:<\/span> <\/strong>Do nothing<br \/>\n<strong><span style=\"color: #3366ff;\">Enabled:<\/span><\/strong> Export the Bone Layer data according to Blender&#8217;s Collada Scheme<\/div>\n<\/div>\n<div class=\"row-fluid\">\n<div class=\"rhcol span7\">\n<p><span style=\"color: #ff6600;\"><strong>Export with Blender Profile: <\/strong><\/span>Use Blender Collada scheme for exporting Blender specific Information<\/p>\n<p><strong><span style=\"color: #3366ff;\">Hint:<\/span> <\/strong>This is only useful when you want to later import back the Dae file to Blender.<\/p>\n<\/div>\n<div class=\"rhcol span5\"><strong><span style=\"color: #3366ff;\">Disabled:<\/span> <\/strong>Do nothing<br \/>\n<strong><span style=\"color: #3366ff;\">Enabled:<\/span><\/strong> Export Extended Options according to Blender&#8217;s Collada Scheme<span style=\"color: #ff0000;\"><br \/>\n<\/span><\/div>\n<\/div>\n<div class=\"row-fluid\">\n<div class=\"rhcol span7\">\n<p>Export with SL Rotation: When you export an Avastar Rig then it must be rotated according to the SL Standards (so that the character looks into the positive X direction).<\/p>\n<p><strong><span style=\"color: #3366ff;\">Hint:<\/span> <\/strong>You want to enable this option when you export to Second Life or similar worlds.<\/p>\n<\/div>\n<div class=\"rhcol span5\"><strong><span style=\"color: #3366ff;\">Disabled:<\/span> <\/strong>Do nothing<br \/>\n<strong><span style=\"color: #3366ff;\">Enabled:<\/span><\/strong> Rotate the Rig by 90 degrees to make it compatible to the SL specifications<\/div>\n<\/div>\n<div class=\"row-fluid\">\n<div class=\"rhcol span7\">\n<p><strong><span style=\"color: #ff6600;\">Accept Attachment Weights:<\/span> <\/strong>SL does not allow weighting of attachment points. Hence we suppress the export of weights for attachment points by default.<\/p>\n<\/div>\n<div class=\"rhcol span5\">This option should indeed never be used for SL! <em><span style=\"color: #ff6600;\">Handle with Care. It is very likely that the SL importer rejects meshes with attachment point weighting at some time in the future.<\/span><\/em><\/div>\n<\/div>\n<p>&nbsp;<\/p>\n<div class=\"row-fluid\">\n<div class=\"rhcol span7\">\n<p>Sanity Checks: Perform tests on the Mesh (tricount, texture face counts, etc&#8230;)<\/p>\n<p><strong><span style=\"color: #3366ff;\">Hint:<\/span> <\/strong>You want to enable this option in most cases.<\/p>\n<\/div>\n<div class=\"rhcol span5\"><\/div>\n<\/div>\n<p>&nbsp;<\/p>\n<h3>Unsupported Options<\/h3>\n<div class=\"row-fluid\">\n<div class=\"rhcol span7\">\n<p>Avastar also provides some advanced export options. However those options are not shown by default as they are only rarely used.<\/p>\n<p>You enable these options in the Avastar Add-on Panel (where you initially enabled the Add-on after you installed it):<\/p>\n<div id=\"attachment_908\" style=\"width: 301px\" class=\"wp-caption aligncenter\"><a href=\"https:\/\/avalab.org\/avastar\/279\/wp-content\/uploads\/2015\/10\/reference-060.png\"><img loading=\"lazy\" decoding=\"async\" aria-describedby=\"caption-attachment-908\" class=\"wp-image-908 size-full\" src=\"https:\/\/avalab.org\/avastar\/279\/wp-content\/uploads\/2015\/10\/reference-060.png\" alt=\"reference-060\" width=\"291\" height=\"142\" \/><\/a><p id=\"caption-attachment-908\" class=\"wp-caption-text\">Tick the advanced export options to get the buttons in the UI<\/p><\/div>\n<\/div>\n<div class=\"rhcol span5\">\n<div id=\"attachment_1513\" style=\"width: 224px\" class=\"wp-caption aligncenter\"><a href=\"https:\/\/avalab.org\/avastar\/279\/wp-content\/uploads\/2015\/10\/Image357.png\"><img loading=\"lazy\" decoding=\"async\" aria-describedby=\"caption-attachment-1513\" class=\"wp-image-1513 size-full\" src=\"https:\/\/avalab.org\/avastar\/279\/wp-content\/uploads\/2015\/10\/Image357.png\" alt=\"Image357\" width=\"214\" height=\"202\" \/><\/a><p id=\"caption-attachment-1513\" class=\"wp-caption-text\">Advanced Export Panel with unsupported options enabled<\/p><\/div>\n<\/div>\n<\/div>\n<div class=\"row-fluid\">\n<div class=\"rhcol span7\">\n<p><strong><span style=\"color: #ff6600;\">Limit Weight Count:<\/span><\/strong> In SL the number of weights per vertex is strictly limited to 4. We believe this number is enough for all weighting tasks. In cases where you think this limit is too low, we always found the real problem was due to bad mesh topology and bad rigging.<\/p>\n<\/div>\n<div class=\"rhcol span5\">\n<p>Setting this number affects the maximum number of weights which are exported by Avastar. We strongly recommend to keep this number set to 4.<\/p>\n<\/div>\n<\/div>\n<div class=\"row-fluid\">\n<div class=\"rhcol span7\"><strong><span style=\"color: #ff6600;\">Include Deformer Shape<\/span><\/strong>: Some virtual worlds support the Mesh deformer which was originally developed for usage in Second Life.<\/div>\n<div class=\"rhcol span5\">When you enable this option, then the exporter creates an extra xml file. This XML file is later used by the SL Importer as reference shape (the Importer must support Deformer shapes, currently used with OpenSim)<\/div>\n<\/div>\n<\/div><\/div>\n\n <span style='color:red;font-size:1.2em;'>[include path='\/avastar-2\/troubleshooting\/export\/'] not found!<\/span> \n","protected":false},"excerpt":{"rendered":"<p>Export as Collada<\/p>\n","protected":false},"author":2,"featured_media":1507,"parent":3761,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"_et_pb_use_builder":"","_et_pb_old_content":"","_et_gb_content_width":"","footnotes":""},"categories":[4],"tags":[],"class_list":["post-286","page","type-page","status-publish","has-post-thumbnail","hentry","category-help"],"_links":{"self":[{"href":"https:\/\/avalab.org\/avastar\/279\/wp-json\/wp\/v2\/pages\/286","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=286"}],"version-history":[{"count":0,"href":"https:\/\/avalab.org\/avastar\/279\/wp-json\/wp\/v2\/pages\/286\/revisions"}],"up":[{"embeddable":true,"href":"https:\/\/avalab.org\/avastar\/279\/wp-json\/wp\/v2\/pages\/3761"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/avalab.org\/avastar\/279\/wp-json\/wp\/v2\/media\/1507"}],"wp:attachment":[{"href":"https:\/\/avalab.org\/avastar\/279\/wp-json\/wp\/v2\/media?parent=286"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/avalab.org\/avastar\/279\/wp-json\/wp\/v2\/categories?post=286"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/avalab.org\/avastar\/279\/wp-json\/wp\/v2\/tags?post=286"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}