Body Scan workflow with flightlog

Hi,

I’m unclear as to how to use flightlog and is there likely to be any benefit?

170 cross polarised camera rig for body scanning.

When I use a highly detailed mannequin as a reference, the results have 170 cameras aligned with great results, with a first pass using no markers.

Some subjects have single tone and low detail compared to this mannequin.
In this instance I may only achieve 150 cameras that have alignment with a first pass.
A second pass, using markers, may bring this up to 160 aligned cameras.

Will flight log help with subjects that are single tone and low detail by using a using the mannequin parameters as a reference with flight log?

If so, I am a little lost with the latest software (1.2) compared to the tutorials of V1.
Can you provide a workflow and description on how to do this please as I am not seeing any real benefit:)?

Hi Mark, 

we are working on updating our knowledge base for this workflow using 1.2, but essentially normally what is done rather than using flightlog is to export xmps. If your rig is rock solid then use “exact” and if not use “draft”. Then so long as your images have the same names every time you scan you can just drop the same xmps into the new image folder and then you will have good prior information for each cam, which should not only speed-up the alignment but also give you better results. It can also be worthwhile adding some markers with known positions to your original mannequin scan and add GCPs to them (before alignment), this way you can georeference the scene and when you save the xmps your new scene will be georeferenced so you could precisely place a georeferenced reconstruction region for example which can be pretty useful.