Topics

1

General / Metashape 1.8.X not using all available GPUs

« on: January 24, 2022, 06:43:47 PM »

Hi

Today I've opened version 1.8.0 and, contrary to vs 1.7.6, the latest version cannot see all the available GPUs.
Cuda is enabled. Version 1.7.6 is behaving normally.
See attached screen captures.
Best Regards

2

Bug Reports / Metashape 1.7.3 not detecting all available hardware

« on: May 28, 2021, 09:21:07 PM »

Metashape 1.7.3 is not detecting all available eGPUs on Macos. In exactly the same conditions the GPU tab in both versions appear as attached images.
Best Regards

3

General / Agisoft support

« on: April 12, 2021, 12:29:06 PM »

Hi

Is the Agisoft support answering questions? I’ve been sending email since last Thursday without any answer.
Best regards

4

Bug Reports / Align chunks crash

« on: September 26, 2020, 04:50:53 PM »

The align chunks function is crashing with the following errors (Both MS 1.5.5 and Metashape 1.6.4 - see image labels for version).

5

General / Rolling Shutter bug?

« on: May 27, 2020, 08:32:01 PM »

While having the Rolling Shutter compensation flag on, the following error message appears if we generate the DEM both from the depth maps or the Dense Cloud.

"clSetKernelArg imageRectifyRollingShutter_uchar#11 (16 bytes) failed: CL_INVALID_ARG_SIZE"

Latest 1.6.2 version. MacOSX Catalina.

No problems in version 1.5.x generating the DEM from the dense cloud.

Cheers


PS: This bug seems to be gone in version 1.6.3 (latest beta). Was it corrected?

6

Bug Reports / Memory unload

« on: April 09, 2019, 12:04:13 AM »

There seems to be a few problems in memory unload, in Metashape 1.5.2 (7838), after finishing a few steps. Lot's of RAM stays locked within Metashape even if it is not needed anymore. This seems to be causing a few "out of memory errors" in further steps. In a complex project, with about 1117 photos, even using RAM cleaner apps, from 64GB only 7 GB are free. If we quit and open Metashape again, 57GB will be free with the same features opened. Even after visualize a dense 3D model, 48GB will be free. However, if a workflow is followed, in the end, after all processes finish, the RAM is still blocked. If we open a project and keep Metashape opened, memory keeps leaking and adding to the app, even without doing nothing.
Cheers

7

General / License problems in Mac OS High Sierra

« on: September 26, 2017, 12:43:21 AM »

In both PS 1.3.4 and PS 1.4 (beta), the legit license fails to register in Mac OS High Sierra, saying that license is already in use.
Even using the terminal, the following text appears:

"Error requesting activation
The activation key you supplied has already been used to activate a license.
Please check the key and ensure that you have entered it correctly.
Details: Activation key already used (-1005)"

Ideas?

Cheers

8

Feature Requests / DEM interface

« on: December 08, 2015, 04:02:42 AM »

Agisoft PhotoScan 1.2 it's an outstanding version! It's now a perfectly capable package (or more capable) to compete with any heavyweight in the photogrammetric terrain restitution.

Some small tweaks could be made into the DEM interface:

- An option should be provided to view a DEM in hillshade mode view. It would be a great visual aid to check for model imperfections and It would also be a great help to design polygons for volume restitution based on relief.

- Any data from the shape measure dialogue should be exportable, including the profile graph (as image or SVG graphics for instance)

- Exported shapefiles should include measuring field names as attributes and all measured values as table values (major and very useful feature).

The Orthophoto polygon image assignment now works incredibly well!


Cheers

9

Bug Reports / Memory management

« on: August 28, 2012, 04:22:41 PM »

It seems that the latest 0.9.0 build (1546) has some problems in the disk memory management.
When trying to use a previous project, Photoscan used about 50 GB of disk memory (about 30 GB used in version 0.8.0). The main problem is related with memory release. Photoscan does not release any disk memory and seem to cumulate that memory in every step, taking several GB after a session. Even after quitting the application, memory is still used for a while until the system slowly releases it. It's not possible to release used memory after the geometry and texture calculation?? It seems that Photoscan needs some routines for memory unload. In my case I got a memory overflow in a portable with only 47 GB available. Photoscan freezes and I had to trash several files to be able to resume it. Previously, in version 0.8, I was able to use the same project with the same amount of available memory.
Cheers

10

Bug Reports / Decimating Mesh

« on: June 22, 2011, 05:55:41 AM »

Something is wrong with the Decimating Mesh step while building geometry in this latest beta. I've run some chunks that took about 2 hours to complete the calculation until the "Integrating depth maps" step. After, the Decimating Mesh starts automatically and says that it has 80.29h to calculate!!!! It takes ages, even considering that the estimation varies. I had to force quit photoscan after one entire day with only 2% completed.  What can be wrong (if anything os wrong)? Is anyone else experiencing this? (MacOSX version)
Cheers

11

Bug Reports / Ortho generation

« on: June 08, 2011, 07:49:58 PM »

Hi

Since the last version (958), at least under the MacOSX version, Orthos are exported with strange brightness stains. In the last beta orthos were perfectly equalized. Now there are some portions of the image that seem to come from sunny obtained images and others from cloudy obtained ones. What can be wrong? The previous image was exported using JPEG and the wrong one was exported using TIFF (mask and world file options).
Cheers