AeroCAD (FlappedEar) errors

7 recurring problems engineers report in AeroCAD (FlappedEar), ranked by impact.

#60 by errors trackedMCADVerification

Recurring AeroCAD (FlappedEar) errors, by impact

  1. 1A remembered cm/in/m import setting was applied again after the STEP, IGES and 3MF readers had already converted to millimetres, so parts came in at the wrong size. The fix applies embedded units once and shows unit provenance in the import status.MCAD · Agent failure · 1 report74
  2. 2A construction plane was meshed as a solid wall in the CFD run and skewed lift and side force: with Other visible parts in the flow on, a reference plane went into context.stl and snappyHexMesh meshed it as a thin wall upstream of the part. Lift read -0.261 N with the plane and -0.155 N without.Verification · Agent failure · 1 report66
  3. 3A fillet on a fin edge down to a scan root reported OK, but the export check then refused print export with 3 to 78 open edges, and some edges failed the B-rep check. Meshing the live shape left mismatched triangulation and changed tolerances that undo still held. The fix makes a fillet count as failed unless the export-resolution mesh is closed.MCAD · Agent failure · 1 report66
  4. 4An open scan shell with 329 open edges went into a CFD run with no warning, and snappyHexMesh cannot tell inside from outside, so the forces depended on the mesh rather than the part. Measured on OpenFOAM, open shell drag was 1.83 N against 0.82 N after repair, and the fix is a warning rather than a refusal.Verification · Agent failure · 1 report66
  5. 5In AeroCAD, an STL in mm imported with unitless files set to m came in 234 m long. The size check named the wrong unit even though the factor was right. The import unit was not stored on the part, so the check guessed from the numbers.MCAD · Agent failure · 1 report66
  6. 6STEP export dropped body names and colours, and import merged bodies. Exported bodies came out with OCCT placeholder names and no colours, and a two-body STEP imported as one part named after the file. Fourth STEP handoff bug in today's sweeps.MCAD · Agent failure · 1 report66
  7. 7The same repo fixed the opposite error on the same scan, a false Approximation warning from a fit that chased scan noise. One scan produced both a missed warning and a false one.Verification · Agent failure · 1 report66

How it fails

  1. Agent failure7

Sourced from public community reports. Costs and delays on individual entries are modeled estimates, not measurements.