An Omniverse Project consists of configuration files, source code, and assets which can be used to perform tasks using the Omniverse Platform APIs. With these components, you can develop:
Applications tailored to specific domains and workflows.
Extensions to enhance application capabilities and behaviors.
Services for headless processing of demanding USD workflows.
USD Data Exchanges for data interoperability with third-party applications and OpenUSD.
The process of developing an Omniverse project involves a series of steps. The role of the Developer tends to start with Creating an Omniverse Project and often ends with Packaging a Build. From there, the Package may be published to a storage system which will then provide it to be Deployed or Installed.
Tip
Quick Start : If you’re eager to jump straight into development, our Kit App Template provides an excellent resource to teach and exhibit a hands-on method of creating your own project.
Before development can begin, you must first create a new Project. There are many ways to create an Omniverse Project, and the method you choose depends on what you intend to build and how you prefer to work. Projects tend to align within distinct categories, yet there remains remarkable flexibility within each category to help you address the needs of the user.
After creating a new Project, the development phase begins. In this phase, you configure and use an assortment of tools and extensions to fit the needs of your project.
Depending on the nature of your project, a ‘build step’ may be required as development progresses. Omniverse supports this step with a variety of scripts and tools that generate a representation of the final product, enabling subsequent testing, debugging, and packaging.
Omniverse provides tooling and automation making testing easier and more efficient. Use the system’s built-in methods to generate UNIT TESTS for extensions, run automated INTEGRATION TESTS for your applications, and perform PERFORMANCE TESTS to ensure your project runs as efficiently as possible.
Recognizing the critical role of debugging in development, Omniverse offers tools and automation to streamline and simplify debugging workflows. In combination with third-party tools, Omniverse accelerates bug and anomaly detection, aiming for steady increases in project stability throughout the development process.
At the conclusion of your development and testing phases, packaging your project is often necessary in preparation for publishing. While some extensions may not require this step, it becomes essential for applications and more complex extensions involving advanced features. The packaging process organizes and structures your project assets for delivery and deployment. The specifics of the packaging step depend on your desired method of distribution.
The ultimate goal is to transform your hard work into a product that others can realize value from. The publishing process helps you to achieve this by relocating the Packaged Build to a location suitable for installation or deployment. Omniverse offers a wide array of endpoints including integrated ZIP files, Cloud systems, Streaming systems, Git repositories, customized CMS, and more. Although the functional content of a package can be consistent across platforms, the delivery and installation methods may vary. This section guides you through the process of publishing your project to reach your intended audience.
