[jane.l]

Hello, for everyone facing my problem, @Alex first answer is working. If you have big meshes with a lot of points, my recommendation is to use MultiThreading if your pc supports it. With it and Alexes answer, I solved the problem.

Best,
Jane

[jane.l]

I do not quite understand what collision response is, if that are the green/red lines that appear when the objects are at alarmingDistance/contactDistance than no I could not see any.

Although I tried to go with the proposed scene, I could still not solve the problem with the collision (may be a problem of high scale computation when the solver is solving big amount of points, the mesh per single vertebra is ~20000 points).

I added StiffSpringForceField at the problematic parts with which did not allow them to move enough so that they can overlap.

Thanks for your time Alex, I really appreciate it!
Best,
Jane.

[jane.l]

If image not loading try this.

[jane.l]

Here is an example image of what i get.
What I would like to have is non overleaping parts of the bones.
I agree with you the TriangleCollisionModel in the main node is redundant, i got a bit frustrated and started trying things out.

[jane.l]

Hi Alex,

Thank you for the reply.

With the current parameters and the adding of line and point collision, the SOFA framework freezes(because of point collision), and after some time I get(because of linear collision):
[WARNING] [LocalMinDistance(Proximity)] Determinant is null

I played around with the LocalMinDistance parameters but they did not help me, unfortunately.

Best,
Jane

[Author]

Posts