The NVIDIA Omniverse™ Unreal Engine Connector offer a simple toolkit for Unreal users to send and live sync their model data to an Omniverse Nucleus server. This not only gives creators users a first class renderer through Omniverse USD Presenter or Omniverse USD Composer but also the ability to open, edit and sync with any of the Omniverse Connect applications. Now, depending on the use case, creators 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.
The Omniverse Unreal Engine Connector plugins are an excellent way to export scene, geometry, and material content to USD and Omniverse. The MDL (Material Definition Language) plugin’s material export unlocks access to using Unreal Engine’s industry-leading material editor as one of the easiest and quickest ways to author MDL materials. Artists can use Unreal Engine’s terrain and landscape editor, and with one click can export geometry and materials straight to Omniverse, stored as a USD mesh. The plugins also support USD and MDL importing as well as live-editing of meshes, materials, and stages.
The Omniverse Unreal Engine Connector works in the following Windows versions of Unreal Editor:
Currently, there are no versions of this Connector available for Linux.
USD and MDL in Unreal Engine¶
USD assets are used by Omniverse USD Actors, just like a Static Mesh is used by a Static Mesh Actor. MDL assets are at first identified with this Omniverse MDL icon. Once they are imported they are represented by an Unreal Material asset icon.
Folders and USD/MDL assets that are red and have a lock on them identify read-only files that are located on an Omniverse Nucleus mount.
Assets Loading and Caching¶
Assets are not actually loaded and converted from Omniverse until they are used. Once loaded, the converted Unreal assets, such as textures, materials, are cached on disks. And they will be updated when necessary. Note that the Content Browser displays USD and MDL files inside the project’s /Content/Omniverse folder, but those files do not exist on disk. As assets are loaded, intermediate Unreal assets are saved to those locations, but the are purely intermediate and only aid in reload times. Do not create assets within the /Content/Omniverse folder as they could be removed from disk when these folders are cleaned.
A Note about the Epic Games USDImporter Plugin¶
Introduced in 102.1
In version 102.1 of the 4.x Omniverse USD Plugins the USD library was modified with prefixed library names to allow the Epic USD plugins to run together with the Omniverse plugins. Note that some export functionality (File : Export : .usd) may be impacted due to the registration order of UExporter extensions.
Introduced in 201.0
In version 201.0 of the 5.x Omniverse USD Plugins the Epic USDImporter plugins are now required because they are using Epic’s USD libraries.
5.0 - USD 21.08 with Python 3.9
5.1 - USD 22.08 with Python 3.9
- Install the Connector
- Project Settings
- Removing a Server
- Live Sessions
- Cleaning Local Assets
- Opening USD Files
- Saving USD Files
- Running Python Scripts
- Copying Omniverse URLs
- The Omniverse USD Layers Tab
- Importing USD as Unreal Assets
- Exporting to Omniverse (as USD and MDL)
- Export USD and MDL to Local Disk
- Export Commandlet
- Exporting Omniverse PBR Materials
- Supported & Unsupported Features
- Release Notes