### Installing python-certifi-win32 Source: https://github.com/nvidia-omniverse/connect-samples/blob/main/README.md Installs the python-certifi-win32 package to allow the Windows certificate store to be used for TLS/SSL requests. This is a workaround for self-signed certificate issues when running the Connect Sample scripts. ```bash tools\packman\python.bat -m pip install python-certifi-win32 --trusted-host pypi.org --trusted-host files.pythonhosted.org ``` -------------------------------- ### Running OmniSimpleSensor Source: https://github.com/nvidia-omniverse/connect-samples/blob/main/README.md Executes the OmniSimpleSensor script with the specified server path, number of inputs, and timeout value. The server path specifies the Nucleus server location, the number of inputs determines how many OmniSensorThread processes will be started, and the timeout specifies how long the processes will run. ```bash run_omniSimpleSensor.bat|sh ``` -------------------------------- ### Creating a Junction Point (Batch) Source: https://github.com/nvidia-omniverse/connect-samples/blob/main/README.md This command creates a junction point (symbolic link) from C:\connect-samples to the specified Connect Samples directory within the user's local application data. This allows Visual Studio to properly build the samples when they are located in the default installation directory. ```batch mklink /J C:\connect-samples %LOCALAPPDATA%\ov\pkg\connectsample-202.0.0 ``` -------------------------------- ### Example Usage of TfMakeValidIdentifier() Source: https://github.com/nvidia-omniverse/connect-samples/blob/main/CHANGELOG.md This snippet demonstrates the usage of TfMakeValidIdentifier() to ensure that prim names are valid. This is important for avoiding issues with asset validation and ensuring compatibility. ```C++ TfMakeValidIdentifier() ``` -------------------------------- ### Running samples on Windows with help Source: https://github.com/nvidia-omniverse/connect-samples/blob/main/README.md This script executes a sample program with a pre-configured environment and displays command-line argument help. ```bash .\run_hello_world.bat --help ``` -------------------------------- ### Running samples on Linux with help Source: https://github.com/nvidia-omniverse/connect-samples/blob/main/README.md This script executes a sample program with a pre-configured environment and displays command-line argument help. ```bash ./run_hello_world.sh --help ``` -------------------------------- ### Building samples on Windows Source: https://github.com/nvidia-omniverse/connect-samples/blob/main/README.md This script downloads dependencies, creates projects, and compiles the code on Windows. ```bash .\repo.bat build ``` -------------------------------- ### Building samples on Linux Source: https://github.com/nvidia-omniverse/connect-samples/blob/main/README.md This script downloads dependencies, creates Makefiles, and compiles the code on Linux. ```bash ./repo.sh build ``` -------------------------------- ### Creating a USD Stage and Adding a Box - Python Source: https://github.com/nvidia-omniverse/connect-samples/blob/main/CHANGELOG.md This Python code demonstrates how to connect to an Omniverse server, create a USD stage, add a polygonal box to the stage, upload an MDL material and its textures, bind materials to the box, add a light, and move/rotate the box with live updates. It requires the Omniverse Client Library and a connection to an Omniverse server. ```python HelloWorld sample that demonstrates how to: * connect to an Omniverse server * create a USD stage * create a polygonal box and add it to the stage * upload an MDL material and its textures to an Omniverse server * bind an MDL and USD Preview Surface material to the box * add a light to the stage * move and rotate the box with live updates * print verbose Omniverse logs * open an existing stage and find a mesh to do live edits ``` -------------------------------- ### Running OmniUSDAWatcher with Live Session URL Source: https://github.com/nvidia-omniverse/connect-samples/blob/main/README.md This command demonstrates how to run the OmniUSDAWatcher utility to monitor a live session stage and save it as a USDA file. It takes the URL of the live layer and the output path for the USDA file as arguments. ```bash run_omniUsdaWatcher.bat|sh omniverse://localhost/Users/test/helloworld.live C:\USD\helloworld.usda ``` -------------------------------- ### C++ UsdLuxLight Compatibility Class Source: https://github.com/nvidia-omniverse/connect-samples/blob/main/CHANGELOG.md This snippet introduces a C++ UsdLuxLight compatibility class designed to address schema and API upgrade issues. It involves renaming the omniLiveSessionLib to omniUtilsLib and moving cppUtils to omniUtilsLib/include. ```C++ C++ UsdLuxLight compatibility class ``` -------------------------------- ### Running Asset Validator with Fix Flag (Bash/Shell) Source: https://github.com/nvidia-omniverse/connect-samples/blob/main/README.md This command executes the Omniverse Asset Validator script with the `--fix` flag, which attempts to automatically repair any validation failures found in the specified USD stage. It demonstrates how to use the validator to ensure assets comply with Omniverse-specific rules. ```bash omni_asset_validator.bat|sh --fix omniverse://localhost/Users/test/helloworld.usd ``` -------------------------------- ### Validating USD Layer File URIs with Asset Validator Source: https://github.com/nvidia-omniverse/connect-samples/blob/main/CHANGELOG.md This snippet demonstrates how to use the Asset Validator to find issues in USD layer file URIs using the omni_asset_validator script. It validates the USD files and reports any issues found. ```Shell omni_asset_validator.bat|sh ``` -------------------------------- ### Validating In-Memory Stage with Asset Validator Source: https://github.com/nvidia-omniverse/connect-samples/blob/main/CHANGELOG.md This snippet shows how to use the Asset Validator on an in-memory stage within pyLiveSession. It demonstrates the 'v' validate option to trigger the asset validation process. ```Python 'v' validate option for pyLiveSession ``` === COMPLETE CONTENT === This response contains all available snippets from this library. No additional content exists. Do not make further requests.