Messages

1

Bug Reports / Re: GPKG export fails with SQL logic error when saving attributes in Metashape 2.3.0

« on: January 12, 2026, 03:32:52 AM »

I found the problem. I shouldn't have had an attribute named "Layer".
The same thing generates an error when saving a project in Agisoft Viewer, after importing shape entities with attributes with this name.

2

Bug Reports / Re: GPKG export fails with SQL logic error when saving attributes in Metashape 2.3.0

« on: January 10, 2026, 03:45:47 PM »

I noticed that when save_attributes=True the export takes 13–20 sec and then fails (exit code 0 but with error), which suggests that the bug occurs when trying to create/write tables/fields in SQLite (attributes). This reinforces the cause.

3

Feature Requests / Re: Request adding 3D Gaussian Splatting into Metashape

« on: January 10, 2026, 03:43:19 PM »

Hi!
The spatial representation is much more realistic and helps me identify the details of the CAD reconstructions much better. I even noticed a better accuracy of the points in 3DGS extracted from PLY compared to those in the point cloud. In addition, I think 3DGS would help with upsampling.

4

Bug Reports / Re: GPKG export fails with SQL logic error when saving attributes in Metashape 2.3.0

« on: January 10, 2026, 03:01:07 PM »

From the log it is clear:
base_min ✅ (labels off, attrs off, student off)
labels_only ✅ (labels on, attrs off, elev off)
elev_only ✅ (labels off, attrs off, elev on)
labels_student ✅ (labels on, attrs off, student on)
But any combination that includes save_attributes = on fails with:
attrs_only ❌ SQL logic error (1)
labels_attrs ❌ SQL logic error (1)
attrs_elev ❌ SQL logic error (1)
full ❌ SQL logic error (1)

Metashape 2.3.0 b21868: GeoPackage export fails with “SQL logic error (1)” when save_attributes=True

5

Bug Reports / Re: GPKG export fails with SQL logic error when saving attributes in Metashape 2.3.0

« on: January 10, 2026, 02:49:03 PM »

I am also attaching the script that queries AG.
I'm back with an attempt to narrow down the problem area.

6

Bug Reports / GPKG export fails with SQL logic error when saving attributes in Metashape 2.3.0

« on: January 10, 2026, 02:45:02 PM »

Hi!
I wanted to see if the GPKG format could be useful to me and a problem occurred during export.

Bug: GeoPackage export produces empty gpkg_contents and SQL logic error when save_attributes/save_elevation are enabled (Metashape 2.3.0 b21868).

n Metashape 2.3.0 (b21868), exporting Shapes to GeoPackage reproducibly fails with “SQL logic error (1)” when save_attributes and/or save_elevation are enabled. The resulting .gpkg file is created but contains only metadata tables and no entries in gpkg_contents.

I tried to present the circumstances in which I get this error through a script made with AI.

I found an older thread that identified the same error.
https://www.agisoft.com/forum/index.php?topic=16227.0

I am attaching the generated report.

""

7

Agisoft Viewer / Re: 3D Models in Agisoft Viewer preferably Georeferenced

« on: October 04, 2025, 12:18:58 PM »

Hi! I have the same needs. Along with georeferenced entities, tilled model, shape entities and point clouds in oc3 format, I need to introduce a layer which is basically a 3D Model. However, is there no possibility?

8

Bug Reports / Re: Agisoft Metashape 2.2.0 and RTX 2060

« on: April 04, 2025, 07:12:45 PM »

  The solution was 100% sufficient.
I share the results of the processes, on the same data set, with the same settings, including those for filtering Tie points.
Overall, version 2.2.0 is faster.
An impressive result is the number of Tie points identified and used, almost double. This increases confidence in photo alignment.
I have thus identified an error in displaying the precision of determining the coordinates.
Thank you!

9

Bug Reports / Re: Agisoft Metashape 2.2.0 and RTX 2060

« on: April 02, 2025, 06:59:42 PM »

I don't have a crash report because the application remains blocked (Not responding)
If I understood correctly what to return with.. :
2025-04-02 18:54:40 Agisoft Metashape Professional Version: 2.2.0 build 19890 (64 bit)
2025-04-02 18:54:40 Platform: Windows
2025-04-02 18:54:40 CPU: AMD Ryzen 9 4900H with Radeon Graphics
2025-04-02 18:54:40 CPU family: 23 model: 96 signature: 860F01h
2025-04-02 18:54:40 RAM: 31.4 GB
2025-04-02 18:54:41 OpenGL Vendor: NVIDIA Corporation
2025-04-02 18:54:41 OpenGL Renderer: NVIDIA GeForce RTX 2060/PCIe/SSE2
2025-04-02 18:54:41 OpenGL Version: 4.6.0 NVIDIA 572.83
2025-04-02 18:54:41 Maximum Texture Size: 32768
2025-04-02 18:54:41 Quad Buffered Stereo: not enabled
2025-04-02 18:54:41 ARB_vertex_buffer_object: supported
2025-04-02 18:54:41 ARB_texture_non_power_of_two: supported

10

Bug Reports / Agisoft Metashape 2.2.0 and RTX 2060

« on: April 01, 2025, 08:56:05 AM »

I have updated repeatedly from v2.1.4 to 2.2.0 but each time I had problems with recognizing the dedicated video card with CUDA. I tried using different versions of drivers (Games/Studio) from Nvidia but without success.
The situation described is on an Asus TUF Gaming A15 Laptop, with AMD processor, updated Windows 10.
As a manifestation: in the settings, when I enter the GPU, Agisoft crashes, if I ignore this and start the image alignment process, in the Log it is seen that it works with the integrated card.
How could I successfully switch to version 2.2.0 on this system?
Thank you!