bentraje

You are near there. Just move the 5 pole vert much closer to arm pit.

@BlastercastG

Reset the points before you used it with the cloner.

In the weight manager, Just lock all other joints except the joints you are working with.
Then hit apply all to the selected joint (i.e. joint C) you want to merge. This will effectively transfer all other unlocked joints (Joint A and Joint B) to Joint C.

I would just use `op.GetRad()`.
Be it noted that if you want to get the whole size you need to multiply it to 2 since it is only getting the "radius".

@Vitaly Anikienko

Yep you can. Normally, I'll just python this but I guess you can just hijack some nodes.


cube_instance.c4d

Classic. Just discovered how to solve this after posting the problem.
Basically, just disable the Use Available option in the Hair Material Tag.

 

The dirt node is just a layman terms. It doesn't really provide dirt per se. It's technically a curvature.
So in redshift it is called curvature node. You can also use AO node on top of it.

Hi @pilF

I'm answering the question for reference. Just in case sometime in the future another member encounters a problem.

RE: So, now the face rig is transform constrained to a newly created child of the BD_Head_int? But that child does not have the same position as its parent. Does the position not matter?

Ah what you have described is the "parent constraint".
There's no default parent constraint in C4D. In Maya it is default as part of its constraint.
I just recreated it manually.

The way it is necessary compared to the position and rotation constraint is that it respects the orientation space of you are constraining.
Previously, you have rotated the body head control to the back, but the face head control rotates to the front or something not 1on1.
that's the problem. Parent constraint solves that.

Have you tried the project asset inspector?
 

By default, it is already reset.
Like when you add a transform node, all the transforms are already at default. Position, 0 0 0. Rotation 0 0 0. Scale 1 1 1.
Even if your base mesh have a scale of 1, 10, 5 or have the default 1, 1, 1. The transform node's behavior is the same.

@Marc Trzepla

RE: apparently it blasts over and ignores the key
The trick is unticking the "Overdub" parameter. By default it is ticked, so it overrides any existing interpolation.

Have you tried enabling the Redshift top bar?
In the top bar, you have the same commands.

@Igor

Thanks for the response.
I got also a reply from Konstantin.
It's a work around but it works.

https://procegen.konstantinmagnus.de/height-field-erosion-on-meshes

 

@srek
Unfortunately, I'm still at R21 so I can't use capsules yet. That said I asked a friend to check it out. And it seems like that's thing I'm looking for.

=========

Anyhow, found a solution with the help from slack.
Basically, 1) Use a Shader Effector set to visibility 2) Use either Terrain Mask or C4D Fall Off Shader

Works as expected 🙂

Got a response from odforce forum.
Basically just use "straight_skeleton_2D" node.

Works as expected! 🙂

After some shower thoughts, I found a way to solve it. It was simple that I feel stupid not going this route the first time around
Instead of using 1 bend deformer. Just use two. Done deal.

 
uber_bend.mp4

After watching several YT videos, I can conclude that there is no such thing.
That said, you can still execute external python scripts in Houdini. You just need to import them.
It's a bit cumbersome but it works.

Check the Modules on Disk section on this page.
https://www.sidefx.com/docs/houdini/hom/locations

With the help of madebygeoff from odforce, I was able to come up with a working prototype.
I know the problem is trivial but might come in handy in the future.

Here is the working file:
 
weight_based_on_attributes_group_v1.4.hipnc

@pfistar

No, you are not missing out. It's the limitation of Redshift materials not completely integrated into C4D, even though they are already been under the same company for some time now.

Not going to rant in the forum again with Maxon/C4D/Redshift.
 
But with regard to your question about playbast. I can confidently say, the hardware/software render is the equivalent. (i.e. rendering what you see at the viewport).