Topics

1

Bug Reports / Proces hangs during 'Estimating surface', can not cancel to save depth maps

« on: September 11, 2019, 09:16:07 PM »

Hi,

I'm  processing a city maquette in 4 chunks, but in the 'Estimating surface' stage of the first chunk, the progress just stops. The depth maps that were generated in over 10 hours cannot be saved, because the process cannot be cancelled; in taskmanager it shows that the CPU is fully utilizing a single core but the process does not get cancelled.

Is there a way to save the depth maps - outside of the GUI - so i can reuse those for another try?

Nvidia driver: 431.7 - Studio Driver
Windows: 1903
Metashape: 1.5.4 build 8885

With kind regards,
Casper

2

Texture De-Lighter / Possible to share .dlz file of example(s)?

« on: August 22, 2019, 11:22:23 AM »

Hi, is it possible to share the .dlz file of the 'stone wall nr1' exemplified in https://www.agisoft.com/index.php?id=71 ? This might make the more complex workflow a bit more clear. I'm currently trying to delight an old artifact with multiple colors and lots of shadow parts.

3

Bug Reports / Curved placement of downward faced cameras

« on: August 02, 2019, 09:53:55 PM »

Hi,

Issue:
I have a problem with the alignment when using cameras fixed on a rig, facing directly downward. The camera's taken under an angle are aligning correctly, but when i use the downward facing photos, the cameras and the model get curved. I did not remove any EXIF data or altered the lensprofile externally.

Object:
The object is a city maquette, approx. 70 x 90 cm.

Lens/Camera used:
I use a fixed 30 mm lens (Sigma C) on a APS-C sony body (A6500).

Driver/OS versions:
Windows: 1903
GPU (nvidia): 431.6

Anyone any idea what causes this and how to fix it?

Greetings, Casper

4

Bug Reports / Mesh generation w. Depth maps | Surface Estimating GPU stop

« on: July 29, 2019, 12:09:08 AM »

Hi,

I've got an issue at the moment while generating a mesh with Depth maps, during 'Estimating Surface'. For the first part (around 25%) both CPU and GPU perform tasks like this:
[GPU 1] 16 Parts 21-36/6770...
[GPU 1]   Initializing octree...
[GPU 1]   Initializing histograms...
[CPU 2]   Initializing...
[CPU 2]   Iterating...
[GPU 1]   Initializing...
[GPU 1]   Iterating...

After the 25%, the GPU is no longer in the picture and the time to complete keeps jumping:
[CPU 2] 2 Parts 682-683/6770...
[CPU 2]   Initializing octree...
[CPU 2]   Initializing histograms...
[CPU 2]   Initializing...
[CPU 2]   Iterating...
[CPU 2]   Updating result...
[CPU 2] Part done in 400.562 sec

 If i calculate by hand it would be around 10 days.. to fully complete.

I use 1.5.3. 412 aligned 24 Mpix photos. 11 GB Video Ram, 64 RAM and  around 200GB virtual mem on SSD's.

Other comparable scans in terms of amount of complexity and amount of photos did not have this issue.

Any idea what could cause this?