Nicholas Ralabate

Ok, got it... I'll probably just go back to making the prop part of the rig for now. Thanks!

I am trying to prototype some NPC behavior for a videogame using the crowd solver and am a little stuck on a simple task.

The behavior is this, like patrolling:

Monster is spawned at spawn point spawn_point
Monster picks a random patrol_spot r units away (on a circle)
Monster walks to patrol_spot
Monster gets to patrol_spot, it hangs out for a sec, then returns to spawn_point
Monster picks a new, different, random patrol_spot r units away (on a circle)
Monster walks to patrol_spot
Etc...

Using the simulate template on the shelf, I wired up the states triggers and transitions... but I am a little stuck on what I should be using for spawn_point and patrol_spot. The options are SOP and DOP Object.

If the patrol_spot is a SOP, wouldn't I have to animate that SOP? How would I know when to animate it? Would I do my own tests, in SOPs, for agent proximity to the patrol_spot?

And if the patrol_spot is a DOP Object, what does that even mean? What kind of object would that be?

If anybody could point me in a direction (ha) or let me know if there is an existing example that does this I would be very greatful. I am very much looking forward to prototyping NPC behavior in Houdini instead of hopping in-engine.

Hi, I am trying out the APEX Scene Add Prop SOP and I notice that it re-names the singular joint to "Control". Is this customizable?

I am having to manually rename things before exporting them to GLTF, otherwise my joint name in the static skeleton doesn't match the joint names in the animated skeleton (since the SOP is renaming one of my joints to "Control").