How to Transfer Substance 3D Painter Textures to Omniverse and Octane

Textures created in Substance 3D Painter can be transferred to other applications through two documented workflows: live transfer to Omniverse USD Composer via Painter Connector and Painter Link Extension, or connecting exported maps to an Octane material in Cinema 4D. This guide is based on official documentation from NVIDIA Omniverse Connect and OTOY. Version compatibility is critical for Omniverse Connector, while UVs and mesh maps are key parts of preparation for Octane.

1. Choose your target workflow and check version compatibility

First, decide whether you want textures to update live in Omniverse USD Composer or to render with Octane in Cinema 4D. Both workflows use Painter, but their setup and material connections differ.

According to the Omniverse Connector documentation, version 203.0 is compatible with Substance 3D Painter versions 8.3–9.1. The same documentation states that Connector does not work with Painter 10.0 or later. For Painter 10.x support, it recommends using built-in USD support. So check your Painter version before setting things up, and don’t expect a live connection to work by installing an incompatible Connector.

The major and minor version numbers of Connector and Painter Link Extension must also match. For example, the documentation pairs Connector 204.0 with Link Extension 204.0. Since Painter Link Extension’s live-sync functionality is being deprecated, it should not be treated as an unchanging part of a long-term production pipeline.

2. Set up live transfers to Omniverse USD Composer

1. Install Painter Connector and the USD Composer Painter Link Extension. Connector and the extension are separate components; Connector is available through the NVIDIA NGC Catalog. The extension can be found by searching for “Painter” in the Extension Manager in Omniverse USD Composer 2023.2.0. Enable the extension and check the AUTOLOAD option.

2. Open or create a project in Painter. If the Connector settings panel is not visible, go to Window > Views > Omniverse-Connector. In Connector versions 203.0 and earlier, the panel is in the JavaScript menu; in 204.0 and later, it is in the Python menu.

3. Note the port number shown in USD Composer’s Painter Link window. In Painter Connector, open Edit > Connection Settings… and enter the same number in the Port field. Although the default is 8111, the port may change when multiple USD Composer instances are running or when using USD Presenter/Code. If the values on the two sides do not match, the connection may fail.

4. In Painter, send the mesh to USD Composer via Export > Mesh. Then paint in Painter. With the live connection enabled, changes to painting or texture set properties trigger texture maps to be re-exported and sent to Composer. Optionally, enable Use Environment Map to create Painter’s environment map as a Dome Light in Composer; enable Show as well if you want it to be visible.

5. Monitor the connection status using the indicator at the bottom left of the panel. It reports exports, connection attempts, and errors. When the live connection is enabled but idle, it displays Idle...; when disabled, it displays Live-Link disabled. Since textures may take time to load, also check the status indicator in Painter Link settings.

3. Configure textures and materials correctly

Connector’s export options let you set the preset, shader type, resolution, bit depth, and file format. The documentation gives PNG and TGA as format examples. In Omniverse USD Composer, Connector supports only OmniPBR and USDPreviewSurface shaders. Some channels in a selected preset may not be supported by the current shader type, so check which channels the material needs when choosing a texture preset.

In Texture Set Settings, only channels listed under Channels are transferred to the OmniPBR material. For example, removing the Opacity channel when transparency is not required prevents that parameter from being enabled in the generated material. This approach aims to create a more efficient material definition without transferring unnecessary channels.

If Submit is enabled, the mesh and textures from Painter are copied to the Mesh and Textures folders in Nucleus with each update. When this option is disabled, root-layer edits reference local texture exports on disk. Choose the transfer location and set Export Folder before starting work; textures are written to a _textures subfolder named after the project within that folder.

4. Prepare textures for Cinema 4D and Octane

For the Octane workflow, first prepare the model in Cinema 4D by unwrapping its UVs. OTOY’s documentation notes that mesh parts can be separated to make selection and texture assignment easier; Vertex tags can be used, and Vertex Colors must be enabled during export.

1. Export the model via File > Export > FBX. If needed, enable additional attributes using the gear icon in the export options.

2. In Substance Painter, load the FBX file via File > New Project. The documented starting resolution is 2048; it can be reduced to 1024 for a smoother workflow. The documentation notes that a higher resolution can be selected for the final texture export.

3. In the Texture Set Settings window, select Bake Mesh Maps. Choose the maps you’ll use and click Bake Selected Textures.

4. After creating the material, export the maps via File > Export Textures (CTRL+SHIFT+E). Set the general export parameters and click Export.

5. In Cinema 4D, create an Octane Universal Material via Live Viewer > Materials. Set Diffuse BRDF to Oren Nayar and BSDF to GGX (Energy Conserving). Then connect the maps to the material in Octane Node Editor and apply it to the object.

Alongside Octane Universal Material, OTOY’s documentation also lists Standard Surface Material as a suitable option for external application material support; however, the example setup uses Universal Material. Use the Painter image as a reference for the final lighting: the lights set up in Cinema 4D are what ultimately determine the scene’s appearance.

What changes in architecture and visualization workflows?

For interior, product, or architectural visualization scenes, a live connection can make it easier to see texture changes made in Painter in USD Composer. However, if you use UDIMs, keep in mind that a change to one tile exports all tiles; during intensive painting, this can add processing overhead and waiting time. In the Octane workflow, UV preparation, baking, and texture resolution should be checked before delivery.

Teams should also verify licensing and compatibility against the application versions they use. Omniverse Connector 203.0 is documented as incompatible with Painter 10.0 and later; built-in USD support is recommended for Painter 10.x. In a Connector-based workflow, test shader and channel limitations; in an Octane workflow, check in a test scene that maps are connected to the correct material inputs.

Common mistakes

• Failing to match the major and minor version numbers of Connector and Painter Link Extension.

• Not setting Painter Connector’s port to match the value shown in the USD Composer Painter Link window.

• Assuming Connector 203.0 will work with Painter 10.0 or later.

• Assuming that changing one tile in a UDIM project exports only that tile.

• Skipping the required Vertex Colors option or UV preparation when exporting from Cinema 4D.

• Expecting existing materials and textures to remain unchanged when importing USD. The documentation states that the current solution does not initially preserve USD materials and textures, and the appearance may turn white. It recommends making copies of existing OmniPBR materials before importing to preserve them.