Table of Contents | ||
---|---|---|
|
Once you have completed photogrammetry, and have produced an Alembic, ST Map(s), and optional Mask Mesh, you can start run the PROCESS step to create PBR textures.
Select the row and click Queue
to configure the PROCESS step.
This will launch a window form to fill with the required information.
Configure Processing
Select Presets
The Light system has been pre-filled from when the job was created. It can be overwritten if the measurements were wrong, however if the new replaced with a different preset if necessary.
Note |
---|
If the selected light system has a different number of lights to the initial configuration, Marso may not work correctly. |
The Exposure Preset defines how your raw files should be processed. These can be created from a single Calibration Image captured with the same setup as you took the scan. See Calibration for more information.
Provide Geometry
Select Shader Workflow
Texture Export Options
Save
to save changesSave Configuration
READY
, meaning it is able to be queued. There should also be no missing fields, coloured red, remaining.Click Start
to begin processing the asset.
This will return you to the main Marso window, where the selected job is now in the run queue. You should see the configuration you entered in the Details panel.
Run Process
Panel | ||||||||
---|---|---|---|---|---|---|---|---|
| ||||||||
Processing can take upwards of 6 8 hours, depending on the mesh size, source photography, export resolution, and the number of cameras and lights. See Processing Times. |
📦 Results
Upon processing completion, the Results
button will be made available and clicking it will open the directory storing the material textures:
A directory named Textures
, containing folders for each supported render engine (currently just BlenderCycles). PBR textures will be generated for the Diffuse, Roughness, Specular and Normals channels in EXR, PNG, and JPEG formats.
☠️ Interrupting a Job
A running job can be interrupted with either the Stop
/Skip
or Pause
buttons. Both will keep any progress up to the current step. Pause
will return it to the front of the queue, while Skip
will remove it from the queue and start processing the next queued item.