To understand the value of Build 1552, one must look at the developmental arc of Agisoft Metashape. Version 1.8.0 brought significant changes to the core architecture, including GPU acceleration refinements and the shift towards Python 3. However, early 1.8.x builds suffered from minor memory leaks and compatibility issues with specific UAV (Unmanned Aerial Vehicle) geotags.
Unlike version 1.9+ which reorganized the export menu, Build 1552 keeps everything logical.
Even a mature build has eccentricities. Here are fixes for three frequent complaints regarding : Agisoft Metashape Professional 1.8.5 Build 1552...
to script and automate entire workflows, from photo alignment to final export. Hardware Acceleration : Utilizes GPU acceleration
For land surveyors using drones, is indispensable due to its support for ground control points (GCPs) and scale bars. This build improved the accuracy of marker detection, allowing users to geo-reference their models with sub-centimeter precision. Whether you are using a Phantom 4 RTK or a Matrice 300, this version ensures that the coordinate reference systems (CRS) are handled correctly, supporting vertical datums and compound CRS with fewer user intervention steps. To understand the value of Build 1552, one
Why stick with 1.8.5 Build 1552 when 2.0.0 is available? Here is an honest comparison:
For repetitive industrial work where uptime is critical, Build 1552 is superior. For R&D or experimental scanning, use version 2.0. Unlike version 1
The team chose Build 1552 specifically for its tie point filtering algorithm, which refused to align moving water surfaces (sea waves) into the static mesh—a common problem in coastal scanning. The resulting 3D model was accurate to ±1.2 cm.