The type indicator isn't necessary, but included as a reminder. Ī list of variables available in wrangles. VEX is the workhorse for geometry, volume and simulation processing in addition to shading and compositing. SIMD is short for Single Instruction/Multiple Data, meaning that your code (instruction) is executed over multiple data (vertices, points, primitives, pixels, voxels, etc). However, it also has an implicitly SIMD evaluation approach. It is a software interpreted language (execute instructions directly and freely, without previously compiling a program into machine-language instructions.) so provides the flexibility of scripting. These attributes will invoke the OnScriptsReloaded function, which automatically creates a new custom interface object, and registers it with HEU_InputUtility when the Unity Editor scripts are reloaded.VEX is a shading language similar to the Renderman Shading Language (RSL). To add a custom input script hook, create a new class that derives from HEU_InputInterface, fill in the required methods, then copy and edit the OnScriptsReloaded function from HEU_InputInterfaceMesh.cs, and add the, and attributes.

HEU_InputInterfaceMesh.cs and HEU_InputInterfaceTerrain.cs both provide examples of HEU_InputInterface derived classes handling uploading of mesh and terrain objects, respectively. When an input object needs to be uploaded into Houdini, HEU_InputUtility finds and uses the registered HEU_InputInterface that can upload that object, based on the priority set by the user. A class derived from HEU_InputInterface registers itself with HEU_InputUtility. HEU_InputUtility.cs is the utility class that manages input interface scripts, which are derived from HEU_InputInterface.cs. For example, users can add their own input script for uploading meshes or terrains instead of using the built-in scripts.

For example, the Create Groups for Tiles will automatically create a point group for each tile type, or output a string point attribute unity_tile_name representing the tile name.Ĭustom scripts can be easily added to the plug-in’s input mechanism allowing to add support for uploading custom input data or override built-in scripts. Tilemap input objects also have a number of options to enable/disable/modify these attributes. The points will have point attributes P (position), Cd (tile color), orient (tilemap rotation), scale (tilemap scale), unity_tile_pos (position in grid), unity_tile_size (tile size), and a detail attribute unity_tile_bounds (size of grid). Tilemap input objects can be set to Houdini Engine as point data representing each tile. This uses Unity’s () which simply compares using the collider’s bounding box. You can also add an object with a HEU_BoundingVolume component attached to it, and it will use all the meshes in its bounding box as input. Transform Offset - Each input object can be assigned a transform offset that adds to the world transform of the input object, if Keep World Transform is enabled. The other options allow you to select an input object with an Object filter for that specific type, and may include additional options for that particular type. This way the material assignment can survive the roundtrip back to Unity. If the GameObject has assigned materials, the material names will also be set on a primitive attribute named _unity_material_.

This attribute can be used in Houdini to separate the meshes. When marshalling the geometry, the name of the GameObject will be assigned as the primitive attribute named _unity_input_mesh_name_. If you want the actual mesh component, the input should be a (GameObjects or Prefabs) that contains Unity Mesh data (specifically should have MeshFilter Component with valid mesh geometry). In other words, if you set the input type to UNITY_MESH, we will marshall Terrain data with default options if it is identified as a Terrain object. Types of Input Objects: Unity Mesh, Terrain, Bounding Box, TilemapsĪll other Input Objects are treated as a special case of the UNITY_MESH option.

Objectinput houdini vex