Procedural modelling in Houdini based on Function Representation

More documents

Recommendations

Info

4.2 Development environment 2. Start Houd<strong>in</strong>i from Term<strong>in</strong>al. This could also be done automatically via a custom build step. However, the term<strong>in</strong>al w<strong>in</strong>dow is at the same time used for logs and therefore useful to display. 3. Optional: The debugger can then be attached to the runn<strong>in</strong>g application with<strong>in</strong> QtCreator via the menu Debug => Start Debugg<strong>in</strong>g => Attach to Runn<strong>in</strong>g External Application... (see Figure 4.3). Figure 4.2: Us<strong>in</strong>g custom build steps <strong>in</strong> QtCreator to compile and bundle the Houd<strong>in</strong>i library from with<strong>in</strong> the IDE 17
4.3 Us<strong>in</strong>g the FRep API Figure 4.3: Debugg<strong>in</strong>g us<strong>in</strong>g QtCreator 4.3 Us<strong>in</strong>g the FRep API 4.3.1 GCC compatibility Various adjustments to the exist<strong>in</strong>g FRep library (see Section 3.1) were required for it to be used <strong>in</strong> the HDK plug<strong>in</strong>. A dynamic library was built and the code, orig<strong>in</strong>ally developed on W<strong>in</strong>dows us<strong>in</strong>g Visual Studio’s compiler, was made GCC compatible. This very time-consum<strong>in</strong>g task was at the same time necessary groundwork. Hav<strong>in</strong>g a standard-compliant code base then allows for cross-platform development. The orig<strong>in</strong>al library heavily relies on templates and some notations needed to be adjusted <strong>in</strong> order to work with the usually more strict GCC. Although be<strong>in</strong>g platform-<strong>in</strong>dependent for the most part, some platform-specific code <strong>in</strong> the FRep library had to be ported as well. 4.3.2 Custom <strong>in</strong>termediate layer The set of Houd<strong>in</strong>i operators create a custom <strong>in</strong>termediate layer, allow<strong>in</strong>g communication between FRep API and Houd<strong>in</strong>i (see Figure 4.4). These patterns were adapted from the exist<strong>in</strong>g plug<strong>in</strong> for Autodesk Maya (Kravtsov 2011). Furthermore, exist<strong>in</strong>g nam<strong>in</strong>g conventions were kept and pre-exist<strong>in</strong>g standards respected to ensure portability and ma<strong>in</strong>ta<strong>in</strong>ability. 18
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 and 22: Chapter 4 Design and implementation
Page 23: 4.2 Development environment 4.2 Dev
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

Create successful ePaper yourself

Delete template?

Save as template?