Skip to content

Find the first representation that contains the defect

Diagnose mesh, topology, export, download, scale, orientation, texture and import problems in ASCAND results.

Start with a repeatable baseline
Browse the complete Tutorials

Find the first representation that contains the defect

Use this page when an identifiable ASCAND result exists, but a generated mesh, export, downloaded file or imported model behaves unexpectedly.

First separate the stages:

  1. reconstructed result;
  2. point cloud or mesh representation;
  3. export generation;
  4. downloaded file package; and
  5. interpretation by the destination application.

These artifacts can be related without being identical. Meshing connects or reconstructs surfaces from earlier geometry. Export preparation serializes a selected representation and may transform coordinate conventions. Transfer copies the result. Import software then interprets the file using its own supported features, unit assumptions and axis conventions.

Start at the earliest artifact you can inspect and move forward one stage at a time. If a hole, distortion or outlier already exists in the reconstructed result, changing formats cannot recover the missing or incorrect evidence. If the result is sound but the defect appears in the mesh, diagnose meshing. If the downloaded file differs from the generated export, diagnose delivery or integrity. If only one destination application displays it incorrectly, diagnose interpretation and compatibility.

A file that opens successfully is readable by that application. It is not thereby accurate, complete, correctly scaled or fit for use.

Preserve the source result, export record and failing files

Do not overwrite the first failing artifact. Keep the complete comparison set together:

  • project and object identity;
  • original source capture or source set;
  • Vision, Laser, Combo or Multi Merge method;
  • last accepted reconstructed result;
  • selected point-cloud, mesh or processed variant;
  • requested export format;
  • generated export and every companion file;
  • original downloaded archive or files;
  • extracted files without renaming or reorganizing them;
  • destination application and version;
  • import choices that were used;
  • exact message, screenshot and affected model region; and
  • every conversion, repair, rescale or re-export already attempted.

Record file size or an integrity value when the platform or operating system already exposes it, but do not invent missing metadata. Preserve both the original package and a separate working copy.

For a controlled comparison, change one factor. Examples include importing the same file with one documented unit choice, opening the same complete package in another compatible viewer, or exporting the same accepted representation in another verified format. Do not change format, scale, repair settings and destination application simultaneously.

Review the general evidence checklist.

Identify the last representation that is still correct

Compare the same model region at each available stage.

Ask:

  • Is the overall form already wrong in the reconstruction preview?
  • Are holes, outliers or doubled surfaces already present in the point cloud?
  • Does the first mesh introduce a bridge, closure, spike or lost feature?
  • Does the generated export differ from the mesh that was selected?
  • Does the local file package contain all expected files?
  • Does the defect appear only after import?

Use consistent viewpoints and, where dimensions matter, compare the same known dimension. Viewer shading, point size, perspective and back-face behavior can make identical geometry look different, so use geometry-aware inspection rather than appearance alone.

If the fault is already present in an accepted Vision result, use Vision Scan Problems. For Laser or Combo evidence, use Laser and Combo Scan Problems. If independently reconstructed scans become doubled or offset during registration, use Multi Merge Problems.

Continue here only when the first defective stage is meshing, export preparation, transfer or import.

Diagnose faces, topology, boundaries and normals

A point cloud contains samples. A mesh connects geometry into faces. The conversion can expose or introduce structural problems that do not exist as the same property in a point cloud.

Inspect for:

  • Open boundaries: edges that belong to an unclosed surface.
  • Non-manifold elements: edges or vertices whose connections do not describe one unambiguous surface neighborhood.
  • Disconnected components: separate shells or fragments.
  • Self-intersections: faces passing through other faces.
  • Degenerate faces: collapsed or near-zero-area triangles.
  • Inconsistent normals: face orientation that changes unexpectedly.
  • Inverted appearance: a shell that appears inside-out because its orientation or the viewer’s face-culling interpretation is inconsistent.

These properties are related but not interchangeable. A mesh can be closed and still self-intersect. It can be manifold and still describe the wrong shape. Normals can be consistent while the underlying geometry is incomplete.

Determine whether an open boundary follows a genuine gap in the reconstructed evidence or was introduced during surface generation. Determine whether a disconnected shell is a retained upstream fragment or a meshing artifact. Compare the mesh with the last accepted representation before repairing it.

Repair may make topology processable. It does not establish that added or changed surfaces match the original object.

Review topology before 3D printing.

Separate missing evidence from surfaces created during meshing or repair

Meshing and preparation can change geometry deliberately.

  • Hole filling creates a surface where the chosen representation had an opening.
  • Watertight reconstruction may infer bottoms, closures or connections.
  • Smoothing can reduce noise and also soften real edges.
  • Decimation can reduce file size and also remove small features.
  • Aggressive cleanup can remove thin structures with the outliers.
  • Surface reconstruction can bridge nearby regions that should remain separate.
  • Normal correction changes orientation, not the location of an incorrect surface.

Trace every unexpected bridge, filled recess, generated bottom, ripple, spike or missing feature to the first artifact that contains it.

If the required surface was never observed or supported by the reconstruction, another repair operation cannot turn an inferred closure into measured evidence. Choose whether the intended use accepts an explicitly inferred surface, requires deliberate remodeling, or requires recapture with complementary views or another evidence method.

Keep the repaired model as a derivative with a clear relationship to the untouched result. For manufacturing, continue with repair versus remodeling.

Verify the representation, format and complete file package

A representation describes the model’s information. A format describes how that information is stored.

Before diagnosing the extension, verify:

  1. which project and result produced the export;
  2. which semantic variant was selected;
  3. whether the intended content is a point cloud, mesh or application-specific model;
  4. whether points, faces, normals, color, texture coordinates or other required attributes are present;
  5. which serialization format was requested;
  6. whether export generation completed;
  7. whether the download contains one file or a package; and
  8. whether companion material, texture or metadata files remain together.

An extension alone is insufficient. PLY, for example, can carry point-based or face-based geometry depending on the export. A geometry-only mesh may correctly contain no texture. A textured model may depend on sidecar images or material definitions that must keep valid relative paths.

Not every scan produces every representation. Availability depends on confirmed processing outcomes. Do not substitute a different export silently or assume that a missing option proves that processing failed.

Choose the representation before the format.

Validate file integrity, units, axes and destination interpretation

Work on a copy of the original download and validate the handoff in order.

  1. Confirm that the transfer completed and the file or archive has a plausible non-zero size.
  2. Extract the package without discarding folders or companion files.
  3. Confirm that the destination application currently supports the representation and format variant.
  4. Import without destructive automatic repair where the application allows a neutral inspection path.
  5. Check whether points, faces, normals, colors, materials and textures appear as expected.
  6. Compare model dimensions with known project evidence.
  7. Check the application’s unit and axis interpretation.
  8. Inspect orientation, face direction and texture paths.
  9. Save any corrected import as a derivative, not over the downloaded original.

ASCAND geometry is established in physical millimeter units before final export. Some formats or applications use meters, centimeters, unitless coordinates, different up axes, different front axes or different handedness. A model that is rotated on import may reflect a coordinate-convention difference. A model that is uniformly too large or too small may reflect unit interpretation. Neither symptom, by itself, proves that the source geometry changed.

Do not apply non-uniform scaling to make a dimensional mismatch disappear. It changes proportions and can invalidate normals. Verify the export dimensions and intended units first.

If textures are missing while geometry is present, check the complete package, filenames, relative paths, material support and import choices. Recoloring the model does not diagnose a missing companion asset.

Use the complete download-validation checklist.

Correct the earliest confirmed fault and keep the original intact

Route the case from the first defective stage:

  • The reconstructed geometry is already missing or distorted: return to Vision or Laser and Combo diagnosis.
  • Independent scans become offset or doubled during registration: use Multi Merge Problems.
  • The first mesh introduces topology or surface problems: preserve the source result and mesh, then follow the bounded 3D-print preparation or appropriate downstream modeling workflow.
  • The selected export was not generated or the download is incomplete: preserve the project and export record and contact Support.
  • The complete file is sound but only one application interprets it incorrectly: use that application’s current format, unit, axis, material and import documentation.
  • The cause remains unclear: send Support the project identity, last accepted representation, selected export identity, original downloaded package, destination application, exact symptom and controlled tests.

Share only the files required for diagnosis and remove unrelated personal or confidential content where practical.

A repaired, watertight, converted or successfully imported model may be useful. It does not prove that its surfaces were observed, its dimensions are correct or it is suitable for the intended physical or functional use.Use this page when an accepted laser-assisted source has reached an ASCAND Laser or Combo result, but the geometry is distorted, sparse, incomplete, noisy, outlier-heavy or otherwise unsuitable.