Procedural modelling in Houdini based on Function Representation

More documents

Recommendations

Info

4.1 System overview The core of the <strong>in</strong>termediate layer consists of a set of custom Houd<strong>in</strong>i nodes (see Figure 4.1). They all <strong>in</strong>herit from FRep_Node which forms the base for primitives and operations. At the same time FRep_Node is responsible for travers<strong>in</strong>g the nodes (see Section 4.4.2), build<strong>in</strong>g the FRep tree and outputt<strong>in</strong>g the mesh (see Section 4.4.3). SOP_Node FRep_Node - m_templateList[] : PRM_Template - m_variables[] : CH_LocalVariable - m_attrNames[] : PRM_Name + myConstructor(i_net : OP_Network, i_name : const char, i_op : OP_Operator) : OP_ERROR + getId() : unsigned <strong>in</strong>t + fillParameters(i_entity : ENTITY_BASE_T*, i_now : double, i_srcNode = NULL : OP_Node) : BOOL + fillParametersTransform(i_entity : ENTITY_BASE_T, i_now : double, i_thisNode : OP_Node) : BOOL + cookMySop(i_context : OP_Context&) : OP_ERROR + cookMyGuide1(i_context : OP_Context&) : OP_ERROR - gather(i_now : double) : OP_ERROR - generateMesh(i_node : ENTITY_NODE_T*, i_now : double) : OP_ERROR - retrieveChildren(i_node : OP_Node, i_now : double) : ENTITY_NODE_T* Box_Node CSG_Node Bend_Node Metamorph_Node Sphere_Node Blend_Node Twist_Node Instancer_Node Torus_Node Bounded_Blend_Node Taper_Node Sphere_Sweep_Node Cone_Node Deform_Po<strong>in</strong>t_Node Cyl<strong>in</strong>der_Node Figure 4.1: Class diagram of custom Houd<strong>in</strong>i nodes 15
4.2 Development environment 4.2 Development environment 4.2.1 Installation and setup The Houd<strong>in</strong>i Development Kit (HDK) is part of Houd<strong>in</strong>i and <strong>in</strong>stalled under $HFS/toolkit. All required header files, makefiles and samples are available <strong>in</strong> Houd<strong>in</strong>i Master as well as the free Apprentice version. This project was developed us<strong>in</strong>g QtCreator <strong>in</strong> order to allow deployment to other platforms. The operat<strong>in</strong>g system used dur<strong>in</strong>g development was Mac OS X 10.7. After the <strong>in</strong>stallation, the $HFS environment variable po<strong>in</strong>ts to the <strong>in</strong>stallation directory, which is typically /Library/Frameworks/Houd<strong>in</strong>i.framework/Resources on a Mac. 4.2.2 Makefiles There are several ways of compil<strong>in</strong>g HDK code. Us<strong>in</strong>g the hcustom command-l<strong>in</strong>e tool is very convenient and useful for test<strong>in</strong>g, but also limited to a s<strong>in</strong>gle C++ source file and therefore not appropriate for the library. The alternative is us<strong>in</strong>g Makefiles which are shipped with the HDK and provide sample Makefiles for L<strong>in</strong>ux and W<strong>in</strong>dows. For the Mac, Schmidt (2011) provides a makefile which was used as a base. Additionally, runn<strong>in</strong>g hcustom -e My_Node.cpp outputs the compiler and l<strong>in</strong>ker commands executed by hcustom and offers an <strong>in</strong>sight <strong>in</strong>to the way plug<strong>in</strong>s are compiled and bundled. This is particularly helpful when compil<strong>in</strong>g from console or for debugg<strong>in</strong>g compiler and l<strong>in</strong>ker flags. 4.2.3 IDE Integration and debugg<strong>in</strong>g It is worth mention<strong>in</strong>g a number of best practices that have been discovered throughout the development, especially s<strong>in</strong>ce effective workflows on different platforms us<strong>in</strong>g various IDEs are scarcely documented. Unfortunately, Houd<strong>in</strong>i’s plug<strong>in</strong> architecture does not (officially) support load<strong>in</strong>g and reload<strong>in</strong>g of plug<strong>in</strong>s. Instead, they are loaded upon startup which requires Houd<strong>in</strong>i to be closed and reopened every time a change to a library is made. Dur<strong>in</strong>g the development of the project, the follow<strong>in</strong>g workflow has proven to be most effective: 1. Apply changes to the code and build project from with<strong>in</strong> QtCreator. Us<strong>in</strong>g custom build steps as shown <strong>in</strong> Figure 4.2, make <strong>in</strong>stall can be run from with<strong>in</strong> the IDE us<strong>in</strong>g the standard shortcut. Note that one can also add a custom build step for make clean to rebuild the project entirely. 16
Page 1 and 2: Procedural <strong
Page 3 and 4: Contents Abstract Table of Contents
Page 5 and 6: List of Figures 2.1 Example of a bo
Page 7 and 8: Acknowledgements I would like to ex
Page 9 and 10: Chapter 2 Previous work There are d
Page 11 and 12: 2.2 The Function Representation (FR
Page 13 and 14: 3.1 FRep API Figure 3.1: Full struc
Page 15 and 16: 3.1 FRep API Figure 3.3: FRep tree
Page 17 and 18: 3.2 Houdini Develo
Page 19 and 20: 3.2 Houdini Develo
Page 21: Chapter 4 Design and implementation
Page 25 and 26: 4.3 Using the FRep
Page 27 and 28: 4.4 Procedural fun
Page 37 and 38: 5.2 Animation Figure 5.2: Pengu<str
Page 39 and 40: 5.4 Limitations 5.4 Limitations All
Page 41 and 42: 6.2 Future work 6.2 Future work In

Procedural modelling in Houdini based on Function Representation

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?