Known Issues

Synchronization with Omniverse

  • The ParaView Connector only exports data out of ParaView to Omniverse, but by design does not allow for data to be imported into ParaView.

  • An Omniverse Connector render view within ParaView does not offer a choice whether to output to Omniverse or not, it will always do so.

    • Use a separate view in ParaView to have a view which does not propagate to Omniverse, or multiple separate views to output different parts of the scene to different locations.

  • For live behavior on timesampled data, it is recommended to generate all timesamples before enabling live mode.


  • Create only animates time series data with (approximately) whole-numbered timestep values.

    • Use the Usd Time Scale field in the Omniverse Connector section of the viewport Properties panel to apply a scale to the timesteps of all pipeline nodes, or…

    • …use a Temporal Shift Scale filter in ParaView to make sure that the timestep values being output are close to whole numbers (doesn’t have to be exact).


  • ParaView’s 3D Glyphs representation:

    • Only supports the shapes sphere, box, cylinder, cone and arrow.

    • Any center, orientation or resolution parameters in ParaView’s left-hand side Properties panel for the selected shape are ignored.

      • For center and orientation, merge with a relevant array selection instead.


  • Colormapped curves and cylinders, or any shape from the glyph representation are not showing up with properly mapped colors in Omniverse USD Composer.

    • This is a known bug in Omniverse USD Composer; create meshes instead, for example by using the Tube filter to create meshed lines, or by using a Glyph filter instead of the representation.

  • Connecting arbitrary primvars to the material inputs (see Working With Material Graphs) in a material graph within Omniverse USD Composer currently only works properly with mesh geometries.


  • Only structured volumes make it through the connector, which are converted to VDB before transfer into Omniverse.

    • Use the Resample To Image filter to transform volumes into structured volumes so that they can be converted.

Misc Features

  • ParaView light kit information is not transferred to Omniverse, instead a single distant light is put into the scene by default.

  • Raytracing cannot be enabled within the Omniverse Connector render view (use a separate view instead).

  • Custom names for ParaView pipeline nodes will not be picked up by the ParaView Connector. The custom names do not propagate to server-side data in any form, so only the automatically generated names will be used.

    • This also prevents ParaView node renaming.

Version Specific

  • Live synchronization with Omniverse USD Composer 2022.2.0 or higher is not possible with connector versions lower than 200.0.0.

  • In ParaView 5.10, the Pass Arrays and Temporal Arrays filters do not work on meshes of type vtkPartitionedDataSetCollection.

    • Use a “Merge Blocks” filter on the data before applying any of the two filters.

  • In ParaView 5.10, colormapped slice geometry can result in corrupted colors in Omniverse USD Composer, in case the number of vertices and triangles stays the same over timesteps, but their topology changes.