Making Mesh goes to infinit loop

[ostiii]

I´m using Photoscan 1.2.6 (tried 1.2.0 and 1.2.4) and every fourth (or third) time I´m generating a mesh it goes into a infinit loop and I have to wait forever. In the first try it always works perfect.

My machine: i7 latest Generation - 32GB RAM - GTX 980

What did I try: remove RAM - did not work
remove GPU - did not work
reduce RAM - did not work

I´m shooting with 70 cameras with 18MP

When I use 1.0.4 it works perfect

Help me please

[Alexey Pasumansky]

Hello ostiii,

Please specify the processing parameters used in the version 1.2 and provide the Console pane output related to the mesh generation process so that we can see the loop actually.

[ostiii]

We are using 70 cameras (EOS 600D) - JPG - Alignment in middle (just standard) - Dense Cloud in middle (just standard) - Mesh in all the qualities (just standard) - we allways have a tree depth of 11 and it stops between Depth 3 and 10. Nothing more happens then - no error. In the task manager nothing happens - but the system is still alive - I can abort any time.

I´m here in China and try to setup this system - so please help - thanks so much...

[Alexey Pasumansky]

Hello ostiii,

The default parameters in the Workflow dialogues contain the last used parameters, so since we are not sure, whether you have ever changed them, please specify all the parameters used in the Build Mesh dialog and the number of points in the dense point cloud. Full processing log that includes the mesh generation process would be also helpful (you can redirect the console pane output to the text file using corresponding option in the Preferences window.

Additionally please check the memory consumption for the current operation.

[ostiii]

The setup for the mesh is: Arbitrary, Dense Cloud, low(34,368), Interpolation enabled

I cant copy and paste from the system - but I have a screenshot from the loop:

Thanks for your help

[Alexey Pasumansky]

Hello ostiii,

Looks quite strange, according to the log there are almost two minutes between two mesh generation stages.
So far we were not able to reproduce the issue, so maybe you can provide some additional information how we can reproduce it?