HiïŒI found a bug in connect sample
If I run run_py_sample.bat, ERROR comesïŒ
Python, USD, and Omniverse Client libraries are missing. Run prebuild.bat to retrieve them.
I solve it by modifying the bat file belowïŒ
setlocal
pushd "%~dp0"
set ROOT_DIR=%~dp0
set USD_LIB_DIR=%ROOT_DIR%_build\target-deps\nv_usd\release\lib
set OMNI_CLIENT_DIR=%ROOT_DIR%_build\target-deps\omni_client_library\release
set PYTHON=%ROOT_DIR%_build\target-deps\python\python.exe
set PATH=%PATH%;%USD_LIB_DIR%;%OMNI_CLIENT_DIR%
set PYTHONPATH=%USD_LIB_DIR%\python;%OMNI_CLIENT_DIR%\bindings-python
if not exist "%PYTHON%" (
echo Python, USD, and Omniverse Client libraries are missing. Run prebuild.bat to retrieve them.
popd
exit /b
)
"%PYTHON%" source\pyHelloWorld\helloWorld.py %*
if errorlevel 1 ( goto Error )
popd
Just change %PYTHON% to â%PYTHON%â
Because sometimes usrers like me will install omniverse in a directory with blank spaceïŒfor example
âE:\ProgramData\NVIDIA Corporation\Omniverse\lib\connectsample-101.1.6â
Thank you for finding this and fixing it. Iâll make sure this makes it into the next update!
102.1.5
In this release weâve fixed a few things that needed cleaning up, but the biggest change was allowing the user to use their own Visual Studio compiler on Windows using a build tool configuration utility if they choose. We added a dome light with an HDR texture and release notes for the Omniverse Client Library.
-
Samples
- OM-31648: Add a windows build tool configuration utility if the user wants to use an installed MSVC and the Windows SDK
- Add a dome light with texture to the stage
- OM-35991: Modify the MDL names and paths to reduce some code redundancy based on a forum post
- Add Nucleus checkpoints to the Python sample
- Avoid writing Nucleus checkpoints when live mode is enabled, this isnât supported properly
- OM-37005: Fix a bug in the Python sample batch file if the sample was installed in a path with spaces
- Make the /Root prim the
defaultPrim
- Update Omniverse Client Library to
1.13.19
-
Omniverse Client Library
- 1.13.19
- OM-36925: Fix omniClientMakeRelative(âomni://host/path/â, âomni://host/path/â);
- 1.13.18
- OM-25931: Fixed some issues around changing and calling the log callback to reduce hangs.
- OM-36755: Fixed possible use-after-delete issue with set_log_callback (Python).
- 1.13.17
- OM-34879: Hard-code âmdlâ as ânot a layerâ to work around a problem that happens if the âusdMdlâ plugin is loaded
- 1.13.16
- OM-36756: Fix crash that could happen if two threads read a layer at the exact same time.
- 1.13.15
- OM-35235: Fix various hangs by changing all bindings to release the GIL except in very specific cases.
- 1.13.14
- OM-34879: Fix hang in some circumstances by delaying USD plugin registration until later
- OM-33732: Remove USD diagnostic delegate
- 1.13.13
- OM-36256: Fixed S3 provider from generating a bad AWS signature when Omni Cache is enabled
- 1.13.12
- 1.13.11
- OM-35397: Fixed a bug that caused Linuxâs File Watcher Thread to peg the CPU in some cases.
- 1.13.10
- OM-32244: Fixed a very rare crash that could occur when reading a local file that another process has locked
- 1.13.9
- OM-35050: Fixed problem reloading a non-live layer after itâs been modified. * 1.13.8
- OM-34739: Fix regression loading MDLs introduced in
- 1.13.3.8
- OM-33949: makeRelativeUrl prepends â./â to relative paths
- OM-34752: Make sure local paths are always using ââ inside USD on Windows
- 1.13.7
- OM-34696: Fixed bug when S3 + cloudfront + omni cache are all used
- 1.13.6
- OM-33914: Fixed crash when accessing http provider from mulitple threads simultaneously
- 1.13.5
- OM-26039: Fixed âRestoring checkpoint while USD stage is opened live wipes the contentâ
- OM-33753: Fixed ârunning massive amounts of live edits together causes massive amounts of checkpointsâ
- OM-34432: Fixed â[Create] It will lose all data or hang Create in live sessionâ
- These were all the same underlying issue: When a layer is overwritten in live mode it was cleared and set as âdirtyâ which would cause the next âSave()â (which happens every frame in live mode) to save the cleared layer back to the Omniverse server.
- 1.13.4
- OM-31830: omniClientCopy() with HTTP/S3 provider as source
- OM-33321: Use Omni Cache 2.4.1+ new reverse proxy feature for HTTPS caching
- 1.13.3
- OM-33483: Donât crash when trying to save a layer that came from a mount
- OM-27233: Support loading non-USD files (abc, drc, etc)
- OM-4613 & OM-34150: Support saving usda files as ascii
- Note this change means live updates no longer work with usda files (though they technically never did â it would silently convert them to usdc files).
1 Like
103.1.0
In this release we added a couple helpful samples referenced in the forums, docs, and the November 2021 GTC âMaking a Connector for Omniverseâ session.
-
Samples
- Added omniUsdReader, a very very simple program for build config demonstration that opens a stage and traverses it, printing all of the prims
- Added omniUsdaWatcher, a live USD watcher that outputs a constantly updating USDA file on disk
- Updated the nv-usd library to one with symbols so the Visual Studio Debug Visualizers work properly
-
Omniverse Client Library
200.0.0
The 200.0 release signifies big changes with the distributed Omniverse libraries. The Omniverse team has separated the USD resolver plugin from the Client library to make it easier to support more versions of USD. Live synchronization is improved for the purposes of performance, simultaneous editors, and supporting the entire USD layer editing feature set. Omniverse applications and Connectors are also now subscribing to the notion of live sessions to support non-destructive workflows. This version of the Connect Samples includes new Python and C++ examples to demonstrate this live session workflow.
-
Samples
- Added the LiveSession examples along with an introductory LiveSession Library that contains many required components to support the new live session workflow
-
Omniverse USD Resolver
-
Omniverse Client Library
200.1.0
This small update to the Connect Samples fixes some simple bugs in the live session classes and updates the Omniverse Client Library and USD Resolver with the latest versions.
-
Samples
- Fix the âMESSAGEâ message type and custom âmessageâ key to be case correct
- Ensure that we flush live layer clears with
omniClientLiveProcess()
- Clear the peer users in LeaveChannel() allows for recycling the class
- Fix the usd_resolver post build copy step in UsdReader example
-
Omniverse USD Resolver
-
Omniverse Client Library
202.0
In this update we added some sample code for adding a reference, payload, and modifying a material parameter from code.
- Samples
- Add a prop payload and reference to a HelloWorld (OM-35218)
- Modify an OmniPBR MDL parameter for a referenced prop
- Change defaultPrim handling to be less hardcoded and more correct
- Update the repo build tools to modern versions (OM-77486)
- Add a test script for all programs (ârepo testâ or tests/test_all.[bat,sh])
- Allow Windows users to use their installed build tools with
repo build --use-devenv (OM-74840)
- Add a function to determine if any prims exist in the root layer before merging (OM-64707)
- Add a note in README.md about Visual Studio failing to iterate on builds (OM-78756)
- Set the defaultPrim to kind=assembly, all others to kind=component
- Correctly set the USD Preview Surface bias, scale, and sourceColorSpace
- Correctly apply the MaterialBindingAPI to the box mesh prim
- Change OmniCLI to overwrite destination folders for copy and move (OM-80541)
- Omniverse USD Resolver
- Omniverse Client Library
- Omniverse Asset Validator
1 Like
203.0
Release Date: June 2023
With this release the shipped USD version is updated to 22.11 and Python 3.10 to align with the rest of the Omniverse platform. Also a skinned skeletal mesh example was added to demonstrate how to author, skin, and animate skeletons in a live layer.
- Samples
- Update USD version to 22.11
- Update Python version to 3.10
- Add a skinned skeletal mesh example with live updates
- Fix 21.08 include guard for UsdPhysics
- Add channel join/send/leave commands to OmniCLI
- Use a mesh rather than a cube to test the invalid extents since a cube always returns an extents attribute
- Set the correct render type for the shader output attributes
- Use an installed OmniPBR rather than including a very old version
- Omniverse USD Resolver
- Omniverse Client Library
- Omniverse Asset Validator
1 Like
