Messages

1

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

« on: September 15, 2019, 11:53:51 AM »

Found the problem i think; i'm pretty sure the problem occurs when setting the desired polycount to more than the default value of 9.000.000.

I had set it to 20.000.000, and also once 12.500.000 i believe, and every time i tried this, the process hanged.

Does anyone have the same experience? It's pretty important to know i think, since it's often desirable to have  > 9.000.000 polys. Still, i'm happy i can go forward with this now.

2

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

« on: September 12, 2019, 10:25:26 PM »

Although i have saved the depth maps, the initial problem persists:  application hangs at the same exact point every time (at 7% into 'Estimating Surface').

I have updated to the latest MS (1.5.5).

Everything is up to date, my RAM is only utilized at 40% or so (have 64GB RAM and around 500 GB of virtual mem).

3

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

« on: September 12, 2019, 05:52:31 PM »

Alright, i will first do the other chunks and then try to redo this recovered chunk.

And absolutely, it would be a great help if the 'option save file after each step' (in Batch process section) would also save after the depth maps were generated. I know it should not be necessary since the process should not crash in the first place, but currently it would be a great pragmatic, and easy to implement feature/change.

Thanks again for the tip, wojtek.

 

4

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

« on: September 12, 2019, 12:03:29 PM »

Hi again,

I'm starting to think that all is lost for these depth maps.

When i look at other (completed) project files, the pyramid folders are empty and there is 1 depth maps folder. In this project the pyramid folder contains a ~33,5 GB pyramid file.

It worked, i overlooked a change in one of the xml's because you should never open an xml with IE!!!

____________________________________________
Changes i made:
I have edited the xml from the chunk.zip and added the following:

Change 1: after -> </camera>
<depth_map_sets next_id="1" active_id="0">
    <depth_maps id="0"/>
  </depth_map_sets>

Change 2:
In the depth maps folder, i added the block paths of the depth maps as in other finished projects.

Change 3:
This is what i failed to find the first time:
Change in the .xml in the frame.zip file. (When you open and search in *cough* Internet explorer, it often does not find what you're looking for because it does not immediately open the whole file)
added:
<depth_maps id="0" path="depth_maps/depth_maps.zip"/>

Change 3:
I removed the depth_maps folder (which only had 2 files) and renamed the large depth_maps.1 folder to depth_maps.
_________________________________________

I have now only 2 important questions:

1) What about the large pyramid file. Do i still need it if i only want to salvage the depth maps and use them to redo the step 'Build mesh' -> ' Reuse Depth maps', or can i delete the file for now?

2) I removed the smaller depth_maps folder; can this folder be of importance for the other depth_maps folder? Or are these separate and can i delete them?



Casper

5

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

« on: September 11, 2019, 11:33:43 PM »

Hi wojtek, thanks for your answer!

I have actually once tried that, but after opening the file, the depth maps did not show in the Metashape gui. I must've done something wrong, i'll try it again and post the results somewhere tomorrow.

Cheers, Casper

6

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

7

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.

8

Bug Reports / Re: Curved placement of downward faced cameras

« on: August 05, 2019, 05:31:58 PM »

Hello Alexey, thank you for the good explanation. I'll keep in mind to make calibration groups more quickly.

9

Bug Reports / Re: Curved placement of downward faced cameras

« on: August 04, 2019, 05:30:59 PM »

Thanks, Alexey, that worked!

Just for thread completion's sake, i've added a screenshot of the correctly aligned model and overview of the camera calibration groups.

One question though: is making camera calibration groups for each camera placing always advisable, even when the camera lens is fixed and the settings are unaltered?

10

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

11

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

« on: July 30, 2019, 09:47:07 PM »

Hi Alexey,

When i use the NVIDIA-SMI utility, for what kind of memory behavior should i watch out for? Any anomalies that i can detect?

The GPU driver version: 430.86
Windows 10 version: 1809

Thanks for the quick reply.

Greetings, Casper

12

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

« on: July 30, 2019, 08:39:27 PM »

Update:

I've cancelled the proces and started it again. I did reuse the Depth maps.

The process is now over the part where my GPU stopped 'helping', and the GPU is still covering tasks, unlike the first try.

My semi-uneducated speculated guess is that my vRAM got full - i was doing some photo editing at the same time - and Metashape stopped distributing tasks to my GPU and did not return doing it, even when my vRAM was cleared.

13

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?

14

General / Re: Model is cut off beyond bounding box

« on: February 28, 2018, 10:26:48 PM »

Hello!

I've got a question about this. I just forgot to check the bounding box when starting the dense PC generation, which was off. The model is pretty complex and took 3,5 hours to complete.

Is there a way to only generate the dense point cloud of the missing part? Or do i have to let the whole cloud generate again?

Thanks in advance!

Greetings, Casper