I'm trying to make a simulation of many sphere-shaped cells that swim around and squish into each other, with each sphere being a Softbody actor in a single Solver. Ideally I'd like to be able to change the size of a single cell during runtime, for instance if one eats a food particle it will bump up in size slightly. The bigger cell would push other cells out of the way as it takes up more space.

I did see one other post on the forum saying that scaling the actors is not possible, but I'm wondering if there's any potential workarounds? I figured that spheres are a lot simpler than a detailed mesh, so it could be possible to achieve the same effect somehow through a force, constraint value, modifying blueprint, etc., but I'm not familiar enough with the plugin yet to know what to try.

Does anyone know how to achieve something like this, or have any ideas for things to try out? Or is this not possible? Thanks!

First, I want to use Obi particle as a way to shoot things > collect contacts > do gameplay things like apply damage.

But when I use the Obi Emitter, I see there is really heavy limitation.
It only has a speed value, albeit having a lot of shapes to spawn from, it still cannot do things like shoot a particle(s) with a target velocity.

The speed value tied to both spawn rate and particle speed.
That is: low speed value will spawn less particles, and the spawned particles also have less speed.
Big speed value will spawn more particles, and they fly with high speed.

This is not good, this leaves a hole where we want a low particle spawn rate, but travel at high-speed.

So can you consider add a scripting API that does Spawn(int count, float velocity);
Thank you!

Edit: Anyway, I think I should forgo this idea about using particle > collect contacts > do damage thing, this is better task for shuriken since it has no limit in collision size.
Obi particle can't have big size as I just tinker with the Granular blueprint, and found out that it can only go as far as max 1.

As shown in the video:
20 softbodies + pool = 5ms.
but 2 ropes + pool = 30ms 
So I think this is a bug.
package: https://drive.google.com/file/d/120oZvq9...sp=sharing
Note that I do not pack the [Graphy] into the package.
scene: Assets/Spike/Scenes/Test OBI.unity

This maybe because I enabled all the constraints there is in the solver, making the simulation more complex than needed.
I know there is a recommend on the website that you should disable all the constraints you don't use to save performance, but to make use of
all the Obi actors, let them interact with each other, shouldn't we have to have a Solver with all the constraints On?
I plan to make a game world with only one Solver, and as my Player run around, I'll add / remove actors into that one Solver as they go into near Player range.
Is this a good setup?
If there is more good practices to setup game world with Obi world, pls tell me, thanks!

Hi, pls take a look at this video



package: https://drive.google.com/file/d/1WNSuRz9...sp=sharing
In this you will find the scene: Assets/Spike/Scenes/Cut the Rope.unity
In the scene you will have the rope cutter object Rope Cutter with script RopeCutOnCollide.cs
and the masterSolver object with script ObiContactDebug.cs

First part of the video, everything is fine, the rope cutter can cut rope at exact element.
But when it hit the softbody ball, it also treated as hit the rope.

Hi, I'm very close to achieve greatness 
The target: I want just the positions that the ObiParticleRenderer script is getting to render those spheres.
If I go to the solver and get the positions, the result is all the positions of particle in the solver, including non-active particles.
Which explains the bad effect in the video, we have many particles that just lying around.

Unity 2022.3.16f1 URP14, VFX graphs + samples installed.
Script and scene in this package: https://drive.google.com/file/d/1mmDuFSi...sp=sharing
Scene: Assets/Spike/Scenes/FireBreath VFX and Fluid.unity
Script: ObiVFXRenderer.cs

The script will set positions buffer to VFX graph through GraphicsBuffer, since there is no computation here, so no ComputeShader is needed.
All it need is correct positions that are same as the ObiParticleRenderer is using to render the spheres.
If this is doable, then I can have fireBreath effect that can collide with environment and damage character using Obi collisions.
The fire effect should match the particle 100%, so I can't use advection.

I have a scene in Unity that uses Obi Fluid. The flow of the fluid can be controlled by rotating the Obi solver's gravity vector in response to WSAD (or the gyroscope input when running on a mobile device, which I haven't tested in the new version but which worked in the old). Note that changing the gravity vector is more convenient programmatically than rotating scene objects because it means I can more easily use a generic script. It also seems to be more stable than rotating geometry.

This all works fine when using `Obi Fluid v6.0.1 in Unity 2021.3.31`, but no longer works using `Obi Fluid 6.5.4 in Unity 2022.3.28`.

In the old version, I set the gravity vector in the `void Update()` method using

When I use ObiBone with my blender model, all bones are clustered together. How can I fix it?
All parameters are same as sample's(CharacterTentacles).
When I use Mixamo's models, everything looks normal.
Is there any specific requirement for obiBone in terms of model setup?

estoy usando el ejemplo de RollingFriction y lo que hice es usar mi modelo de un grano de elote el cual lo tuve que escalar 100 en el Scale Factor. luego tengo el modelo de un Vaso el cual tiene un MeshCollider y la opcion de Convex activado



Pero cuando le ejecuto el programa los granos salen por debajo del vaso


también cuando termina de emitir los granos estos quedan flotando no se quedan juntos como en el el ejemplo de RollingFriction que todas las piedras quedan juntas.




Aquí se ve como quedan flotando los granos dentro del vaso aunque afuera si estan juntas, según yo deberían de quedar en el vaso también juntas como si se tratara del ejemplo de Granular (no use granular porque ese solo dibuja circulos ) y el RollingFriction se parece al granular pero usa un Modelo3D





   




que estare haciendo mal, porque yo solo modifique el modelo de Rock por mi modelo 3D de una Grano?

Hello, I'm trying to do something seemingly trivial - to cleanly delete an object with an ObiCollider and not have my pin constraints blow up - but apparently it's complicated.

I'm creating these pins via scripting, following examples from the documentation. The pinning works fine until I destroy a collider in my scene. When that happens, my console starts getting spammed with the following: