{ "version": "https:\/\/jsonfeed.org\/version\/1.1", "title": "Photoindra: posts tagged plasticity", "_rss_description": "My telegram", "_rss_language": "en", "_itunes_email": "", "_itunes_categories_xml": "", "_itunes_image": "", "_itunes_explicit": "", "home_page_url": "https:\/\/photoindra.com\/tags\/plasticity\/", "feed_url": "https:\/\/photoindra.com\/tags\/plasticity\/json\/", "icon": "https:\/\/photoindra.com\/pictures\/userpic\/userpic@2x.jpg?1578579456", "authors": [ { "name": "Russian in Panama", "url": "https:\/\/photoindra.com\/", "avatar": "https:\/\/photoindra.com\/pictures\/userpic\/userpic@2x.jpg?1578579456" } ], "items": [ { "id": "286", "url": "https:\/\/photoindra.com\/all\/plasticity-to-houdini-21-recipe\/", "title": "Plasticity to Houdini 21 recipe", "content_html": "

I’ve been using a lot Plasticity<\/a> lately. It’s a simple CAD tool for surface modeling – much easier than Fusion 360 or MOI. I can do modeling with booleans and curves there much faster.
\nThen I import the geometry into Houdini, and usually my import process looks like this:<\/p>\n

\n\"\"\n<\/div>\n
    \n
  1. Align the axis to the only correct way: Y is up, Z points forward to the viewer, and X points right.<\/li>\n
  2. Scale to meters.<\/li>\n
  3. Use a Match Size node in case I modeled without real-world dimensions.<\/li>\n
  4. If you name your layers in Plasticity they will come into Houdini as a “path” attribute, so you can easily convert them to groups with the Groups from Name node.<\/li>\n<\/ol>\n

    To make this transition as easy as possible I use the new Recipes system (added in Houdini 20.5). To share those recipes between my different workstations, I created a recipes.json file inside the Houdini packages folder with this content:<\/p>\n

    {\n  "hpath": "path_to_your_cloud_folder\/Documents\/Houdini\/recipes_folder",\n  "env": [\n    { "HOUDINI_CUSTOM_RECIPE_DIR": "path_to_your_cloud_folder\/Documents\/Houdini\/recipes_folder" },\n    { "HOUDINI_CUSTOM_RECIPE_LIBRARY": "custom_recipes" }\n  ]\n}<\/code><\/pre>
    In this setup, when you save a new tool as a recipe, Houdini automatically locks the Save To field to Custom File Path, pointing to:
    \npath_to_your_cloud_folder\/Documents\/Houdini\/recipes_folder\/olts\/custom_recipes.hda<\/p>\n
    Here’s example of another recipe that helps process low- and high-poly meshes for baking in Marmoset:<\/p>\n
    \n\"\"\n<\/div>\n
    I’ll post more details about this project later, but the main idea is to use crude low-res geo from Plasticity, clean it up in Houdini, and at the same time import mid-poly. Then, use it in combination with Marmoset’s rounded edge baking<\/a>.
    \nNo more micro-beveling inside Plasticity or ZBrush.<\/p>\n",
            "date_published": "2025-09-10T14:19:35-05:00",
            "date_modified": "2025-09-10T14:19:12-05:00",
            "tags": [
                "houdini",
                "plasticity"
            ],
            "image": "https:\/\/photoindra.com\/pictures\/plast_import_01.jpg",
            "_date_published_rfc2822": "Wed, 10 Sep 2025 14:19:35 -0500",
            "_rss_guid_is_permalink": "false",
            "_rss_guid": "286",
            "_e2_data": {
                "is_favourite": false,
                "links_required": [
                    "highlight\/highlight.js",
                    "highlight\/highlight.css"
                ],
                "og_images": [
                    "https:\/\/photoindra.com\/pictures\/plast_import_01.jpg",
                    "https:\/\/photoindra.com\/pictures\/plast_import_02@2x.jpg"
                ]
            }
        }
    ],
    "_e2_version": 4134,
    "_e2_ua_string": "Aegea 11.3 (v4134)"
}