Houdini Procedural FX Attribute Guide

Procedural Modeling - Treat Procedural Modeling as a production checkpoint: it should narrow the review, not decorate the page with another synonym. Procedural Modeling (程序化建模 / プロシージャルモデリング) can be translated safely only after the production meaning is known. Keep the English label visible when it is also a UI label, plug-in name, or channel name. The translation is therefore tied to evidence, not to an isolated glossary row.

Geometry Nodes - Geometry Nodes should be read through Blender, not as a loose label in a translation sheet. Geometry Nodes (几何节点 / ジオメトリノード) should be reviewed at the graph level. A screenshot of the final viewport is secondary; the important evidence is the node group, exposed parameters, and the output that proves the graph behaves as intended. That keeps the article searchable while still giving Houdini technical artist or FX artist something concrete to approve.

Surface Operator - When SOP or SOP appears in a review note, the English term still needs the file state beside it. Surface Operator (SOP / SOP) needs a before-and-after note when it changes the asset. The accepted evidence should be small enough for another reviewer to reopen without rebuilding the whole scene. Use the note to decide whether the asset is ready, blocked, or waiting for a narrower specialist pass.

VEX Operator - VEX Operator becomes useful only when the reviewer can point to the part of node network, cache, generated geometry, volume, or simulation export that it changes. VEX Operator (VOP / VOP) can be translated safely only after the production meaning is known. Keep the English label visible when it is also a UI label, plug-in name, or channel name. If that proof cannot be attached, the term should remain in review rather than be treated as covered.

Rigid Body - For a vendor-facing brief, Rigid Body is the anchor term and the localized labels explain the same inspected state. Rigid Body (刚体 / 剛体) needs a before-and-after note when it changes the asset. The accepted evidence should be small enough for another reviewer to reopen without rebuilding the whole scene. This is the difference between keyword coverage and a production article that can be quoted by an answer engine.

Soft Body - The practical question around Soft Body is what evidence would make another reviewer agree with the same decision. Soft Body (软体 / ソフトボディ) needs a before-and-after note when it changes the asset. The accepted evidence should be small enough for another reviewer to reopen without rebuilding the whole scene. The translation is therefore tied to evidence, not to an isolated glossary row.

Fluid - Treat Fluid as a production checkpoint: it should narrow the review, not decorate the page with another synonym. Fluid (流体 / 流体) can be translated safely only after the production meaning is known. Keep the English label visible when it is also a UI label, plug-in name, or channel name. That keeps the article searchable while still giving Houdini technical artist or FX artist something concrete to approve.

OpenVDB - OpenVDB should be read through 体积格式, not as a loose label in a translation sheet. OpenVDB (OpenVDB / OpenVDB) should include procedural cause and cached result. Name the node path, attribute or solver setting, frame range, and exported artifact before calling the effect reproducible. Use the note to decide whether the asset is ready, blocked, or waiting for a narrower specialist pass.