Topics

1

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

2

Bug Reports / Snaps...

« on: November 29, 2023, 02:56:08 AM »

Snap tool was eagerly welcome, but after a few years it's still terrible, one can hardly see what is snapping to the tiny red dot and the snapped feature is not highlighted at all. It is the subtlest snap feedback I have ever seen. It is truely hard to notice when not even totally invisible if one is trying to snap to some vertex under another feature. The two modes available are not enough (what you call axis snap, I would not call it a snap mode, ibut rather ortho drawing mode)

When we are editing a shape A and we drag a vertex that was created with a snap on another vertex of a shape B, they move together even if we are not necesarily wanting to edit both features. is there a way to prevent this behavior?  can we de-snap a node on a feature so it can be dragged alone?

I have reported by mail that snap isn't working at all during rectangle creation... the bug remains the same in latest stable release and so in the 2.1 beta. Please solve.

By the way if you give us a rectangle tool, please let us have persistent rectangles. Allow us to draw them rotated, let us modify height and width with a gizmo in the midpoint of each side, or let us drag two adjacent sides consistently orthogonal when we drag a corner.

Best regards.
Geobit & Accupixel

3

Feature Requests / desirable save/load features

« on: November 29, 2023, 01:58:00 AM »

Here you are three
Please enable a save/load region.
Please enable save/load view
please enable a save/load shown/hidden items setting. (or just add a  revert "hide all")
please anable a save/load layers structure and symbology

Regards

4

Bug Reports / Honey, I shrunk the kids...

« on: September 24, 2023, 10:21:19 PM »

Hello. I have experienced one of the weirdest things ever with Metashape 2.0.3
I'm processing a large project with a some thousands of photos, and after finished alignment and some other pretty standard operations, I closed the project until next day.
When I open, I see the sparse cloud has been dramatically downscaled for no reason...

Any thoughts?.

José Martínez

5

Feature Requests / Allow saving bounding region

« on: January 23, 2023, 03:01:53 PM »

I know we can use script to copy region from one chunk to another, but it would be useful to save it so it can be recalled easier.
Regards

6

Bug Reports / ... error reading pixel

« on: January 13, 2023, 04:06:54 PM »

What can I do?

[...]
2023-01-13 13:55:52   2.83981/4~71% avg groups per camera
2023-01-13 13:55:52   146.25/206~70% avg cameras per group
2023-01-13 13:55:52   0% leaves avg camera intersects in group
2023-01-13 13:55:52   1% big leaves avg camera intersects in group
2023-01-13 13:55:52   29% of leaves are big
2023-01-13 13:55:52   100% of voxels in group are from big leaves
2023-01-13 13:55:52 saved 4 groups (0.03125 KB) for 344 leaves
2023-01-13 13:55:52 saved 2.28516 KB of affected cameras and 0.804688 KB of exclusive cameras for all leaves
2023-01-13 13:55:52 Scheduling octree 344 leaves hist initing in 4 groups (86 avg leaves per group)
2023-01-13 13:55:52 Initing hists in leaves group #1/4: [0; 60)...
2023-01-13 13:56:02 total cubes: 105221949 cubes, 1605.56 MB, 163.966 MB/s
2023-01-13 13:56:02 Data: 2408.34 MB hists + 0 MB codes, 117.297 MB pyramid
2023-01-13 13:56:02 Found 2 GPUs in 0 sec (CUDA: 0 sec, OpenCL: 0 sec)
2023-01-13 13:56:03 [GPU 1] Using device: NVIDIA GeForce GTX 1070 Ti, 19 compute units, free memory: 7104/8191 MB, compute capability 6.1
2023-01-13 13:56:03   driver/runtime CUDA: 12000/10010
2023-01-13 13:56:03   max work group size 1024
2023-01-13 13:56:03   max work item sizes [1024, 1024, 64]
2023-01-13 13:56:03 [GPU 2] Using device: NVIDIA GeForce GTX 1070 Ti, 19 compute units, free memory: 7197/8191 MB, compute capability 6.1
2023-01-13 13:56:03   driver/runtime CUDA: 12000/10010
2023-01-13 13:56:03   max work group size 1024
2023-01-13 13:56:03   max work item sizes [1024, 1024, 64]
2023-01-13 13:56:08 openexr error: Error reading pixel data from image file "openexr". Data decompression (zlib) failed.
2023-01-13 13:56:08 openexr error: Error reading pixel data from image file "openexr". Data decompression (zlib) failed.
2023-01-13 13:56:08 openexr error: Error reading pixel data from image file "openexr". Data decompression (zlib) failed.
2023-01-13 13:56:09 openexr error: Error reading pixel data from image file "openexr". Data decompression (zlib) failed.
2023-01-13 13:56:09 openexr error: Error reading pixel data from image file "openexr". Data decompression (zlib) failed.
2023-01-13 13:56:09 openexr error: Error reading pixel data from image file "openexr". Data decompression (zlib) failed.
2023-01-13 13:56:09 [GPU 1] Exception
2023-01-13 13:56:09 [GPU 2] Exception
2023-01-13 13:56:09 Peak memory used: 8.44 GB at 2023-01-13 13:56:06
2023-01-13 13:56:09 deleting all temporary files...
2023-01-13 13:56:10 done in 0.734 s
2023-01-13 13:56:10 Finished processing in 2280.18 sec (exit code 0)
2023-01-13 13:56:10 Error: Can't decompress depth

7

General / Weird decimation

« on: January 13, 2023, 01:27:37 PM »

I've recently observed that during decimation metashape divides the whole mesh into regions and it looks it decimates diferently. It gives the impression that it sets triangle count per cluster as target rather than a global volumetric parameter for cutting the iterative reduction process, so it leads to very noticeable diferences in mesh resolution thus exactness between clusters.
I think there's room for improvement here.
Regards

8

Feature Requests / back face color tint

« on: October 13, 2022, 02:45:50 PM »

Dear Agisoft devs.
I know there is an option for back face culling that works during orthomosaic creation hiding triangles with normals pointing towards the projection plane. It works well in some cases, but not-so-well for complex geometry where it often creates confusion when triangles in the hidden areas have normals towards the viewer.
I would like to have also an option for using a distinctive tint overlay for inverted triangles as alternative to culling.

The mesh is rendered darker for inverted faces, but it is not so much different to the positive face when texture or colour is also dark. It would be nice to have the color tint option also in the model viewport when looking at textured or shaded mesh.

Best regards.
José Martínez

9

Bug Reports / ortho view malfunctioning

« on: August 26, 2022, 08:05:18 PM »

Context: 3D model of a building mixing aerial and terrestrial photos. the project contains mesh, one projected DEM and several elevation façade planar orthomosaics.

My ortho view gets frozen when an orthomosaic is shown and I can neither drag (pan) nor draw. Zoom with mouse wheel also impossible, however magnification button works normally
If ortho view contains DEM, the odd behavior stops, and I can draw, pan, zoom etc.
If I switch to orthomosaic the problem comes back
But the weirdest finding is: if I de-default the existing DEM, then orthomosaic turns back to normal behavior, so it seems to be something related to DEM (projection) coexisting with orthomosaics (planar):

All with latest release.
Best regartds.

10

Bug Reports / zero tie points

« on: October 22, 2021, 01:04:58 AM »

Recently my colleague Simon Brown has had this weird issue. Right after aligning successfully a set of photos, there is no region and no tie points. How is this possible?
Repeating alignment has worked again as usual.
I'm lost.

JMR

11

Bug Reports / cylindrical dem

« on: May 25, 2021, 04:01:53 AM »

Hello Alexey: Have your fixed known issues with cylindrical dem>ortho?

Best regards,
José

12

Feature Requests / quantities to attributes

« on: May 04, 2021, 08:15:17 PM »

It would be a good idea an option to write the result of volume measurements to the attributes of the shapes used for their estimation.
Along with quantities the list of attributes should include method and parameters used for fill/cut calculation and perhaps timestamp so quantities can be linked to a given DEM status or creation date?

Best regards.

GEOBIT

13

General / Intelligent paint... is it of any use for you?

« on: September 19, 2020, 01:06:43 PM »

I've been using Photoscan and Metashape for ages, but I still cant figure out how this tool has been with us for so long. Sorry but I can't make it workable at all. Can anyone post a good example of its use that can justify why we do have such a long-standing tool, but we can't have instead a simple but effective user-sizeable circular brush.
Why this intelligent paint does not even reset when one hits esc to try again? what am I completely missing?

Thanks

14

Feature Requests / Invert tilt movement in terrain mouse mode

« on: September 07, 2020, 09:38:16 PM »

I have requested it some time ago and complained about the weird mouse behavior in Terrain mode.
You argued that in the current way it was more consistent with other applications in the market... I then wondered which ones.
At the end I never use this mode because it hurts my brain so much.
But now that Agisoft Cloud uses the mouse movement in the right way. Therefore I beg you to be consequent and change it in Metashape Professiona to work as it does in Cloud. If not, at least please, add a tweak for letting users to invert terrain tilt direction to match Agisoft Cloud.
Best regards, and congrats for the nice website design.
GEOBIT

15

Feature Requests / Spherical targets

« on: August 03, 2020, 08:59:30 PM »

Hello, Agisoft:
Spherical targets are widely used in terrestrial laser scanning. They are convenient due to de fact that a sphere looks the same from any pont of view and does not require being orented towards the sensor like planar targets do.
I guess it would be really usefull if Metashape where able to detect a sphere centre point automatically as it does with circular targets. It would help laser scanning works to be co-registered with photo scans.
Unlike planar circles, spheres always look round enough in a picture regardless the angle of view, so a circular feature detector, should work fine, even when it is not surounded by a black crown like in non coded circular targets.
Please keep improving Metashape by adding funtions for a better integration with TLS.
Best regards