Material Mapper

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

Rhino Materials

Rhino materials can be exported in both Rhino 6 and Rhino 7. For Physical Materials, Rhino 7 is required. These materials will be converted and saved as part of the project.

Core Library Materials (CSV)

The CSV Mapping File for Rhino 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 MS 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 Rhino 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


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