Topics

1

Feature Requests / Interactive lighting and new shader

« on: February 25, 2026, 12:28:37 PM »

Hi Agisoft team:
The ability to move interactively the light source both in the DEM view and in the model view would be very welcome. Sometimes raking lighting helps a lot to show 3D features that are hardly visible.
Also, It would be very nice to have another render mode for the monochrome 3D model similar to the radiance scaling shader like we have in Meshlab.

Best regards,
Geobit

2

Bug Reports / Masks not merging as well

« on: February 03, 2026, 10:18:34 AM »

I’ve noticed when I merge two chunks with their own set of masks, the merged chunk has masks only from one chunk, making it necessary to export masks from the children chunks and then import to the merged one. Very inconvenient generally but even more if image labels are the same.
Is it a know/wanted behaviour for some reason?
Regards

3

General / Minimal inputs for global transform

« on: November 12, 2025, 07:57:54 PM »

what if
One single reference point could be used to translate a chunk to a given coordinates keeping scale and angles as they are.
Two reference points could be used to translate and scale keeping angles about x and y while rotating about z
wouldn't it be useful for many of you?
what if the trackball could be constrained to work with the Z always vertical for referenced chunks (similar to the terrain mode but in a more standard way). When the Z axis is tied to gravity (most of cases) one wants vertical objects to stay vertical
Regards,

4

Bug Reports / I can't edit reference source values cells

« on: November 10, 2025, 12:29:37 AM »

Hello:
Quite strangely, since some day I cannot tell when, it has started to be impossible to edit source values in the reference panel table as always by doble click on the cell one wants to edit. So now I need to right click and choose modify, then choose easting, etc... that's painfully slower, as much as I find it has become slower to change orthomosaic photo assignments. Please agisoft stop moving tools if any change adds one o more clics unnecessarily.
Instead of making changes no one is asking for, make the interface improvements that users have been requesting for years: a polygon selection tool, a cursor icon that corresponds to the current tool, etc.
Regards

5

Feature Requests / Back face darken in orthomosaic.

« on: August 19, 2025, 09:12:38 PM »

I find truely disapointing not being possible to notice when a face is showing its back side to othomosaic. It is necessary and in my opinion more useful than  the existing back face culling option.
Also it woulf be nice an option to highlight the line of intersection between the bounding box and the mesh.

Regards

6

General / point cloud precission degraded during export

« on: May 17, 2025, 03:17:26 PM »

Here is what I find.
Build a dense cloud within Metashape and pick a random collection of points. (I have done by means of the point drawing tool and then exported shape layer as survey point)
what I get is a list of points with coordinates like this. I have forced 4 decimal places on purpose.

469198.0893   4625535.6525   1020.9728
469200.9825   4625551.8803   1020.9609
469216.0177   4625558.8820   1020.7016
469235.0625   4625544.2959   1020.5023
469259.3013   4625557.6343   1020.7807
469272.4699   4625569.4271   1020.6212
469253.4956   4625577.6966   1020.1291
469223.2505   4625592.8820   1020.1857
469201.0821   4625580.1614   1020.6648
469180.5939   4625594.9720   1020.4086
469200.7915   4625598.4140   1020.4623
469222.4491   4625573.0174   1020.4413
469205.2609   4625563.3425   1020.8171
469234.5305   4625580.4200   1020.2658
469238.0023   4625565.8765   1020.3454
469228.7112   4625549.2787   1020.5605
469224.8822   4625529.2167   1021.2488
469212.8580   4625520.4667   1021.3260
469235.9866   4625517.7975   1020.7513
469262.2400   4625536.9397   1020.6720
469289.2738   4625544.9382   1020.3045
469297.8275   4625565.9952   1019.9460
469290.8024   4625580.5749   1019.9231
469257.4640   4625590.1000   1020.0492
469233.1867   4625595.1511   1020.1426
469250.0749   4625603.2549   1020.0406
469212.4016   4625582.2603   1020.4655
469178.2591   4625560.1662   1018.1213
469176.1339   4625535.1855   1020.6418
469205.2949   4625525.7642   1021.1719


Then I have exported the dense cloud and open into CloudCompare and picked a similar collection (not the same ones, I said its a random sample)
Here is what I have

469212.8600   4625596.7200   1020.3900
469193.0000   4625609.5200   1020.4000
469273.4700   4625628.8600   1019.9400
469236.1300   4625634.8300   1020.1400
469365.8400   4625617.5800   1019.4100
469335.3000   4625558.8000   1020.1400
469269.9900   4625564.1500   1020.6700
469238.5000   4625556.9900   1020.4500
469196.2000   4625576.6500   1020.9900
469174.4100   4625563.3200   1020.8000
469176.0100   4625538.6600   1020.8900
469233.8900   4625493.7500   1020.5500
469287.3700   4625511.6400   1020.3300
469304.8600   4625540.0500   1020.0500
469350.1100   4625617.9000   1019.1800
469353.5000   4625662.0400   1019.3200
469205.2900   4625511.9200   1021.3300
469201.3000   4625540.5200   1021.0300
469219.8300   4625568.7100   1020.5900
469250.2700   4625592.5300   1020.0800
469282.8000   4625578.4500   1020.4100
469244.4800   4625579.8600   1020.2400
469235.8800   4625597.7900   1020.1500
469224.9600   4625581.8400   1020.3300
469193.8700   4625594.0400   1020.5600
469203.3101   4625555.5700   1020.9900
469224.1200   4625544.0600   1020.7800
469235.2500   4625526.6700   1021.0000
469273.4900   4625524.4900   1020.7700
469287.3300   4625542.0800   1020.3800

all milimetres have gone! Why?

Same happens within Global Mapper or any program, so is it maybe Metashape degrading the point cloud accuracy during export?

Regards

7

Feature Requests / Obect vs terrain modes

« on: May 16, 2025, 09:51:36 PM »

I'll be frank. There are a number of things about the way we navigate in the model view that truly demonstrate how pathologically lazy our Agisoft heroes are when it comes to improve the GUI user experience.

We've spent years and years getting used to a stone in our shoe, but the callus on my foot hasn't made me forget about that damn stone.
Object mode is the only one I use because switching from it to terrain mode is so much painful as telling a violinist to switch the bow and violin to play Beethoven and use the other mode to play Vivaldi. They aren't two modes that can coexist in the same standard brain. IMHO

Since mostly all users I know prefer object mode, couldn't a toggle be added so that in referenced models, all movements could be forced to always keep Z up, but without changing anything else in that mode?

Is there anyone here, leaving aside those who feel comfortable watching the Tower of Pisa, who likes not being able to prevent the view from rolling to one side or the other when using free rotation without  fighting to pick the trackball's equator?

Only if the model isn't referenced, or hasn't yet been transformed into a world with Z up, should the current mode's crazy rotation be the default. This current "zero gravity" mode may be desirable in very specific cases and yes, keep it for such very specific operations, but for my taste, it's exceptional, not universal.

But if what I suggest doesn't seem like a sensible request, why not just add special screen zones near the window margins  that can be made visible and active by holding certain key to constrain the rotations of the current mode to rotations about camera view axis? Something like this:


Best regards.

8

Bug Reports / merge chunks + masks fails

« on: April 15, 2025, 04:03:25 PM »

Ive got 2 chunks both with masks, when I merge with "merge masks" checked, the merged chunk comes out with masks only in one set of images.

Regards
Geobit

9

General / Filter photos by shape

« on: April 14, 2025, 10:59:45 AM »

Filter photos by shape works only for the vertices of the given shape. There should be an option to select all the photos that can see the shape along the edges and optionally also inside a closed shape.

Agisoft, please, give us a proper polygon selection tool, (or at least let us use any closed shape for selections as serves for dense points), you can't keep ignoring this simple tool requested for years, freehand is fast but is very imprecise.
Let us select photos by polygon, select triangles by polygon, select tie points by polygon, PLEASE

10

Feature Requests / larger recent project list

« on: March 07, 2025, 08:56:33 PM »

I wish the recent projects list was longer, why not at least 12 rather than only 5?
Thanks

11

Bug Reports / Ambient occlussion messed up by block model

« on: February 18, 2025, 10:49:03 PM »

I had to build my mesh partitioned into blocks due to bad allocation error (not enough memory?). After that, I merged the blocks and got one single mesh model that appartently is clean and appears to be gapless in the seams.
However, the mesh topology in the seams is faulty and that causes these ugly black strips on the occlussion map.
The merge blocks operation needs some rework in my opinion
Regards
Geobit

12

Bug Reports / Mask from model has gone?

« on: February 01, 2025, 03:03:09 PM »

Edit: No, it is now under tools menu.

Regards

13

General / importing E57 scans. I'm lost

« on: September 24, 2024, 04:04:41 PM »

Hi, Agisofties
Why some e57 exported from a terrestria laser scanner turns into an equirectangular depth panorama and sometimes as a set of cube faces, and sometimes there is no image version at all. Is there a way to choose how Metashape reads a scan, and more importantly, is there any reason to consider one format result comes with any particular benefit or is better suited for any workflow.
The following image shows the result of importing three E57 scans, and ech behaves differently even if I use same settings at import dialog.

Best regards

JMR

14

Feature Requests / Align chunks by laser scans

« on: April 30, 2024, 11:33:49 AM »

I think it would be useful and I'd love to see this added to the methods. If I have two chunks connected by a common laser scan or point cloud, it would be super easy and fast to use it as reference source for transforming one chunk to the other.
Cheers

GEOBIT

15

Bug Reports / invisible boundary shapes

« on: December 01, 2023, 10:24:19 PM »

Dear Agisoft team.
Boundary shapes remain active in spite of the layer status. I wished to be able to keep different sets of boundaries stored in layers with different purposes, and thought I would be allowed to choose the active set of boundaries to produce desired deliverables with different extents according to the active layer while the remaining layers were disabled... but nope, it does not work. Boundary action override the layer status and the clipping was always the same. I think this is not the right behaviour.
Regards

Geobit