Reader
Yesterday we learned that the gap - between the idea in your head and your ability to execute it in Houdini - that gap is everything you need to do in Houdini to actually create your project.
And the skill that lets you cross it is the ability to translate ideas into instructions.
This skill is the secret language that a good artist has to master.
Today, we learn that crossing this gap is done by putting this skill in practice.
Chapter 2 of 3: How To Cross The Gap
Let me ask you something.
Have you ever followed a tutorial perfectly - every node, every step - and it worked exactly as expected? And then a week later you tried to build something similar on your own, and you were completely lost?
Not because you forgot the nodes.
But because the tutorial gave you the answer without teaching you how to find it yourself.
That's the difference between following a GPS turn by turn, and actually knowing how to read a map.
And the reason this keeps happening is simple: the gap between your idea and your ability to execute it is still too wide.
When you follow a tutorial, someone else has already crossed that gap for you.
They broke the project down, made every decision, and handed you the steps. All you did was follow them.
But the moment you're working on your own, that gap is yours to cross.
And without the skills to break a goal down yourself, layer by layer, until it reaches "node-level" decisions, you'll always need someone else to do it for you.
That's what we're learning here. The approach and ability to take any idea, at any scale, and break it down further and further until the next node becomes obvious.
Here's what I mean.
When you look at the spaceship shot from yesterday as a single goal, your brain tries to solve it all at once. And it can't, because it's too abstract. There are too many unknowns at that level.
(in case you didn't read yesterday's Chapter 1, this shot was a spaceship flying through a city shooting down enemy ships)
The fix is to break it down. Not just once, but in layers, until you hit something your brain can actually act on.
So let's take the spaceship shot and do exactly that.
First layer: what are the main stages of this project?
- The environment (the city)
- The spaceship animation
- The blaster effects
- The explosion
Now instead of one impossible problem, you have four smaller ones. Still complex but already more manageable.
Now we'll take just one of those smaller parts, the explosion. And break it down again.
Second Layer:
- Sourcing the explosion
- Prepping the simulation
- Running the simulation
- Post processing the final cache
Four stages again. Each one clearer than before.
Now lets take sourcing the explosion, and break it down one more time.
Third Layer:
- What shape is the source?
- What attributes does that source need?
- How long are we sourcing for?
- Do we need any collisions?
The answers to these questions will start getting us close to “node-level thinking”. And now that gap from before is a little more cross-able.
If we broke it down one more time to a forth layer, we could get to a point where the nodes we need start to reveal themselves.
And specifically, the problems we need the nodes to solve starts to become obvious. Once we know the problem the node needs to solve, finding the right node becomes the easy step.
The goal isn't to know every node. The goal is to learn to break the problem down far enough that the node you need becomes obvious.
This is the skill that separates Houdini artists who feel stuck from the artists who can open a blank file and know exactly where to start.
And the more you practice this, the faster you get at it. What takes hours for you now might end up taking ten minutes once you’ve had 6 months of practice.
So now you have the system. You now know how to break any goal down until the next step becomes obvious.
Once you do this you’ve reached “node level thinking”, and that process alone will save you hours of frustration.
But here's the thing - when you're mid-project and you're stuck, you need some actionable tips to apply this idea yourself.
So tomorrow I'll give you three things you can do right away, so the next time you open Houdini, this system actually sticks.
P.S. My answer to yesterday's question of "what node would you place first?", would be a "Geometry Container", and then the second node I'd place would be a LOP Network.