Settings

The Settings window uses the same tabs as Publish View, but the footer buttons differ by context. From the Settings ribbon button, use Save, Import Json, and Export to Json. From Publish View or Batch, the dialog shows Start Export and Cancel instead. The intent is to let you configure exports for batch, save a JSON settings file, or store settings in the Revit project directly.

Output

Action Result Save Saves configuration to ‘Documents/Omniverse/Revit/[model]/settings.json’, or internally in the Revit Project if ‘Enable 1-Click Export’ of Advanced Import Json Imports configuration from a Json file Export Json Exports configuration to a Json file

File

Action	Result
Name	Name of the file to save
Extension	Choose between .usd, .usda, or .usdc
Folder	Press the Select button to specify the destination folder for export

Usd

Action	Result
Material Style	Export with internal, or as an external library
Material Prim + Folder	The name of the Prim under which to write materials, and the name of the folder where texture assets will be saved
File Composition	For external material libraries and family assets, choose between USD Payloads (can be delayed-read on open) and References (will always be loaded)
Units	Specify the unit of the USD stage when exporting. The default is Feet

Note

The function to select Prop or Project when exporting that existed in v.202 has been removed.

The Revit model is exported as a usd file.

Advanced

Action	Result
Enable 1-Click Export	If enabled, settings will be saved internally to the Revit Project and require a Synchronization / Save of the Model to persist. When enabled and Publish View is clicked in the Ribbon, the internal settings will be used and no dialog will be presented before starting the export
Override with Json	Settings in the provided Json file will be used to override settings currently displayed in the dialog

Options

Element Result Include Cameras Include cameras in export Include Links Include linked model geometry in export (linked models are always exported as USD payloads) Include Lights Include lights in export without instancing Include BIM Data Write Building Information Modeling (BIM) data Include Rooms Include rooms in export– Color is specified by selecting a color scheme from the drop-down Include Spaces Include spaces in export– Color is specified by selecting a color scheme from the drop-down Include Drawings Include drawings in export– Select a publish set to include from the drop-down Instance Families Instance repeated family geometry in export—choose Internal Classes or External Assets from the drop-down Coordinate System Options are Internal Origin, Project Base Point, Survey Point, or Shared Coordinates

Note

When using ‘Include drawings’, drawings that meet the following conditions will be exported:

• Plan view created from the model. The drawing must have a position that can be placed in 3D space. Sheets and rendered images are not output as drawings.

• Crop View option must be enabled for each 2D Drawing in Revit. Drawings without a crop region (CropBox) will not be included in the export.

View

Element Result View(s) to Export Check Views from this list to export selected Views Detail Level Detail level to apply to the view(s) on export– can be Fine, Medium, or Coarse Phase Filter Phase Filter to apply to the view(s) on export View Template View template to apply to the view(s) on export

Mappings

Element Result Library Specify the Library from which to take alternative material or geometry, or Add Library to add an existing library on disk or on a Nucleus server Group Group from which to choose alternate files File Choose an MDL from the current group for Materials, or USD for Families Module Further customize which module from within the file, when available Category Only available when in Families mode, this allows the user to filter down by Category. Search Useful for searching for specific items in the Project

Note

When mapping a family, you cannot apply mapping to the nested child families.

You can apply replacement mappings only to the root of a family.

Batch

Element Result Input Folder Folder of Revit files to process Output Folder Destination folder for USD files Folder Depth If greater than zero, recursively look in child folders of the Input Folder for more files to convert View to Find Text to search for in View names for export. For example, using coordination as input would export any view with the text in its name like MEP - coordination or Structural_coordination. Keep in mind that only geometry present in the view will be converted, and if no views can be found containing the input text, no views will be exported from the model.

JSON Settings File

Export settings can be saved to, loaded from, and driven by a JSON file. The JSON structure mirrors the Settings dialog and is used for batch export, automation, and sharing configurations between projects.

Using JSON in the UI

• Export Json (Settings ribbon): saves the current configuration, including material and family mappings, to a JSON file.

• Import Json (Settings or Batch dialog): loads a JSON file into the Settings window.

• Override with Json (Output tab, Advanced): applies settings from a JSON file over the values currently shown in the dialog.

• Per-model settings: when 1-Click Export is disabled, settings are also stored at Documents/Omniverse/Revit/[model]/settings.json.

JSON Structure

The top-level keys match the Settings tabs:

Key	Description
File	Output folder, file name, and USD extension
ViewsToExport	List of 3D view names to export (Publish View)
View	Detail level, phase filter, and view template overrides
Options	Include cameras, lights, links, BIM data, rooms, spaces, drawings, instance families, coordinate system, units, and material options
Mappings	Material and family type library mappings
Batch	Input folder, output folder, folder depth, and view-to-find string
OverrideJsonPath	Path to a JSON override file (when saved in settings)

NOT USED

Put the value NOT USED in any string field that should be ignored during export—for example, detail level, phase filter, view template, or color scheme fields you do not want applied.

String Matching

During batch export, string fields are matched against model data in this order: exact match, then prefix match, then substring match.

The View to Find field (Batch.ViewToFind) searches 3D view names. If multiple views match, each matching view is exported. The default is 3D.

Folder Paths

Use forward slashes / in all folder paths, including local paths and Nucleus URIs.

Folder Depth

Batch.FolderDepth controls how deeply batch export searches beneath the input folder. 0 searches only the input folder; 1 includes one level of subfolders, and so on.

Batch Output Layout

For each Revit file, batch export creates {outputFolder}/{modelTitle}/{viewName}/ and writes a USD file named from the model and view. Filename pattern tokens such as <fileName> from earlier releases are no longer used in 203.0.

Legacy Format

JSON files that use the older standard_export_settings format are automatically migrated when imported.