{"id":892,"date":"2015-11-03T20:49:04","date_gmt":"2015-11-03T20:49:04","guid":{"rendered":"http:\/\/avastar.online\/?page_id=892"},"modified":"2015-11-03T20:49:04","modified_gmt":"2015-11-03T20:49:04","slug":"export","status":"publish","type":"page","link":"https:\/\/avalab.org\/avastar\/292\/reference\/troubleshooting\/export\/","title":{"rendered":"Export Errors"},"content":{"rendered":"

<\/i> Troubleshoot Collada Export Warnings\/Errors<\/span><\/h3>\n

Warnings<\/h3>\n
\n
\n

When exporting meshes with the Avastar Collada exporter, our tool detects possible issues which may or may not become an issue when you later upload to the target system. In that case you get a popup window after export with a list of possible issues.<\/p>\n<\/div>\n

\n

\"\"<\/a><\/p>\n<\/div>\n<\/div>\n

Errors<\/h3>\n
\n
\n

Sometimes Avastar detects serious issues which can not be exported in a good way. In this case You will get another similar popup that lists all issues.<\/p>\n<\/div>\n

\n

\"\"<\/a><\/p>\n<\/div>\n<\/div>\n

If there is more detailed information available, then you find an additional (?) Icon on the left side of the message. Click on this icon to open a web page with more information.<\/p>\n

Known Issues with Importing to SL<\/h3>\n

MAV_BLOCK Parsing error<\/h3>
\n
\n
\n

If you create small objects with disconnected sub-meshes, then you often get errors labelled as MAV_BLOCK Error when you try to upload your mesh to Second Life.<\/p>\n

The image aside gives a nice example of a single object that is made of many smaller disconnected submeshes. While there is nothing wrong with this mesh, the SL Importer often has trouble to import the mesh.<\/p>\n<\/div>\n

\n

\"reference-058\"<\/a><\/p>\n<\/div>\n<\/div>\n

The reason for this issue is hidden somewhere in the Second Life Upload process. We believe the reason for the issue is that the SL Importer deletes Submeshes when they become too small. Then suddenly a part of the Mesh gets removed and this can end in a situation where a complete texture face is no longer available in one of the LOD’s. Then the SL Importer runs into this issue.<\/p>\n

A known Workaround<\/h3>\n

In all cases where small submeshes where involved, we found that adding your own (simple) physics mesh to your Object solves the problems:<\/p>\n

    \n
  • Create a simple mesh like a cube or a tetrahedron for example. The size of the mesh does not matter.<\/li>\n
  • Export this simple mesh as Collada file<\/li>\n
  • Import your Mesh as usual.<\/li>\n
  • But before uploading visit the physics tab of the SL importer<\/li>\n
  • There add Physics mesh from file<\/li>\n
  • select your simple object<\/li>\n<\/ul>\n

    Now the upload should work.
    \n<\/div><\/div>\n\n

    DAE Parsing Errors<\/h3>
    \n

    Second Life users frequently report a Dae parsing error<\/span><\/em><\/strong>. We found a couple of situations where this error appears (see below). However, in general your first step is to look into the Second Life Viewer Logfile…<\/p>\n

    Find the Viewer Logfile<\/h3>\n
    \n
    The logfile is named SecondLife.log<\/em><\/span> (assuming you use the default SL Viewer). Different viewers might use different names.<\/div>\n
    Typical locations where the logfiles can be found:<\/div>\n
    <\/div>\n
    Windows XP<\/span><\/strong> C:\\Documents and Settings\\%USERNAME%\\Application Data\\SecondLife\\logs\\<\/div>\n
    Windows 7<\/span><\/strong> C:\\Users\\%USERNAME%\\AppData\\Roaming\\SecondLife\\logs\\<\/div>\n<\/div>\n

    Typical causes for this issue<\/h3>\n
    \n
    \n

    Special characters in Object names<\/h4>\n

    Most dangerous characters are: & < ! > # $ ‘ “<\/strong><\/span><\/p>\n<\/div>\n

    \n

    Resolution:<\/h4>\n

    Remove special characters in Object names and then export again<\/p>\n<\/div>\n<\/div>\n

    \n
    \n

    Special characters in File names<\/h4>\n

    Most dangerous characters are: & < ! > # $ ( * ) [ ] { } ‘ “<\/span><\/p>\n<\/div>\n

    \n

    Resolution:<\/h4>\n

    Remove special characters in file names (renaming the .dae file should be enough)<\/p>\n<\/div>\n<\/div>\n

    \n
    \n

    Extremely dense Meshes<\/h4>\n

    Please check if your mesh contains areas with very small triangles (edge length smaller than about 1 millimeter)<\/p>\n<\/div>\n

    \n

    Resolution:<\/h4>\n

    Try to avoid high resolution meshes. You are doing better when you put high density into textures and normal maps (Normal maps are now supported by Second Life)<\/p>\n<\/div>\n<\/div>\n

    \n
    \n

    Orphaned edges and vertices<\/h4>\n

    If your mesh contains edges which do not belong to any face or disconnected vertices.<\/p>\n<\/div>\n

    \n

    Resolution:<\/h4>\n

    Remove these edges and vertices.
    \nHint:<\/strong> <\/span>in Edit mode Select -> Non Manifold<\/em> to find candidates. You may want to disable the “boundary” option in the operator panel.<\/p>\n<\/div>\n<\/div>\n

    \n
    \n

    Duplicate Vertices<\/h4>\n

    If your mesh contains duplicate vertices this can cause issues. However sometimes duplicate verts are on purpose (for example when you use the split edge modifier in Blender 2.73 or older) so you need to test if this issue is caused by split edge or by accidental duplicates.<\/p>\n<\/div>\n

    \n

    Resolution:<\/h4>\n

    Remove the duplicate vertices.
    \nHint:<\/strong> <\/span>in Edit mode ‘W’ -> Remove Doubles<\/em> to delete the duplicates.<\/p>\n<\/div>\n<\/div>\n

     <\/p>\n\n<\/div><\/div>\n","protected":false},"excerpt":{"rendered":"

    Troubleshoot Collada Export Warnings\/Errors Warnings When exporting meshes with the Avastar Collada exporter, our tool detects possible issues which may or may not become an issue when you later upload to the target system. In that case you get a popup window after export with a list of possible issues. Errors Sometimes Avastar detects serious […]<\/p>\n","protected":false},"author":2,"featured_media":5819,"parent":2489,"menu_order":20,"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-892","page","type-page","status-publish","has-post-thumbnail","hentry","category-help"],"_links":{"self":[{"href":"https:\/\/avalab.org\/avastar\/292\/wp-json\/wp\/v2\/pages\/892","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/avalab.org\/avastar\/292\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/avalab.org\/avastar\/292\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/avalab.org\/avastar\/292\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/avalab.org\/avastar\/292\/wp-json\/wp\/v2\/comments?post=892"}],"version-history":[{"count":0,"href":"https:\/\/avalab.org\/avastar\/292\/wp-json\/wp\/v2\/pages\/892\/revisions"}],"up":[{"embeddable":true,"href":"https:\/\/avalab.org\/avastar\/292\/wp-json\/wp\/v2\/pages\/2489"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/avalab.org\/avastar\/292\/wp-json\/wp\/v2\/media\/5819"}],"wp:attachment":[{"href":"https:\/\/avalab.org\/avastar\/292\/wp-json\/wp\/v2\/media?parent=892"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/avalab.org\/avastar\/292\/wp-json\/wp\/v2\/categories?post=892"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/avalab.org\/avastar\/292\/wp-json\/wp\/v2\/tags?post=892"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}