Forums

In my Houdini Solaris scene, I have three cameras with different frame ranges: cam1: frames 48–96 cam2: frames 24–140 cam3: frames 120–200 I want to render them sequentially (one after another) using Karma — but all in a single render submission. In other words, I want to press “Render to Disk” once and have it automatically render cam1, then cam2, then cam3, each with its own frame range and output path. Is there a way to set this up directly in Solaris without having to manually render each camera separately?

Segmentation faults are generally hardware related. Perform a surface scan on the drive your installing Houdini on. If you are overclocking a motherboard, visit the bios and drop your CPU multiplier down 0.5 or one step. Don't overclock ram.

What is this fatal problem? Please help. 6156: Fatal error: Segmentation fault Saving application data to

Small update. I've made sim only around paddle. Model is scaled up 2x from the proper, original scale. I've multiplied velocity by 5x. There is 20mil points in this square sim. There are some ripples, although tiny and only around paddle. So I assume I would need a 1billion point simulation on my whole region to get proper dynamics? Something seems off. 25mil.mp4

Hi! I’ve been struggling with a water simulation for over a week now. I have a boat animation, the boat itself is 4 meters long. I export the whole simulation as an Alembic to Blender afterward (that’s just the workflow, can’t change it). To create the simulation, I’m using the Guided Ocean Layer from the shelf tools as a base. I resize the tank, crank up the particle separation to get around 20 million particles, and here’s what happens: proper_scale_grainy_sim_PS_0.0065_27mil.mp4 The water surface has a lot of noise, so when I mesh it, it looks like this: I have to increase the particle radius scale to 2.0 just to make the surface look somewhat smooth, but that makes the water around the paddle look like jelly. Of course, I can apply filtering and smoothing. I even tried using Delta Mush to smooth it out but then I lose detail in the collision areas, whether it’s the paddle or the net I later drop into the water. And even with these operations, the water surface still ends up with little dots on it, making it look like it’s lightly raining.   If I scale the whole simulation, including the collision geometry, by a factor of two (adjusting the particle separation so that the domain still fits around ~25 million particles), it slightly improves the situation, although not much (visualizer is cranked up here compared to the first one so it might not be obvious): The surface no longer has that heavy grain. However, another issue is the lack of proper water interaction with the collision objects. There are no ripples spreading across the surface from the paddle. What I’m aiming for is the look of a boat gently moving across a calm lake surface: scale_2x_no_paddle_detail_18mil.mp4 If I scale everything up 5x, the water surface in the simulation becomes much smoother or more precisely, the velocity field is smoother. The dots disappear, and the mesh instantly looks better: 5x_scale_flip_smooth_surface.mp4   I also get visible waves spreading from the paddle on the water surface. But now everything looks like it’s in slow motion because, well, the boat is now 20 meters long.   5x_scale.mp4 This is still nowhere near good, you can see grain on the surface, but interaction with collisions are much more dynamic, fluid, than in the smaller, proper scale (also waves are too high here, just a side note). So my question is: for a simulation on this kind of scale (around 4 meters), where I want subtle water movement on the surface but also nice ripples spreading out, I shouldn't be using flip sim? How can I correctly achieve that effect? I'm honestly exhausted. Watched dozens of tutorials, asked in many places, waited around 60 hours for all these sims and I still can't get it right. Even thought about buying LiquiGen of FlipFluids for Blender...   This is the look I'm aiming for (with throwing a net later on in the same scene, so I guess ripple solver isn't a solution here? [made in Veo3..]): veo3.mp4