Agisoft PhotoScan 1.4.0 pre-release

[James]

Tab order in the 'Build Orthomosaic' dialog is very mixed up.

ps pro v1.4 64bit build 5532

[James]

The images are almost completely featureless white painted surfaces so the best way to check overlap used to be to visually identify tiny defects in the paint finish and flip to the next image and back quickly multiple times to see if they exist in adjacent images or not.

This is impossible to do now the image disappears, reappears pixelated, and then takes a couple of seconds to load in full each time you switch.

FYI I have found that opening the relevant images into multiple tabs pretty much solves this for me.

[macsurveyr]

When exporting a sparse point cloud as ply, with Point colors selected, the RGB values are all 0

1.4.0 build 5532 macOS

Tom

[Paulo]

Hello,

it seems with latest release, in Model View, the Filter Photos by Point is no longer available (greyed out) in context menu (right click).. see screen shot

[Alexey Pasumansky]

When exporting a sparse point cloud as ply, with Point colors selected, the RGB values are all 0

Hello Tom,

Thank you for reporting.

Seems like all the colors were affected in the latest update, we'll fix it in the next version.

[Alexey Pasumansky]

it seems with latest release, in Model View, the Filter Photos by Point is no longer available (greyed out) in context menu (right click).. see screen shot

Hello Paul,

Thank you for reporting. It would be also fixed in the next update.

[chehroma]

Can you say how i can build mesh faster with new volumetric mask. All process very long? Are there working processor or video card? What performance are you recommend that new change work faster? Very often i have an error with message "Not enough memory".

[Alexey Pasumansky]

Can you say how i can build mesh faster with new volumetric mask. All process very long? Are there working processor or video card? What performance are you recommend that new change work faster? Very often i have an error with message "Not enough memory".

Can you please provide the processing log related to the Build Mesh operation and specify the number of images in the project, their resolution, number of masks applied and system specs (CPU, GPU, RAM, OS version)?

[chehroma]

Can you say how i can build mesh faster with new volumetric mask. All process very long? Are there working processor or video card? What performance are you recommend that new change work faster? Very often i have an error with message "Not enough memory".

Can you please provide the processing log related to the Build Mesh operation and specify the number of images in the project, their resolution, number of masks applied and system specs (CPU, GPU, RAM, OS version)?

I have 160 photo(3280*2464), 7 masks, mesh build with very high parameter and it still build more than 15 hours. RAM at maximum. Video card GTX 750. Windows server 2012. Screen shots added.

[chehroma]

And one more when i use chunk.BuildPoints() there are no effect. No any point....

[Alexey Pasumansky]

it seems with latest release, in Model View, the Filter Photos by Point is no longer available (greyed out) in context menu (right click).. see screen shot

When exporting a sparse point cloud as ply, with Point colors selected, the RGB values are all 0

Tab order in the 'Build Orthomosaic' dialog is very mixed up.

Should be fixed in the version 1.4.0 build 5585.

[Alexey Pasumansky]

And one more when i use chunk.BuildPoints() there are no effect. No any point....

buildPoints() function assumes that you have imported exterior and interior orientation parameters for the cameras and have used matchPhotos() operation as well.

[Alexey Pasumansky]

I have 160 photo(3280*2464), 7 masks, mesh build with very high parameter and it still build more than 15 hours. RAM at maximum. Video card GTX 750. Windows server 2012. Screen shots added.

More masks means that the process will be longer and higher memory will be required. Have you tried running the process without strict masks and see how long does it takes and what was the memory consumption peak?

[Heinrich]

Alexey,
it seems a lot of people have issues with the 1.3.0 dense cloud process. Many of us (I think) do not run drone images. Thus, why not make the dense cloud dialog window a parameter for "depth_filtering_limit"?

This way, those affected by a low value could keep it low, those (like me) fine with a low value of 50 or 80 could enter it right there. And the eternal bitching about slow dense cloud building would cease.

[chehroma]

And one more when i use chunk.BuildPoints() there are no effect. No any point....

buildPoints() function assumes that you have imported exterior and interior orientation parameters for the cameras and have used matchPhotos() operation as well.

I know, in version 1.3.4 all work good. But here there are no any point after buildPoints(). Its may code which work in version 1.3.4.

Code: [Select]

chunk.importCameras(locationpath, format=PhotoScan.CamerasFormatXML)
chunk.matchPhotos(accuracy=PhotoScan.HighAccuracy,  generic_preselection=True, filter_mask=True, keypoint_limit=100000, tiepoint_limit=4000)
chunk.buildPoints()