Agisoft Metashape 1.6.0 pre-release

[BjFaeTorphins]

I've had a few failures when building mesh from depth maps.  Here are a couple of example error messages...

2019-12-28 14:22:00 level part done in 172.15 s (53% loading + 0% blocks + 0% sorting + 1% iters (0% queueing) + 46% saving)
2019-12-28 14:22:02 Peak memory used: 5.64 GB at 2019-12-28 12:04:39
2019-12-28 14:22:02 deleting all temporary files...
2019-12-28 14:33:48 done in 705.696 s
2019-12-28 14:33:48 Finished processing in 25429.5 sec (exit code 0)
2019-12-28 14:33:48 Error: Can't rename file or directory: Access is denied (5): H:/2019/2019-11-17 HMS/2019-11-26 AM/Gangway.files/11/0/model.tmp/leaves/u/pre


and...

2019-12-28 16:41:56 level part done in 136.006 s (49% loading + 0% blocks + 0% sorting + 1% iters (0% queueing) + 50% saving)
2019-12-28 16:41:58 Peak memory used: 5.10 GB at 2019-12-28 15:40:19
2019-12-28 16:41:58 deleting all temporary files...
2019-12-28 16:49:59 done in 481.096 s
2019-12-28 16:49:59 Finished processing in 14239.8 sec (exit code 0)
2019-12-28 16:49:59 Error: Can't rename file or directory: Access is denied (5): H:/2019/2019-11-17 HMS/2019-11-18 AM/AA Guns to Casemates 333mS.files/13/0/model.tmp/leaves/u/pre

[Mak11]

Alexey,

I'm still getting those random topology issues on meshes (low poly patches & inverted polygons) as reported a few weeks ago while generating meshes via depth maps. Reconstruction detail & noise reduction have been greatly improved and this is now the last oddity I'm seing. 1.6 is shaping up to be a huge update.







It happens on all quality settings (LOW/MED/HIGH/ULTRA-HIGH)



Cheers

Mak

[Alexey Pasumansky]

Hello BjFaeTorphins,

Is it the latest pre-release build that you are using?

Is the project data stored locally or the path leads to the network/external drive?

[Alexey Pasumansky]

Hello Mak,

We'll try to reproduce the issue, but if you can share the project (in PSZ format) with the depth maps related to the problematic area that we can re-use to observe the issue, it would be helpful.

[BjFaeTorphins]

Hello BjFaeTorphins,

Is it the latest pre-release build that you are using?

Is the project data stored locally or the path leads to the network/external drive?

yes Build 9862.

it was on the NAS in the case of the two errors i logged above. 

I did try moving the project files to the local SSD drive and leaving the photos on the NAS and so far that has been working.  I've had some successful mesh builds so i've not been able to isolate what combination of things always cause the error.

[BjFaeTorphins]

Are you using the latest Nvidia Drivers?
What are the specs of your photos (JPG/PNG..16/24/32bit) ? Could be an issue the new GPU accelerate texture generation. One way to find out would be to disable it (Alexey could probably share the tweak to manually turn it off).

Mak

version 441.41 released 26 November so not that old.  There is a newer build released on 10 December which i'll download.

I've updated to the latest 441.66 20th December drivers and still get the issue.

I note if i go back into the build texture item on the workflow menu that the mapping mode is set to Keep UV,  I've tried setting this to Generic and re-running the texture build but the same happens.

[Mak11]

Hello Mak,

We'll try to reproduce the issue, but if you can share the project (in PSZ format) with the depth maps related to the problematic area that we can re-use to observe the issue, it would be helpful.

Alexey,

I've sent you WEtransfer link by mail.

Cheers

Mak

[BjFaeTorphins]

I just noticed that there are an excessive number of handles when running and alignment of 8000 images.  7000 out of 8000 aligned first time.  it was when selecting all images and running the alignment for the 2nd time to add the unaligned images that i noticed the handles.  So far this has not caused a problem but i have seen windows become unresponsive when a process does not clean up handles.

[BjFaeTorphins]

Hello BjFaeTorphins,

Is it the latest pre-release build that you are using?

Is the project data stored locally or the path leads to the network/external drive?

yes Build 9862.

it was on the NAS in the case of the two errors i logged above. 

I did try moving the project files to the local SSD drive and leaving the photos on the NAS and so far that has been working.  I've had some successful mesh builds so i've not been able to isolate what combination of things always cause the error.

Alexey,

I got the "Can't rename file or directory: Access is denied" running a mesh from depth maps on the local SSD drive so the NAS vs local drive theory is not the answer.

[Alexey Pasumansky]

Hello BjFaeTorphins,

I think that something messed up with the access rights - for some reason the created files cannot be removed or rewritten. Do you observe any similar behavior when trying to export anything from Metashape to the new file or to the file with existing filename?

[eltama]

Hello Alexey,

Aligned photos with 9852 version
Build mesh - deph map 9862 version

I had these errors:
2019-12-24 13:18:52 checking for missing images...Checking for missing images...
2019-12-24 13:18:54  done in 2.637 sec
2019-12-24 13:18:54 Finished processing in 2.637 sec (exit code 1)
2019-12-24 13:18:54 BuildModel: quality = Ultra high, depth filtering = Mild, source data = Depth maps, surface type = Arbitrary, face count = High, volumetric masking = 0, OOC version, interpolation = Enabled, vertex colors = 1
2019-12-24 13:18:54 Generating depth maps...
2019-12-24 13:18:54 Initializing...
2019-12-24 13:18:54 sorting point cloud... done in 1.812 sec
2019-12-24 13:18:56 processing matches... done in 1.642 sec
2019-12-24 13:18:58 initializing...
2019-12-24 13:19:16 selected 9902 cameras from 10354 in 17.673 sec
2019-12-24 13:19:16 groups: 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 100 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 99 100
2019-12-24 13:19:16 29013 of 9902 used (293.001%)
2019-12-24 13:19:16 scheduled 100 depth map groups
2019-12-24 13:19:16 saved depth map partition in 0.303 sec
2019-12-24 13:19:28 loaded depth map partition in 12.22 sec
2019-12-24 13:19:28 Initializing...
2019-12-24 13:19:28 Found 3 GPUs in 0.002 sec (CUDA: 0.001 sec, OpenCL: 0.001 sec)
2019-12-24 13:19:29 Using device: GeForce RTX 2070 SUPER, 40 compute units, free memory: 6711/8192 MB, compute capability 7.5
2019-12-24 13:19:29   driver/runtime CUDA: 10020/8000
2019-12-24 13:19:29   max work group size 1024
2019-12-24 13:19:29   max work item sizes [1024, 1024, 64]
2019-12-24 13:19:29 Using device: GeForce RTX 2070 SUPER, 40 compute units, free memory: 6711/8192 MB, compute capability 7.5
2019-12-24 13:19:29   driver/runtime CUDA: 10020/8000
2019-12-24 13:19:29   max work group size 1024
2019-12-24 13:19:29   max work item sizes [1024, 1024, 64]
2019-12-24 13:19:30 Using device: GeForce RTX 2080 Ti, 68 compute units, free memory: 9133/11264 MB, compute capability 7.5
2019-12-24 13:19:30   driver/runtime CUDA: 10020/8000
2019-12-24 13:19:30   max work group size 1024
2019-12-24 13:19:30   max work item sizes [1024, 1024, 64]
2019-12-24 13:19:30 Using CUDA device 'GeForce RTX 2080 Ti' in concurrent. (2 times)
2019-12-24 13:19:33 Loading photos...
2019-12-24 13:21:51 loaded photos in 138.19 seconds
2019-12-24 13:21:51 Generating depth maps...
2019-12-24 13:21:52 [GPU] estimating 9188x5090x1024 disparity using 1532x1280x8u tiles
2019-12-24 13:21:52 [GPU] estimating 8058x4928x2624 disparity using 1343x1280x8u tiles
...
2019-12-30 08:48:39 Error: Unsupported depth image
...
2019-12-30 15:04:51 Error: Null image
...
2019-12-30 15:16:20 Error: Too small depth map!
...
2019-12-31 19:56:42 Finished processing in 90728.3 sec (exit code 0)
2019-12-31 19:56:42 Error: Broken data order in file D:/10445 clean.files/0/0/model.tmp/cubes/1/12.data at index=354263496


But in the meantime

Thanks to devolp this beautiful software!
Happy new Year !!!

[Alexey Pasumansky]

Hello eltama,

Do you have these errors during the depth maps generation step or already during the mesh reconstruction (all depth maps are already generated)?

[eltama]

I checked reuse deph map (ultra setting) and yes I have errors on both steps, now I had installed the latest version 9925, and build mesh without reuse depth maps with high quality.

I have some duplicated images, now deleted, runs as admin.
I noticed a strange behavior, even if I am admin, I can’t disable read only mode on files.

Best regards

[BjFaeTorphins]

Hello BjFaeTorphins,

I think that something messed up with the access rights - for some reason the created files cannot be removed or rewritten. Do you observe any similar behavior when trying to export anything from Metashape to the new file or to the file with existing filename?

Alexey

After the error happens the model.tmp directory mentioned in the error message is gone.  I've not seen any permission errors and the project file can be saved after the error.

[BjFaeTorphins]

Are you using the latest Nvidia Drivers?
What are the specs of your photos (JPG/PNG..16/24/32bit) ? Could be an issue the new GPU accelerate texture generation. One way to find out would be to disable it (Alexey could probably share the tweak to manually turn it off).

Mak

version 441.41 released 26 November so not that old.  There is a newer build released on 10 December which i'll download.

I've updated to the latest 441.66 20th December drivers and still get the issue.

I note if i go back into the build texture item on the workflow menu that the mapping mode is set to Keep UV,  I've tried setting this to Generic and re-running the texture build but the same happens.

Alexey
I've updated to the 9925 build and am still getting this weird looking almost greyscale texture.