Agisoft PhotoScan 1.3.0 pre-release

[Alexey Pasumansky]

What are the improvements? Because I have projects with an overlap of over 6.
The stage of depth map  generation goes fast, but the actually dense cloud generation takes a long time.

Hello PK_2509,

The performance of the dense cloud generation (second step of Build Dense Cloud stage) should be improved in the version 1.3 for the projects with the excessive overlap. What is the Effective Overlap value from the chunk info for your project?
Have you compared the processing time for this stage between the versions 1.2 and 1.3?

[PK_2509]

Hi Alexey,

I use PhotoScan for my thesis, so I was not sure if Version 1.3 is stable.
Therefore I haven't compared the versions. I will process my Projekt again in Version 1.3.

The Effective Overlap in my Project is 6.45.

Edit: One other thing, my Propertys says i have checked the Adaptive camera model fitting, but i don´t.
The change comes when I optimized my project with markes. I have a precalibration for my cameras and also set they fix at the Camera Calibration section, so is this a bug? (see picture two)

[Alexey Pasumansky]

Hello PK_2509,

If you run the test on 1.3, it would be helpful to save the processing log as well (you can enable it's redirection to the external file in the Preferences).

[Alexey Pasumansky]

Hello Hello PK_2509,

I've tried optimization for the chunk where all the cameras have fixed calibration and the Adaptive camera model fitting flag remain the same, maybe some other steps should be followed to reproduce the issue?

[PK_2509]

Hello Alexey,

at the moment i can't reproduce the issue. I will try to find the Probelm.
Also I will upload the processing log, if the project is reprocessed.

[BenjaminG]

Hi,

I have a problem when running script from command line:
PhotoScan.app.gpu_mask doesn't work (AttributeError: 'PhotoScan.Application' object has no attribute 'gpu_mask')
It works when running from the interface, and the GPU is used in command line just fine (depending on the option set through the interface before running the script)

Thank you so much for the command line and floating license functionality, Regards,

[Alexey Pasumansky]

Hello BenjaminG,

We have slightly updated Python API, but haven't yet updated the reference file.

It should be gpu_mask_opencl now.

[Airgo]

Hello,
what is this "image based shape drawing support" feature?
How does it work?
Thank you
Mathias

[Alexey Pasumansky]

Hello Mathias,

It means that now you can also draw a shapes in Photo view, providing that the corresponding camera is aligned. In the version 1.2 it was only possible to draw shapes in Model and Ortho view.

If you also have "attach markers to the shape vertices" flag on in the Preferences, you'll be able to adjust the projections of each vertex of such shape (like regular markers) to achieve better accuracy of the shape positioning.

[PK_2509]

Hi Alexey,

I think I've found the issue for the adaptive camera model fitting change.
After the alignment one camera was not aligned. So I aligned the single camera afterwards and then adaptive camera model fitting changes to yes.

[Alexey Pasumansky]

Hello PK_2509,

When you run the Align Selected Cameras procedure PhotoScan will refine the interior parameters of camera orientation, unless the Fix Calibration flag is turned on for the calibration group.

[PK_2509]

Hi Alexey,

I turned the Fix Calibration on, so the interior parameters of the camera orientation doesn't change. Only the Info says yes.
There is no issue with my project or something else, I only noticed it.

[Jendri Silalahi]

im using Phantom 4 for collect data and Pix4Dcapture for Flight Plan.
whether using pix4Dcapture on a Phantom 4, photos can be processed data on Agisoft?

[cadm8]

I don't know if this has been proposed, but I think it would be helpful to be able to create multiple point clouds within the same chunk. That would help in cases where you would like to reproduce certain areas of a project in high accuracy while others in lower accuracies (ie ground data)

[mwillis]

Hi Alexey, unrelated to my recent bug post for 1.2.6, I noticed that 1.3.0 appears to have an issue with processing photos at the edge of chunks.  See this image:



In version 1.2.6, there is not a gap between the upper two chunks when the data is processed. In 1.3.0 data is lost at the edges.

Mark