Messages

1

Feature Requests / Re: Cropping orthophotos

« on: January 21, 2026, 11:59:35 PM »

HI Alexey or Maxime,

Could you elaborate on how that mask would be created at the ratios required then applied to all photos? Sorry for my ignorance but if haven't worked with masking before.

Kind regards,
Ben

2

Feature Requests / Re: Preview of tile size and location prior to exporting Tiled Ortho or other items

« on: January 21, 2026, 11:45:26 PM »

Just trying to raise this suggestion again. When my terrain boundaries are irregular (most projects) I have to repeat exporting the ortho many times until i obtain a satisfactory tile schema.
Hopefully my suggestion above could be considered for inclusion in upcoming versions?

Thanks
Ben

3

General / Re: Importing Model- Unable to select coord system - Coord diagolue box greyed out

« on: August 21, 2025, 07:37:16 AM »

Thanks Alexey

4

General / Re: Importing Model- Unable to select coord system - Coord diagolue box greyed out

« on: August 19, 2025, 08:06:57 AM »

Also Alexey,

Could I suggest that the functionality if the python script be included  as standard functionality (without the need of the script) for a future version of Metashape

Thanks again

Ben

5

General / Re: Importing Model- Unable to select coord system - Coord diagolue box greyed out

« on: August 19, 2025, 05:12:27 AM »

Hi Alexey,

Thank you! The python script (PS210_import_mesh_DXF_OBJ_w_shift.py) from that thread, worked.

Thanks again

Ben

6

General / Importing Model- Unable to select coord system - Coord diagolue box greyed out

« on: August 18, 2025, 04:22:02 AM »

Hi,

I have created a new metashape project (using version 2.2.1).

I want to import a 2.5d model of the ground surface which is about 250 metres long by 50 metres wide. The model is is AutoCAD 3d faces in dxf format.

My steps -
1. Create and save new project
2. In reference settings change reference coordinate system from Local Coordinates to MGA2020 / Zone 55 (ESPG 7855) + AHD   (that is an Australian system)
3. Save project
4. File / Import / Model  -  select the dxf file and import
5. This is where the import model dialogue box that appears is all greyed out. In grey it shows "local coordinates " but i can't change it as it is greyed out. See attachment

I have also tried running the following setting on the console command line but that didn;t work -  Metashape.app.document.chunk.transform.matrix=Metashape.app.document.chunk.transform.matrix

Would anyone have any suggestions?

Thanks
Ben

7

Feature Requests / Preview of tile size and location prior to exporting Tiled Ortho or other items

« on: July 13, 2025, 06:52:50 AM »

Hi

This suggestion is for when exporting an Orthomosaic (or any other data) where the user wants the exported data split into tiles or blocks.

I would like to suggest that when defining the size of the blocks or tiles in the current dialogue box that a   "preview" schema or linework is shown in the viewer over the ortho or other data (model, dem, point cloud). This would show the user what tiles are going to be exported and specifically what data will be in each tile. If the user does not like the proposed extent of each tile they could then adjust the size in the dialogue box.

Currently the user has no idea of the actual extent of the tiles / blocks until they are viewed in other software.

Currently, when I export a tiled ortho, i may have to do it several times because the tiling function may create a tiles that have very little data. It is not until i view the schema that I know the tile extent that has been exported. A "preview" function, like suggested above, would stop this problem

Thanks for reading
Ben

8

General / Re: Error - Too small max compute workgroup

« on: May 13, 2025, 12:54:06 PM »

Hi Olihar,

I am now. 2.2.1

9

General / Re: 2.2.1 issue? - Sparse Point Cloud not showing in Model view port

« on: May 13, 2025, 12:52:24 PM »

Hi Olihar,

Thanks for replying.

Nothing shows up.

10

General / Re: Error - Too small max compute workgroup

« on: May 10, 2025, 04:00:59 AM »

Hi Alexey,


Thanks for looking at this problem. But I seem to have fixed it.


Because my client was waiting on the data my first work around was to tick the "split into blocks" option when creating a model. This worked, I didn't get the error.


But my proper solution was to update all NVidia drivers. The fixed the problem and I was also able to create the model as a single entity.


Thanks again
Ben


P.S. if you could have a look at the other issue I posted yesterday that would be great  [size=78%]- [/size]Topic: 2.2.1 issue? - Sparse Point Cloud not showing in Model view port


Snapshot of my GPU preferences, attached as requested

11

General / 2.2.1 issue? - Sparse Point Cloud not showing in Model view port

« on: May 09, 2025, 04:30:29 PM »

Hi,

I have replicated this issue twice now using 2.2.1. I have not seen it in previous versions.

I have create a sparse cloud from 6500 images. The sparse cloud has about 8.4 million tie points. I go to do a gradual selection clean (now called Clean Tie Point in 2.2.1). After selecting 200,000 points using the Project accuracy slider and deleting them, then running optimization, the sparse cloud disappears from the viewer. The tie point counter, in the bottom left of the screen, is showing me the correct number of points (8.1 million) but there is nothing on the screen. I have tried resetting the view, resetting the region but nothing shows the tie points. And obviously the tie point button is clicked to show tie points on.

Luckily i had duplicated the chunk before I started the gradual selection clean. The sparse cloud shows up perfectly in the first chunk

Would any one have any suggestions?

Regards
Ben

12

Feature Requests / Smart Marker detections by Surveyed GCP Location

« on: May 09, 2025, 07:23:25 AM »

Hi,

Could you please consider adding this option to marker detection -

1. a csv or txt file (import reference command) is used to import the GCP locations.
2. Detect Marker command is run but with the option of only searching images within a nominated radius of the imported markers. The user would nominate the radius e,g 20 metres

Using this suggestion Metashape will only search images in the areas of the imported GCPs, which should speed up the process. Instead of every image or selected images

I have a project of 350 hectare area - 6500 images and 32 non-coded markers. I think if my suggestion  was implemented the process of detecting markers would be very quick.

Thanks for reading

Kind Regards
Ben

13

Feature Requests / Re: Selection Toolset -> Add Polygon Tool

« on: May 09, 2025, 07:11:20 AM »

+1 - this is really needed

14

General / Error - Too small max compute workgroup

« on: May 08, 2025, 02:01:42 PM »

Hi,

When starting the "Build Model" command I get an error which stops the command. The problem is listed in the log file -

2025-05-08 20:45:23 Vulkan device Intel(R) UHD Graphics 770 skipped: too small max compute workgroup count 65536x65536x65536 (at least 524288x16384x16384 required)
2025-05-08 20:45:23 Found 2 GPUs in 0.016 sec (CUDA: 0 sec, OpenCL: 0 sec, Vulkan: 0.016 sec)

This job has only around 2000 photos. I have processed jobs many times bigger than that on this computer.

Could someone please tell me why this would happen -  "too small max compute workgroup count 65536x65536x65536 (at least 524288x16384x16384 required) "

I am using professional version - 2.2.0 build 19890

Thanks
Ben

15

Feature Requests / Re: Select mesh by shapes

« on: March 08, 2025, 03:49:43 AM »

+1