Split your chunk into smaller pieces before mesh generation, there are scripts that can do this for you
Scripting is a pro feature that I can't afford for my hobby scans... You did have me excited until I found that out.
I wish I could select cameras after an initial alignment, so I can see the best clusters of photos to move into a new chunk. What bothers me most is I had no issue processing all of this years ago with an older version of Photoscan.. I thought maybe I'd get an improved version re-processing this time around.
Hello bcoyle,
Number of polygons in the target model doesn't matter, as in Arbitrary mode PhotoScan will generate the mesh with the max possible number of faces and then will decimate it to the user-defined number.
So what is the number of points in the dense cloud (and quality used for dense cloud generation), number of images and their resolution?
That's interesting to know that the mesh target wont matter. So when having meshing issues it's better to go back and reduce the point cloud. There's no way to limit the points used in the meshing is there? I'd have to go and re-process again at a different quality level?
# of points in sparse cloud: 33,226
# of points in dense cloud: 463,155,348
quality used for generation: Ultra High, Aggressive filtering
number of images: 316
image resolutions: 5616 x 3744 (shot with Canon 5D mk II) - each image is roughly 100mb .tif
At what point would it help me to double my RAM to 64gig? Or would it help at all? Is there a way to calculate photos + point cloud = memory needs?
thanks