Accessing the Course Assets#
Before we begin building our digital twin, we need to set up the application and workspace that we’ll use throughout this course. We’ll be working with a customized Kit App Template that has been pre-configured with the necessary extensions and settings to ensure a consistent learning experience.
Download the Course Assets#
You can follow this course using your own factory assets or the provided files. The concepts and workflows apply to any USD project, but this course was written for the provided files.
Tip
We recommend using the provided assets for your first time through the course.
To download:
Navigate to Asset Download Link
Warning
This download file is over 700mb. It contains all of the USD assets of the machines and the factory.
Course Application Options#
You have two options for following along with this course. We’ll be using Visual Studio Code in this course.
Option 1: Use the Provided Pre-configured Application (Recommended)#
We’ve prepared a Kit App Template specifically for this course that includes all necessary extensions and workspace settings. This ensures you’ll have the same experience as demonstrated in the course materials.
Warning
The repo.sh script included in the package has known errors when run on Linux. If you’re using Linux, you will need to clone the Kit App Template repository directly and set it up manually.
Option 2: Use Your Own Kit Installation#
If you prefer to use your existing Omniverse or Kit setup, you can follow along, but you’ll need to manually configure the settings outlined below to match the course environment.
Downloading the PhysicalAI_SceneAssembly_KAT.zip#
If you choose to use the provided pre-configured application:
Navigate to the Download Link
Extract the files to your desired working directory
Make note of the extraction location as you’ll need this path for building and launching
Note
The provided application is the standard Kit App Template with a few key extensions enabled and workspace preferences configured for this course.
Pre-configured Settings (For Reference)#
Extensions#
View the available extensions from the top toolbar under Developer > Extensions.
Extensions to Enable:#
Asset Validator (Core) version 0.16.2 - Essential for validating USD assets and ensuring quality standards throughout our workflow.
NVIDIA Assets Extensions (omni.assets.plugins) - Enables the NVIDIA Assets tab accessible through the top Toolbar.
Note
To Enable the NVIDIA Assets tab:
Navigate to Windows > Browsers > Assets.
This provides access to NVIDIA’s curated asset library that we’ll use later in the course.
Workspace Preferences#
The following preferences have been set to standardize our working environment:
Up Axis: Z-Up - Ensures consistent orientation across all assets and scenes.
Meters Per Unit: 0.001 - This standardizes our stage to work in millimeters, matching the scale of the provided machine assets.
Default Reference Behavior - When dragging assets into the stage, the application defaults to creating references rather than payloads, giving us access to all prims within referenced files.
Why These Settings Matter#
Z-Up Axis: Manufacturing and CAD assets typically use Z-up orientation, so this setting ensures proper alignment when working with industrial assets.
Milimeter Units: The machine assets provided in this course were authored in millimeters. By setting our stage to millimeters (0.001 meters per unit), we ensure proper scaling and avoid unit conversion issues.
Reference Defaults: Using references instead of payloads allows us to immediately access and work with all components within our machine assets, which is essential for the assembly workflows we’ll be learning.
Setting Up Your Own Installation#
If you choose to use your existing Kit installation, you’ll need to manually configure these settings:
Install the Asset Validator (Core) extension version 0.16.2
Set your stage preferences to Z-Up axis
Configure meters per unit to 0.001 (millimeters)
Change the default behavior to create references when dragging assets
Note
We’ll walk through how to verify and adjust these settings as needed during the course, so don’t worry if you’re not familiar with these configurations yet.
With your application downloaded and ready, we’ll move on to the next module where we’ll build and launch the Kit App Template, open our first project, and begin exploring the course assets.
Launching USD Composer#
In this module, we will use the Kit App Template to set up and launch the Kit application that we will use throughout this course.
Open the Project Folder in Visual Studio Code#
Open Visual Studio Code.
From the top menu bar, select File > Open Folder.
Navigate to the location you downloaded the application to.
Select the folder, then choose Select Folder to open it.
Tip
Keeping your project folder open makes it easy to access scripts, configuration files, and any code snippets used in later modules.
Build and Launch the Application#
Next, we need to build and run the Kit App Template:
Open a new terminal window in Visual Studio Code.
Run the following command to build the application:
Windows:
.\repo.bat build
Linux:
./repo.sh build
This compiles all files and gets the Kit App Template ready to launch. If this is your first time building, it may take some time to collect all the needed dependencies to install.
Once the build process is complete, run:
Windows:
.\repo.bat launch
Linux:
./repo.sh launch
This starts the custom Kit application.
Add Your Project Folder to Bookmarks#
To make navigation easier as we work:
In the running Kit App, locate your project folder in the left navigation panel.
Right-click the project folder and select Add Bookmark.
Note
Your folder structure and asset names may differ from the screenshots shown throughout this course. You should work with your own project assets and folder organization.
Confirm that the folder is now listed in your Bookmarks for quick access.
By completing these steps, we ensure our working environment is consistent and ready. From here, we can confidently move on to exploring and organizing our digital assets, knowing that all tools are properly set up.