Good you can use curves. Mine here always crash

For less content, SideFX and more fixes!

We have no viewport color customization easily, many other things in viewport gives us crash.

We're on 2023 and the error still exists. What a shame SideFx

For me, this error is gone when I check the camera I will use in the karma node. I don`t know this tip would help, but I think it is important to say.

You have to specify which kind of camera you are using, because it is set up the "cameras/camera1" by default.

OneBigTree

dlee
Hi. Karma does not yet support shadow matte or have a shadow catcher. As a workaround you could output shadowed and unshadowed AOVs and take the difference to generate a shadow pass in comp.

Still no solution in 19.5?
What's the holdup?

Create a matte geometry, so add an extra AOV on Karma settings. You will see the shadow pass in mplay

Maybe in 5 years

cwhite
You'll want to either turn off the Limit Particle Speed to Gait Speed Range on the Crowd State DOP, or increase the Allowed Variance parameter accordingly. This is what was preventing the agents from slowing down to a stop.

Then, on the crowd solver you can either decrease the minimum speed at which orientation changes are allowed to occur, and / or turn off the option to constrain the velocity by the max turn rate.

What do I do when using locomotion?

JoshFoster
Hey guys,

I'm hitting a mental road block trying to understand how to rotate a particle around its velocity axis with a POP Torque DOP. In the attached file I've set a force and defined an orient attribute with Z aligned to its velocity. On the POP Torque there's an option labeled "Axis Relative to Particle's Orientation." The description of this option says, "The provided goal axis will be rotated into the particle's own reference frame. Thus a value of (0,1,0) will be up in the space of the particle rather than in world space."

I figured enabeling this option would allow me to set the Axis parameter on POP Torque and it would look at the incoming orient attribute before determining the final rotation axis. However, when I feed in an orient attribute it doesn't even rotate at all.

In the file I've also included a separate setup (to the right) showing what I'm hoping to achieve with the POP Torque node.

Any insight would be appreciated!

Hope this helps someone, but for me, I had to use a rotation matrix after the simulation. If you want just randomize it, you can set an attribute randomize (rot) and you will have the particles rotating.

Faitel
It seems we should report it as a bug.
Temporary you can use non-uniform scale in LOP camera parameters to get similar effect but it will work only with manual camera animation, not with path constraint for example (at least without attribute hacks).
Also, even if it will be fixed, it will work only in render time, same as other karma tab parameters, so I think ortho camera requires farther development and maybe an RFE.

Seems like SideFX didn't fix this bug.

I think it's time for them to fix things instead of releasing new ones.

I made all these things and nothing changed. So I started to test the "render curve as" to see what is happening. I've created a pscale attribute in object level and set it to 0 with a wrangle after import to Solaris.

So the weird spheres disappeared.

Andy_23
Hello,

I have many curves I bring into a stage, they have a pscale attribute to vary width/thickness along the curve. I'd like to control that in my scene graph but can't figure out how. If I apply a basis curve width property I can change the width on the fly, but it's uniform along the curve.

Is there a way to use pscale as basis and multiply from there? Something along a wrangle in my scene graph?

Click on geometry and in the scene graph properties tab right click on width attribute and set it to edit. The Edit property node will open, so you can edit it in Solaris.

Enivob
What I have done, is to generate a goal point per-agent. You need a walk state and an idle state. While the agents are walking, the Use VEXpression code set the goal for each agent, causing them to approach a point in the logo or design. A crowd trigger measures the distance between the goal and the agent. After a threshold is crossed, the state is switched to idle, indicating arrival at goal.

This is an older scene, but it might get you going.

Image Not Found

Thank you so much!

Took me much time to find this!

Walter How
Anyone ever figure this out?

I have the same problem here. Agents going through each other, even though avoidance AND separation forces and weights are turned up high.

I figure this has something to do with agents not slowing down at all and simply running through the agents in front of them. If this is the case, how can I get these agents to slow down?

This is why many Seniors had to work until lose their lives. Not many people wants to help and share learning...
We're still lucky for having the moderators here for helping in some cases.

I have the same problem here and more: All other nodes including ostacles and forces doesn't work.

Konstantin Magnus

Nathan Apffel
Its hard to believe that these are the best solutions in Houdini for extracting a curve from an edge.

Houdini is a toolbox, not a toy.

This is why the Houdini artists lack of creativity.

yeatshai

WillA

Sammer1
Hi WillA,

It sounds like what you might be looking for is 'Current Operation' in the Parameters pane. When the Curve SOP is selected and you are in edit mode you can enter values and move relative to the current position. (Either select points in the view scene view and then enter the value or enter the point # and then the value)

I hope this is helpful,

Sam

I would like to be able to type in the actual coordinate value.
For example, I want to make sure that certain points in a curve are a specific Z value.

A somewhat cumbersome method, select the point in the view, press the K key, right-click on the handle, select move handle to world origin, and enter the absolute position value in the parameter on the right.

Another more concise method is to set the absolute position value you need in pivot translate in curve sop parameter, and then set the current operator scale to 0, then press enter.

These kinds of things make me miss XSI...I'm trying to animate points for a tracked camera and the transformation always reset to 0.

jsmack
Why not use the name attribute to split the geometry into multiple mesh prims rather than use geometry subsets? The name sop can create names from existing groups. I've found geometry subsets sometimes have funky behavior with materials bleeding from one subset onto another.

When you have more than 300 pieces imported from a modeler that didn't name all, it's kinda hard. That's why assign by groups is good

Hello everyone,

I started to work on a studio a few weeks ago and I faced a problem with my python 3 version of houdini. Also, I had an another error on Shotgun related to a utf-8 code.

I'm going to show both because something asks me that they appear for probably the same reason.

Shotgun error: UnicodeDecodeError: 'utf-8' codec can't decode byte 0xed in position 148: invalid continuation byte


Houdini error: File "C:\PROGRA~1\SIDEEF~1\HOUDIN~1.745\python37\lib\threading.py", line 926, in _bootstrap_inner
self.run()
File "C:/PROGRA~1/SIDEEF~1/HOUDIN~1.745/houdini/python3.7libs\houdinihelp\api.py", line 590, in run
indexer.update_with(w, pages, overlay=True)
File "C:/PROGRA~1/SIDEEF~1/HOUDIN~1.745/houdini/python3.7libs\bookish\search.py", line 486, in update_with
writer, pages, update_paths, needs_delete=changed
File "C:/PROGRA~1/SIDEEF~1/HOUDIN~1.745/houdini/python3.7libs\bookish\search.py", line 516, in index_paths_with
for doc in self.documents(pages, path):
File "C:/PROGRA~1/SIDEEF~1/HOUDIN~1.745/houdini/python3.7libs\bookish\search.py", line 417, in documents
jsondata = pages.json(path, postprocess=False)
File "C:/PROGRA~1/SIDEEF~1/HOUDIN~1.745/houdini/python3.7libs\bookish\wiki\wikipages.py", line 607, in json
self._pre_pipeline.apply(jsondata, wcontext)
File "C:/PROGRA~1/SIDEEF~1/HOUDIN~1.745/houdini/python3.7libs\bookish\wiki\pipeline.py", line 118, in apply
v.apply(block, context)
File "C:/PROGRA~1/SIDEEF~1/HOUDIN~1.745/houdini/python3.7libs\houdinihelp\hpages.py", line 327, in apply
self.apply(subblock, context)
File "C:/PROGRA~1/SIDEEF~1/HOUDIN~1.745/houdini/python3.7libs\houdinihelp\hpages.py", line 323, in apply
self.text(block, context)
File "C:/PROGRA~1/SIDEEF~1/HOUDIN~1.745/houdini/python3.7libs\houdinihelp\hpages.py", line 343, in text
value = self._parse_opdef(context, value)
File "C:/PROGRA~1/SIDEEF~1/HOUDIN~1.745/houdini/python3.7libs\houdinihelp\hpages.py", line 287, in _parse_opdef
table, nodetype = nodetype.split("/")
ValueError: not enough values to unpack (expected 2, got 1)

If someone can help me I will be grateful for this. I've already reinstalled my windows to see what is happening

Thanks so much. Sometimes the artists here thinks that we are lazy, but focused information is really hard to find.

First, thanks to answer!!

I realize the pieces name changed to @name prefix, but the last thing to do I didn't get well.

The first thing I thought is to randomize those groups to get the result, but I'm not sure if it is work.

It's like you know what to do, but don't know how hahahha

Also, I could see that all geo disappear from points when I choose one of the group “name”

Hello people!!

Hope you all alright!

I have a noob question about copy different geometries to a point without using VEX (I just have 2 weeks of learning and I'm not
ready for VEX yet).

I'm trying to model a river cliff with some uniform rocks using voronoi fracture and transform pieces. However, every single time I made this, the whole fractured model goes to the scattered template.

Need some help, because I can't find anything on youtube

Thanks!