Messages

1

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.

2

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.

3

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.

4

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'

5

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?

6

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.

7

Bug Reports / Re: Assertion "3478972301441" failed at line 720

« on: March 22, 2023, 12:43:45 AM »

Hello bassistas,

You have Assertion 23671468921001171 in the log, it is a different one.

Can you confirm, if you are working with the newly created project or using some old one? This assertion could be related to rare cases, when the project has been created with the laser scans added in some 2.0.0 version pre-releases.

I found what was causing the issue. For some reason one of the imported laser scans was without the panoramic image althought the original e57 has the color information and I opened this exact file on cloudcompare to check if everything is alright. I deleted this laser scan and the process now completed sucesfully. Fortunately the missing laser scan wasnt necessary to cover the area but I cant imagine why all other laser scans imported with their panoramic images and not this one.

8

Bug Reports / Re: Assertion "3478972301441" failed at line 720

« on: March 20, 2023, 07:12:29 PM »

Its not resolved, I still get the Assertion failed error in 2.0.2 

Hello bassistas,

Can you share the complete log from 2.0.2 related to the failure? Either post it here or send to support@agisoft.com.

Here is the complete log from 2.0.2 https://drive.google.com/file/d/1KjeacAUi0oZFJiTSe2aEwPsnEr50KQmA/view?usp=share_link
In this project I have 62 laser scans and 927 photos. I managed to align everything but I'm stuck in the build mesh as I always get this error.

9

Bug Reports / Re: Sketchfab upload from version 2 not working

« on: March 19, 2023, 05:46:29 PM »

Hello bassistas,

Do you mean loading to laser scans to Metashape or uploading them to Sketchfab?

Can you share the log related to the operation, including Metashape starting lines?

I mean loading laser scans to Metashape, but I finally resolved the issue. I checked the log and I had to save the project in psx format first for large laser scans.

10

Bug Reports / Re: Assertion "3478972301441" failed at line 720

« on: March 19, 2023, 05:42:03 PM »

Its not resolved, I still get the Assertion failed error in 2.0.2 

11

Bug Reports / Re: Sketchfab upload from version 2 not working

« on: March 15, 2023, 12:30:59 AM »

I am using the 2.0.1.15925 version and when I'm trying to load some laser scans which are with a high density point cloud (1/2 resolution from a Faro focus scanner) I get a "not enough memory" error. I have 128GB ram and free disk space but still does the same every time i try to load the scans. I also tried  from another pc with similar specs and I still get the same exact error. Is this a bug?

12

General / Re: Agisoft Metashape 2.0.0 pre-release

« on: January 15, 2023, 06:38:19 AM »

Hello, I have imported some laser scans using the new option but as some of them don't contain colour and only intensity Metashape doesn't show any image from these (in grayscale) so I can't add any markers to improve the alignment of the photos from the camera.  Is there any solution to this?

13

Bug Reports / metashape 1.8.5. corrupt frame.zip

« on: December 22, 2022, 01:58:00 AM »

Hello!
I'm using metashape 1.8.5 and for some reason, the frame.zip suddenly got corrupted. I didn't have any power loss or blue screen, I just saved the project normally through the save button and I closed the program. When I tried to open it again I got this error message: Can't locate zip directory , Error: Can't open archive:  ....../frame.zip. I tried to open the frame.zip manually but I got an error that says it's corrupted.
Is there any way to recover my project? I have spent hundreds of hours manually placing markers on thousands of photos to be able to have a successful alignment with photos and laser scans and I also had the model ready for export with textures but now I can't access it. Is there a way to recover at least the model? thanks

14

General / Re: Agisoft Metashape 2.0.0 pre-release

« on: October 19, 2022, 06:00:05 PM »

Dear bassistas,
It would be helpful, if you can share the sample data (your E57 file).
If you are able to share the data, please send the download link to support@agisoft.com

Here is a link to a sample e57 file https://drive.google.com/file/d/1KXlUsAUTf8BV-qOzeN3-cm3G11Q7WFNA/view?usp=sharing
Please let me know if you are able to reproduce the problem.

15

General / Re: Agisoft Metashape 2.0.0 pre-release

« on: October 19, 2022, 11:28:28 AM »

Hello bassistas,

Do you use Import Depth Images or Import Point Cloud for E57 files? Also can you share the processing log related to the file import (enable Write Log to File option in the General Preferences tab and try to reproduce the issue)?

I'm using the import point cloud option for the E57 files. Here is my log file, I don't see any errors, it just crashes:

2022-10-18 18:29:52 ImportPointCloud: path = D:/Faro scene projects/arnaia scans 1-10-2022/Faro scene Gerovasiliou/e57 export/gerovasiliou_Gerovasiliou000.e57, format = PointCloudFormatE57, crs = Local Coordinates (m), shift = [0, 0, 0], precision = default, point neighbors = 28, use trajectory (origin)
2022-10-18 18:29:52 Working in temporary directory D:/temp//import_points.tmp.11
2022-10-18 18:29:52 Importing point cloud in memory. Save project in .psx format for big file import.
2022-10-18 18:29:52 Importing point cloud...
2022-10-18 18:29:53 Analyzing points...
2022-10-18 18:29:53 processing 68983239 points...
2022-10-18 18:30:45 Calculating normals...
2022-10-18 18:30:45 Required 25.9399 GB RAM for extended block
2022-10-18 18:30:45 Available: 80.6923 GB
2022-10-18 18:30:45 Using extended block
2022-10-18 18:30:45 Using 32 threads
2022-10-18 18:30:45 Expected max memory usage: 25.9399 GB
2022-10-18 18:31:17 computed normals in 32.536 sec

I just tried to export the laser scans in another format (pts) and now they are loading without any errors but it takes a lot of time to load as the files are double the size now.
So maybe there is a bug with the e57 format.
Now I'm stuck on the "reset current alignment" option which is not active (greyed out) and if I proceed with the alignment it doesn't align the photos with the scans.