Forum

Author Topic: 1.6.3 buildUV fallback to legacy paramterization  (Read 2231 times)

BerndS

  • Newbie
  • *
  • Posts: 2
    • View Profile
1.6.3 buildUV fallback to legacy paramterization
« on: June 24, 2020, 03:14:04 PM »
When performing the buildUV step, Metashape occasionaly restarts and falls back to legacy parameterization. This has quite an impact on total processing time.
What causes this? Is there a possibility to always use legacy parameterization so the processing time is consistent?

Code: [Select]
  chunk.buildUV(
    mapping_mode=Metashape.MappingMode.values['GenericMapping'],
    page_count=1,
  )

Code: [Select]
[2020-06-24 07:18:17,854 ; INFO] Build UV progress: 77.5%
Pack iteration 0 ratio 0.525
[2020-06-24 07:18:23,612 ; INFO] Build UV progress: 78.4%
[2020-06-24 07:27:07,175 ; INFO] Build UV progress: 80.2%
Pack iteration 1 ratio 0.3875
[2020-06-24 07:37:03,775 ; INFO] Build UV progress: 82.0%
Pack iteration 2 ratio 0.31875
[2020-06-24 07:41:18,511 ; INFO] Build UV progress: 82.9%
[2020-06-24 07:47:38,643 ; INFO] Build UV progress: 84.7%
Pack iteration 3 ratio 0.284375
[2020-06-24 07:58:01,363 ; INFO] Build UV progress: 86.5%
Pack iteration 4 ratio 0.267188
[2020-06-24 08:08:07,043 ; INFO] Build UV progress: 87.4%
[2020-06-24 08:08:17,819 ; INFO] Build UV progress: 88.3%
done. (in 3000.14 sec)
Falling back to legacy parameterization
[2020-06-24 08:08:31,830 ; INFO] Build UV progress: 10.0%
[2020-06-24 08:09:36,172 ; INFO] Build UV progress: 10.9%
[2020-06-24 08:09:43,020 ; INFO] Build UV progress: 11.8%
[2020-06-24 08:09:59,182 ; INFO] Build UV progress: 12.7%
[2020-06-24 08:10:00,599 ; INFO] Build UV progress: 13.6%
[2020-06-24 08:10:10,627 ; INFO] Build UV progress: 14.5%
]2020-06-24 08:10:18,242 ; INFO] Build UV progress: 15.4%

Alexey Pasumansky

  • Agisoft Technical Support
  • Hero Member
  • *****
  • Posts: 14813
    • View Profile
Re: 1.6.3 buildUV fallback to legacy paramterization
« Reply #1 on: June 27, 2020, 02:17:27 AM »
Hello BerndS,

Are you observing that problem on the particular project only? If so, then would it be possible to send the mesh model from that project to us (support@agisoft.com), so that we could try to reproduce similar behavior on our side and investigate the problem in detail?
Best regards,
Alexey Pasumansky,
Agisoft LLC

BerndS

  • Newbie
  • *
  • Posts: 2
    • View Profile
Re: 1.6.3 buildUV fallback to legacy paramterization
« Reply #2 on: July 02, 2020, 10:49:42 AM »
It's not limited to a particular project, a number of projects are affected by this since we upgraded to Metashape 1.6.3 (from 1.5.0). Below are the parameters we use by default to construct other parts of the project:

Code: [Select]
chunk.buildDepthMaps(
    downscale=2,
    filter_mode=Metashape.MildFiltering,
)

chunk.buildDenseCloud(
    point_colors=True,
)

chunk.buildModel(
    source_data=Metashape.DenseCloudData,
    surface_type=Metashape.HeightField,
    interpolation=True,
    face_count: Metashape.CustomFaceCount,
    face_count_custom: 500000
)

chunk.buildUV(
    mapping_mode=Metashape.MappingMode.values['GenericMapping'],
    page_count=1,
    adaptive_resolution=False,
 )

Is there any way to force this legacy parameterization to be used? Would using the legacy mapping mode force this?

Alexey Pasumansky

  • Agisoft Technical Support
  • Hero Member
  • *****
  • Posts: 14813
    • View Profile
Re: 1.6.3 buildUV fallback to legacy paramterization
« Reply #3 on: July 11, 2020, 02:17:18 AM »
Hello BerndS,

It seems that the generic mapping mode is not optimal for the mesh model generated in Height Field mode. Such mesh contains many long and thin faces which are problematic for the proper packing even using Legacy parametrization mode (mapping_mode = Metashape.LegacyMapping). In the latter case you'll end with ultra high number of isolated texture charts which would considerably affect the resulting texture quality.

I would rather suggest to use Adaptive Orthophoto or even Orthophoto mapping mode for the given model.

Alternatively you can build mesh using Arbitrary option from the depth maps source. Or generate a tiled model, if you need the resulting model for the visualization purposes mainly.
Best regards,
Alexey Pasumansky,
Agisoft LLC