Hi,

I tried to keep the subject short. I migrated my project from Unity 2020 LTS on a Windows 10 Laptop to Unity 2021.2.1f1 on a M1 Mac.

It actually went way better than I though but when I enter play mode I get these type of errors spammed with different call stacks. Here are two examples:

Hi there,

Obi 6.3 is near release and includes many improvements, among them:

- Character cloth scaling support.
- Full-body volumetric softbodies, and overall improved softbody blueprint generation.
- ObiBone.

ObiBone is a new type of actor included with ObiRope. It leverages the technology behind rods to endow character bones with physical simulation, while respecting the original animation - if any. Braids, tails, breasts, tentacles, wings, and other appendages can be easily and efficiently simulated with this component. Supports full two-way coupling with other actors and rigidbodies, surface collisions, and most other Obi goodies.

You can check its WIP manual page here:
http://obi.virtualmethodstudio.com/manua...setup.html

Wait, I already own ObiRope, do I get this for free?
Yes .

What does this have to do with ropes and rods? Why is it not an asset of its own?
Many bone hierarchies have roughly the same topology as a rope: a list of particles attached to each other in a chain-like fashion. Many of its use cases are also similar: a braid or a reptilian tail can be modeled as a rope, you *could* use ObiRope to simulate them but it's very awkward and uncomfortable. ObiBone takes the pain away from this, so in many ways it's an improvement over ObiRope. Does not feel right to make you pay more to "fix" a shortcoming on an existing asset.

I don't own ObiRope, will its price increase in the future as a result of this additional feature?
Nope.

Hi, I'm looking for a formula to get the active number of particles for a given rope. (using actor.activeParticleCount).

I noticed that it only depended on the blueprint and that the formula looked like :

Hello!

I'm currently trying to integrate UMA and OBI Cloth for more realism.
Basically, all I did is detect when I add a ''Wardrobe Item' and then add Obi skinned components with the right blueprint. Btw the blueprint mesh was pre-generated from the slot mesh data generated by UMA so they are the same... For now, there is no painting on blueprints.

Video: https://youtu.be/WdDoFctGanU\

But I have 3 problems:

- At the start, the top cloth is colliding properly with the top cloth but as soon as I change the TOP item the top part is not colliding anymore, all I do is switch the blueprint, do I have to destroy everything and add new components? How can I improve TOP and BOTTOM collision?

- I noticed that I'm getting this error:
   
Is it because the ObiSkinnedRenderer replaces the generated mesh by UMA with the mesh from the blueprint? Do you know how to create a copy of the mesh at runtime so UMA can delete it and it will not cause problems... 

- The sleeves of the shirt are always clipping? I'm not sure why but If I paint low skin radius they will not move as much as they should move. Do you have some tips for the sleeves of the shirt?

The simulation is pretty good, I'm sure that with proper painting will be amazing!! Thank you again for the amazing asset. I can't wait for new updates!!!

I came across this post http://obi.virtualmethodstudio.com/forum...-1205.html, which was posted two years ago, and it says the best method to use is Distance Constraint.

I want to know is that still the way to go for attaching two softbodies together.

And if I want to attach particles within the same softbody, should I also use Distance Constraint?

How will it behave differently if I create a arbitrary Unity Rigidbody as an "anchor" then attach both particles to it using Pin Constraint?

I made a game with an ocean and a whole physical system associated with it.

Is it possible to add forces on given particles in a rope ? That way I could identify the particles under water and add resistance force to them.

I have used the parachute demo as a base of reference for what I am trying to do.

I have what would be considered a kite - large sheet, psudo round(photo attached).

I have tried so many different ways to make this thing behave sort of like a kite.  Like blowing wind into it while its attached to various things(including itself).

One of my experiments is in the photo.

So am I approaching this all wrong because I can't get any of it to work.  Either it sort of floats like a kite but twists and gets messed up or it ends up in what looks like a pool of debris on the ground.

I have been attacking this for weeks now.  I would appreciate any and all opinions or if I should change direction completely.  I just need it to look like a kite - not really fly like one(I can make it fly).

I am now considering using obi-fluid and somehow proxying a mesh to another for the effect.

I don't want to give up but am just about out of ideas.

Thanks,

David

Attached Files

Thumbnail(s)
   

Hi there, in my project I have 3 obi ropes and they share the same rope blueprint. At runtime, these ropes collide with each other. I want to disable those collisions between ropes. I've already tried collision filtering but once I change the category of one control point, it changes on all ropes. Also I saw in some threads, there is a property called "phase", but in my obirope version there is no "SetPhase" method. Is there a simple way to disable collisions between ropes that share same blueprint? Thanks in advance.

Hi devs, I've just implemented Obi Softbody plugin in game. And I don't know how to detect 2 softbody in scene (With others object is not softbody it's work perfect) here is my scripts for object softbody:

Hello again!

https://www.youtube.com/watch?v=Gqkz-JlseRw

I created this pendulum, found that script on the net and refactored it to obi rope.

By the way it looks like very weird. How can I create a more nicer look?

script is here:


public class ObiRopePendulum : MonoBehaviour
{
    [Range(0.3f, 10)] public float moveSpeed = 0.8f;
    [Range(5f, 40)] public float angleScale = 20f;
   
    private float _leftAngle = -10;
    private float _rightAngle = 10;
    private bool _clockwise;
    private CreateObiRope _createObiRope;

    private void Start()
    {
        _createObiRope = GetComponent<CreateObiRope>();
        _clockwise = true;
        _rightAngle = moveSpeed * angleScale;
        _leftAngle = -_rightAngle;
    }

    private void Update() => Move();

    private void Move()
    {
        var angle = _createObiRope.GetSignedRopeAngle();
        if (angle > _rightAngle)
            _clockwise = false;
        if (angle < _leftAngle)
            _clockwise = true;
       
        var speed = !_clockwise ? moveSpeed : -moveSpeed;
        var v = new Vector3(speed, 0, 0);
        _createObiRope.PendulumVelocity(v);
    }
}

and the PendulumVelocity:

public void PendulumVelocity(Vector3 velocity)
{
    /*
    var lpIndex1 = GetFirstParticleIndex();
    var lpIndex2 = GetLastParticleIndex();
    for (var i = lpIndex1; i <= lpIndex2; i++)
    {
        rope.solver.velocities[i] = velocity.ToVector4();     
[/i][i]    }*/
    rope.solver.velocities[GetLastParticleIndex()] = velocity.ToVector4();
}[/i]

I want the lamp swinging always left/right but with a physics correct way.

How can I improve it to a better way? It is now not so good at the moment