[RELEASED]Physical Bone - Make your bone system colourfully

Community Showcases
1

Physical Bone is a asset that can use bone systems to simulate soft body physics.
It can simulate hair, ragdolls, cloth, rope or other soft bodies.

It supports colliders and wind zones to receive wind forces and interact with collisions(Supports sphere collider, box collider, capsule collider and terrain colliders)
Physical Bone is easy to set up with basic functionality and can generate much more diversified results with some more involvement

Version info
v1.0 First release
New in v1.01
- Fixed bug that cause error when use AddComponent and AddComponent in script at runtime.
- Add functions to setup bones dynamically.
- Add demo ‘DemoDynamicalSetup’ for guide to setup bones dynamically.

Physical Bone on Store

WebDemo
Demo01
Demo02
Demo03

If you have some questions or suggests or found some bugs, please send E-mail to contact@TheNextGames.com, and you can also post a reply here.
We will get to It as soon as possible.

1 Like
2

This is a really nice looking tool.
I’m interested, is there any documentation for the package available to review before purchasing?
Can you define the limitations of this tool and what’s on the roadmap for future iterations?

3

Hi theANMATOR2b
If you need a documentation before purchasing, please E-mail us and we will send that to you.
One thing to note is this asset can not simulate planer objects perfect like cloth, you must to make some limit to the bone(please consult the skirt in Demo01).But we have a schedule to develop a special cloth simulation for bone system.
All in all, we will make performance of this tool more realistically, and can simulate more type of soft body.

1 Like
4

It’s problematic to add physical bones at runtime. Just doing AddComponent() will cause several errors. You need to manually go in and fill arrays. It would be neat if that was handled automatically.

Also, foreach-loops are used by this asset at runtime, which is bad. Foreach-loops cause garbage, so for-loops should be used instead.

It would be a good idea to namespace this too, so the global namespace isn’t cluttered.

Other than that, great asset.

1 Like
5

Hi SunnySunshine
Thanks very much for your suggestions.
We will solve that as soon as possible.

6

Great!

Actually, I am wrong about foreach. It seems foreach over arrays is OK.

Please see:

However, over collections it’s not OK:

So if PhysicalBone only uses arrays foreach it is alright.

7

hi! Can i attach in a easy way the bear to the end of rope?

8

Hi sirio21
You can just attach the bear to the end of rope by a new script at present, I’m sorry for this.
But we will add this function as a option that could attach any object to a bone in a later version.

Here is the simple script code for reference.

using UnityEngine;
using System.Collections;

public class Attach : MonoBehaviour {

    public Transform endofRope;
    public Transform bear;
    public Vector3 offset;

    void LateUpdate () {
        bear.position = endofRope.position + offset;
    }
}
9

Looks like it couldnt control the softness?:wink:
Just want something like damping, elasticity and stiffness to control the softness
I’m glad to have it if this component has been finished:)

10

Hello

I am sugikami

Your aseet

Using this app

I want to suppress the shaking of my hair

Is there a way?

11

Hi, does your asset work with physics forces?

12

This asset is good but it is not performant for high number of bones / colliders. The author set up a limit of max 500 bones, but that can be changed easily if you’re a coder.

But saying that, having only 50-100 bones & colliders already eats up FPS a LOT.
For 20-30 bones it still performs ok, I still to manage to hit 100 fps. Adding another 20-30 bones drop it to 50 fps. Close to a hundred bones and the my games chugs along 10-15 fps.

Hopefully the author can optimize it in the future. I implemented my own fix and managed to gain about 40 fps more, now I can have 50++ bones & colliders at 80-90 fps.

13

Someone asked how I made the performance gains from my previous post, so I’ll share it here for others.
Hope this helps.

WindZone

In PhysicalBoneManager.cs

There’s a GetComponent<WindZone> in the update loop. Move to it to start. It’s not necessary to get component every frame.

== null checks

The biggest performance gain can be made here.

In PhysicalBone.cs, PhysicalBoneBase.cs & PhysicalBoneCollider.cs.

Replace every == null check with:

bool isNull = ReferenceEquals(someVariable, null);

Manual vector3 operations

In PhysicalBone.cs, PhysicalBoneBase.cs & PhysicalBoneCollider.cs.

The most tedious, but you can also gain quite a number of fps here.
For every addition, multiplication etc2

Instead of vectorA + vectorBdo

vectorA.x += vectorB.x;
vectorA.y += vectorB.y;
vectorA.z += vectorB.z;

For hundreds of colliders

This changes the usage workflow, so thinks if it’s really necessary.

PhysicalBoneCollider.cs loops through all the colliders, at all times. So you’re wasting CPU time here on bones that doesn’t even collide.

I made every child in Bone Attributes have its own collider. Use sphere collider because it’s what PhysicalBoneCollider uses.

I also made PhysicalBoneCollider have Unity colliders + kinematic rigidbody + no gravity.

Do a collision check in OnTriggerStay & OnTriggerExit for the custom unity collider.

In the for loops, I made sure that the PhysicalBoneCollider only checks if any custom bone collider is colliding with it based on layer specified.

Now you can have hundreds of colliders with no performance loss.

Editor Performance

PhysicalBone.cs uses custom inspector for BoneAttributes. It’s not performant as in every redraw if does a whole lot of loops & variable referencing that is very resource heavy. (I think it uses .Net reflection? Might be wrong.)

I moved BoneAttributes into a custom class and just uses the default drawing behavior for the inspector.

Now your editor won’t freeze every time. You can also do multiple component edits like this, very useful if you have hundreds of bones and you need to freeze certain child.

Referencing x4000 review on the asset store:
Implementing my fixes above, I can manage to just use a single PhysicalBoneManager.
In Start, do a find components for PhysicalBone & global PhysicalBoneCollider.
Voila, all bones share the same colliders with no performance loss.

1 Like
14

Hi! I have a problem with this asset. After finding a configuration that looks good for my character, it only works well when facing its initial direction. When I press Play I can see it working well and I can run and jump and whatever and the hair looks awesome, but when I turn to a different direction (specially when facing back) the hair becomes totally deformed until I turn again to face the initial direction of the character. If I rotate the character in the editor before pressing Play it works well, so the initial direction works in any direction, but allways gets messed up when turning arund. If that helps, for some reason even the bone axis direction of my model joints and the ones in the demo character are the same, I need to set the Bone Axis in the Physical Bone script to X Reverse instead of Y in order for it to work with my model (but with the problem said above).
Any ideas?
Thanks in advance!

15

Is it possible to suspend a rope on two ends with this asset?