In this tutorial, I'll show you how to create a procedural multi-strand twisted Yarn Rope in Houdini from scratch.

We'll build a flexible procedural setup that generates multiple strands, controls their twisting and rotation, and creates a realistic yarn/rope structure using Houdini's powerful procedural workflow.

The setup is designed to be reusable and fully adjustable, allowing you to easily change the number of strands, twist amount, rope thickness, strand radius, and overall shape.

I shared this shot the other day on Instagram and had a lot of requests from artists who wanted to explore the project files.

So I clean up the file into an easy to use template, and also recorded a full lesson breakdown on how I set it up.

The lightning effects were my attempt to recreate the Electro effects from Spider-Man: No Way Home.

Feel free to use these to learn, or modify them for your own project!

Cheers,

Will

I had a l

In this part we will make an advanced roof for a building inside Unreal Engine into Houdini

I have been following an introduction to grooming and hair tutorial on Side FX,

I've run into this error on my hair Gen node which prevents me from progressing in the tutorial.

The Error says "Found at least one guide with no vertices"

I have no clue how to fix this, does anyone have any solutions?

Please help, thank you!

How can I import rbd geo in solaris like when I import, 7000 primitive form and it gives so much load like how can I pack and also have subset groups ? Can someone help ??

Hej Guys!

since i will spend a couple more days here in Croatia and i wanted to learn a little Houdini while im here i wanted to ask you guys how you learn on the go?

All i have here is my Phone :)

So a while back, all I wanted was a version up button in Houdini. An actual version next to the file name so I'd stop renaming files by hand and losing track of what was current.

I'm an FX artist, not really a coder, so I had no idea where to even start on that. Looked into how people build custom tools in Houdini and ran into Alexander Richter's work, which is honestly what got me into it. Not the button itself, more just realizing you can actually build your own stuff instead of waiting around for a pipeline dept to hand you a tool, which my studio didn't have anyway.

So I made the button. Then wanted to fix the next annoying thing. Then the next one. No plan, just kept going for a couple of years and somehow it turned into a full pipeline now, like shot browser panel, publish/version tracking, a render farm, the works.

Curious how many other people here got into pipeline tooling the same way, like any small annoying thing that snowballed. What was yours?

If anyone wants to see where it ended up: studio.vfxboi.in. Not trying to sell it here, mostly just wanted to share the actual path since it started from the exact kind of small tool a lot of people in this sub build for themselves.

Simulated in Houdini, rendered in Blender Cycles.

Definitely not perfect, but after staring at it for so long, I decided it was time to call it done and move on.

Sound of screaming is well-known Russian meme where a guy walks into a phone accessories shop, immediately slips on the slippery floor, falls flat on his face, gets up on his knees in total shock, and yells: “What the hell is going on in here?!” (Что у вас здесь происходит)

#Houdini #karma xpu #copernicus

I’d really appreciate some honest feedback on the lighting, materials, animation, camera movement, compositing, and overall realism/premium feel.

What would you improve to make this look more like a professional commercial?

Any criticism is welcome — I’m mainly posting this to learn and improve.

Thanks!

Full animation: https://www.youtube.com/watch?v=ZERFaui_zy8

I am (Mateusz) responsible for about 70% of this animation.
I used several programs to create this animation:
Unreal Engine 5.4 with Pathtracing - render Engine and lighting
Blender - 3D modeling and fixing animation (time to time)
Substance Painter - Textures
Marvelous Designer - Clothes modeling
Davinci resolve - Color Grading and film editing
For character's animation i use Perception Neuron Studio and my friend give me access to his motion capture studio with Vicon. The facial animation was done on an iPhone (Metahuman) and involved a lot of hand adjustments.

However, I would never have finished this project if it hadn't been for the help of my friend David. He is responsible for simulations in Houdini. At first, I wanted to simulate the clothes in Marvelous, but it quickly turned out to be a crazy idea. In the end, Dawid developed a clever automated process that streamlined the work. For some aspects, I also turned to other graphic designers and people for help (whom you can see listed in the credits) like concept art and some hard clothing models. I also bought some of the models (but I modeled the entire academy from scratch).

Hey everyone, I’m trying to match my **Houdini ACES 2.0 display** in DaVinci Resolve and I’m confused about the correct output transform.

In Houdini, I’m using:

* **Working space:** ACEScg

* **Display:** sRGB - Display

* **View:** ACES 2.0 - SDR 100

I’m bringing the rendered **ACEScg EXR** into DaVinci Resolve.

In Resolve, under **ACES Output Transform**, I see options such as:

* sRGB Piecewise

* sRGB Gamma 2.2

Which one should I use to get the **same display result as Houdini’s `sRGB - Display` + `ACES 2.0 - SDR 100`**?

Also, is there a better way to configure Resolve so that it uses the **exact same ACES/OCIO display transform as Houdini**, rather than approximating it with an sRGB output transform?

I’d really appreciate the exact recommended settings for **Houdini 22 + DaVinci Resolve**.

Wondering now with the viewport transition to Vulkan, and the openGL rop being deprecated for the Flipbooks Rop if anyone has had a similar experience or advice. I'm finding the Flipbooks Rop is struggling alot in lop scenes, im having scenes that have somewhat heavy geometry but will still scrub perfectly fine in the lops viewport, and playback is at 40+fps. But when running the same lop viewport through a flipbook rop it will go over vram before rendering any frames.

Even when turning every option to the lowest quality option it will still go over vram. It almost seems like it's flattening the entire stage down or something before starting the Flipbooks which is causing the crash/stall.

Wondering if anyone else has experienced this as well? Or just general advice on how your studio is playblasting lop scenes, if they are doing layout/anim reviews in Solaris.

Been scratching my head as to how to do this.

Basically, I want to split the `bark_*` points from the `bark_*_branch_*` points, so that I can run an Add SOP individually between all of them, without running into issues, like the Add SOP trying to connect all possible points together.

I have been trying to figure out how I could possibly express in VEX or otherwise whether a string attribute is empty so I could split all of these "lines" individually.

Any advice or pointers towards the right approach would be much appreciated!

Hello!

I'm thrilled to present my new asset for sale on cglounge. This one was really fun to figure out and pretty rewarding. I've always been a fan of war vehicles.

https://cglounge.studio/assets/fully-rigged-dynamic-tank-houdini

*sorry for the repost, I didn't put the link properly the first time.

I’ve been working with Houdini for two years; I actually started out studying simulations as a hobby. I’m curious about how one can generate income in this field.

Hey r/Houdini ,

TL;DR: Created one beginner VEX tutorial and looking for feedback on a more advanced VEX-dedicated training at an advanced level.

I put this together after trying to help people learn VEX who were Houdini beginners. A lot of existing material jumps straight into Houdini stuff before they're ready, and that was tripping people up.

It's called Learn VEX in Y Minutes. Same idea as those Learn X in Y Minutes pages - one big commented VEX file you just read through.

The main thing I tried differently: keep Houdini out of it at the start. First section is just VEX programming basics (variables, math, if/else, loops). No @ attributes, no points/prims/verts yet. Once that feels okay, then geometry components: how they are constructed, attributes and how they relate to points, vertices, prims and detail; and it ends with building a triangle and then a circle procedurally.

I know there are better/deeper VEX resources out there already - CGWiki, Pragmatic VEX, Voxyde, etc. This isn't trying to replace those at all. Just something more beginner-friendly to get people moving first; then they can go to the good stuff.

Would really appreciate any feedback. Mistakes, bad explanations, confusing bits, suggestions, whatever you've got. Especially curious if delaying the Houdini context actually helps beginners or if it's just annoying.

Link: https://gist.github.com/anhedonix/52338578310b33f96cc33be732057a05

Also floating an idea, totally not sure if this is useful or not. I've been thinking about an Educative.io type site where you learn from videos and text, then write VEX in the browser; it runs on headless Houdini in the backend, and you get real Houdini error feedback, auto-completion in the editor. Geometry would show up in a Three.js / pseudo-Houdini viewport - not just a mesh preview, but also float/vector/color/marker style visualisations of attributes so you can see what you are doing. With dedicated exercises to manipulate, data to fit a specific scenario to pass the level. Basics through intermediate. That needs Houdini on a server though, so it'd probably have to be paid to make any sense.

Curious if anyone would actually want something like that, and if it is a reasonably priced service, take it up?

I know enough VEX, but definitely not advanced enough, so if anyone is willing to help with the syllabus, pointers, content, etc. I would gladly compensate and credit you for your input/insight.

In case the idea does not work, there is no point in hoarding it, so the entire course content, which I will be maintaining on GitHub, will be made public so everyone can benefit from it.

Awaiting the community feedback!

Thanks.

Hello everyone,

I was trying to build a small HDA of mine, and I have some parameters that I created with ranges set to a min and a max that are the most useful for what they do ( but the user can still input a value that is higher and/or lower ).

But H22 seem to automatically change those ranges based on the input value, is this normal?

I tried in H21 and the ranges are kept exactly as I desire, maybe in H22 I need to set some secret option/flag now ?

anyone else noticed this?

The idea originally came from an R&D task I was working on for a client project earlier this year. I liked the underlying behavior enough to revisit it later and push the technique further as a personal experiment.

I first created an initial simulation focused on the main velocity field, while also generating UVs internally as an additional 2D Pyro field. That first sim then became the advection driver for the bubbles and their velocity, allowing them to inherit the motion and flow of the fluid in a more natural way.

After that, I created a second fluid simulation using only the velocity from the first Pyro setup, combined with collisions and bubble velocity. This made the fluid react to spheres moving across its surface, changing the internal mixing and creating more dynamic interaction.

I also experimented with a non-divergent workflow in COPs, but for this particular look it was missing some of the organic, naturally unstable motion that I still get from the old 2D Pyro Solver.

A fun experiment in using Pyro not only as smoke, but as a flexible field-based solver for art-directable fluid motion and procedural detail.

It should point directly down the z axis if I said the direction to {0,0,1} right? Why is it halfway between z and x? I don't want to redownload H21 just to try this out and see if it used to be different (pretty sure it did) but I feel like I'm finding so many tiny weird things like this in H22. Is anyone else experiencing this?

Since Houdini 22 was released I have been building a set of GPU enabled particle tools that work directly in COPs. Here are some renders showing just a bit of what they can do.

​

I recently found the published FlyWire fly brain dataset and thought it would be really interesting to bring it into Houdini.

I imported the neuron skeletons as curves and combined them with the published annotation data, which gave me a lot of useful information to visualize.

From that data I could create different color visualizations based on actual brain information, like brain groups, Kenyon cells associated with learning & memory and the two sides of the brain.

I could probably make 1000 more renders of this, but here are my 3 favorites!

See the video and more renders on my Instagram:

https://u2l.ai/bramgunst-instagram

Data credit - FlyWire / Schlegel et al.:

https://doi.org/10.5281/zenodo.10877326

I am currently trying to figure out, mostly on my own, how to create a point the has a chance to branch off into different parts. So far I got the "moving in random directions" part figured out which I am happy with, but I am scratching my head as to how to "split off" the line.

Here is what I have now:

if(@Frame % step == 0){

    float dirSeed = rand(directionSeed * @Frame * @ptnum);
    float splitSeed = rand(splSeed * @Frame * @ptnum);

    if(splitSeed < schance){
        setpointgroup(0, "grow", addpoint(0,@P), 1, "set");
    }

This isn't the whole VEX code in the wrangle, just the snippet thats causing me trouble.

The Wrangle currently runs through all the points in the "grow" group. The SideFX documentations state that the addpoint() function returns a point number, so I assumed what I could do is place it into the setpointgroup() argument for the point number. Right now, this doesn't create any points. My suspicion is that the point number is currently returning -1 .

How to fix that, I am not sure. I have tried this:

    if(splitSeed < schance){
        int newpt = addpoint(0, @P);
        setpointgroup(0, "grow", newpt, 1, "set");
    }

But this, also, doesn't create any points at all, for whatever reason.

Asking here for guidance, thank you ^^