The format is based on Keep a Changelog.
- Added
repo template modifytooling enabling developers to add Template Layers to existing applications created with 107.3 or newer.
- Updated to
Kit 107.3.0 - Updated packman version to 7.29 to address customer issues with network restrictions Issue #80
- Added tooltip information to the VSCode debug extensions to clarify usage.
- Added tooling checks for path whitespace and OneDrive paths to improve developer experience.
- Updated to
Kit 107.2.0 - Remove hard .git dependency from tooling
- Exclude
_repofrom packaging operations.
- Fixed nondeterministic tool loading behavior raised in Issue #65
- Addressed spelling errors raised in Issue #63
- Addressed default repository definition causing issues with bootstrapping thin packages from Issue #70
- Fixed issues with run time available registries by adding them directly to
.kittemplates - Fixed issues with test time available registries by adding user.toml registry configurations
- Added the ability select of application layers (streaming configurations) individually during templating
- Added a dedicated streaming configuration for NVCF based Omniverse Cloud (OVC) deployments
- Added C++ With Python Extension Template and Documentation
- Added streaming application creation and configuration documentation
- Added Developer Bundle extension by default to Base Editor, Composer, and Explorer templates
- Added an exclusion for Developer Bundle on streaming application layers
- Updated to
Kit 107.0.3- Kit 107.0 Release Notes
- Kit 107.0 Release Highlights
- Updated repo tooling UX to clarify tool use and improve user experience
- Changed previous Omniverse Cloud (OVC) streaming configuration to Omniverse Cloud Streaming (Legacy)
- Updated to
Cad Converter 203.0.0Release - Moved extension
typedeclaration to the extension definition section within the templates.toml file - Removed
omni.usd.fileformat.sbasarandomni.kit.property.sbsarextensions from the USD Composer Template kit file. The extensions will be available at a later date.
- Fixed Windows long path issues during
repo package
- Added
app.environmentname setting for all kit file templates
- Removed
WALK_VISIBLE_PATHfrom USD Explorer Setup Extension
- Updated to
Kit 106.5.0 - Updated Asset browser URLs
- Optimized OVC streaming file kit settings for OVC streaming deployments
- Updated Editor tutorial away from deprecated methods to use action based method for show/hide of menus
- Added
stream_sdk.txtto set timeout for stream SDK and updated container packaging to add it to container images - Added
replayto thetemplate newtooling to allow for replaying app and extension creation to support automation - Added companion tutorial section for using python pip packages
- Updated to
Kit 106.4.0 - Updated the
omni.kit.asset.browserextension URLs to point to current asset libraries when not specified in Kit file - Updated to
Cad Converter 202.0.0Release
- Added missing notification of successful build
BUILD (RELEASE) SUCCEEDEDfor Python only builds for Windows
- Removed the USD Viewer setup samples folder and the light_rigs folders from the USD Composer and USD Explorer setup templates. That data is now accessible from the
omni.usd_viewer.setupandomni.light_rigsextension dependencies.
- Built app containers support
NVDA_KIT_ARGSandNVDA_KIT_NUCLEUSenvironment variablesNVDA_KIT_ARGSis passed directly into the kit executableNVDA_KIT_NUCLEUSif set causes the container entrypoint to create an omniverse.toml configuration file with a single entry pointing at the provided nucleus server. This will also set the kit arg --/ovc/nucleus/server with the envvar value.repo launch --containermaps in these variables from the local environment as well
- Added
omni.kit.menu.commonto Kit Base Editor, USD Composer, and USD Explorer Template Kit files to enable Toggle Viewport Fullscreen and UI overlay with F7 and F11
- Updated to
Kit 106.3.0 - Updated build process to support auto-detection or user-specified host versions of
MSVCandWinSDK, providing flexibility for Windows C++ developers to leverage their existing installations. Windows C++ Developer Configuration - Updated
omni.kit.usd_explorer.main.menubarto version 1.0.38 so that it works correctly withomni.kit.menu.common - Moved Light Rig binary data from kit-app-template repo to
omni.light_rigsextension and added the extension to Kit Base Editor, USD Composer, and USD Explorer Template Kit files - Moved USD Viewer sample assets from kit-app-template repo to
omni.usd_viewer.samplesextension and added the extension USD Viewer Template Kit file - Moved Kit Service Template to bottom of Application list
- BUILD (RELEASE) SUCCEEDED message not supported for all build configurations
- Removed Services dependencies from USD Composer Template that caused a firewall popup on first launch
- Updated to
Kit 106.2.0 - Refactored Viewer Template default tests to avoid unnecessary dependencies
- Unused
simulationmenu item from USD Composer Template
- Support for containerization of streaming applications and services via
repo package --container - Support extension only builds via
repo build - Support the ability to launch created containers via
repo launch --container - repo_usd tooling dependency
- Support for USD Viewer Template to send scene loading state to client via messaging
- Updated to
Kit 106.1.0 - Aligned default testing for applications and extensions
- Update and align code formatting/style across templates
- Extra setup extensions appear in standard extension template menu
- "Could not find cgroup memory limit" error during build
- Fixed default manipulator pivot back to "bounding box base" in USD Explorer Template
- Updated to
Kit 106.0.3
- Support for local streaming configurations for UI based Applications
- Support for multiple setup extensions per application
- Ability to pass arguments to Kit via the
repo launchtool - USD Composer Application Template and Documentation
- USD Viewer Application Template and Documentation
- USD Composer Setup Extension and Documentation
- USD Viewer Setup Extension and Documentation
- Repository Issue Templates Bug/Question/Feature Request
- Omniverse Product-Specific Terms (PRODUCT_TERMS_OMNIVERSE)
- Support for type ordering in templates.toml
- Metrics Assembler to Kit Base Editor Template to support unit correct assets
- Support for automatic launch if only single
.kitfile is present insource/apps
- Updated to
Kit 106.0.2 - Updated all relevant application templates READMEs to reflect the addition of local streaming configurations
- Updated .gitattributes to ensure LFS is used for all relevant file types
- Updated .gitignore to exclude streaming app event traces
- Updated .vscode/launch.json to better support debugging behavior
- Updated LICENSE to separate NVIDIA License from Omniverse Product-Specific Terms
- Updated top level README.md to reflect additional templates and improve documentation clarity
- Updated Developer Bundle extension availability and corresponding documentation
- Updated public extension registry to reflect current Kit 106 registry location
- Updated templates.toml to support multiple setup extensions and new templates
- Kit Base Editor Application Template and Documentation
- USD Explorer Application Template and Documentation
- USD Explorer Setup Extension and Documentation
- Kit Service Template and Documentation
- Simple Python Extension Template and Documentation
- Simple C++ Extension Template and Documentation
- Python UI Extension Template and Documentation
- Template configuration file (templates.toml)
- Added local
repo launchtool for launching applications and fat packages directly - Added local
repo packagefunctionality to improve package naming - Omniverse EULA acceptance to Kit App Template via tooling
- tasks.json for better VSCode support
- SECURITY.md for security policy
- Notice for data collection and use
- Early access Developer Bundle extensions
- Kit App Template related Developer Bundle documentation (developer_bundle_extensions.md)
- Kit App Template related repo tools documentation (kit_app_template_tooling_guide.md)
- Usage and troubleshooting documentation for Kit App Template (usage_and_troubleshooting.md)
- repo_tools.toml to configure local repo tools
- Updated to
Kit 106.0.0 - Updated repo_kit_template tooling to support Applications and Extensions
- Updated repo_kit_template tooling to allow for application setup extensions
- Updated top level README.md to reflect updated tooling and templates
- Updated LICENSE.md to reflect updated tooling and templates
- Updated .gitattributes to reflect use of templates rather directly from source
- Added configuration to repo.toml to support new tools and templates
- Top level build .bat/.sh scripts in favor of using
repo builddirectly - Predefined
define_appdeclarations frompremake5.luain favor of developer defined applications - Predefined source/apps in favor of templates for developers to build from