1
Feature Requests / Re: Selection Toolset -> Add Polygon Tool
« on: May 10, 2026, 10:20:55 PM »
PLEASE AGISOFT. KILL THE LARGELY USELESS INTELLIGENT PAINT AND ADD A POLYGON SELECTOR WHICH IS WAY MORE USEFUL THAN LASSO
Show Posts
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
2
General / Re: High reprojection error when aligning mixed rotated and non-rotated drone images
« on: February 25, 2026, 08:07:17 PM »
Clarify what you mean by rotation. If you've rotated some images 180 degrees around the optical axis, and Metashape doesn't recognize this, you've made a fatal error. The calibration parameters will have to be adjusted to some approximate intermediate value valid enough for both sets of photos—and this is detrimental to both sets. You need to split the calibration group between two cameras, as distortion is generally neither symmetrical nor centered. This way, Metashape will know it can estimate a center point and different distortion coefficients for each set.
What you've done is, by definition, a bad idea, but it shouldn't be too serious. With such a large number of photos, the project won't be in any way compromised in ensuring robust self-calibration of both sets of parameters.
What you've done is, by definition, a bad idea, but it shouldn't be too serious. With such a large number of photos, the project won't be in any way compromised in ensuring robust self-calibration of both sets of parameters.
3
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
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
4
Bug Reports / Re: Masks not merging as well
« on: February 09, 2026, 03:57:07 PM »
My experience differs from your description:
if I merge with "merge masks" I get a merged chunk with two masks sets. kinda weird to add the need of a new merge to actually merge. But learnt.
I might sometime find a case when having two sets requiring the re-merge makes me feel lucky.
if I merge without "merge masks! I get a merged chunk with no masks at all
Regards
if I merge with "merge masks" I get a merged chunk with two masks sets. kinda weird to add the need of a new merge to actually merge. But learnt.
I might sometime find a case when having two sets requiring the re-merge makes me feel lucky.
if I merge without "merge masks! I get a merged chunk with no masks at all
Regards
5
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
Is it a know/wanted behaviour for some reason?
Regards
6
General / Re: Accuracy differences in drone flights at 50 m vs. 100 m for final thesis
« on: January 28, 2026, 08:30:46 PM »
Hi, Haenni:
There is little to do with a simplr psx file without the project folder.
I'm not fully understanding the real question but to you need to explain more in detail the two datasets under analysis. It is hard to say what is going on when you campare flight at 100m and 50m altitude. do you keep overlap the same, are also the same the number and distribution of ground control points? within the two blocks? are you halving the flight speed for the 50m survey to make both flights comparable in terms of pixel quality?
There are so many factors that it is hard to say how you can establish seriously the relationship between ground accuracy and flight altitude out af a real life case. I think these inferences must come out of error propagation theory (pure maths and stats) or at least out of a very well controlled use case that hardly fits in the real life. In any case, we would need to check your very case to see if there's something obvious.
As when it comes to the Mini you must start by understanding the limitations of a sensor with e-shutter and adjust the flight mission accordingly to exclude the rolling shutter effect in your analysis.
There is little to do with a simplr psx file without the project folder.
I'm not fully understanding the real question but to you need to explain more in detail the two datasets under analysis. It is hard to say what is going on when you campare flight at 100m and 50m altitude. do you keep overlap the same, are also the same the number and distribution of ground control points? within the two blocks? are you halving the flight speed for the 50m survey to make both flights comparable in terms of pixel quality?
There are so many factors that it is hard to say how you can establish seriously the relationship between ground accuracy and flight altitude out af a real life case. I think these inferences must come out of error propagation theory (pure maths and stats) or at least out of a very well controlled use case that hardly fits in the real life. In any case, we would need to check your very case to see if there's something obvious.
As when it comes to the Mini you must start by understanding the limitations of a sensor with e-shutter and adjust the flight mission accordingly to exclude the rolling shutter effect in your analysis.
7
General / Re: Equidistant vs Equisolid Fisheye?
« on: January 04, 2026, 12:52:55 PM »
Equisolid and equidistant are different planar projections of points on a sphere. While the former tries to keep areas undistorted, the later keeps distances to the center of the image equivalent to distances on the sphere. A fisheye lenses can be designed to counteract the inherent distortion of a planar projection of a spherical image aimed to mimic one of these projections. Rectilinear projection is imposible if FOV is equal to 180 because points on the extremes would be projected parallel to the image plane towards the infinity.
I haven’t seen any fisheye lens vendor quantifying the lens with this respect, so it’s a bit unclear for me as well why Agi has found it necessary to add this distinction.
I haven’t seen any fisheye lens vendor quantifying the lens with this respect, so it’s a bit unclear for me as well why Agi has found it necessary to add this distinction.
8
General / Re: Allign Scans and Fotos
« on: November 12, 2025, 08:15:09 PM »
Hi Dieter: I've found a simple way.You can place, by eye and without worrying too much about where, three or more non-aligned points on one of your scans right after import so they take their absolute coordinates from your referenced scans. Then follow the awkward procedure that is meant to allow Metashape to tie photos and scans.
After that, check on the three points and update transform. All the chunk will turn back to the original global position.
It works, at least it is an easy escape from the situation to which the recommended procedure leads, which involves disregarding the georeferencing work of the scan as well as the very precise leveling constrained by the inclination sensors inside of your scanner.
Regards, José Martínez
After that, check on the three points and update transform. All the chunk will turn back to the original global position.
It works, at least it is an easy escape from the situation to which the recommended procedure leads, which involves disregarding the georeferencing work of the scan as well as the very precise leveling constrained by the inclination sensors inside of your scanner.
Regards, José Martínez
9
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,
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,
10
Bug Reports / Re: I can't edit reference source values cells
« on: November 12, 2025, 04:53:07 AM »
yes F2, sorry, the bug is in my memory. I must have known this some day in the past but I had forgotten because I rarely edit camera coordinares one by one; this is something most of us do by importing a file. Thanks for reminding me and again I'm sorry.Regarding the command that's been taken one click further, I admit that it's not so bad if I have a free hand for the keyboard shortcut.
That said, is it too much to ask for a method to make easy to transfer user settings from one computer to another, saved in a dedicated file?
Regards
11
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
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
12
General / Re: Developing Terrestrial SFM Workflow
« on: October 20, 2025, 10:45:27 PM »
Drone imagery comes with geotags and that provides Metashape with a good hint to guess how images overlap their neighbors and saves a lot of useless matching attempts. If your terrestrial images are geotagged and have similar overlap as you aerials, times should be similar. if not, that's possibly the reason for the delay. Use high and not ultrahigh for alignment, and let default keypoint/tiepoint limits unless you know you have a reason to increase or decrease them. They are very well tested and found tobe the ideal compromise between computational cost and success.
Regards.
Regards.
13
General / Re: Concurrent versions installed
« on: October 20, 2025, 10:33:31 PM »
Your license is tied to your machine, so you can run multiple instances in your computer and multiple versions too with a single license.
Regards,
José Martínez
Regards,
José Martínez
14
General / Re: Licencing -- identify the node locked licence on a machine
« on: October 13, 2025, 12:28:23 PM »
what if you deactivate all of them and start from scratch activation taking note of association computer name - license key
15
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
Also it woulf be nice an option to highlight the line of intersection between the bounding box and the mesh.
Regards
