Recent Posts

31

Bug Reports / Re: Build Texture broken with GPU's enabled

« Last post by Alexey Pasumansky on December 02, 2024, 02:31:19 PM »

RTX 4050 on 566.14 Studio driver, using 2.2 pre-release and I'm still having this issue. Anyone else?

Hello johnnokomis,

What 2.2.0 build you are using? Have you tried the latest available (build 19522)?

32

General / Re: Access node locked license from docker container

« Last post by Alexey Pasumansky on December 02, 2024, 01:50:06 PM »

Hello Benjamin,

You need to deactivate the license on the physical machine, then start the docker and activate the license using the same key inside the docker itself. Then do not forget to deactivate the license before terminating the docker.

33

Python and Java API / Re: Optimizing cameras after importing edited point cloud to chunk

« Last post by Alexey Pasumansky on December 02, 2024, 01:30:49 PM »

Hello itaidotan,

Using this code you are importing Point Cloud, not Tie Points. If you need to import the tie points, you may consider using Bundler.out format.

34

Python and Java API / Re: chunk.tie_points.export() exports full PointCloud

« Last post by Alexey Pasumansky on December 02, 2024, 01:24:55 PM »

Hello itaidotan,

Please try the following:

Code: [Select]

chunk.exportPointCloud(path, source_data =Metashape.TiePointsData)Additional optional arguments can be added depending on the export needs.


If you need to access tie points coordinates, then you can use the following:

Code: [Select]

tie_points = chunk.tie_points.points
for point in tie_points:
   v_internal = point.coord
   v_internal.size = 3
   v_geocentric = chunk.transform.matrix.mulp(v)
   v_geographic = chunk.crs.project(v)

If the chunk is georeferenced, you'll get geographic coordinates in the chunk's coordinate system in v_geographic variable.

35

Python and Java API / Re: Issues with Camera Alignment in Metashape 2.2

« Last post by Alexey Pasumansky on December 02, 2024, 01:22:51 PM »

Hello mrv2020,

Thank you for reporting, however, I was not able to reproduce the issue on some random projects, can you please confirm that the issue persists in 2.2.0 build 19522?
If so, would it be possible to share any small minimal project (project file + images) to reproduce the issue on our side?

36

General / Re: Agisoft Metashape 2.2.0 pre-release

« Last post by Alexey Pasumansky on December 02, 2024, 12:34:15 PM »

I have two display adapters in my computer, an AMD Radeon RX 6600 XT and an NVIDIA GeForce RTX 3050. In Metashape Preferences it list the AMD Radeon RX 6600 XT twice, one Vulkan and the other OpenCL. By default the OpenCL one is checked. Is this the prefered settings, and what is the difference?

Hello bisenberger,

The issue with AMD graphic card doubling in Preferences would be fixed in the next 2.2.0 pre-release update.

As for the Vulkan checkbox, you can check it on, but in the current version it does not have any effect. Later it would have meaning for GPU-based texturing and vertex colorization procedure.

37

General / Re: Scale bar "Update" Button is not working

« Last post by Alexey Pasumansky on December 02, 2024, 12:05:35 PM »

Hello Riko,

Please make sure that both markers in the ends of scale bar have at least two projections on the aligned images and that scale bar is checked on in the Reference pane before pressing the Update button.

If it doesn't help, please specify, how many scale bars are there in the Reference pane and whether there are any cameras or markers with input source coordinates that are checked on.

38

General / Re: Agisoft Metashape 2.2.0 pre-release

« Last post by Alexey Pasumansky on December 02, 2024, 12:01:29 PM »

Hello dcobra,

Thank you for reporting.

We will fix it in the next update, as the splash screen should not show up, when Metashape is stated in network worker mode.

39

General / Re: Agisoft Metashape 2.2.0 pre-release

« Last post by dcobra on December 02, 2024, 12:15:28 AM »

.

40

Agisoft Cloud / Re: Ortho view (2D)

« Last post by wojtas on November 29, 2024, 11:55:02 PM »

I mainly do surveying and mapping job and in my personal experience there is a value in simplification of our data to the clients. This affects not only the products we create but also the tools we provide them to use the data. For example, I do a lot of construction mapping to gather spatial information about the site, in particular classified point clouds and orthomosaics, but I can clearly divide the customers to two groups: proffesionals who use my data into CAD envicoment to create analysis, cross section etc. but they do have they own software to do that. On the other hand, there is a second group of engineers who would like to simply review the orthomosaics with the CAD layers in the background but they do not have proper software, probably they are not very willing to learn new software and advanced tools, and there is a great space for online geoportals just like Agisoft Cloud to fill this gap. I do belive that enabling Cloud viewer to 2D ortho view would be a great optimization to this group of customers, providing them simply tools to quick analyze of data.

Edit: I forgot to mention that currently I do have mixed feelings about the navigation tools in the 3D model view - lack of tools to reset the top view, aling the view to north etc. First thing came to my mind was the 2D ortho view and that was the reason I suggested it.