Summary
Importing iPhone Pro LiDAR exports (.PLY/.LAS/.E57 from 3D Scanner App) into RealityCapture/RealityScan desktop fails. Import after photo alignment errors out, and importing .PLY with the shown settings always ends with an “unexpected error,” regardless of whether photos were aligned first.
Please select what you are reporting on:
Creative
What Type of Bug are you experiencing?
Assets
Steps to Reproduce
Capture with iPhone Pro via 3D Scanner App.
Export RGB photos + point clouds: .PLY, .LAS, .E57.
In RealityCapture/RealityScan desktop:
a) Path A: Import photos → Align (components created) → Workflow → LiDAR Scan → Import the LiDAR file → choose Use camera poses = From component → pick the created component.
b) Path B: Workflow → LiDAR Scan → Import the .PLY → set options exactly as in the attached screenshot (the only configuration that initially accepts the file) → proceed.
Expected Result
Path A: LiDAR imports successfully, virtual cameras are created, and .lsp files are generated so registration/meshing can continue.
Path B: .PLY imports successfully with the provided settings, converts to .lsp, and proceeds without exceptions.
Observed Result
Path A: Import fails with component/camera/georeference errors, e.g.:
“could not create virtual cameras, because specified component does not exist”
“could not create virtual cameras, because specified component does not exist or the file does not contain any cameras”
“could not derive virtual camera from specified component, because that component is not georeferenced”
Path B: Import accepts the .PLY with the screenshot settings, then immediately throws “unexpected error” (exception dialog). Happens with or without prior photo alignment.
Platform(s)
App: RealityCapture / RealityScan desktop (version: 2.0.1)
OS: Windows 11
