Hello, I've come across some problem on rendering with URP. 
If I use builtin, I can enable the property [Render] in ObiParticleRenderer to render paticles, but when I use URP, it just renders fluid. Does Obi support rendering paticles instead of fluid in URP ?

Hello, I have a problem - I do not know how to fix the vertex of my wire.
The video shows that I pulled the wire (rope), but when I leave, it still returns to its place. I want to make a wire, but it turns out some kind of silicone. Help me please.
https://youtu.be/0JJjDErnuHU

I am learn sample scene 'CharacterCloth' in Unity 2021，but when I play in editor(windows platform),the trenchcoat doesn't have any physics simulation, and it stretches down very strangely. 
Does obi cloth still support unity2021?

Hi there, I met a problem while attach one Obi Softbody object to a normal object.


As the picture showing above, the white part is a softbody, and the gray part is a normal object.


My purpose is to link them together with no movement or mismatch, and it now does not work well.




The following video is a screenshot of it, and I attach my parameters setting below.


Please could you kindly help me figure this problem? Thanks a lot.




Avoiding video post failed, paste the link here: https://www.facebook.com/100080982352505/videos/3155701804694430/ 

Attached Files

Thumbnail(s)
       

I'm currently trying to fix the obi softbody object. I want it only occurs deformation rather than transformation on the object. I can't find a good way, how can I do this?

Hi
I am writing to ask for help. I have been working on a project using Obi softbody for over three months now. It used to simulate the flexing of a pregnant woman's body under the pressure of the usg head.

Previously a test model of a woman, being only a torso, generated to blueprint without much problem. It usually took about 5/10 seconds.

Since the graphic designer generated the new, final model, the torso object completely refuses to work with the plugin. Blueprint generates instantly, as if it skips the object completely. Additionally, the particle model consists of large, dense and disproportionate particles with normal ones facing one way. (I checked and the normal of the model is correct). Applying and running an object with this blueprint ends up with a completely distorted mesh.

My question is: Am I doing something wrong or is it the fault of the model? If you know the answer then please give suggestions in the comments. My graphic designer doesn't know anything about coding and I don't know anything about modelling and for over 3 days we have been trying various tricks to make the new model work like the old one, to no result.

I added some screenshots below

Thanks in advice for any help.

EDIT. I couldn't add all screenshoots so I posted them there:
https://drive.google.com/drive/folders/1...sp=sharing

Attached Files

Thumbnail(s)
                   

Look at this: https://youtu.be/Y3trDSWeQh0

The fluid behaves normally when I first pour it into the container with a sticky collision material, but as soon as I pick it up it suddenly starts crawling out of the container in all directions, and as soon as I let go it stops again. This happens with any non-zero stickiness value, which sucks because I really need to fluid to stick at least enough to not fall straight out of the bowl when you hold it at an angle or upside down. I tried increasing the solver substeps up to 8 since that fixed some inconsistencies I had in other cases, but it didn't make any difference here.

The container rigidbody doesn't become kinematic when grabbed by a hand in case you suspect that's the issue. It doesn't get parented either, both the hand and the container stay exactly where they are in the hierarchy and only connect through this configurable joint: https://imgur.com/a/AtHImSd

Here are my relevant obi component settings: https://imgur.com/a/hkMHo14

Hi, 

I've been using obi cloth for the past year - with minimal problems 

It seems unity 2021.3 may have broken obi cloth, as collisions are no longer working


I created a fresh project in 2021.3.2f1
freshly imported the obi cloth package from my assets in package manager
- new scene
- Right click > Create 3d object > obi > obi cloth
- assigned the cloth sheet sample cloth blueprint
- surface collisions enabled
- Create a box collider underneath 
- Assigned obi collider component to the box collider

The cloth has no interaction with the box collider at all and falls through it.

I've tried both backends, and all dependencies are installed

I sanity checked myself by following this tutorial exactly - https://www.youtube.com/watch?v=q2Qsh7P79q8
my cloth flys straight through the object 

Any clarity on this issue would be greatly apreciated 

(Btw i was unable to get my licence ID when creating my account, if needed ill follow up with my producer who was the one who purchased the package for my seat in the organization)

Hi,

I recently took over a project (from people no longer at my company) and am trying to upgrade Obi (Cloth and Rope) from version 4.0 to 6.4. I get a handful of errors because of API changes and managed to adjust most of the code, but one method in particular is hard to update. One part of the problem is that our code is not well documented (or well written, sadly), but also I'm having trouble finding info on how to replace methods that no longer exist, especially ObiConstraint(s)Batch#GetConstraintsInvolvingParticle(int particleIndex). In the old version, our method borrowed heavily from ObiTearableCloth#ApplyTearing(), but it changed drastically after the upgrade. Our method was added to ObiTearableCloth and is called from within a solver collision callback with the index of a ParticleInActor for each contact in the ObiCollisionEventArgs.
Here's the method, I added comments behind the lines I believe to be unnecessary:
DistanceConstraints.AddToSolver(this); // unnecessary? ApplyTearing() no longer calls it

Question about calculating lambda
According to the formula in PBD, we just use the sum of the square of gradient to calculate the lambda, but in the code of CalculateLambdasJob in BurstDensityConstraint, it adds the square of the sum of gradient（data[2] * data [2]） too. Is there some reason to add this term ?