Messages

1

General / Re: Agisoft Metashape 2.1.0 pre-release

« on: March 19, 2024, 12:45:37 AM »

Hello bassistas,

Can you provide more detailed description of the steps followed starting from model generation (also specify the coordinate system of the chunk, model and CS options in export/import dialog)? I was not able to reproduce any problem with export-import workflow for FBX model in the latest pre-release version.

The issue still exists in the latest stable release 2.1.0. The project contains photos from a DJI drone and laser scans imported as e57 files. The coordinate system is WGS 84, it doesn't matter which options I choose during the export or what file format, the exported model always comes up shifted by a few meters from the original position. I can send you an example project  (without the photos and laser scans) to investigate if you want.

Sounds like your problem is because you are using WGS84 as coordinate space, why not use a real coordinate space with accuracy and measurements, not something in degrees.

I don't care about the coordinate space as I don't georeference my model, I use the laser scans as reference which are in local coordinates and I just need to export the 3d model in local coordinates also. That is the workflow I always follow but now with the latest version of Metashape when I export the model it doesn't hold its original position and I cant re-import back to re-texture it after the cleanup in another program.

I just tested the previous 2.0.0 version and the bug does not exist there. I can export/import the model and it stays in the same position as it should

2

General / Re: Agisoft Metashape 2.1.0 pre-release

« on: March 16, 2024, 08:26:33 AM »

Hello bassistas,

Can you provide more detailed description of the steps followed starting from model generation (also specify the coordinate system of the chunk, model and CS options in export/import dialog)? I was not able to reproduce any problem with export-import workflow for FBX model in the latest pre-release version.

The issue still exists in the latest stable release 2.1.0. The project contains photos from a DJI drone and laser scans imported as e57 files. The coordinate system is WGS 84, it doesn't matter which options I choose during the export or what file format, the exported model always comes up shifted by a few meters from the original position. I can send you an example project  (without the photos and laser scans) to investigate if you want.

3

General / Re: Agisoft Metashape 2.1.0 pre-release

« on: November 23, 2023, 06:52:27 AM »

With this release, if I export the model and import it back it comes up in a different position, so its impossible to do any editing on the mesh on another program and then re-import it back for re-texturing. It seems that during the export the model is shifted by a few meters.
Also sometimes the model rotates by itself inside metashape if I decimate it through the decimate model command.

Can you please check, if the issue is resolved in the newly released 2.1.0 update (build 17343)?

Hello, I just tried this build, the issue still exists when I export an FBX file but when I  export an obj file and then import it back again it comes in the same position. So it is partially solved, at least for the obj format and I can continue working with my projects now, thank you!

4

General / Re: Decimated Model not aligned to original

« on: November 18, 2023, 04:26:33 AM »

I produced a model after aligning multiple laser scans to supliment the photogrammetry. I selected the resulting model (with an [R] alignment designation) and decimated it to create a 2nd smaller model. The resulting decimated model is tilted at an angle and not aligned to any other model or point cloud in the project (even in other chunks). This of course makes it impossible to build new textures from the images.

Metashape Professional v. 2.1.0 build 17262 (64 bit)
Windows 10 Pro v. 22H2 OS Build 19045.3693

It happens to me also, using the same version (2.1.0 17262), not always but in most cases 8 out of 10 times. There is a similar bug in this version, sometimes when you export the model it is moved by a few meters from its original position and when you import it back it's impossible to re-texture.
I hope they can fix this soon in the next update as I'm stuck with this version now, I'm unable to open my saved projects with an older version of metashape and continue my work.

5

General / Re: Agisoft Metashape 2.1.0 pre-release

« on: November 15, 2023, 09:08:19 AM »

With this release, if I export the model and import it back it comes up in a different position, so its impossible to do any editing on the mesh on another program and then re-import it back for re-texturing. It seems that during the export the model is shifted by a few meters.
Also sometimes the model rotates by itself inside metashape if I decimate it through the decimate model command.

6

Bug Reports / Re: Texture artifacts after mesh decimation

« on: November 15, 2023, 02:20:29 AM »

Hello MAVtrix,

Can you send the archive with the original and decimated models (for example, in OBJ formats) to support@agisoft.com? It would be easier for us to check the problem, as we weren't able to reproduce the issue on some similar projects.
Additionally please include the PDF report exported from the complete project.

This issue with the texture artifacts still exists in the latest 2.1.0 pre-release version. Are there any plans to fix this or do you have any workaround to avoid having them on my model?

Also at the moment, there is no way to have a smooth texture for indoors when using a flash.  If I choose Mosaic each photo blends nicely in terms of exposure but the texture is not smooth (in some areas is very sharp and high res and in other areas blurry. I understand this is because of the distance and angle I take each photo).  On the other side, If I select average mode, I get a nice smooth texture but with a lot of lines everywhere (check the attached screenshots). On top of these if I have a decimated mesh or if I have re-imported the mesh which I have cleaned and decimated on another program then I get all these triangle artifacts spreaded everywhere in my model and even if I want to fix them manually using, for example, the substance painter then also the UDIM support is still broken in 2.1.0 and substance throws errors when I try to import. It only works when I have a small model/object with just 1 texture.

7

General / Re: Circular bands in texture

« on: November 07, 2023, 03:32:43 AM »

hello

I'm doing some test scans of a room and sometimes I see these circular bands appear in the texture. Just now I repeated the 'build texture' step and the bands seem to be gone (see attachments). Luckily I uploaded the 'banded' model to sketchfab so you can still view it:

bands:
https://sketchfab.com/3d-models/corridor-test-312d91081890457db86e7f00c2e02367

no bands:
https://sketchfab.com/3d-models/corridor-test-2-f2a395148dfb4b8e94ec1143547c55f5

At first I thought it had to do with using images with multiple exposures. This resulted in the banded texture. I then used the manual setting on the camera and took all the images with the same settings, then the bands were gone. But as said, I just ran the build texture step again on the images with multiple different exposures (I used a single aperture and automatic exposure time) but now the circles are also gone..

So I was wondering if this could be a bug, or did I forget to change some setting? I used the 'mosaic' setting in the texture dialog in both cases as far as I know.....

thnx!

I have the same problem when I choose Mosaic, in average mode I don't get these lines but I also get other types of lines (check the attachment), which are the edges of each photo due to different exposed areas when I use on-camera flash. I noticed that this bug isn't present in the 1.8.5 version. They seem to appear only on newer versions of metashape.

8

General / Re: Metashape 2.0 Laser Scan Referencing

« on: November 03, 2023, 10:15:19 PM »

I'm hoping to revive this thread, as I attempted to use the script but didn't do so successfully. It's also a topic that multiple folks are attempting to tackle (https://www.agisoft.com/forum/index.php?topic=15939.msg68793#msg68793).

I ran the script with a slightly different workflow and didn't get anticipated results. Is anyone willing to provide some insight into how I might be misusing or misinterpreting the Python code?

• I imported laser scans and independent photos per the workflow documented here:  https://agisoft.freshdesk.com/support/solutions/articles/31000168474-terrestrial-laser-scans-processing-in-metashape-2-0-0#Processing-of-terrestrial-laser-scans-with-images
• I discovered this thread after performing several other time-intensive tasks (point cloud generation, manual classification, meshing trials, etc.). Consequently, I tried duplicating the chunk, re-importing a laser scan in its original position, and applying a transform matrix post-alignment.
• I'll give an example of one of the many trials I ran that correlates with the edited code below. Steps:  1) align laser scans and photos, 2) duplicate the chunk, 3) re-import a laser scan into the duplicate chunk and re-name it so there wasn't a duplicate "camera" name, 4) confirm that the re-imported laser scan loaded in the correct position by reviewing the associated estimated coordinates and rotation values in the Reference Pane, 5) run the script below in reference to the aligned chunk[0] / aligned laser scan and the duplicate chunk[5] / re-imported laser scan.

I won't confuse matters with the myriad of other solutions I attempted - any input is greatly appreciated!

Code: [Select]

# gets chunks to use
non_aligned_chunk = Metashape.app.document.chunks[0]
aligned_chunk = Metashape.app.document.chunks[5]

# function to get camera based on label
def get_camera(chunk,label):
    for camera in chunk.cameras:
        if camera.label == label:
            return camera
    return None

# gets a spherical from a laser scan for both chunks
non_aligned_camera = get_camera(non_aligned_chunk, "Ground-Ext-100")
aligned_camera = get_camera(aligned_chunk, "Ground-Ext-001")

# non aligned camera is in the correct position so we work out chunk transform to equal non aligned camera position
aligned_chunk.transform.matrix = non_aligned_camera.transform * aligned_camera.transform.inv()


What works for me is something very simple, first I mark some of my targets on the laser scans right after I import them in metashape and then I duplicate the chunk to preserve the original orientation of the scans. When the alignment of photos and laser scans from the first chunk is finished I align the first chunk with the second (duplicated) using my previously placed targes (which are now present in both chunks) and using the second chunk as a reference.

9

Feature Requests / Re: Weighted Average Texture Blending Mode

« on: November 02, 2023, 03:31:36 AM »

Actually I might try just masking out the flash area... too simple... doh

Edit: It didn't help greatly, I think the mottled effect is more down to general changes in the lighting, rather than the flash alone.

Have you managed to find a solution to this issue? I'm using the latest 2.1 pre-release now and I still get these lines when I use the average texture mode. If I select mosaic it comes out almost perfect but as I took the photos by free hand in different distances and angles I get some blurry areas with this mode as expected. Only average gives me a smooth texture but I can't get rid of these lines. I tried to mask areas, and readjust photos exposure in Lightroom but its a lot of trial and error until I see some improvement and it's still not good enough.

10

General / Re: Metashape to Substance Painter with UDIMs

« on: July 12, 2023, 06:14:21 PM »

I had this problem and found the solution in editing the obj with udims from metashape in c4D with arnold. (redshift will work as well probably). Then the obj will be imported in Painter correctly.

I'm trying to import an obj which has 65x 8K textures from metashape 2.0.2 to substance painter and I get this error:
''Errors have been found while splitting meshes per UV tile: Mesh 'defaultobject' has faces in out of bounds UDIM indices: [10,5].''

Also I tried to delete all lines with mtl from the obj but still does the same. I can open the obj in 3dsmax or any other viewer without any errors and the model looks fine. I checked also the uv tiles and they seem fine. Can you describe what you did exactly in cinema4d or if there is any tutorial about how to fix udims in C4D with arnold please let me know.

11

Bug Reports / Re: 2.0.2 depth maps bug in high resolution laserscans

« on: June 28, 2023, 01:30:59 AM »

Hello bassistas,

Is it possible to share any small scan example with 1/1 and 1/2 resolution to support@agisoft.com, so that we could check it on our side?

I just sent you the two scans to support@agisoft.com . Please check it and let me know if you can reproduce the problem.

12

Bug Reports / 2.0.2 depth maps bug in high resolution laserscans

« on: June 23, 2023, 07:11:57 AM »

There is a bug in version 2.0.2 , If I import a full-resolution point cloud file from my Faro laser scanner (resolution set on scanner at 1/1) metashape shows the point cloud correctly but not the depth map. If I import a lower resolution scan (such as 1/2 or 1/4) then the depth map shows up in metashape and I can add markers, masks etc without any problem. Also, if I subsample the 1/1 laser scan from Faro scene and export a smaller e57 file then the depth shows up in metashape without any problem.

13

General / Re: Metashape 2.0 Laser Scan Referencing

« on: April 11, 2023, 07:16:59 AM »

I figured out how to fix this. I had to compute the chunk transform that would ensure that the laser scans are in the correct position. To do this prior to alignment I duplicated the chunk, and then aligned the original chunk. From there I had to use the python console.

Code: [Select]

# gets chunks to use
non_aligned_chunk = Metashape.app.document.chunks[1]
aligned_chunk = Metashape.app.document.chunks[0]

# function to get camera based on label
def get_camera(chunk,label):
    for camera in chunk.cameras:
        if camera.label == label:
            return camera
    return None

# gets a spherical from a laser scan for both chunks
non_aligned_camera = get_camera(non_aligned_chunk, "Scan_001")
aligned_camera = get_camera(aligned_chunk, "Scan_001")

# non aligned camera is in the correct position so we work out chunk transform to equal non aligned camera position
aligned_chunk.transform.matrix = non_aligned_camera.transform * aligned_camera.transform.inv()


Can you please give me some more details on how you managed to do this? I duplicated the chunk, I aligned them using markers and then I tried to run your script but I get this error: 'NoneType' object has no attribut 'transform'

14

General / Re: Agisoft Metashape 2.0.0 pre-release

« on: April 10, 2023, 02:22:57 AM »

From reading this and the knowledge base entry I'm still not clear on exactly what effect this procedure will have on the transforms of the Laser Scans. Will the grouped and fixed laser scans maintain their position relative to each other while the entire group is still allowed to move?

Dear Jed,
Yes, the grouped and fixed laser scans will maintain their position relative to each other while the entire group is still allowed to move.

Can the entire group be locked in to place easily so that it is not allowed to move? That's something we've been asking for ever since laser scan support was introduced, e.g. this comment in the 1.7.0 prerelease thread:

https://www.agisoft.com/forum/index.php?topic=12653.msg56372#msg56372

Dear Jed,
Currently alignment with preserving absolute transform is not supported. However, even after resetting alignment for fixed laser scan group the relative orientations will be preserved and group as a rigid structure will be aligned to photogrammetric tie points.

Hello,
I'm using Metashape 2.0.2 and as I can see there is still no way to preserve the orientation of the group. Sometimes my final model is tilted very much or only by a few degrees, its not predictable. Is there any way to fix the orientation of the grouped scans to prevent this?

15

Bug Reports / orthomosaic generation error (metashape 2.0.2)

« on: March 22, 2023, 04:42:04 AM »

I cant create an orthomosaic on a project I have photos combined with laser scans. I always get this error: can't open file: The device does not recognize the command
If I disable the laser scans and leave only the photos the process starts and creates the orthomosaic successfully without any error.
I'm attaching also the log file.