Hello @i_mazlov ,
As I mentioned, as a developer I am trying to provide to users the option of newly added Simulation system to use it in the my ragdoll plugin. Ideally, I want to use the new trigidbody tag in my code the same way as I use the old Bullet Dynamic Body now.
But I can't understand how to do instead of this:

BaseTag* const DBtag = BaseTag::Alloc(180000102); DBtag->SetParameter(ConstDescID(DescLevel(RIGID_BODY_SHAPE)), 11, DESCFLAGS_SET::NONE);

this:

BaseTag* const DBtag = BaseTag::Alloc(trigidbody); DBtag->SetParameter(ConstDescID(DescLevel(???)), ???, DESCFLAGS_SET::NONE);

As I mentioned above, for a ragdoll I need a compound collision shape. Where the top of a hierarchy is a joint object and it owns the trigidbody tag. The second level of a hierarchy is the child mesh object - it represents the shape of the joint. In the settings of trigidbody tag I want to set it as a Compound collision shape. And then connect these nodes via Connectors to create the ragdoll structure.
So my question is:

is my desires are possible on this stage of provided simulation engine? if it does not, then is it in plans to add it in the near future? Because this option already exists in old Bullet tag.

Hi @m_adam ,

Thanks for your reply, it worked well.

But I still have some doubts about the usage of Node Path, such as how to calculate the port through NodePath instead of concatenating strings (which can easily lead to misoperation).

There are few examples and answers for NodePath on the forum, and it seems that people rarely use it. Do you have any insights on this, or in other words, what usage scenarios do you think NodePath is more suitable for.

Cheers~
DunHou