Holes in computed point cloud

Why do I get holes in the point cloud like in this image below. As you can see camera positions are equally dense/spaced out in all areas so these holes shouldn't happen, right ?

Capture.PNG

In high detail reconstruction I run out of memory (64 GB), how can I tune the reconstruction to be better then normal but still fit in memory. I found these settings but it seems that normal and high have the same parameters ( but in reality normal runs faster and does not run out of memory). Why are these settings then the same ?

Capture2.PNG

471Capture.PNGhttps://www.capturingreality.com/forum/download/file.php?id=4712097283imageFile png

Capture.PNG
472Capture2.PNGhttps://www.capturingreality.com/forum/download/file.php?id=4722097283imageFile png

Capture2.PNG

chris

October 03, 2016 02:58

decimation factor for high by default should be 1.

but if your running out ram not a bad idea.

the big difference that your not seeing there is that all the images get scaled by half when run in normal mode.

something that I've started experimenting with is the minimal distance between to vertices.

I managed to get one project out on high, that was crashing before.

I'm having my second go at this setting is still processing. I'll let know next week how it goes.

Wishgranter

October 03, 2016 13:24

Hi Boris Goreta
as Chris has said, change the DETAIL DECIMATION FACTOR to default value of 1.
Is it a sort of river bed or a city near a river ??

Boris Goreta

October 03, 2016 20:43

It is a city near sea bay. I found out I had to increase maximum vertices count per part, then I didn't get this empty patches.

Comments