Agisoft Metashape 1.8.0 pre-release

[Mak11]

Version 1.8.0 (build 13597) mesh better results than 1.7.4 on this model:

Yes it's a total crap-shoot. Some are better and others are worst.  I can't find any logic as to why it's acting like that.

Mak

[bisenberger]

I ran Batch Process - Build Mesh on 2 chunks. On one of the chunks it created mesh outside the bounding box.

[Alexey Pasumansky]

Hello Bill,

I cannot reproduce the problem on our side, can you please send this chunk as PSZ project to support@agisoft.com?

[bisenberger]

Hello Bill,

I cannot reproduce the problem on our side, can you please send this chunk as PSZ project to support@agisoft.com?

I just zipped up the whole project and emailed a link since it was so small. Let me know if you have problems downloading.

[Alexey Pasumansky]

Hello Bill,

Thank you for sending the project, it helped to find the bug in Batch Process, it will be fixed in the next version update.

[bgreenstone]

I don't know if this is the same issue as the Batch bug reported above, but I have noticed that if I am processing multiple Chunks in a single Batch, the first Chuck works fine, but the meshes on the remaining Chunks tend to be malformed.  For example, attached are two screenshots of Chunk #2.  The first shows the malformed mesh that was created during the Batch.  However, if I simply build the Mesh again manually I get the correct results as shown in the 2nd screenshot.

In this particular instance I had 4 chunks in the Batch.  The first was fine, but the other 3 were completely malformed.

[bgreenstone]

Also, I get error messages and failures on some Chunks during a batch.  In that last example, the 4th Chunk will always fail to generate a mesh when using Batch.  I get "Error: Operation not applicable" and "Error: Null model" towards the end of the batch on that.  But as always, just doing it by hand works perfectly fine.  It only fails during a Batch.

[wojtek]

Also, I get error messages and failures on some Chunks during a batch.  In that last example, the 4th Chunk will always fail to generate a mesh when using Batch.  I get "Error: Operation not applicable" and "Error: Null model" towards the end of the batch on that.  But as always, just doing it by hand works perfectly fine.  It only fails during a Batch.

Been getting the same, first model is good but the latter ones are partially or completely empty. This seems to do only with the Mesh Generation step as the depth maps produced are fine.

[Alexey Pasumansky]

Hello,

Can you please check, if the issue with the Batch Process mesh generation is resolved in the latest pre-release build (13706)?

[wojtek]

Hello,

Can you please check, if the issue with the Batch Process mesh generation is resolved in the latest pre-release build (13706)?

Don't know about Batch mode yet but this build did fix a crash I had with Depth Map generation step. 

[bgreenstone]

Last night I did a test with 3 chunks in a batch and it seemed to work properly.  I’ll try more today to confirm.

[Mak11]

The Changelog hasn't been updated for the latest build ?

Mak

[bgreenstone]

Just did another small Batch test on a 2 Chunks and it seems to have worked correctly.  The only annoying issue I'm still seeing is that if I leave the room my Mac will go to sleep after 15 minutes and this cause the Batch to pause.  Metashape should be calling UpdateSystemActivity(OverallAct); every few seconds to prevent the Mac from going to sleep while it's working.  Otherwise, I have to keep moving the mouse to prevent the Mac from dozing off and pausing Metashape.

[bisenberger]

So far the batch is working for me.
 More testing later. 

[bgreenstone]

Ok, something I've never seen happen before just happened.  I was creating a new Chunk from 64 JPEG files that I shot with my iPhone 13.  For some reason it decided that these photos were multilayer files (I didn't think JPEGs could be multilayer), so it bought up a dialog box asking if I wanted to add 128 cameras to one chunk or create 64 chunks with 2 cameras each.  Bizarre.

When I loaded them in each JPEG showed as the normal color photo along with a black and white version of it.  I have no idea what that black and white version is.

So, then I ran 1.7.3 to see if the same thing happened there and it did not.  It just loaded the JPEGs normally.

Any ideas?

-Brian