Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Version History

« Previous Version 9 Next »

When using Marso, photogrammetry must only be done with images generated from Marso, rather than using the RAW images, or your own JPEGs/EXRs.

These are generated using the DEVELOP step.

Photogrammetry Images

17_queue_new_job.png

[SCREENSHOT]

The DEVELOP step can be configured. If the preview image looks too dark the brightness can be adjusted.

[SCREENSHOT]

You can also use EXRs instead of JPGs if you prefer, and optionally customize the directory where the photogrammetry images will be written

[SCREENSHOT]

Click ‘Queue’ once you are happy with the configuration

18_new_job_queued.png
19_preparing_job_row.png

[SCREENSHOT]

Once the DEVELOP step is complete, click ‘Images’ to open explorer at the folder containing the images that should be used for photogrammetry.

Photogrammetry Checklist

You are free to follow your normal process for obtaining a photogrammetry solve, as long as the photogrammetry images are used. You can modify the contents of these images as long as they are not renamed or re-ordered.

See below for specific tips for the photogrammetry solution you use:

Camera solve

As well as solving the mesh of the subject, it is important to also get a good solve of the positions of the cameras.

Poorly solved cameras can lead to artifacts in the material measurement later on. We recommend attempting to re-align any bad camera solves or removing those cameras from the 3D solve all together.

Subject Mesh

Poly-Count

A high number of polygons in the mesh may cause Marso to exceed the available VRAM on your system. If this occurs, simplify the mesh and reattempt the process. Marso can produce highly detailed normals, even on medium to low poly meshes. See Examples

Bounding Box

When drawing a bounding box around your subject for mesh reconstruction, it is important to also include any stands or supports. This additional geometry will ensure that pixels are correctly traced onto this geometry and not onto the subject itself.

Using one of the lower cameras (as shown below) can be a helpful reference to see how much geometry is required to avoid unwanted pixels being projected onto the subject.

Bounding_Box_Good0013.pngBounding_Box_Good_POV0013.png
Bounding_Box_Bad0013.pngBounding_Box_Bad_POV0013.png

 

 

Using a Mask Mesh will allow you to reconstruct just the subject, whilst avoiding occlusion issues by providing a Subject Mesh & Mask Mesh

RB.png

UV Unwrap

For Marso to work the subject mesh must be exported with a UV unwrap. By default, a 3D mesh within a photogrammetry application will not have a UV, so you must either run the texturing process within the application, or do a Manual UV Unwrap.

For optimal UVs we recommend generating the texture at the same resolution or lower resolution than what you wish to output from Marso.

Example: A RealityCapture texture of 1024px can be used to create a Marso texture of 1024 -> 8192px , but Marso may create artifacts at 512px.

Scale

It is essential that the 3D scene is correctly scaled, we suggest using markers to automatically set the scale of a scene within your photogrammetry software.

You can also Re-Scale with Blender

Export

The mesh should be exported as an Alembic (.abc) file, with cameras and normals enabled.

ST Maps 

Export the ST Map(s) as exr so that Marso can account for any lens distortion.

  • No labels