Messages

1

Bug Reports / Re: error Kernel failed: an illegal memory access was encountered (700) at line 143

« on: April 23, 2024, 09:01:26 PM »

Hello bgodfrey,

In the most cases such error indicates to the GPU driver issues, so I can suggest to make a clean install of the latest NVIDIA driver compatible to your system.

If the issue persists with the new driver installed, please share the log corresponding to the failed operation.

2

Python and Java API / Re: Orthomosaic export after raster calculation formula

« on: April 23, 2024, 02:24:27 PM »

Hello Corensia,

Can you please duplicate the chunk with only orthomosaic, remove the orthophotos from that duplicated chunk, save the project and send the following files from the chunk's folder in project.files directory to support@agisoft.com: chunk.zip, frame.zip and contents of orthomosaic subdirectory.

3

Python and Java API / Re: Metashape model.pickPoint issue in version 2.1

« on: April 23, 2024, 02:18:48 PM »

In the next version update we will improve the performance of pickPoint operation, even if mesh display is not active in the Model view, the used mesh will be cached on the first call, providing that the following assignment is used:

Code: [Select]

model = chunk.model
for i in range(10):
    p = model.pickPoint(camera.center, camera.transform.mulp(sensor.calibration.unproject(Metashape.Vector([i*100,i*100]))))
    print(p)

4

General / Re: PARAMETROS PARA FILTRAR NUVEM DE PONTOS - Ground

« on: April 22, 2024, 06:27:53 PM »

Hello adenilson,

If speaking about parameters for the Ground Points Classification procedure, the optimal set may vary depending on the terrain type.

Please check the following article which describes several most common cases: https://agisoft.freshdesk.com/support/solutions/articles/31000160729-parameters-for-ground-point-classification

5

General / Re: Build and export orthomosaic of imported .obj textured model from Polycam

« on: April 22, 2024, 06:16:14 PM »

Hello Iacopo,

If you import the point cloud to Metashape you should be able to generate the orthomosaic directly using the point cloud as a source option (in Surface field), just do not forget to save the project in PSX format before using Build Orthomosaic command.

In case the geographic/projected system is used for the point cloud registration, you should select that coordinate system in Import Points dialog.

6

General / Re: Build and export orthomosaic of imported .obj textured model from Polycam

« on: April 22, 2024, 03:58:21 PM »

Hello Iacopo,

Do you have a laser scan data in E57 format, for example, coming from the scanner?


I doubt that there is any convenient workaround to generate the orthomosaic based on the textured mesh only. The one that you can try though is to switch the display mode in the Model view to Orthographic, adjust the orientation of the model in space to fit the desired projection plane, switch to full screen mode, adjust zoom and then use Capture View tool to make a high-resolution screenshot.

7

General / Re: Splitting up a multicam rig after the alignment process?

« on: April 22, 2024, 12:26:20 PM »

Hello HaydenMartin,

Would it be possible to share a small example of the project that you have problems with?

8

Other Languages / Re: Insta 360

« on: April 19, 2024, 01:34:30 PM »

Максим, посмотрите ролики на канале Григория Кулько:
https://www.youtube.com/watch?v=qNgLpQq8aJ4
https://www.youtube.com/watch?v=lYLdQ0tpcQg

9

Python and Java API / Re: Model vertex coordinate to camera frame

« on: April 18, 2024, 06:40:06 PM »

Hello SamT,

Can you give some additional details about the task? Do you have cameras with the spherical sensor type and would like to project the coordinates of the mesh vertices on them to get 2D image coordinates?

10

Python and Java API / Re: Metashape model.pickPoint issue in version 2.1

« on: April 18, 2024, 06:38:16 PM »

Hello Fabio,

Can you please share the Console pane output related to the following code execution:

Code: [Select]

for i in range(10):
    p = chunk.model.pickPoint(camera.center, camera.transform.mulp(sensor.calibration.unproject(Metashape.Vector([i*100,i*100]))))
    print(p)
providing that chunk, camera and sensor are properly defined.

Additionally please specify the number of faces in the model.

11

General / Re: Import Video

« on: April 18, 2024, 05:36:56 PM »

Hello luisSeyfer,

Thank you for sharing the sample files.

It seems that the problem is caused by pulseaudio package. For example, described in the following discussion thread: https://gitlab.freedesktop.org/gstreamer/gstreamer/-/issues/1477

For a fix we can suggest to add GST_PLUGIN_FEATURE_RANK=pulsesink:NONE line to metashape.sh script, so that it look as following:

Code: [Select]

#!/bin/sh
appname=`basename "$0" | sed s,\.sh$,,`
dirname=`dirname "$0"`
tmp="${dirname#?}"
if [ "${dirname%$tmp}" != "/" ]; then
dirname=$PWD/$dirname
fi
TCL_LIBRARY=$dirname/python/lib/tcl8.6
TK_LIBRARY=$dirname/python/lib/tk8.6
export TCL_LIBRARY
export TK_LIBRARY
LD_LIBRARY_PATH=$dirname/lib:$dirname/python/lib:$LD_LIBRARY_PATH
export LD_LIBRARY_PATH
GST_PLUGIN_FEATURE_RANK=pulsesink:NONE
export GST_PLUGIN_FEATURE_RANK
"$dirname/$appname" "$@"
It should fix the video import issue. Some warning messages could appear in the Console pane during the video import process, but you can ignore them.

12

General / Re: DEM Fill Tool

« on: April 17, 2024, 03:46:30 PM »

Hello Dave,

We are currently working on fixes in DEM editing tools behavior and few are to come in the next version update, however, we were not able yet to reproduce the fill issue, when by default you get the value larger than max DEM value.

If you are working in Metashape Pro 2.1.1, maybe then you can share a sample project, where this issue can be reproduced: PSX project file that includes camera alignment results, DEM and drawn shapes.

13

General / Re: Large error for the estimated yaw/pitch/roll

« on: April 17, 2024, 12:09:59 PM »

Hello Jacky,

In case you are using different convention for XYZ axis orientation, I think you should expect that camera orientation angles estimated in Metashape would not correspond to your expectations in this case.

But if you use Z-up, Y-north, X-east orientation, then you need also to check, the rotation order and direction convention defined in Metashape for yaw, pitch, roll angles, see pages 97-98 of Metashape Pro manual:
https://www.agisoft.com/pdf/metashape-pro_2_1_en.pdf
You may need to input some offset values to Camera Calibration -> GPS/IMU Offset tab for the camera orientation angles to fit the expected convention. For example, if in your case pitch=0 means that camera is looking straight forward, you need to use 90 degree offset, as pitch=0, roll=0 in Metashape means that camera is looking vertically down.

14

General / Re: Splitting up a multicam rig after the alignment process?

« on: April 17, 2024, 12:00:48 PM »

Hello HaydenMartin,

Do you actually need to "split" master+slave systems into independent calibration groups, or whether you require any modification to Gaussian splatting script so that it could work with multi-camera systems?

15

General / Re: Model Texture oddities

« on: April 16, 2024, 06:19:33 PM »

Hello Robert,

It could happen, if the solar panel images are taken with big oblique angle, while the model of the corresponding panel are incomplete, so texture contains artifacts because the image parts are projected to the wrong geometry.

You can try to enable Ghosting Filter option in the Build Texture dialog and check if rebuild texture is better.