Build model 1.6.3. seems to stop after loading kernels

[mcstieg]

Hello,
as the header says...Seems to stop at this point for hours now.
Any suggestions? Thank you!

[Alexey Pasumansky]

Hello mcstieg,

It would be helpful, if you provide the processing log related to the operation and also specify the available GPUs and the related driver versions. Thus we could try to reproduce the problem on similar configuration and find out what causes the problem.

[mcstieg]

This time not at loading kernels but still not working.
Please open the attached log file.

2x Vega 64 rog strix
driver 20.4.2

Thank you!

[Alexey Pasumansky]

Hello mcstieg,

Which OS you are using?

Is the problem reproducible on your side? If so, then check, whether you can also reproduce it with only one GPU selected at a time - does the processing freezes then in any case or only when a particular GPU is used for the processing?

[mcstieg]

OS is Win 10 - 64 bit

I will try to deactivate one or the other one and keep you up to date when its done.

[mcstieg]

I've updated to the latest version and gave it another try.

I deactivated one gpu, the other gpu and activated both and cpu.
None of those tests where positive.  At some point Metashape stopped for hours and did nothing.
It was also not reacting to the cancel button.

Normal setup:
CPU1: Socket E5 2683 V3
CPU2: Socket E5 2683 V3

GPU1: Vega 64 ROG Strix
GPU2: Vega 64 ROG Strix (Crossfire not active)

RAM: 128 GB

Windows 10 64 bit

SSD Free space C: 194 GB (Windows)
SSD Free space E: 199 GB (project)

Both GPUs are activated. CPU is disabled.

Image set:

- this time 1129 fisheye cameras aligned
- alignment: highest, not generic, reference(source), 40000, 0, adaptive camera model fitting
- a lot of overlapping images
- therefore disabled half of the images
- mesh via depth maps: high, interpolation enabled, mild, no vertex colors

I also noticed that it could have to do with the optimization process.
- python script optimizes 10 times for me
-  f, cx, cy, k1, k2, k3, p1, p2
- Do you have any suggestions on which parameters should be activated or disabled?

When estimating camera locations GPU1 is active at about 25% (attachment) even thought bth GPUs are activated.
Most problems occur when calculating depth maps. Metashape just stops after some time. CPU & GPU usage is then 0%.
CPU was running 100%, both GPUs where working.

The same system was able to calculate models with double the images even at ultra quality before.

Thank you!