DepthMap slow or red bar or crash

DepthMap too slow

You can speed up the Depth Map process. Here is what you need to do:

Increasing the Downscale factor will speed up the process and may resolve a red bar error, but will reduce the precision.

Reducing the number of T cameras (sgmMaxTCams (Semi Global Matching: Number of neighbour cameras), refineMaxTCams) will directly reduce the computation time linearly, so if you change from 10 to 5 you will get a 2x speedup.

A minimum value of 3 is necessary, 4 already gives decent results in many cases if the density of your acquisition process regular enough.

The default value is necessary in large scale environment where it is difficult to have 4 images that cover the same area.(#228)

DepthMap Red bar error

https://github.com/alicevision/meshroom/wiki/Error:-This-program-needs-a-CUDA-Enabled-GPU

DepthMap crash / freeze

Meshroom crashes or freezes when running DepthMap node.

Windows [has a] feature called TDR (Timeout Detection and Recovery) that resets the GPU after detection of more than 2 seconds of freeze (GPU not responding). This 2 seconds seem reasonable running realtime graphics but for heavy number crunching this value is to low (at least with a slow GPU) https://github.com/alicevision/meshroom/issues/741#issuecomment-583902412

Solution: GPU drivers crash with long computations (TDR crash)

Possible causes of TDR issues: overclocked components, incorrect component compatibility and settings (especially memory configuration and timings), defective parts (memory modules, motherboards, etc.), insufficient system cooling, and insufficient system power. https://community.amd.com/thread/217905