Recent Posts

Pages: [1] 2 3 ... 10
General / Re: Footprints script
« Last post by PROBERT1968 on Today at 10:19:55 PM »


I was experiment because I had some areas that were smeared..

What is the reason for not to set higher tie points than the keypoints ?

Thanks for your checking and answering to most of requests.
The best capability for Metashape in mapping is drawing polyline with snapping on vertices.
Please please please add snapping to Metashape!!!
General / Re: Footprints script
« Last post by JMR on Today at 09:00:25 PM »
it is a nonsense to set higher the tie points limit than the key points limit
Bug Reports / Re: Cylindrical orthomosaic fails
« Last post by JMR on Today at 08:53:15 PM »
Here you are.
Hello Yeshwanth,

Yes, in the version 1.5.5 reset_alignment is only available for Tasks approach. However, the argument would be available in the version 1.6.0 API.

I recommend to use Tasks if you are processing large projects with big number of images, since network_distribute option would allow to reduce the memory consumption.
General / Re: rotate a georeferenced model
« Last post by ioannitiko on Today at 10:27:09 AM »
thank you kostas! that was also very helpfull!
Costa, I thought the same thing so I set my BIOS back to optimized Defaults. And the same thing happened.

Alexey I'll send that over to you when i get a chance.

General / Re: Footprints script
« Last post by PROBERT1968 on October 18, 2019, 10:51:04 PM »
Never mind.

Just had to reset the transform in order to have the footprints show up...
Hi Alexey,

I tried your above code for realigning the unaligned cameras and I am getting the following error.

File "", line 59, in <module>
    chunk.alignCameras(cameras = not_aligned, reset_alignment=False)
TypeError: 'reset_alignment' is an invalid keyword argument for this function

I checked the documentation. There is no argument called reset_alignment=false for alignCameras(). it is only there for the alignment using the tasks approach. But it requires a chunk object as a parameter. So my trial of passing not_aligned to task did not work. Kindly suggest.
Code I used:
if len(not_aligned) > len(aligned) * 0.1:
    task2 = Metashape.Tasks.AlignCameras()
    task2.adaptive_fitting = False
    task2.network_distribute = True
    task2.reset_alignment = False

Face and Body Scanning / Re: Image Dataset of Full Body 88 images for 3D Scan
« Last post by Mak11 on October 18, 2019, 09:46:33 PM »
Yes, detect markers is available in Pro only. But you can try to optimize the alignment even in Standard edition.

I've used that due to the workflow description on the model's page on Sketchfab:

Align -> Detect Markers -> Align 2 times

Set reconstruction region around the subject.

Reconstruction : Normal

Close Holes -> Clean Model

Simplify -> Smooth

And I have removed any trimming radius related tweaks prior to the processing the mesh. Used pre-release of 1.6.0 though.

Yes, missing the detect markers feature doesn't seem to be that big of an issue here.

BTW I'm testing on Build 1.6.0 build 9217.

The fact that the algorithm still insists on creating unwanted polys when there isn't enough depth data is still the most annoying thing ever...I would literately be happy with a simple hole in the mesh (or how it was handled pre-1.5.1) instead  of this mess which is a real pain to clean up afterwards in 3DCoat/Zbrush. 


Pages: [1] 2 3 ... 10