Metashape - Out of memory error when building dense cloud

[holoped]

Hey guys,

I've long since moved to RealityCapture but with this new version decided to give Agisoft another try, since the UX is so much better.

I have a scan with 312 images. I did alignment, which took oven an hour (not happy about that, RC aligned these images in less than 10 minutes)
I then run build dense cloud on Medium settings and after a few minutes got out of memory error. I have a GTX 1070 and 32gb of ram.

Any ideas?
Thanks.

[Mak11]

Holoped,

You'll have to provide more info:

- Photo resolution & type of photos (UAV survey? Turntable ?)
- Alignement parameters
- Your full config (and GPU driver version)
- Why build dense cloud instead of the new method using the Depth maps ?

Cheers

Mak

[holoped]

Perhaps i'm missing something, but I don't see any option to create depth maps.
It's not in the workflow?

[Alexey Pasumansky]

Hello holoped,

Can you specify the parameters that you are using and, if possible, the complete processing log from the Console pane?

If you are interested in the mesh and texture and do not need the dense cloud as a separate product, I can also suggest to try the version 1.5.0 and use mesh generation based on the depth maps.

[woodengun]

Hi all.
I am getting the same "out of memory" issue after about 2 days worth of build time on Ulra high build mesh settings. Only I'm not using the dense mesh calculation but instead am using the build mesh straight from the depth maps.

I am using a linux maching with an Nvidia Quadro K4000. 32 gigs of Ram.
I am solving about 40 photos at about 5-6k (raw tifs from cr2s).

I have turned on the GPU check button in the preferences and have tried turning "use CPU" on and off but get the same out of memory error. I actually dont know if this is a bug or just the limitation of Ultra High settings and my current machine.

Any advice / suggestions?
Thanks!

[Alexey Pasumansky]

Hello woodengun,

Can you share the PSZ project file with the alignment results and generated depth maps, so that we could check it on our side and see the memory consumption peak?