pype | Main repo of OpenPype | Game Engine library

So thanks to Bodo I found the issue Here is a correct version of the code:

The solution I found after a week of trying and searching:

1. git clone the vmtk repo onto your computer and follow the VMTK download instructions on how to build it from source. It will absolutely feel like a headache and be a long process; just wait it out.

   • If you don't have cmake installed on your computer, they offer a GUI version on their website. I'm not sure how it would work for Windows, but it definitely works for Mac.

2. Once you've built it, make sure that each terminal instance of VMTK you set source vmtk_env.sh from the path where that file is. This will allow you to use the VMTK environment.

3. After writing the custom script, making sure to follow all the directions in the tutorial (assuming this is the first time), make sure to save it in the "site-packages" folder in the build folder. The path for me is "vmtk-build/lib/python-2.7/site-packages/vmtk/". I'm currently looking to update the version of Python it's using, but that's not the point.

4. Once that's done, navigate to that folder from within terminal and run chmod u+x name_of_script.py (if you're in a Unix-based operating system). This will allow you to execute the file with ./name_of_script.py.

5. I believe it was due to the version of Python VMTK is using, but I had two "No module named" errors come up, each one a separate time: one for tkinter and one for joblib.

   • The tkinter issue is one that can be resolved by going into the file where the import is, I believe vmtkscripts.py, and changing all instances of tkinter to Tkinter (capital T). This is because they changed the name of the module from Python 2 to 3, so in newer versions of Python it would be tkinter. That fixed the first error.

   • When I attempted to fix the joblib issue, I saw that the other version of Python available on my system already had it, thus I couldn't install it through pip. Instead, you can do python-2.7 -m pip install joblib to install it for a specific version of Python. Although I did uninstall joblib as a whole from my computer before doing that.

That should fix everything. The next time I attempted to run my script, it ran without any errors.

Extra: I wasn't using any Anaconda environment for this. Might go back and try to set that up, but I'm just glad I got it to work. Additionally, I deleted the binary install of VMTK from my computer. No need to keep it around if you're just going to build it from source. You can run VMTK through the terminal after setting source vmtk_env.sh by running the vmtk command.