The folder you point to should be the one that contains "otls", "scripts", and "toolbar": MOPS="/path/to/MOPS"įinally, add $MOPS to your HOUDINI_PATH: HOUDINI_PATH=$HOUDINI_PATH $MOPS & Edit your houdini.env file and create a variable called MOPS that points to the new folder you just extracted MOPs to. For more information about the Houdini environment file, see this help link. Option 2: Edit Houdini.env You need to add the MOPS root directory to your Houdini environment file. Important: on Windows, you must change any backslashes to forward slashes when defining the MOPS variable! Then edit MOPS.json and change the "MOPS" variable to match the MOPs install path (the directory that contains "otls", "scripts", etc.). Simply create a folder inside your Houdini preferences directory (where the houdini.env typically is) called "packages", and place the MOPS.json file from the MOPs download into that folder. Option 1: Plugin (17.5+ only) For those of you running Houdini 17.5 or later, you have an option for a much easier install. It's recommended that you do not extract MOPs directly to your existing /houdiniXX.X/ home directory. Option 2 (what's Git?): Download the desired release directly from the releases page and extract it to your hard drive or network share. Option 1 (users who are familiar with Git): Navigate to the folder you want to contain MOPs, and from BASH / Git BASH type: git clone It's highly recommended that you use packages instead of messing with houdini.env. MOPs is pretty easy to install with the new Packages method.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |