Hi there,
I am getting this error when I want to export USD format with Omniverse in 3dsmax 2023 and 2024.
Error in 3dsmax 2023:
Traceback (most recent call last):
File “C:\Program Files\Autodesk\3ds Max 2023\Python\Lib\site-packages\shiboken2\files.dir\shibokensupport_feature_.py”, line 142, in _import
return original_import(name, *args, **kwargs)
File “”, line 8, in find
ModuleNotFoundError: No module named ‘pxr.GeomUtil’
Error in 3dsmax 2024:
Traceback (most recent call last):
File “C:\Program Files\Autodesk\3ds Max 2024\Python\Lib\site-packages\shiboken2\files.dir\shibokensupport_feature_.py”, line 148, in import
return original_import(name, *args, **kwargs)
File “”, line 8, in find
File "C:\USD\lib\python\pxr\GeomUtil_init.py", line 28, in
from . import geomUtil
File "C:\Program Files\Autodesk\3ds Max 2024\Python\Lib\site-packages\shiboken2\files.dir\shibokensupport_feature.py", line 148, in _import
return original_import(name, *args, **kwargs)
File “”, line 8, in find
ImportError: DLL load failed while importing _geomUtil: The specified module could not be found.
as I searched a lot in this forum and also internet about this issue, I explained some points and previous tries to fix this issue. but none of them work for me !!
Windows version: 11
omniverse connector version: 201.1.0 ( I also uninstalled and installed it again but it did not fix the issue ! )
USD exporter for 3dsmax: installed( I also uninstalled it because of a conflict with Omniverse but it did not fix ! )
VisualStudio Version: Visual Studio 17 2022" -A x64
I do not know if it is a conflict between these three USDexporter/ OpenUSD / Omniverse connector or is it a conflict between versions of python or env variables?!
@majid.adab does it happen to any mesh you are trying to export? do you get the same issue through the USD plugin from ADSK (when you have it installed) and with OV’s Max Connector? has this issue happened before?
Yes, it happens to every mesh which I want to export. even when I open 3dsmax and I create a box and want to export it, it gives me this error.
No, with the Adsk USD exported models export well without any errors. just with the omniverse.
honestly, I did not pay attention to this warning in the Maxscript listener before.
today I noticed this error in the listener. ( maybe before installing USD exporter it was there, I think )
because actually after this error the USD file create with omniverse exporter too.
just IDK if this error can affect the exported USD file or not?
because if it is something wrong with the file, I only can use Adsk USDexporter.
but that exported does not support MDL materials I think !! :(
because of this, I want to use this exporter and I am not sure about the result.
the USD file opens okay both in the usdviewer and USD composer.
but this error shows both in the 3dsmax 2023 and 2024 listeners.
if you think it is just a simple warning and nothing serious happens to the file, I ignore it.
thanks
i don’t recall seeing those errors on my end, so i can’t say it’s the expected behavior. That said, i don’t have a C:\USD directory, so not sure where that’s from. the only thing i have no experience with is the OpenUSD exporter you mentioned. did you compile it locally from pixar’s github repo at some point?
have you looked into disabling the ADSK plugins from the Plug-in Manager? i’ve seen reports of USD plugin conflicts between ADSK and Nvidia’s but have not seen it for Max yet (though not to say it doesn’t exist).
yes, exactly. I compiled it from the Pixar GitHub repo myself in the C:\USD directory.
yes, I disabled USD plugin too but it does not fix this error. :(
Also, I removed the env variables for OpenUSD too, but it also did not fix this issue.
yes, I read about the conflict between USDexporter and Omniverse connector too.
anyway, thanks for your fast response.
do you know what is this pxr.geomUtil ? and what is it for?
because as I mentioned the file exported by this error in the listener, I want to know what does this module do in the USD file and is it critical or not in the file ?
i am afraid i don’t have the answer to what geomUtil does in the context of OpenUSD. but i can only speculate based on the files inside of the github repo (OpenUSD/pxr/imaging/geomUtil) that it’s a library with a couple mesh generators (supports capsule, cone, cuboid, cylinder, and sphere) for prims. whether or not you need it? i don’t feel comfortable answering that because i never compiled it myself and haven’t had issues with the OV connector.
i feel like given the error message, the compile you did might’ve had issues or something didn’t get compiled correctly. worst case is to reinstall Max, but honestly, i wouldn’t know with certainty that’ll resolve the issue. to your point, here is what i have in my environment variables (note nothing with USD)
oh yeah. thank you so much. @Simplychenable .it solved that error. thank youuuuu. :))
it seems that the problem was from that env var “C:\USD\lib”.
it was there because of compiling OpenUSD in my system. and the conflict was between the Python version of GeomUtil in the OpenUSD Pxr folder comparison to GeomUtil used by Omniverse connector.
I think I should use Python 3.9 version of OpenUSD to compile in my system ( not Python 3.10 )
because 3dsmax 2023 Python version is 3.9.
I thought that it was a conflict between USDexporter and Omniverse. Now, I found that it is the conflict between OpenUSD and Omniverse. I put this env var there because of this solution in the below link.
also here it was mentioned to pay attention to Python versions. I did not read carefully.
because the 3dsmax USD Exporter also uses Pixar openUSD libraries, the Python version of that is also important in this issue too.
so for me, I was forced to uninstall all three USD exported/ omniverse connector / remove OpenUSD Env Var.
and then install just a clean omniverse connector, and the error was solved completely.
JFYI, in building and installing OpenUSD github repo we can choose the right python version and correct release compatible with omniverse connector.
but IDK for the usd exporter what can we do ? because it is msi installer and it automatically installs its own python version on 3dsmax?!
though i cannot answer the question either, the person i know of who is most knowledgeable with ADSK’s implementation of Max’s USD plugin would be Louis Marcoux. he’s on the Nvidia OV team now (i think) and might be able to address that question.
