Reduce Overlap = Error: empty geometry

[CheeseAndJamSandwich]

Metashape Standard 1.8.0 build 13794

Aligned, done some mild Gradual Selection, ran Optimise Cameras, then created a mesh from Tie Points (i guess this is 'Sparse Point Cloud' renamed??)... Mesh looks normal.
Then, running Reduce Overlap set to 9 gives the Error: empty geometry.

Code: [Select]

2022-01-06 00:50:33 Reducing overlap...
2022-01-06 00:50:33 Building params...
2022-01-06 00:50:33 ROI: [-123.287, -95.6844, -12.6808] - [138.38, 146.938, 5.44214]
2022-01-06 00:50:33 n voxels g: 292 -> 250
2022-01-06 00:50:33 n voxels n: 292 -> 292
2022-01-06 00:50:33 voxels in meter g: 0.955414
2022-01-06 00:50:33 voxels in meter n: 1.11592
2022-01-06 00:50:33 restricted distance in voxels g: 15
2022-01-06 00:50:33 capture distance in voxels g: 1
2022-01-06 00:50:33 margin g: 3
2022-01-06 00:50:33 restricted distance in voxels n: 17
2022-01-06 00:50:33 capture distance in voxels n: 1
2022-01-06 00:50:33 margin n: 3
2022-01-06 00:50:33 filling geometry...
2022-01-06 00:50:33 fillGeometryInfo : fill
2022-01-06 00:50:33 fillGeometryInfo : no voxels found
2022-01-06 00:50:33 filling geometry...
2022-01-06 00:50:33 fillGeometryInfo : fill
2022-01-06 00:50:33 fillGeometryInfo : no voxels found
2022-01-06 00:50:33 Finished processing in 0.019 sec (exit code 0)
2022-01-06 00:50:33 Error: empty geometry
This workflow i've done dozens of times before on 1.7.n

Thanks.

[Alexey Pasumansky]

Hello CheeseAndJamSandwich,

I have to request a project file with the aligned cameras, tie points and the mesh model from you, so that we could reproduce the problem on our side, as it doesn't happen on several random projects.

[Mak11]

I'm getting exactly the same error in 1.8 and 1.8.1 Build 13875.

2022-01-26 03:18:25 ReduceOverlap: overlap = 1, use_selection = 1
2022-01-26 03:18:25 Reducing overlap...
2022-01-26 03:18:25 Building params...
2022-01-26 03:18:25 ROI: [-2.5024, -1.83628, -11.3296] - [3.4799, 1.00196, -8.43277]
2022-01-26 03:18:25 n voxels g: 177 -> 177
2022-01-26 03:18:25 n voxels n: 177 -> 177
2022-01-26 03:18:25 voxels in meter g: 29.5873
2022-01-26 03:18:25 voxels in meter n: 29.5873
2022-01-26 03:18:25 restricted distance in voxels g: 444
2022-01-26 03:18:25 capture distance in voxels g: 1
2022-01-26 03:18:25 margin g: 3
2022-01-26 03:18:25 restricted distance in voxels n: 444
2022-01-26 03:18:25 capture distance in voxels n: 1
2022-01-26 03:18:25 margin n: 3
2022-01-26 03:18:25 filling geometry...
2022-01-26 03:18:25 fillGeometryInfo : fill
2022-01-26 03:18:25 fillGeometryInfo : no voxels found
2022-01-26 03:18:25 fillGeometryInfo : fill
2022-01-26 03:18:25 fillGeometryInfo : no voxels found
2022-01-26 03:18:25 Finished processing in 0.011 sec (exit code 0)
2022-01-26 03:18:25 Error: empty geometry

Mak

[Alexey Pasumansky]

Hello Mak,

If you have the project that can be used to reproduce the problem on our side, please send it to support@agisoft.com. It is sufficient to have aligned cameras, tie points and mesh model in the project contents.

[Mak11]

Hello Mak,

If you have the project that can be used to reproduce the problem on our side, please send it to support@agisoft.com. It is sufficient to have aligned cameras, tie points and mesh model in the project contents.

Alexey,
So I don't need to send the actual images files, right?

PS: I've sent you a PM about an another subject which I hope you could answer.

Cheers

Mak

[Alexey Pasumansky]

Hello Mak,

Yes, images used for the processing are not required. Just Metashape project with the alignment results and mesh model.

[Alexey Pasumansky]

Please check the 1.8.1 release version (build 13915), the issue should be fixed now.