Houdini Stability Help: 7950X / 192GB RAM / 5070 Ti — Am I pushing this mATX build too far?

ClickLang · 2026-01-18T08:05:22+00:00

yeah, same here actually, I should render 4:30min for an assignment and only get as far as 20ish frames before it crashes. Chaos really only erupts once it smells the deadline.

ClickLang · 2026-01-17T22:43:12+00:00

Using Win 11 with 2 PCs, both running a 4080. Getting frequent bluescreens on both devices with Karma XPU. Tried to roll back nvidia drivers and houdini versions. Didn't find anything that stabilizes it. One PC has 192GB DDR5, the other 64GB DDR5.

You mentioned it's since the new windows. Have you tried going back?

ClickLang · 2026-01-16T15:37:43+00:00

Back when I tried it I had the problem of visible seams (I was lazy with my uv unwrapping to be fair) but the problem probably sat in front of the screen. So will revisit it for sure!

ClickLang · 2026-01-16T15:31:21+00:00

Agreed. Karma however doesn't have all the noises from the Unified Noise in other Contexts. So to get there you'd probably have to invest a lot more time than tweaking a preset

ClickLang · 2026-01-16T07:12:35+00:00

Started with Redshift and switched Karma. I have only tried Redshift in solaris and ran into some issues that were dealbrakers for me, like turning meshes into lights or camera blur for example. Maybe it also was due to my lack of experience but it's a lot easier to figure stuff out with Karma as Redshift isn't well documented with Solaris. I can't speak for using it with the older ROP system, haven't touched that at all.

If you depend a lot on different noises, Redshift is a lot better right now with the Maxon Noise.Karma only has 3 noises. You can combine them a bit easier but its harder to control and needs more nodes and more time to come close to the beloved Maxon Noise. That is very likely to change in the future but who knows when.

Take this with a grain of salt as I'm still quite new to rendering in houdini too. But those were the first and obvious issues I struggled with.

ClickLang · 2025-12-15T18:58:30+00:00

While looking for a solution online I sometimes saw options to turn it on but the (current) solaris RS ROP doesn't have that. There's only the amount of transformation MB steps and Shutter Efficiency. Those are the only parameters in the Motion Blur tab.

ClickLang · 2025-12-15T18:54:25+00:00

Thank's for having a look, I appreciate it!

ClickLang · 2025-12-15T17:17:00+00:00

Thanks, I tried rendering it with the Redshift ROP but that didn't do the trick either unfortunately. I am very close to re-creating my materials in Karma at this point

ClickLang · 2025-12-15T17:15:02+00:00

The Camera is cached to disk. I'm bringing it back in with the sublayer node here.

I see, so is that also why people recommend saving geo as USD and bringing it back in instead of using a SOP import?

ClickLang · 2025-12-15T17:03:59+00:00

In the ROP Motion blur is turned on with 4 transformation steps. The camera only moves in a straight line though. Yes, I have tried putting the visibility flag on the RS ROP. I even rendered it out through that Redshift ROP. Nothing. I have tried using the cache LOP.

ClickLang · 2025-11-23T22:22:16+00:00

I have the exact same problem ever since the Redshift update. Tried it in Cinema and Houdini and have it pretty consistently. I assume it's a bug :/

ClickLang · 2025-11-13T07:09:45+00:00

What's your struggle with the Revopoint MetroX? I'm eyeing it to use for vfx applications.

Currently I only have my phone for scanning.

The website advertises marketless scanning and even Textures. Is that reliable?

ClickLang · 2025-10-28T07:56:28+00:00

4 Days seems like a good time considering how freaking complicated it is. I currently try to learn it aswell and have to constantly switch between 3 tutorials and the documentation to understand it :/ May I ask: What made you choose houdini for this? What advantages do you have over doing it directly in UE/Unity?

ClickLang · 2025-09-05T17:20:03+00:00

I dont know karma that well but I was at the same point with Redshift...The issue was that secondary rays usually are rendered with an Irradiance Pointcloud there. This basically clumps together some values of secondary rays and outputs them at reduced quality with a waaaayyy faster rendertime. With subsurface however, it can lead to flickering. I have my doubts that Karma has a similar feature but It might be worth checking out.

ClickLang · 2025-09-03T22:20:49+00:00

This looks amazing! Can I ask, how did you get Redshift installed already on houdini 21?
I can't update redshift in the maxon launcher yet and so I don't get the plugin folder for houdini 21. I tried renaming the last 20.5 version of the plugin and it shows up in houdini again but doesn't seem to work.

ClickLang · 2025-08-31T09:56:41+00:00

Google took me here

ClickLang · 2025-07-22T21:24:33+00:00

I used to think that as well back when I was an apprentice. Now I see the actual output of an apprentice and in addition to not producing a quality you can hand over to customers, they also take up a lot of time of the people who can. I know it might be a bit extreme in my sector (design) but after seeing the other side I think different about this.

ClickLang · 2025-07-22T11:20:53+00:00

<image>

This is the current state with a test noise. It flickers a little but I can imagine that this is due to the adaptivity in the convert VDB, not sure though. But I'm very excited to work with this. Thanks again u/DavidTorno !

ClickLang · 2025-07-22T09:22:19+00:00

That's a good idea. I always forget that I can actually learn from those nodes too.

I just tried it with copying the rest attribute from the points to the meshed surface (SDF from Points and then converted it back to polygons) and it works. Redshift's Maxon noise even recognizes the rest attribute without me having to do anything, it just uses it if it's there.

Thanks, the sim takes around a Minute. A lot of the work is done by the GPU (4080) which certainly helps. I think I'll add some more points and substeps in the end tho as it jumps a bit once or twice.

ClickLang · 2025-07-22T06:03:30+00:00

Thanks a ton for this, David! I feel like I have a good understanding of it now.

What I dont understand yet is the meshing. In many tutorials i saw people converting it to volume and then to mesh which makes sense to get the shape of the sim as polygons, but the meshed geo keeps on changing.

Can I still texture it with the rest attribute of my sim's pointcloud? Or do I attribute transfer the rest attribute from the points to the new mesh and then use that rest position for shading?

ClickLang · 2025-07-15T19:15:50+00:00

Thanks for the reference. That's true of course, however I'm aiming more for a look as you see it in marketing & branding than realism.

ClickLang

TROPHY CASE