Closed melMass closed 1 year ago
I since downloaded the full prebuilt standalone that worked fine so I compared the files in pxr/Tf
and it was matching.
So I just tried to use a lower version virtual env (3.9.10) and it does load the dynamic library properly!
So I guess it could be specified for the instructions using PismPipeline prebuilds :)
I recommend you not to relly on pre-built versions of packages like OpenUSD. It will cause more issues than solve, since it has many compile-time options for specific environments which e.g. require support for MaterialX or bundled Hydra renderer.
Nvidia's builds of OpenUSD are outdated, and mainly configured to work with Python 3.7/3.8 for their Omniverse platform.
Thanks, I mostly use it in Houdini for now where it uses the libraries from SideFX but I wanted to try the standalone mode using the prebuilds from Prim no NVIDIA's, in Quiltix's readme it doesn't specify that they are only compatible with python 3.9
QuiltiX works with multiple Python versions, not only 3.9. But the prebuild USD version which you linked was build with Python 3.9. It's a good idea to mention the prebuild Python version in the repo. If you want to use QuiltiX with Python 3.10 you need to build your own USD version (or find a precompiled Python 3.10 USD build).
Hi,
I'm trying to use the prebuilt wheels (OpenUSD and MaterialX) on Windows 11 with Python 10.11, but when I try to run QuiltiX I get the following trace:
Traceback
```console ❯ python -m QuiltiX Traceback (most recent call last): File "C:\Users\User\.pyenv\pyenv-win\versions\3.10.11\lib\runpy.py", line 86, in _run_code exec(code, run_globals) File "C:\Users\User\.dot\.venv\lib\site-packages\QuiltiX\__main__.py", line 1, inI found this forum message over nvidia that suggest it could be an ABI issue or something not in PATH. Any help is appreciated
Thanks