Omniverse Renderer Microservice

Description

The Omniverse renderer microservice renders an avatar scene with audio and streams the result with RTP over UDP. The pose of the avatar can be updated frame-by-frame through a gRPC interface.

Usage

The UCS microservice name is ucf.svc.ia-omniverse-renderer-microservice.

The microservice supports various configuration parameters that are defined in the microservice manifest.

Supported Platforms

  • CPU: x86 compatible

  • Linux (e.g. Ubuntu 22.04)

Performance

The Omniverse renderer microservice supports a single stream. The GPU utilization will depend on the actual USD scene being rendered. Please take a look at the performance overview in the Avatar Configurator section if you are using a scene created with the Avatar Configurator.

Minimum Hardware Requirements

  • 24 GB available system RAM

  • 12 core CPU

  • 1 NVIDIA RTX-compatible GPU

  • 8 GB of GPU RAM

  • 5 GB of SSD space

Versions

  • This microservice is based on kit-kernel version 105.1.2+release.135279.09b309e7.tc.linux-x86_64.release.

License

NVIDIA Proprietary License

Deployment requirements

  • RTX-compatible GPU (e.g. RTX 3080, RTX 3090, RTX 6000, A10, A40, etc.)

  • The GPU requirement depend on the scene complexity (meshes, textures, lights, etc.)

  • The Tesla T4 GPU is at the lower performance bound, but it may work for some scenes.

Known Issues / Limitations

  • NVIDIA driver version 545 is currently not supported. We recommend driver version 535.

  • DLSS frame generation has been disabled due to renderer stalls. Thus, this microservice cannot benefit from the DLSS frame generation performance improvements available on Ada GPUs and newer generations. This will be addressed in a future version.