Error when building UV for object

[Jernej]

When building UV map for an object, I get an error saying "invalid vector<T> subscript". I'm building 4 8k textures for this object. If I lower the count of those textures, the problem dissapears. Any way to avoid or solve this issues without lowering the quanitity of textures? UV mapping mode is generic.

Thanks for your help

[Alexey Pasumansky]

Hello Jernej,

Which version of Metashape do you use?

And please share the log from the Console pane related to the failed operation and specify the number of polygons in the source model and the parameters used for mesh generation.

[Jernej]

The version of Metashape is 1.7.4.
For the mesh generation process I used depth maps, on High quality and 14 milion polygons as the target count.

Output on the node:
2021-07-15 10:21:18 Gutter changed ( 4 -> 0)
2021-07-15 10:21:18 Pack iteration 0 ratio 0.525
2021-07-15 10:22:54 Error: invalid vector<T> subscript
2021-07-15 10:22:54 processing failed in 218.077 sec

Output on the server:
[xx.xx.xx.xx:56507] failed #61 BuildUV: invalid vector<T> subscript

[Alexey Pasumansky]

Hello Jernej,

Can you please send the mesh in OBJ format to support@agisoft.com that you are trying to build texture for and also specify the version build number?

[Jernej]

Sent to support. There also appears to be another problem after generating the textures. The UV map generated on some large surfaces is very small and cannot hold sufficient detail.

Example in the attachment

[Alexey Pasumansky]

Hello Jernej,

Thank you for sending the OBJ file, however, we were not yet able to reproduce the UV parametrization failure neither in 1.7.3, nor in 1.7.4 pre-release versions.

As for the parametrization results, can you provide the screenshot for Color, Scaling and Overlap tabs from View Mesh UVs dialog (accessible from the Tools menu) for all the texture atlas pages?

[Jernej]

Sent to support because of file size restraints. Hope it helps to solve this issue.

Also, I have tried to texture the object in version 1.7.1 and the problem does not appear there