Messages

1

General / Re: how to combine two meshes (ship 3D model)

« on: February 05, 2019, 10:55:45 PM »

NOTE: if you do this in the current version, you need to make sure that in BOTH chunks you join the mesh you wish to be joined in the new chunk is set to "default".

2

General / Re: Agisoft PhotoScan 1.4.0 pre-release

« on: December 25, 2017, 10:00:02 PM »

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.

3

Bug Reports / Re: launch error at line 67

« on: March 21, 2017, 01:02:52 AM »

Alexey,
I now - after runnin many models without issue on Build 3772 - also face this issue. May I test Build 3943?


Running an NVIDIA Tesla M2070-Q on a XEON X5670 (12 cores).

4

Bug Reports / Re: PLY export with texture gives huge and invalid mesh

« on: March 13, 2017, 06:14:03 PM »

Alexey,

any change I make to the mesh and all is fine.
It happens consistently across a set of models a colleague created - I was helping him handle the scaling as he only has a standard edition.

sorry, it is not possible to share this data right now.

5

General / Re: Disabling all estimated marker projections

« on: March 09, 2017, 12:02:13 AM »

Alexey,
this is very useful, many thanks!

6

Bug Reports / PLY export with texture gives huge and invalid mesh

« on: March 08, 2017, 11:58:31 PM »

When I export the same mesh (ca. 1.2 million polygons) as a PLY, once with texture and once without (both with vertex color exported), the with-texture mesh is 54.8 MB and will not load in Rhinoceros ("faile to read binaries properly") and GOMinspect ("a surface with 53 corners was found"). The mesh exported without the texture is only 24.7 MB and loads without issues. 

This is new with version 1.3.0 3772 64bit

7

Bug Reports / Re: Problems reconstructing simple object

« on: June 03, 2016, 09:46:25 AM »

I'd do as the previous poster suggested: use a highly structured background, so that Photoscan has a chance to align the images even if the minifig gives too few tie points. Also, you can place the fig on a small perspex cube or a smooth-sided box of styrofoam or so - makes cutting off the unwanted stuff easier.

Do take a LOT of photos! The worse the desired surface is for feature detection, the more images will you need to get a good model.

8

General / Re: not able to align photo

« on: June 03, 2016, 09:41:03 AM »

sometimes, it helps to simply mark the non-aligned images in the work pane list, right-click and select "align selected cameras".

9

General / Re: imported markers too high - no "filter by marker" option

« on: June 03, 2016, 09:39:57 AM »

in the marker list, mark one or more markers (using SHIFT or CTRL key), then right-click. There you will find "filter photos by marker". The filtered photos will be visible in the Photo Pane, all others will be hidden.

10

General / Re: How to reduce the marker error (pix)

« on: June 03, 2016, 09:36:54 AM »

Do you know exact distances between your markers? I guess you do, as you know their positions and can calculate the distances.
Try making scale bars between them, and update.

11

Feature Requests / Re: Gradual Selection as part of the batch process...

« on: May 25, 2016, 03:12:03 PM »

I could really make use of this option, too! Please?
Having run hundreds of models of similar objects with similar data capture, I found that I always end up with the same parameters for the same variables, so if this option was available in the batch queue I would save a LOT of clicking

12

General / Re: Photoscan rocks my colletion digitizing project!

« on: October 17, 2015, 12:57:38 AM »

might be good idea to put the bones on small supports from underneath then, and leave some space between the bone and the table.

that's pretty much what we try to do! We use Ethafoam which is cut as a tapering pedestal, so that the bone overhangs the support a bit.

Btw, interested in coming to the follow-up conference in 2017: http://www.naturkundemuseum-berlin.de/forschung/tagungen/digitalspecimen-2014/home/?Fsize=0&Lightversion=0

13

General / Re: Photoscan rocks my colletion digitizing project!

« on: October 15, 2015, 01:40:02 AM »

Are the tables filtered out automatically (since they're only recognised in half the images) or do you have to clean them out of the point cloud manually ?

I need to clean them out, but usually that is quick work. There normally is a small gap between the bone and the supporting material. It is just a matter of rotating the dense cloud so that the view looks right at the gap, then lasso the unwanted points and delete them. 

14

General / Re: Photoscan rocks my colletion digitizing project!

« on: October 11, 2015, 09:02:07 PM »

How long does the processing take for one bone in your PC ? Would you say something about its hardware configuration?

It really depends on CPU, GPU, and number of images. Between 4 and 12 hours per bone, on some really nice machines with 8 to 12 cores.

15

General / Re: Anybody use general selection to clean up sparse points?

« on: September 10, 2015, 10:11:34 AM »

I always do so; it is a key step for getting good models with very littel noise.
However, the exact parameters vary, thus I do not need the ability to skipt this (but it would be nice=)