Processing Hung up

[dsmapping]

I am having issues with the newest version of Metashape. I am trying to process a job with less than 500 images and it is stuck on generating depth maps. It has been on 20% for 7 hours. I am using Metashape version 2.2.1. Here are my computer's specs

Processor   Intel(R) Core(TM) i9-14900K   3.20 GHz
Installed RAM   128 GB (128 GB usable)
Device ID   AE267FEE-8EA2-4901-B685-BC93AF0A601A
Product ID   00355-61030-56959-AAOEM
System type   64-bit operating system, x64-based processor
Pen and touch   Touch support with 10 touch points

GPU is an Nvidia RTX 5080


Why would it be taking so long?

[Bzuco]

If you see zero activity on gpu/cpu on depth maps stage, then no need to wait 7 hours. Just restart this stage and it will be probably finished without issue.
Something similar happened to me at another stage and after restart MS it was OK.

[Eric Gilson]

Restart works but I am finding that it is stalling multiple times during the depth maps stage. Using an 5080 as well. Pain in the backside having to babysit this stage. every other process seems fine. Does not seem to be any pattern that i can see on when it will hang.

An update that fixes this would be AWESOME....

[olihar]

Restart works but I am finding that it is stalling multiple times during the depth maps stage. Using an 5080 as well. Pain in the backside having to babysit this stage. every other process seems fine. Does not seem to be any pattern that i can see on when it will hang.

An update that fixes this would be AWESOME....

BuildDepthMaps/max_gpu_multiplier = 1

is the fix for now, it makes it 2X slower but at least it will not freeze.

[Eric Gilson]

I tried that and it still crashed, then for sh*ts and giggles, i set the value to 3, also used main/gpu_enable_cuda to false....anyways, working now and not really seeing too much of a reduction in processing. I am not a programming guy, all I know is that this seems to be working for me and not crashing which is a huge win at this point.

[Alexey Pasumansky]

Hello dsmapping,

Currently we recommend to set BuildDepthMaps/max_gpu_multiplier tweak to 1 value as a workaround.

If we have a solution in the next updates or if NVIDIA implement some fixes in their driver that will resolve the problem with GeForce RTX 50 series, we'll inform additionally.