I’m reconstructing one region out of a large alignment, headless on Linux (bundled
Wine build), 32 threads / 252 GB / RTX 3090. After the mesh finishes, the
process sits for ~36 minutes doing something it never logs.
The whole tail of the run, with RealityScan’s own reported durations:
Reconstruction in Normal Detail completed in 3900.120 seconds.
Executing command 'renameSelectedModel' with parameter 'r12e'
Executing command 'save' with parameter 'Z:\data\areas\gorge\master.rsproj'
Saving Project completed in 1.560 seconds.
Executing command 'exportSelectedModel' with parameter 'Z:\...\r12e.ply'
Exporting Textured and Colored Mesh completed in 1.302 seconds.
That accounts for ~3 seconds. In wall clock the reconstruction line was written
at 17:55 and the .ply appeared at 18:31.
During those 36 minutes: ~2 cores of CPU burned
continuously, RSS flat at 6.8 GB, and zero files written anywhere under the
project, cache or output directories. The last line in the log is the save
reporting complete — Executing command 'exportSelectedModel' is not even
echoed until the end.
It is not the save flushing: the model’s 10 model*.dat parts are written when
the reconstruction finishes, before save is called, and nothing is written
after.
It is not the export being slow in general: a later run reloads the project,
textures the same model and exports it again — writing more data (1.79M
vertices with UVs vs 1.63M, 78 MB vs 62 MB) in about 3 minutes.
So something runs once, after reconstruction, on ~2 threads, and is attributed
to nothing.
I have 20 regions to mesh, texture, and export, so it’s adding a lot of time.