RealityScan produces holes on a repetitive roof where Agisoft Metashape produces a continuous surface from the same photos

On a house with a repetitive slat/tile roof, we processed the same 436 drone photos (DJI Air 3S, 4096x3072) in RealityScan and in Agisoft Metashape (2.3.1):

  • Metashape: continuous, client-presentable roof surface.
  • RealityScan: rows of holes and double-surface pockets across the roof planes (screenshots attached). Same photos.

We measured both results: RealityScan’s camera geometry is far MORE accurate (cameras within ~1-2 cm of GPS ground truth, scale 1.000; Metashape carries a hidden ~41 cm offset between its two camera groups). We prefer RealityScan and want to stay on it - but we cannot deliver roofs with holes to clients. How can we get a continuous surface from this photo set in RealityScan?

Alignment settings (CLI names; all other settings default):

  • sfmMaxFeaturesPerMpx 20000, sfmMaxFeaturesPerImage 80000
  • sfmDetectorSensitivity Ultra, sfmImagesOverlap High, sfmPreselectorFeatures 20000
  • sfmForceComponentRematch true, sfmMergeGeoreferencedComponents true
  • camera prior accuracy (inpuTx/y/z) 0.1 m, sfmImageDownscaleFactor 1
  • sfmDistortionModel Brown3, sfmMaxFeatureReprojectionError 2.0

Steps:

  1. Align the 436 photos with the settings above → one component, 435/436 registered. Verified against GPS ground truth: positions within ~1-2 cm, scale 1.000 (per-camera export and modeling report available on request).
  2. Normal-detail reconstruction, default settings.
  3. Observe rows of holes/pockets on the roof planes, following the slat pattern. High detail (96M tris) shows the same defects.

As you can see from the screenshots, on the left is with RS and on the right is with Agisoft. Originally, RS even produced two separate components, they cannot be merged automatically. The result on the left is after we have tried our best to merge the two components to form a house, whereas Agisoft did it easily

Any help is much appreciated!