The stupid decision of Unity to hide required packages used by Obi, but still installed with Burst/Jobs...
sorry for them making it harder to handle the burst backend.

Anyway, I noticed some of the examples have major issues using the burst backend.

Cloth - Wind
Softbody - Barrels
*a few others, assume common issues

These run at best 2FPS+

Something seems broke with the Burst backend in some samples. (most run great)

Is this a known issue?
I can provide more info if can't be reproduced.

Oni backend works great on all the samples.


*system info - AMD 3900x, 2080 Super,64gig ram

Hello.

I have a softbody to simulate like Slime where I have used Volume blueprint instead of Surface blueprint.

Now I have a requirement where small spheres kinematic rigidbodies are spread across the scene and as soon as the Softbody collides with small spheres, those spheres should "stick" to slime softbody.

Anyway to do this?

Thanks.

I have a rope attached at two points, when disabling the rope component or its game object and then re-enabling it, one of the attachments bugs out and is offset by a few meters. How can fix this? Whats the proper way of disabling and then re-enabling a rope?

Thanks

Hello, I want to create a spring rod in Unity but the rod length on the SpringRod scene is too short for me. How can I make this spiral longer? When I bend it with my hand, it becomes very distorted. : /

Hello Guys, I would like to know how much can you squeeze off the Obi Cloth simulation.

See my scene here please: https://imgur.com/UCR0iXP

I am getting 0.3 FPS as soon as the shirt collides with the male.

One static human - 14.5k vertices - w/ Obi Collider
One shirt - 3.2k vertices - w/ Distance and Bend Constraints

Obi Solver - w/ Distance and Collision constraints on 1 iteration value
Obi FIex Updater - 1 Substep value

Yes the shirt is stretching over the man, but increasing iterations / substep values would result into fever frames.
Don't get me wrong, I am not flaming, shaming a neither blaming. I might have a wrong setup, but I cant see where.

My question is, is the 14.5k + 3.2k vertices over the limit? Why does the Stats show 76.4K, there is only an extra plane with 121 vertices in the scene.

Hey friends,

I am not quite sure what I am missing. I followed the first tutorial video and can't seem to get a rope to render. I took a video of what I am encountering. I'd sure appreciate anyone's insight! I am using unity 2019.25 and URP. 

If I make other ropes from the example scenes prefabs, it will come in just fine. But I can't seem to create one from scratch.



Thanks!
KJ

Hello,

I have one persistent ObiSolver and an instantiated prefab which contains several ObiColliders. When I change the prefab during the game (i.e destroy old prefab and instantiate new one in a single frame), sometimes the collisions for new prefab are not working and I got these errors:

Hi,

I really would like particles increasing in number around obstacles. This will really increase performance since the areas far away from obstacles will include significantly fewer particles. Moreover, this will also increase accuracy drastically since the interaction of fluids with obstacles will be solved with much more particles. Is it possible with the latest version? Can ve manually code it? Please see this 2 minutes paper video

Hello, Obi seems amazing, I am considering buying the add-on.
I have one question though.
If I buy Obi Cloth and Obi Softbody, will I be able to simulate cloth on softbodies? and vice versa?

Thank you for your answer

Hey, I've had a look over previous forum questions and have seen some answers that i think are related to an older system with pins...

I have a rope that i'm at runtime I'm wanting to be able to grab...   Previously it seemed like you would do this by creating a pin at the point where your hand touched the rope...

My current approach is to try and find the closest particle to where your hand is, create a particle group at that point, and use a particle attachment to make a connection between that point and the transform of your hand.  

I'm abit stuck though, i can't figure out how to make a particle group at runtime, nor figure out how to specify the location of where the particle group should be. I have a convoluted idea that I could create a particle collision and see where the collision point is...

Very curious if someone has a suggestion on if I'm approaching this in the right direction, and if i am -  how to create a particle group at runtime at the point of collision...