Kit Air Gap Overview

This Kit Air Gap package includes all CORE and SAMPLE extensions normally retrieved from the kit/sdk registry as well as all repo_tools and dependencies needed for building applications with the Kit App Template.

It is meant to be used in conjunction with the Kit Extension Registry package, which contains all the latest extensions available from the kit/default registry for this major version of Kit.

Usage:

1. Download and unpack the Kit Air Gap packages from NGC.

e.g. in c:/temp/kit-sdk and c:/temp/kit-extensions-registry

• Kit Air Gap Packages:

  • Kit Air Gap - Windows
  • Kit Air Gap - Linux

• Kit Extension Registry

2. Navigate to the folder where Kit Air Gap was extracted.

e.g. cd c:/temp/kit-sdk

3. Run new_project.bat/ ./new_project.sh (Follow the instructions and create your new Kit App Template based project somewhere, e.g. c:/temp/my-project)

Note: new_project.bat and other repo commands that use interactive prompts must be run from a native Windows console (cmd.exe or Windows Terminal). Running from WSL, Git Bash, or a non-native terminal emulator will produce errors. Additionally, git must be installed and available in your PATH — its absence will cause an import error during the setup stage.

4. Navigate to your new project folder.

e.g. cd c:/temp/my-project

5. Run repo template new to interactively scaffold a new app or extension from a template.

Windows: repo.bat template new

Linux: ./repo.sh template new

See Extensions and Creating Kit Apps in the Kit Manual for background on the available template types.

6. Before building, you need to point to your local registry. Open repo.toml and add a registry to the [repo_precache_exts] section e.g.:

[repo_precache_exts]
 registries = [
     { name = "my_registry", url = "c:/temp/kit-extensions-registry" },
 ]

Note: Paths in .toml files must use forward slashes (/), even on Windows. See Configuring Kit in the Kit Manual for more on Kit's configuration system.

7. You can now build and launch your application:

Windows: repo.bat build / repo.bat launch

Linux: ./repo.sh build / ./repo.sh launch

8. If you wish to load extensions at runtime from the application (necessary for running repo launch -d), you will need to also configure your application's .kit file to use the local registry:

[settings.exts."omni.kit.registry.nucleus"]
 registries = [
     { name = "kit/airgap", url = "c:/temp/kit-extensions-registry" },
 ]

See Extension Registries in the Kit Manual for more on how the extension registry system works.

Air Gap Content Considerations

Applications based on the USD Composer template include content browser panes (Materials, Environments, Configurator Samples) that fetch assets from NVIDIA's hosted content servers by default. In an air-gap environment these panes will fail to populate and may cause the application to stall at startup.

To resolve this, after building locate the relevant extension config files under _build/<platform>/release/extscache/ and either comment out the remote source URLs or replace them with paths to locally downloaded asset packs. Alternatively, disable the affected content browser extensions in your .kit file.

Downloadable asset packs are available at NVIDIA Omniverse USD Content Samples.

Known Issues

On Linux, some .sh script files may need to be set to executable.

• Use chmod +x <file_path> to set the executable flag for a file.
• Extract the kit-sdk-airgap package using the -K flag to preserve executable flags from the zip file.

These script files may need executable flag set:

./new_project.sh
./python.sh

After creating a new project with new_project.sh, these script files may need executable flag set:

./repo.sh
./tools/packman/python.sh

Get Help

Enterprise Support

Access Omniverse Knowledge Base articles and submit support cases: File a Support Ticket

Omniverse Documentation

Explore detailed guides for deploying and managing NVIDIA Omniverse applications: Documentation Hub

Licensing Portal

Manage your software licenses: NVIDIA Licensing Portal

Community Support

Join the developer and user community to share knowledge, ask questions, and connect with experts:

• NVIDIA Omniverse Dev Community
• NVIDIA Omniverse Discord Server
• NVIDIA Omniverse Forums

Governing Terms

NVIDIA Omniverse is governed by the NVIDIA Agreements | Enterprise Software | NVIDIA Software License Agreement and NVIDIA Agreements | Enterprise Software | Product Specific Terms for AI Products.

By downloading or using NVIDIA Omniverse, you agree to the NVIDIA Omniverse terms.