Messages

16

Python and Java API / Re: Metashape.Viepoint not writeable

« on: August 17, 2021, 05:04:54 PM »

Thank you very much! Works perfectly for me! 

The last challenge is to "zoom" in/out so that the model fits the size of the model pane ("mouse wheel function") (fov=0)

Do you have any idea how solve this?   
I'm searching for a way to find out it a point on my mesh is visible in the model pane or not.

Thanks again

17

Python and Java API / Re: Update view and bounding box for each chunk

« on: July 25, 2021, 03:40:35 PM »

Is it possible to change the viewpoints center?

18

Python and Java API / Metashape.Viepoint not writeable

« on: July 25, 2021, 03:36:29 PM »

Hello Alexey!

After rotating and scaling my model I calculate the middle of my model (vector "c") because I want to set the viewpoint there.
But the console tells me it is not writeable:

Metashape.app.model_view.viewpoint.center = c
2021-07-25 14:29:55 AttributeError: attribute 'center' of 'Metashape.Viewpoint' objects is not writable
2021-07-25 14:29:55 Error: attribute 'center' of 'Metashape.Viewpoint' objects is not writable   

Can you please tell me how to change the viewpoint?
Thank you very much!

19

General / Re: Agisoft Metashape 1.7.0 pre-release - Dropbox API

« on: December 27, 2020, 05:07:39 PM »

Hello Alexey!

Is it possible to add the dropbox API zu metashape so we are able to read/write files to dropbox?
Thank you and best wishes for 2021! 

20

General / Re: Agisoft Metashape 1.7.0 pre-release

« on: December 02, 2020, 06:25:21 PM »

Driver update did the job! It works. 

21

General / Re: Agisoft Metashape 1.7.0 pre-release

« on: December 02, 2020, 12:22:50 PM »

Have been able to download the photos from dropbox (had a ticket 6.11. 147228) to verify a depth maps problem with 1.7 I didn't have with 1.6x? (Medium quality if fine, both higher ones lead to holes in the model).

Hello mcstieg,

Pre-release has been just updated, hopefully you will no longer observe those holes in the mesh. At least I haven't observed any problems when re-processing your project in the recent pre-release version.

Hello Alexey,

just sent you an E-Mail this morning. Unfortunately, the holes are still there with the new release - with and without gradual selection and optimization. Medium works. High and ultra look terrible.
Thank you for your work! Hopefully this can be found and fixed. 

22

General / Re: Agisoft Metashape 1.7.0 pre-release

« on: November 24, 2020, 04:31:07 PM »

Hello Alexey!

Have been able to download the photos from dropbox (had a ticket 6.11. 147228) to verify a depth maps problem with 1.7 I didn't have with 1.6x? (Medium quality if fine, both higher ones lead to holes in the model).

Thank you! 

23

Python and Java API / Re: calculating ground sample distance (GSD) or ground sample resolution

« on: November 01, 2020, 03:13:40 PM »

Can someone please help?

24

Bug Reports / Re: Error starting Metashape with USB-docking station

« on: October 31, 2020, 03:38:15 PM »

Hello Alexey!

Lenovo GL72M-7REX with GTX 1050 Ti and Intel HD Graphics 630

Nvidia GeForce Experience 3.20.5.70
GTX Driver 457.09

Win 10 Pro Version 2004 Build 19041.572

The error message is just the Agisoft Crash Reporter telling me that metashape crashed.

25

Bug Reports / Re: Error starting Metashape with USB-docking station

« on: October 30, 2020, 02:29:43 PM »

Nothing? Please help!

26

Bug Reports / Re: v1.6.4 and previous - ground altitude vs capture distance (Reference Settings)

« on: October 02, 2020, 10:09:11 AM »

Hello andyroo,

The idea of "capture distance" is quite simple. If it is not set, the Reference preselection consider the source XYZ coordinates from the Reference pane when checking for the camera neighbors.

When the Capture Distance parameter is used and camera orientation angles are loaded to the Source tab of the Reference pane the preseelction is based on the new 3D points calculated as original 3D point + vector in the direction of the camera view with the length equal to the input Capture Distance value.

So the use of the Capture Distance parameter may be important for aerial surveys captured with highly oblique angle, when the Reference preselection should be used (thousands of images).

P.S. the information in the Manual seems outdated and describes the meaning of the Ground Altitude parameter that is no longer available. We'll try to fix the description soon.

A question about cameras that don't write orientation angles:

Does Metashape benefit from an expected pitch and roll angle?
In my data sets all the cameras have nearly the same pitch and roll angle. only yaw changes.
So if I would manually write expected pitch & roll angles to the set - Does that speed up the process?

Thank you very much! 

27

Bug Reports / Re: Program crashes when trying to open (1.6.4)

« on: October 02, 2020, 09:46:32 AM »

TXPE can you please tell me how to disable Nahimic?

28

Bug Reports / Re: Build model 1.6.3. seems to stop after loading kernels

« on: October 01, 2020, 09:15:37 AM »

I've updated to the latest version and gave it another try.

I deactivated one gpu, the other gpu and activated both and cpu.
None of those tests where positive.  At some point Metashape stopped for hours and did nothing.
It was also not reacting to the cancel button.

Normal setup:
CPU1: Socket E5 2683 V3
CPU2: Socket E5 2683 V3

GPU1: Vega 64 ROG Strix
GPU2: Vega 64 ROG Strix (Crossfire not active)

RAM: 128 GB

Windows 10 64 bit

SSD Free space C: 194 GB (Windows)
SSD Free space E: 199 GB (project)

Both GPUs are activated. CPU is disabled.

Image set:

- this time 1129 fisheye cameras aligned
- alignment: highest, not generic, reference(source), 40000, 0, adaptive camera model fitting
- a lot of overlapping images
- therefore disabled half of the images
- mesh via depth maps: high, interpolation enabled, mild, no vertex colors

I also noticed that it could have to do with the optimization process.
- python script optimizes 10 times for me
-  f, cx, cy, k1, k2, k3, p1, p2
- Do you have any suggestions on which parameters should be activated or disabled?

When estimating camera locations GPU1 is active at about 25% (attachment) even thought bth GPUs are activated.
Most problems occur when calculating depth maps. Metashape just stops after some time. CPU & GPU usage is then 0%.
CPU was running 100%, both GPUs where working.

The same system was able to calculate models with double the images even at ultra quality before.

Thank you!

29

Bug Reports / Error starting Metashape with USB-docking station

« on: September 29, 2020, 08:41:59 PM »

Hello everybody!

Whenever I start Metashape a little console pane opens and immediately disappears.
Then an error message pops up. Metashape doesnt start.

When I disconnect my USB 3.0 - docking station (2 monitors, mic, speakers) Metashape starts correctly.

Do you have any solution for that?

THANK YOU VERY MUCH! 

Edit: The docking station is an "i-tec USB 3.0 Dual docking station" with DisplayLink 

30

Bug Reports / Re: Build model 1.6.3. seems to stop after loading kernels

« on: September 28, 2020, 09:08:10 AM »

OS is Win 10 - 64 bit

I will try to deactivate one or the other one and keep you up to date when its done.