Messages

1

Bug Reports / Linux Metashape 1.7.6 and rasterio

« on: December 09, 2022, 03:17:01 AM »

I seem to have found a strange bug when trying to use rasterio 1.2.+ and Linux Metashape (the version I was mainly testing on was 1.7.6 but I have seen this in other versions as well)

I have only tested this when using the API or Python console with the installed Metashape version (not the .whl)

Specifically, Metashape crashes with a "Segmentation fault (core dumped)" message when attempting a simple rasterio open call such as:

Code: [Select]

import rasterio
f1 = rasterio.open("/path/to/raster/ortho.tif")

I uninstalled rasterio 1.2+ and installed rasterio 1.1.5 and the error disappeared.

I do not seem to see this bug in Windows Metashape and rasterio 1.2+, however.

2

Python and Java API / Re: External python modules not found

« on: May 26, 2020, 07:01:26 PM »

I'm having the same error with Ubuntu 20.04 and Metashape 1.5.5:
ImportError: cannot import name 'HTTPSHandler'

I installed libssl according to https://agisoft.freshdesk.com/support/solutions/articles/31000136860-how-to-install-external-python-module-to-metashape-professional-package

Default Python is 3.8 but even did an alt install of 3.5.2. Still getting the same HTTPSHandler error when running this command:

Code: [Select]

LD_LIBRARY_PATH=/usr/local/metashape-pro/python/lib:/usr/local/bin/python3.5:/usr/local/lib/python3.5:/usr/lib/x86_64-linux-gnu ./python3.5 -m pip install numpy
Should I revert back to an earlier Ubuntu release and/or upgrade to the latest Metashape? (Dragging my feet on upgrading to latest Metashape because it would involve rewriting a lot of code for the API..)

As an update, I'm seeing the same "HTTPSHandler" issue with Ubuntu 20.04 and the latest Metashape (1.6.2)

SOLVED (for now): As another update, this works perfectly normally with Ubuntu 18.04. So, I would suggest sticking with the older Ubuntu release until a workaround for 20.04 is determined.

3

Python and Java API / Re: External python modules not found

« on: May 26, 2020, 02:19:36 PM »

I'm having the same error with Ubuntu 20.04 and Metashape 1.5.5:
ImportError: cannot import name 'HTTPSHandler'

I installed libssl according to https://agisoft.freshdesk.com/support/solutions/articles/31000136860-how-to-install-external-python-module-to-metashape-professional-package

Default Python is 3.8 but even did an alt install of 3.5.2. Still getting the same HTTPSHandler error when running this command:

Code: [Select]

LD_LIBRARY_PATH=/usr/local/metashape-pro/python/lib:/usr/local/bin/python3.5:/usr/local/lib/python3.5:/usr/lib/x86_64-linux-gnu ./python3.5 -m pip install numpy
Should I revert back to an earlier Ubuntu release and/or upgrade to the latest Metashape? (Dragging my feet on upgrading to latest Metashape because it would involve rewriting a lot of code for the API..)

As an update, I'm seeing the same "HTTPSHandler" issue with Ubuntu 20.04 and the latest Metashape (1.6.2)

4

Python and Java API / Re: External python modules not found

« on: May 25, 2020, 10:32:00 PM »

I'm having the same error with Ubuntu 20.04 and Metashape 1.5.5:
ImportError: cannot import name 'HTTPSHandler'

I installed libssl according to https://agisoft.freshdesk.com/support/solutions/articles/31000136860-how-to-install-external-python-module-to-metashape-professional-package

Default Python is 3.8 but even did an alt install of 3.5.2. Still getting the same HTTPSHandler error when running this command:

Code: [Select]

LD_LIBRARY_PATH=/usr/local/metashape-pro/python/lib:/usr/local/bin/python3.5:/usr/local/lib/python3.5:/usr/lib/x86_64-linux-gnu ./python3.5 -m pip install numpy
Should I revert back to an earlier Ubuntu release and/or upgrade to the latest Metashape? (Dragging my feet on upgrading to latest Metashape because it would involve rewriting a lot of code for the API..)

5

Bug Reports / Re: Texture Generation problem

« on: July 22, 2018, 03:56:54 AM »

Hi Alexey,

Yes - i'm seeing it in 1.4.2.  I have not tried 1.4.3 yet.

Thanks!
Ricky

6

Bug Reports / Re: Texture Generation problem

« on: July 21, 2018, 10:05:45 PM »

Just revisiting this issue - it seems to happen only with models that are smaller in scale. The textures of my large area sUAS models turn out fine and they have millions of faces. However, smaller areas with a large amount of photogrammetric overlap seem to cause the problem. For example i have an area the size of 50 m x 40 m with approximately 40 images covering it. When i try to texture the ~250,000 face model, i get the blurry striped texture issue. If I decimate that same mesh to 50,000 faces and re-texture then it turns out fine. So it seems to be related to overlap percentage somehow..?

7

Bug Reports / Re: Texture Generation problem

« on: June 22, 2018, 10:52:19 PM »

Hi Alexey,

It seems as though 1.4.2 has fixed the texturing issue that I was experiencing. I'll reply back on here if I run into any more issues.

Thanks!
-Ricky

8

General / Re: Crash at dense cloud processing - CUDA ERROR

« on: June 18, 2018, 11:52:32 PM »

We got the same error with the latest version 1.4.2 of Agisoft. We are using NVIDIA Quadro P6000. Interestingly, 1.3.5 cannot even “see” the GPU

Seconded. Having the exact same issue with a Quadro M6000 24GB GPU.

9

Python and Java API / Re: Camera estimated angles from reference pane

« on: June 05, 2018, 02:14:06 AM »

Please disregard - my next search turned up this post that is exactly what i was looking for
http://www.agisoft.com/forum/index.php?topic=6340.msg30868#msg30868

10

Python and Java API / Camera estimated angles from reference pane

« on: June 05, 2018, 02:06:10 AM »

Is there a way to calculate the camera estimated angles (yaw, pitch, roll) that we see in the Reference pane?

11

Bug Reports / Re: Texture Generation problem

« on: June 01, 2018, 03:14:45 AM »

Hello,
I'm having the same issue. I've upgraded to 1.4.1 also.
-Ricky

12

General / Re: How to Export Realistic KMZ

« on: April 30, 2017, 05:38:15 PM »

Been awhile since this topic was posted, but still seeing the same issues with the kmz model and elevation. It seems the elevation of the exported model above the terrain is always around 30 meters or so. Wondering if the model can be exported without that +30 m bias?

13

General / Re: Texture import / export problems.

« on: February 05, 2017, 04:56:09 AM »

Nick,

I'm having similar issues. I want to get the Photoscan model into the Hololens (.fbx only). Apparently, the textures need to be baked into the fbx model. I've tried using Blender to do this but the best I can achieve is the shaded texture colors as you mentioned (not the high-res texture).

I've tried quite a few options (like importing/exporting from Meshlab, then into Blender, etc) but still no luck!

-Ricky

14

Bug Reports / Re: Crash Photoscan when opening OpenCL PReferences

« on: June 29, 2016, 03:47:20 PM »

I was just having this problem with a brand new laptop. I have an NVIDIA Qaudro M5000M GPU. Seems to have been fixed when I went into the NVIDIA Control Panel and changed "3D Settings -> Manage 3D Settings -> OpenGL Rendering GPU" to the installed GPU (not Auto-Select). Also changed the PhysX processor to the GPU for good measure.

15

Feature Requests / Re: Tiled Model export to kml/kmz

« on: March 01, 2016, 09:48:36 PM »

nevermind! answered my own question - exporting as an agisoft tiled model (.zip) and changing extension to .kmz seems to do the trick