unmergedPolygon list too long (length of triangles instead of polygons)

If there were any quads or other type of submeshes in the model, then
the unmergedPolygon list would be too long and add dummy values at the
end. This was causing the crash in Max.

Author: vkovec

Assets/FbxExporters/Editor/FbxExporter.cs

@@ -585,8 +585,7 @@ void ExportMesh (MeshInfo meshInfo, FbxNode fbxNode)
                     }
                 }
 
-                int[] unmergedPolygons = new int[meshInfo.Triangles.Length];
-                int current = 0;
+                var unmergedPolygons = new List<int> ();
                 var mesh = meshInfo.mesh;
                 for (int s = 0; s < mesh.subMeshCount; s++) {
                     var topology = mesh.GetTopology (s);
@@ -624,12 +623,11 @@ void ExportMesh (MeshInfo meshInfo, FbxNode fbxNode)
 
                             // Save the polygon order (without merging vertices) so we
                             // properly export UVs, normals, binormals, etc.
-                            unmergedPolygons [current] = polyVert;
+                            unmergedPolygons.Add(polyVert);
 
                             polyVert = ControlPointToIndex [meshInfo.Vertices [polyVert]];
                             fbxMesh.AddPolygon (polyVert);
 
-                            current++;
                         }
                         fbxMesh.EndPolygon ();
                     }
@@ -643,7 +641,7 @@ void ExportMesh (MeshInfo meshInfo, FbxNode fbxNode)
                 AssignLayerElementMaterial (fbxMesh, meshInfo.mesh, meshInfo.Materials.Length);
 
                 // Set up normals, etc.
-                ExportComponentAttributes (meshInfo, fbxMesh, unmergedPolygons);
+                ExportComponentAttributes (meshInfo, fbxMesh, unmergedPolygons.ToArray());
 
                 // set the fbxNode containing the mesh
                 fbxNode.SetNodeAttribute (fbxMesh);