1 | Introduction

In section 2, we are going to focus on getting our development environment set up so we can then move onto building our procedural system with TOP’s and PDG. If you are familiar with Installing Houdini and the Houdini Engine, you can skip those particular lectures, but it is highly recommended to watch from the “Creating Our First Top Network” lecture and all lectures after that.

2 | Getting the Latest Houdini Build

For those users who are new to Houdini, it is very important to know how to get the latest version of Houdini for this course. We will look at where to get the latest Daily build from the Side FX website.

3 | Installing the Latest Houdini Build

Now that we have downloaded the latest build let’s take a look at installing it.  This will walk us through the installation process as well as show us how to make sure we have the Houdini Engine plugin as well.

4 | Creating a Houdini Project

With Houdini up and running, let’s get ourselves organized by creating a Houdini Project.  This is very important when working with PDG and TOP’s as we will be generating a lot of files.  So we should make it easy for us to manage all those files, by creating a project directory structure.

5 | Create your First TOP Network

Now the real fun begins!  We are going to create our first TOP network!  This lecture will show you the ultimate basics of using TOP’s.  It is meant to give you a gentle introduction to how the nodes works, how the data works, and the overall workflow of using TOPs.  

6 | Quickstart to the HDA Processor

With the general concept of a TOP network out of the way let’s take a look at one of the more important TOP nodes we will be using throughout this course. The HDA processor allows us to plug in HDA functionality to process incoming geometry. This is super powerful when it comes to developing a Procedural level systems as it gives us a way to create tons of functionality with just a single TOP network.

7 | Visualizing the TOP Network Results

If you have been following along so far, you might have noticed that we cannot see the results of the TOP nodes after they cook.  While they are producing geometry, it would be nice to see the results, on a per node basis, after each node cooks.  IN this lecture we will learn how to do just that.

8 | Setting up Unity for TOPS

Now that we have become a bit more familiar with TOP networks in Houdini, we now need to apply this knowledge to our game development environment.  In this lecture we are going to get the Houdini Engine up and running inside of Unity, so we can begin to test our TOP network in the Unity editor.

9 | Testing our TOP HDA in Unity

We are almost done with our complete TOP / PDG setup.  The last thing we need to do is test out our TOP network inside of Unity.  So we are going to bring our TOP HDA into Unity and learn to use the basics of the PDG Asset Link tool that comes with the Houdini Engine.


  • Alfredo _ Brite Bone 1 ヶ月, 1 週間 前  | 

    fantastic, I will study all this material because it is very well explained.

  • Animate4evr 1 ヶ月, 1 週間 前  | 

    Thanks Alfredo! Do let me know if you have any questions! I try to respond as fast as I can. Thanks so much! :-)

  • Sam Bivens 1 ヶ月, 1 週間 前  | 

    Why does the HDA Processor cook so slow? That is like the most basic hda ever and it takes multiple seconds per hda. Just seemed weird to me.

  • Animate4evr 1 ヶ月, 1 週間 前  | 

    Well we are writing the geometry out to files on the disk and loading them back into the scene. This way we have the data on disk as well. For something as simple as a box, you wouldnt really need to use PDG, it was more of an example of explaining how TOPS work with Unity and HEngine. TOPs and PDG becomes very fast and useful when dealing with massive procedural systems. So when creating a PDG system for HEngine, we still create smaller HDA's that produce props or tools for level designers, and then pass that data into our PDG system. It saves a bunch of time since we arent dragging and dropping a ton of HDA's to build a whole level. Hopefully that helps! Thanks! :-)

  • Sam Bivens 1 ヶ月, 1 週間 前  | 

    That makes sense. Thanks for the answer and thanks for the tutorials! I've learned a lot from you over the past year or two.

  • Animate4evr 1 ヶ月, 1 週間 前  | 

    Howdy Sam!
    If you want to bypass the saving of the geometry from the TOP network, then you can use an Invoke TOP node...this will make the geo result in memory, instead of writing it to disk. This will make it fast but you lose the write to disk. So it becomes a pipeline decision at that point. Hope that helps! :-)

  • Bill_Sansky 1 ヶ月, 1 週間 前  | 

    Thanks a lot for the tutorial, really well explained and easy to follow!
    I have the same issue with the time it takes to cook the hda processor node. For me each hda took around 72 seconds to cook, and I'm writing on an SSD drive: could there be a problem somewhere? I understand that there is an overhead linked to the fact that we write to a file, but the files are less than 2kb large: that doesn't sound right to me :D

  • Bill_Sansky 1 ヶ月, 1 週間 前  | 

    Maybe it's linked, maybe not, but I also cannot visualize the result when right-clicking on the task result and selecting View Task Output: it tells me the file couldn't' be found (but it's there, and when I select it manually it works)

  • Animate4evr 1 ヶ月, 1 週間 前  | 

    Thanks Bill! Im glad you are enjoying the course so far! :-)
    With regards to the speed in the HDA processor, try using a ROP Geometry Output to load geometry in dynamically and get around the I/O process. It works just like any other subnet. Double click the node to dive in and start to build out the network yourd like just like if you were working inside of a geo node. You can also speed things up by putting things into compile blocks and invoking them from within TOP's. But I didnt dive into that stuff in this course as it is a bit too much for a beginner course. Take a look at those and let me know if any questions pop up.

    I think that may be a bug with TOPs...the geo file not being found....I have enocountered that before as well. Might need to report it to Side FX. Which node is giving you the issue?

    Thanks! :-)

  • Bill_Sansky 1 ヶ月 前  | 

    Thanks for your answer :)
    I also tried to disable the "Write to geometry" option, and it seems that I was wrong about the I/O: the node cook in roughly the same time when disabling it.
    I will check out those options you mentioned. I also found out that by changing the "Maximum CPU to Use" to something big allows the nodes to be cooked at the same time, which speeds up the process.

  • 3clipse 2 週間, 2 日 前  | 

    Brilliantly explained... Best SFX tutorial I have come across... onto the next part and the fun.

  • Dean Deakyne 1 日, 13 時間 前  | 

    Hi Kenny,

    Not sue what was skipped in the video but I got lost at the point where you were changing the directory in Visual Studio.
    After the failed cook in Unity took place you opened the asset in a new instance of Houdini and opened up the Variables tab.
    Your path in the variables was HUE_ENVPATH_JOB BUT Mine is still set to HIP and nothing that I do changes that path variable.
    What step am I missing? I wanting to create all my assets from scratch so I can follow along, I am not using the project you provided.

    Dean Deakyne

Please log in to leave a comment.