Good afternoon, how to find out the tension force or remove the rope tension
There is a character with three ropes, there is the sum of the length of the ropes. In the screenshot, the left one has a length of 1, the right rope is 5. When I start to reduce the length of the right rope, it pulls the character along, thereby lengthening the left rope, I need it not to go beyond the range of its current length, if it comes out, then uncouple, how to find out when it goes beyond the range
   
By this method I change the length of the rope
ropeCursor.ChangeLength(rope.restLength + length)
Below I tried to find out how long the rope stretches when stretched, but unsuccessfully
x = rope.restLength;
y = rope.CalculateLength();
z = rope.restLength - rope.CalculateLength();
If you look at these values, then x = 1, y will range from 1 and above

Hello! My current project uses Zibra Liquids, but recently they introduced a "Pro" version with a subscription fee. The asset itself worked great, but the ability to collide different fluids together is locked behind the Pro version. Which sucks really, as that was something I really needed, and after spending 100 USD it hurts not being able to use it for my project.

So, I purchased Obi Fluids. I played around with it a bit, but I was hoping to get some quick questions answered before digging too deep into it.

My project is 3D but locked in a 2D view. It involves 4 players, each with their own slime gun. Similar to Splatoon in ways. As for questions, again I only played a little bit with the assets so I don't need a "How to" just yet, I just want to know if it's possible. First question, am I able to "launch" fluid from an emitter, depending on the direction it's facing? I couldn't seem to find a way to send the liquid in any direction, other than straight down from where the emitter is.

Other question, in Zibra Liquids they have voids, where if particles hit the void they are deleted. Is there a similar ability in Obi Fluids? The way my current setup with Zibra worked, was that the player had voids attached to them, and if an enemy slime particle hit that void, it would be deleted and added to the total deleted particles. Once the deleted particles hit the limit I had set, the player would be "dead". The downside to that way was I couldn't have particles stick to the players, so there was no visual effect unless I added something janky.\

Thanks! I may have more questions down the road, but I'll do my best to investigate it myself and read the docs. I just need a starting point.

I have an old question and I have the source code,
http://obi.virtualmethodstudio.com/forum...-2422.html

An error occurs with the latest version of obi Cloth (Obi6.5).
I think this error location is due to the difference in versions (this source is for Obi 5.6)
How should it be described in the latest version (Obi6.5)?

Attached Files

Thumbnail(s)
       

unity ver 2020.3.41f1

cannot edit blueprint in unity2020

The scene is blank and I get the error message below

Attached Files

Thumbnail(s)
           

unity ver 2021.3.f1



The front and back are scratched in the cloth sample scene
In the following example scene
・ClothRigidbodyInteraction

Attached Files

Thumbnail(s)
       

unity ver 2021.3.f1

In the following example scene, the mesh is messed up.
・CharacterCloth
・SoccerGoal
・ClothRaycast

Attached Files

Thumbnail(s)
       

  Pasted Graphic 2.png (Size: 24.9 KB / Downloads: 13)

Hello,

I just recently purchased this asset to see if it would be possible to use it for simulating aerodynamics and ran into some performance issues when trying to simulate lots of fluid particles. The low hanging fruit seemed to be tons of GC Allocations per frame in the ObiFixedUpdater/ObiSolver (Using Burst).

The following profiler was run with about 10,000 particles with Collision and Density Contsraints enabled. I did notice that when Disabling Density, the GC Alloc drops quite abit and performance improves.

   

Density disabled:

   

Deep profiler shows that the issue comes from setting the capacity of the List every frame and calling ToArray on it. (I was able to fix this by just using an array instead of a list and only allocating memory when the capacity needed to grow).

   

Here is a video of the scene I was running and what I'm trying to do. Not sure if you have any better suggestions on how I could go about trying to do an aerodynamics simulation (for a high speed boat / hydroplane)?

Hi team,

I already discovered that it's possible to scale a softbody via the scaling solver way.
However, when I do this, many world coordinates change and (for instance) a camera script following the softbody introduces glitches.
Is there a better way to scale (increasingly, grow) softbodies or how do I compensate the glitches of the solver updates?

I hope it's clear what I wanna achieve. Obi is fantastic, but with some specific tasks I run into problems/limitations...

best regards
Michael

I wanna make a kinda stretchy rope obstacle in my game, kinda like boxing ring ropes.

But most of the times if my ragdoll is running fast enough it will pass through the rope, unless i increase its control points thickness to something like 2, which looks just too big.

Any ideas?

Hi, it may be something explained somewhere and I missed it, if so I'm sorry. I did search the user manual and forum for answers.

Turning transparency down makes the fluid go darker till it turns black instead of making it the color set in particle emitter.

I tested this behaviour on clean 3D URP template in Unity 2021.3.14f1, Windows. Almost all settings are default, I only set Opaque and Depth texture in renderer, added rendering feature and lowered the transparency. Fluid turns black when lowering opacity in all sample scenes.

I don't know if it's intended behaviour and how to change it I played around with blending modes to no effect). In user manual transparency example shows fluid turning to the color that was set in emitter.

How can I fix/change it? I want the fluid to be almost solid color, only getting transparent when it's thin (for example ketchup).