Having trouble with Adobe Conversion Plugins

I have been trying to get the Adobe Conversion plugins (GitHub - adobe/USD-Fileformat-plugins: A collection of USD fileformat plugins) to work for my project and after I built the plugin, nether my project nor the test exe are able to find the module in the dll. I tested this on a fresh install of the plugin and I ran into the same issues. I have added the paths to the environment variables as instructed and I have still encountered the same error (see below). Any idea what I might be doing wrong? Did I setup the environment variables wrong? This is with the C++ version of OpenUSD on Windows 11.

Try to set TF_DEBUG:

set TF_DEBUG=*

Open a Python shell, execute the following USD code

from pxr import Usd
Usd.Stage.Open("./USD-Fileformat-plugins/obj/tests/SanityCube.obj")

If the environment variable of obj plugin is set correctly, you should see a message similar to: Registering shared library plugin 'usdObj_plugin' at 'your_install_path/plugin/usd/usdObj.dll'.

1 Like

Here is what happens when I do the above. (Made a mistake in there at first because I was in the wrong directory. The bottom chunk is the more interesting set of errors)

Here is how it looks once I add cube.mtl

I think the reason I dont see any debug info is my openUSD is the release build. However, this is making me think that it is a environment variable issue. Errors are not being thrown around when I am running the tests where it can easily find the dlls.

Happy to see that the OBJ plugin worked correctly in the Python shell!
However, the debug information didn’t display because the usage of environment variables in PowerShell is different from the Command Prompt.
You should use the following commands:

$env:TF_DEBUG="*"  # Set the environment variable
$env:PATH          # Check your PATH environment variable

Since your OBJ plugin looks good in the Python shell, you can try copying the DLLs to the same directory as the executable. If the program works, then it’s likely an environment variable issue.

1 Like

I did the above and was able to see the debug messages! I revisited both the sanity check and my original project and it looks like the plugins are working now! The original project I think was fixed after I moved some missing files into the library section. The Sanity check didn’t work at first but with the debug flag turned on I found out I was running it in the wrong place and so was able to get a good result! Now I am trying to figure out why my test model isn’t being exported when I use the export function, but that is a separate issue to what this thread is about. Thank you for the help with debugging! The python and TF_DEBUG env info has been very helpful in debugging this project!