Agisoft Metashape 1.8.0 pre-release

[Alexey Pasumansky]

Hello Paul,

You can access the coordinates of the shape vertices via

Code: [Select]

shape.geometry.coordinates.

[Alexey Pasumansky]

Hello Bill,

To avoid VCRUNTIME140_1.dll error you may need to download and install Microsoft Visual Studio Redistributable Package.

[Paulo]

When I load a DTM and shape in Viewer, they do not display while they are perfectly viewable in Global mapper,

As for the DEM/Orthomosaic display in Agisoft Viewer, they can be only shown if Show Basemap layer option is enabled and these rasters are georeferenced in the coordinate system that can be transformed to WGS84.

Thanks again,

now shape file does display in Viewer but not DTM.... both were exported from Metashape in WGS84/UTM 10N
see fllowing....

[bisenberger]

Hello bisenberger,

Are there any disabled cameras in the chunk? Please also check, if the depth maps thumbnails show adequate information in the Photos pane or Photo view mode for all the cameras, or whether some depth maps are completely black?
P.S. the latest pre-release build number is 13597.

Here is a screen grab of the depth maps for one of the chunks that has an incomplete mesh:

[Paulo]

Hello Paul,

You can access the coordinates of the shape vertices via

Code: [Select]

shape.geometry.coordinates.

OK,
but the structure of shape.geometry.coordinates is different from shape.vertices as seen in:

Code: [Select]

shape
Out[6]: 2021-11-30 07:35:48 <Shape '1'>

shape.vertices
Out[7]: 2021-11-30 07:35:56 Shape.Vertices([Vector([683479.6620444183, 5618402.325884395, 349.5898219660391]), Vector([683484.8314030222, 5618401.859365016, 349.46954668612625]), Vector([683484.0623676204, 5618394.528231934, 349.49292624746954]), Vector([683478.7677394338, 5618395.108553094, 349.59959399146913]), Vector([683479.6620444183, 5618402.325884395, 349.5898219660391])])

shape.geometry.coordinates
Out[8]: 2021-11-30 07:36:54
2021-11-30 07:36:54 [[Vector([683479.6620444183, 5618402.325884395, 349.5898219660391]),
2021-11-30 07:36:54   Vector([683484.8314030222, 5618401.859365016, 349.46954668612625]),
2021-11-30 07:36:54   Vector([683484.0623676204, 5618394.528231934, 349.49292624746954]),
2021-11-30 07:36:54   Vector([683478.7677394338, 5618395.108553094, 349.59959399146913]),
2021-11-30 07:36:54   Vector([683479.6620444183, 5618402.325884395, 349.5898219660391])]]

shape.vertices[0]
Out[9]: 2021-11-30 07:38:22 Vector([683479.6620444183, 5618402.325884395, 349.5898219660391])

shape.geometry.coordinates[0]
Out[10]: 2021-11-30 07:38:51
2021-11-30 07:38:51 [Vector([683479.6620444183, 5618402.325884395, 349.5898219660391]),
2021-11-30 07:38:51  Vector([683484.8314030222, 5618401.859365016, 349.46954668612625]),
2021-11-30 07:38:51  Vector([683484.0623676204, 5618394.528231934, 349.49292624746954]),
2021-11-30 07:38:51  Vector([683478.7677394338, 5618395.108553094, 349.59959399146913]),
2021-11-30 07:38:51  Vector([683479.6620444183, 5618402.325884395, 349.5898219660391])]
How to access first vertex coordinates in shape.geometry.coordinates?

[Alexey Pasumansky]

Hello Paul,

shapes in 1.8 version may be represented by the collection of multiple elements and will appear as list of lists via API. So if there's only single shape, then to access the coordinates of the Nth vertex you should use:

Code: [Select]

shape.geometry.coordinates[0][N]

[bgreenstone]

I just ran two tests with build 13597 and I'm happy to report that the blobby mess on the underside of the geometry has been almost entirely fixed.  It's still not quite as clean as 1.7.3, but it's MUCH better than any version from 1.7.4 to the previous beta.  In my first test the geometry was 100% clean with no blobs.  In my second test I had some very tiny blobs, but they were disconnected from the main geometry and far away, so very easy to clean up in Blender.  I have attached a screenshot showing this.

I did see one error in the Log during Texture map generation:  "Failed to initialize context.  Reason:  VK Error: VkResult is "ERROR_INITIALIZATION_FAILED" at line 66".  However, it seemed to have created the texture just fine despite this error message.  I have uploaded a screenshot of that as well.

The last observation I have that it is now showing both [GPU1] and [GPU2] in the log.  With 1.7.3 it only showed one GPU on my MacBook Pro M1 Max.  In the Log you can see that it says "Found 1 GPUs", so I'm not sure why it's acting like there are 2.  Is that normal?

This is the first version since 1.7.3 that I think I will be able to use, so thanks for the great work!

-Brian

[bisenberger]

Are these scripts compatible with 1.8.0?
https://github.com/agisoft-llc/metashape-scripts

[Paulo]

Hello Paul,

shapes in 1.8 version may be represented by the collection of multiple elements and will appear as list of lists via API. So if there's only single shape, then to access the coordinates of the Nth vertex you should use:

Code: [Select]

shape.geometry.coordinates[0][N]

Thanks again Alexey.

But it seems you could still keep the old shape vertices object though deprecated and that would avoid a lot of script adaptation, no?

[Paulo]

Another question for Alexey,

in case of shape with attached markers we use to access them through shape.vertex_ids. Now in 1.8, how o we do that?

[Alexey Pasumansky]

Hello Paulo,

If the shape has attached markers to its vertices (shape.is_attached == True), then the list of shape.geometry.coordinates will contain the keys of the related markers (marker.key).

[Mak11]

I know that it's still very early pre-release but here's a first test. Same settings with Mesh generated from depthmaps:

1.7.4

1.8

1.7.4

1.8


On the plus side this issue which was introduced with 1.7 seems to have been mitigated:

1.7.4

1.8




Mak

Just wanted to point out that things are even worst in version 1.8.0 build 13354 

Mak

Version 13597 is unfortunately still not as good as 1.7.x in terms of reconstruction in certain cases..



but is way better at eliminating (or simply not creating) all the messy geometry inside (and outside) the models (finally!).

1.7.x


1.8



Mak

[wojtek]

Second example looks good!

I will be doing some testing as well

[Mak11]

Second example looks good!

I will be doing some testing as well

Well..I took a closer look at the 1.7 & 1.8 results all over the mesh and unfortunately in some places 1.8 is worst than 1.7.x..its really random 😪

Mak

[bisenberger]

Are these scripts compatible with 1.8.0?
https://github.com/agisoft-llc/metashape-scripts

I changed compatible_major_version = "1.8" in bounding_box_to_coordinate_system.py script, and it works.