Atom

Maybe check out Sohey's bug swarm file. It still works, even in H20.

The Vimeo hip is kind of old. I went ahead and upgraded some of the H14 old nodes to H20 equivalents and added a popnet to implement the escaping particles. Make sure to keep their life low, or they'll build up quickly. Danil's original file did not have an animated source. This version uses MocapBiped3 to drive the effect, but any FBX or Alembic should do. ap_danil_lidar_041824.hiplc

I guess what I see are errors as well. They are annoying, but generally don't impact my workflow. Here's what I see every time I put down a Karma ROP in the /out context.

I agree it's kind of sloppy coding for the current release to generate warning messages. Repeated print statements can impact performance. To a new user, it presents the appearance that Houdini has a bug, or the user did something wrong. Even now, when I create a Karma node, it errors out. It still works, however, so why spit those messages at me? It is possible to disable the console, which might improve performance for your tool. Try setting HOUDINI_DISABLE_CONSOLE=1 inside your houdini.env file? Houdini is like the matrix. I just look past that gobblygook to see what lies beyond. https://www.sidefx.com/docs/houdini/ref/env.html

I worked through the room map setup inside the Houdini 20 help. Here's an example file setup to produce a Karma render using the default room map. I'm attaching the roommap_debug.exr file so you'll have an example of how to create your own room maps. Just remember to preserve the alpha channel on boxes marked S1-S4. It would be nice if SideFX would post a few starter room maps to the Content Library. It looks like there are a few free maps here: (scroll down-free scene) https://wparallax.com/ roommap_debug.exr ap_sidefx_room_map_styles_041424.hiplc

I'll just say it. AMD is a waste of money. You'll find much more compatibility by choosing nVidia. Yes, Karma uses Cuda (like Cycles), but sims default to OpenCL acceleration, which AMD does support. If you're strapped for cash, consider a low end 8Gb RTX card. I'm using the cheapest one, and it works great with Houdini, Blender, and AI text to image generation.

Sounds like a hardware issue. Back off on your overclock multiplier, monitor heat. A recent build I put together, I couldn't get the CPU stable beyond 3.6Ghz. If its a hobbiest build, maybe reconsider applying new heat sink compound or upgrading your cooler.

Locate your RBDPackedObject node, Physical TAB. Right-click on the bold values and choose Revert To Defaults.

Thanks everyone for the suggestions. I think can I make it from here.

I'm trying to create something like this. I'm drawing a blank? Two grids rotating, but they need to loop. Would this just be an animated twist node?

The simplest fix might be to simply special case frame #1. if(@Frame!=1){ if ($FF % chi("shoot_every_frames")){ removepoint(0,@ptnum); } }

You control the point input count. Just use a scatter before the popnet instead of an add to set the number of points per second. Or do the math to alter the expression. $FPS defaults to 24. $SF%24==1 is one per second. $SF%12==1 is two per second.

Try setting the source emission type to "All Points" and try this expression in the impulse activation field. $SF%$FPS==1 By referencing the FPS, you can determine what one second is.

Here's Tomas' original ocean ball to play around with. Another set of links might help you build up the effect. ts_ocean_on_ball - v00.hip

I doubt if a laptop is going to have the hardware to run Houdini. Did you check the requirements? https://www.sidefx.com/Support/system-requirements/