What would be the best approach for acheiving a HD sdf collision map close to the player? I would love to reach a resolution of 1-5 centimeters (in a VR setting).

I'm working on a smooth voxel system with detailing through tesselation and displacement. Next up for me is generating this HD collsion map but I'm stumped at finding a solution here.
So far the implemented process is:

1. Have a low resolution SDF field
   
2. Generate mesh from SDF
   
3. Unwrap mesh UV's and apply virtual texturing
   
4. Use tesselation+displacement when rendering. It now looks HD and photorealistic!
   

Hi!

I've added some explanation/tips about mass to the manual:
https://obi.virtualmethodstudio.com/manu....html#mass

This is a common topic that pops up in support very often, so I tried to condense the top 3 takeaway points.

any feedback is welcome!

kind regards

I need to reset the rope to its initial position. My rope is attached to and object and I have moved that object. Now when I reset my object back the rope swings all the way back due to solver and physics. I just want to reset the rope as I reset my attached object. I'm currently using the solution I got from this forum

Hello

What I want to do is really simple but I couldn't solve it because I'm a beginner. To tie the ship to the land with a rope. I create an obi solver and tie the ship. The ship is big and has a high volume, about 700,000 mass. When I move the ship, the rope constantly stretches and doesn't hold the ship. I couldn't figure out what other settings I should make and what I'm missing.

I switched the one that attaches the rope to the boat to dynamic. The one on land is static. other settings are default.

I'd be glad if you could help.
Thank you.

Hello. I am using the latest Obi Fluid 7 with Unity 2022.3.43f1.

I noticed that when running a script with the following code while the Backend mode of the Obi Solver is set to GPU, performance deteriorates. Regardless of the processing inside the Solver_OnCollision function, simply registering a function as an event listener to .OnCollision causes a performance drop.

Example:
void OnEnable()
{
    if (solver != null)
    {
        solver.OnCollision += Solver_OnCollision;
    }
}

void OnDisable()
{
    if (solver != null)
    {
        solver.OnCollision -= Solver_OnCollision;
    }
}

private void Solver_OnCollision(object sender, ObiNativeContactList e)
{

}
However, when the Backend mode is set to CPU, the impact on performance is minimal.

Why does this happen?
Is there a way to use GPU Backend mode without causing a performance drop while still using this script?

New component coming to ObiRope 7.0.5: ObiPinhole.

This is something that has been requested quite often: the ability to attach a rope to a point while allowing it to slide/pass trough that point - just like a thread passing trough the eye of a needle.

Pinholes implement that and a lot more: they have full two-way coupling with rigidbodies, they're motorized, and you can even define the friction between the rope and the pinhole. They work for ropes and rods, both open and closed/looped, and fully support rope tearing/cutting. Here's the WIP manual page for them, which contains more details and some use cases:

https://obi.virtualmethodstudio.com/manu...nhole.html

Let me know if you have some feedback, questions or suggestions!

Hi,

I need to track the the transform of cloth particles or specially 2 individual corner particles who I have assigned Particle Group named lets say "Left Corner Particle" and "Right Corner Particle".

Is there is any way I can fetch the transform using Particle Group?

Hi,

I am using Obi Fluid 7.0.4 in Unity 2023.1.3f1 with Universal 2D, and I encountered the following error message:

Hi,

I am testing collision between Fluid and cloth. 
Works fine between ObiCloth and ObiFluid, but when switching to ObiTearableCloth, fluid doesn't collide anymore with Tearable cloth. Do I need extra setup for collision to work ?

thanks,
Diego

First off, I just want to say how amazing Obi Fluid is! I've had so much fun creating various liquids for my projects—huge thanks for the fantastic work. Keep it up! 

The Issue:
I initially ran into an issue with the compute backend struggling when handling a large number of colliders in the scene. The fluid wouldn't collide with anything, but I found a fix on the forum by adjusting:

• Colliders: ~150 (mostly Box Colliders), positioned close together.
  
• Fluid Resolution: 3
  
• Particle Count: Around 185k particles—at this point, the fluid starts ignoring colliders and becomes jittery.
  

1. Instability at High Particle Count
   • Even with a high-end GPU, the compute backend becomes unpredictable when the particle count increases.
     
   • Reducing the resolution only delays the breaking point.
     
2. Collisions Causing Jitter
   • The fluid behaves erratically when colliding with many objects, even with particle count around 100k.
     
   • This jitteriness leads to excessive foam generation.
     

1. Jittering Fluid at High Particle Count 
   demo
   
2. Fluid Passing Through Multiple Colliders
   demo