PTC Creo


The NVIDIA Omniverse™ Creo Connector Plug-In offers a toolkit for PTC Creo Users to send and live sync their model(s) to an Omniverse Nucleus Server. This not only gives Creo access to a first class renderer through Omniverse Apps but also the ability to open, edit and sync with any of the NVIDIA Omniverse™ Connect applications. Now, depending on the use case, Creo users can choose the workflows and pipelines that work best for their needs while maintaining up to date revisions for all downstream consumers of their work.

Install Instructions

Please see Launcher Documentation for Installing Connectors.

User Manual

The Omniverse Creo Connect Plugin brings Creo into the Omniverse Platform through the use of NVIDIA Omniverse™ Connect tools similar to other NVIDIA Omniverse™ Connect applications. With the Plugin installed, Creo should display an Omniverse toolbar.


Clicking this menu will reveal the ribbon panel for Omniverse Interactions.



Send to Omniverse

Sends to Omniverse View using the AEC Project Workflow

Publish project

Exports as a USD scene within a project container.

Export as Prop

Exports scene as a prop (No project container) to be used within a project.

Omniverse Connection

Allows sign in to an Omniverse Server.


Adjust connections and settings of the Creo Omniverse Connector.


Directs users to this page.


Displays version and other useful information regarding the connect_creo_about Omniverse Connector.

Publish Project


Exports the current scene to a selected Location using the AEC Project Workflow.

Export as Prop


Exports scene as a prop (no project container) to be used within a project. This is helpful when exporting items like signs, streetlamps, and other accessories to a scene.

Omniverse Connection

Allows users to log into a specified Omniverse Server



Simple informational dialogue displaying relevant Omniverse Creo Connector version information.



The settings menu allows you to select a preferred View or Create install as your viewer.


You will need to have View or Create installed and selected to use Send to Omniverse.





No View Settings (This setting disables Send to View)

Send to Locally Installed Viewer

Omniverse Viewer Launch Path
‘’Use Current View’’ to automatically use most recently installed View version.

Custom View Location

Allows Selections of View and Create Installs not Found by Automatic

Send to View on Server

Omniverse View Launch Path on a Remote Server

Custom Kit Remote Location

Allows for Selection of a Specified Remote Kit Location

Server IP Address

Allows manual entry of a remote IP Address

Render Size

Render Quality to Use in View when Launching Remotely

Send to Omniverse Project

When using Send to Omniverse, a project style output is created

Send to Omniverse Prop

When using Send to Omniverse, a project style output is created

Material and Asset Location

Location of swap-able content


Commits the Changes and Closes the Window


Closes the Window and Discarding the Changes


When sending your materials to Omniverse View and Create, we replace the low quality textures and shaders associated with Creo and replace them with High Quality Custom Materials inside of Omniverse View. This is done by material mapping and can be controlled via CSV.

CSV and Materials

The CSV Mapping File for Creo can be located in the following directory.


CSV File Structure

A CSV file is a Comma Separated Values table of data whose field’s end is defined by a comma ‘,’.

Using Spreadsheet Tools

These tables are a very common format and can be opened/edited inside of Excel (or other spreadsheet tools) and will have 5 columns in them when viewed.



Expected Value

Column A

Name of the material from the application.
Note: Any commas (,) are replaced with an asterisk (*)

Column B

Indicates if there is a parameter override | NONE: default, no special characteristics | COLOR: the 5th column (Column E) will have the parameter name in the MDL
GENERIC: keyword and last resort match in mapping (looks for the value in Column A
in the string of the material name we get from the application e.g. if Column A is
glass and the material from Creo was Special Glass then it would match)
EXCLUDE: materials found in the application but NOT mapped, user could convert these
to real mappings by setting to NONE and changing the values in Column C/D/E (potentially)

Column C

MDL name (no .MDL)

Column D

Path into the location in the Omniverse database (points to a Mount)

Column E

If necessary, the parameter override in MDL


Blue Paint,COLOR,Paint_Satin,/NVIDIA/AEC/Library/Materials/Miscellaneous,diffuse_tint
Some Material Name,EXCLUDE,WhiteMode,/NVIDIA/AEC/Library/Materials/Styles

code …