The Omniverse Connector for CityEngine provides an uni-directional link to Omniverse Nucleus. On top of the basic export functionality, repeated exports with the same name will accumulate using USD composition techniques. This allows for convenient tweaking of an exported model (e.g. updating a single building in a large city) without having to re-run full exports (which are potentially time-consuming).
The Omniverse Connector is available through a CityEngine model exporter and behaves like the default USD exporter. The only difference is that the USD data is sent to Nucleus instead of to disk.
The typical steps to send a CityEngine scene to Omniverse are as follows:
/Users/CityEngine/myName/myName_root.usdcfile directly or add it as sub-layer or reference to an existing scene.
To use the update functionality, first use Create or View to activate the “live mode” on the sub-layer or the layer which references the root USD file from CityEngine.
Note: in recent Omniverse Create/View apps there is no per-layer “live mode” anymore. Instead, a prompt will ask for layer reloading.
If the connector detects a prior export (e.g.
/Users/CityEngine/myCity/myCity_root.usdc) on Nucleus with the same name (e.g.
myCity), it will non-destructively layer the new models on top of the existing data and hide the outdated models. The data of each such iteration is placed in corresponding
edit directories, e.g.
Note: to identify updated models between CityEngine and Omniverse, the connector concatenates the CityEngine
Shape Name and
ObjectID with an underscore
_ in between.
In above example, the resulting prim in Omniverse will be called
Nucleus Host: host name of the Nucleus server (default:
Nucleus Path: path on Nucleus server to store the exported USD data (default:
Base Name: used to create a new directory below
<base name>_root.usdc(the default value is derived from the current scene name).
Terrain Layers: control the export of terrain layers based on selection. By default, all selected terrain layers will be exported.
Simplify Terrain Meshes: If enabled, uses the CGA
reduceGeometryoperation to simplify the terrain geometry prior to export. This can take a long time, especially on higher resolution terrains (enabled by default).
Terrain Mesh Resolution: Determines the number of mesh vertices in the U and V directions of each exported terrain layer.
Global Offset: Offset the exported geometry. The
centerbutton will compute an offset so that the combined bounding box will be centered around the origin. This is useful to de-georeference a scene to prevent floating point precision issues in Omniverse. By default, no offset is applied.
Up Vector: Sets the stage up-vector and transforms the CityEngine models accordingly. This is useful to work with AEC content which is typically stored as
z-Up. Default is
Triangulate Meshes: If enabled, converts general polygons into triangles for proper rendering in Omniverse. Enabled by default.
Please also refer to the model export section in the CityEngine Manual.
Read articles from the CityEngine team.→ Go to the blog
Discover recently added capabilities of CityEngine.→ See what's new
Build expertise and connect with the CityEngine community→ Build expertise
Share experiences and learn tricks from the CityEngine community.→ Join the conversation