Softbody version 6.5.4
I have test with another character, it can generate just fine.
But this Slime model can not, I have no idea.
This is the error shown:

Hi there, I can use this code to collide with the Obi softbody and push my character up,
I just have a problem with debugging the collision position and normal.
In this picture, the yellow line is the debug line, it does not look like it's drawing correct contact position or normal.
From my understanding, using solver.transform.TransformPoint and solver.transform.TransformDirection is the way to convert those local data to world space, but why it's incorrect?

Hello. My project breaks and opens only in safe mode after installing Obi Rope. I believe it has something to do with Fluxy as I have it in the project too and one of the errors mentioned Fluxy. I've never had this error with Fluxy before. 

I've deleted the Fluxy character controller folder in samples that produced the error, error disappeared, but I still get these 2 other errors, I'm stuck and the project is broken, unfortunately. 

1. Assets\Obi\Scripts\Common\Backends\Burst\DataStructures\NativeMultilevelGrid.cs(74,46): error CS1061: 'UnsafeList<K>' does not contain a definition for 'length' and no accessible extension method 'length' accepting a first argument of type 'UnsafeList<K>' could be found (are you missing a using directive or an assembly reference?)

2. Failed to find entry-points:
Mono.Cecil.AssemblyResolutionException: Failed to resolve assembly: 'Obi.Editor, Version=0.0.0.0, Culture=neutral, PublicKeyToken=null' ---> System.Exception: Failed to resolve assembly 'Obi.Editor, Version=0.0.0.0, Culture=neutral, PublicKeyToken=null' in directories: C:\Program Files\Unity\Hub\Editor\2022.3.21f1\Editor\Data\MonoBleedingEdge\lib\mono\unityjit-win32

Full error makes flags this message and doesn't let me post it. So I can pm it to you if requested

Unity 2022.3.21

From what I've observed, Obi bone always works very unexpected when the original skeletal animation has scales on bones. Is there any way to make it work? I thought particles have only positions and velocities, so in theory they can just ignore scales, right?

Hello, I am trying to find a way to simulate collision or resistance through proximity instead of Obi colliders. I have been working with the snake controller from Obi rope and thought I would attempt to make a snake that can move on the surface of water. This obviously would require my water to be a mesh object and have an Obi collider. I would like to avoid that.

To make objects float/roll with waves I currently search for the height of the water at that position of my object. I generated multiple colliders that float on the water around the snake and it worked but not very well. 

I was wondering if there is a way to use distance fields with transforms instead of colliders. Something that isn't a hard collision but more of an add forcer per rope particle to move towards the transform position I apply. 

Any ideas are helpful! 

Thanks,

Hi!

We recently had a crash in a obi job "IdentifyMovingColliders.Execute" (see attached picture to have the exact line).
We are using Obi Rope 6.4 but the code I'll talks about remains the same in 6.5

After few investigation, the crash seems to happen when for some reasons we loaded, then unloaded some scenes containing colliders without letting them do the UpdateIfNeeded on the tracker. By doing this, the shapes remaings zeroed (just allocated).

I wanted to check what was the initial cause of the bug by reading a bit more the sourcecode, and there is something I'm missing.

1. BurstColliderWorld.cellSpans will always grow to at least match the colliderCount (as seen in BurstColliderWorld.SetColliders)
   
2. When preparing the IdentifyMovingColliders parralel for job (inside BurstColliderWorld.UpdateWorld), we transfer ObiColliderWorld.colliderShapes into a NativeArray by doing so: 
   shapes = world.colliderShapes.AsNativeArray<BurstColliderShape>(cellSpans.count).
   We then have a shapes native array matching the cellSpans.count... but not world.colliderShapes.count
   
3. Then we schedule the parrallel for with cellSpans.count as parameter, so we are iterating on non initialized or removed shapes sometimes (since cellSpans.count >= colliderShapes.count)
   
4. Since we loaded/unloaded the shapes without them having time to UpdateIfNeeded, the shape.materialIndex stay at 0 (and the other parameters of the shape are zero-ed too!)
   
5. We then test shapes[i].materialIndex >= 0 which is true (since we are not using material, we should have put a -1 in the skipped UpdateIfNeeded)
   
6. Then we crash on the line velocityBounds.Expand(collisionMaterials[shapes[i].materialIndex].stickDistance); since collisionMaterials is empty (that make me think we should use materials for our ropes!)
   

1. bounds[i] which be the size of shapes 
   
2. shapes[i] since we matched the size of the initial shapes array
   
3. shapes[i].materialIndex >= 0 test will always be relevent since we are not iterating on a "ghost" shape that could have been added to the shapes, then removed before doing the UpdateIfNeeded thing (since UpdateIfNeeded is called in the ObiColliderWorld.GetInstance().UpdateColliders(); during the ObiUpdater.BeginStep)
   

Hello, pretty simple question I was hoping for some help with.

I have a rod; I want to know how much force is acting on one of its elements/particles. That is, how much total force are the constraints exerting (how deformed the rod is).

I don't know how to approach this, outside of doing a clunky measurement of the particle's position vs its rest position. I imagine it involves something to do with reading the constraint batch data in the solver?

Hi, I'm a newbie! and diving into this amazing asset!


What I'm trying to do is make a 3d avatar wearing obi applied-clothes "realistic".
Reason why I use this term is that I desperately need your help regarding blueprint and/or solver setting which decides the condition of a garment on the 3d world.
When I apply obi skinnedcloth seems like a bit hardware(like cans, or object etc) is placed on the avatar surface, and using obi cloth seems like banding slowly dropping down towards the ground. Probably affected by too much gravity I think.

When I use obi skinnedcloth and its blueprint, I adjust skin backstop(-0.005~-0.001) and skin radius(0.02~0.05) and it's all I do  right now.

Using cloth blueprint, I see the garment pass through the avatar body bcuz the avatar has only mesh collider which is not changeable so that I use neither capsule nor sphere collider!
The body has Mesh Collider, Obi Collider with HighFriction, Rigidbody, and Obi Rigidbody.

Still trying to make the garment more soft, sophisticated, natural playing with blueprint back and forth.
Should I keep doing with blueprint setting in detail?
Objects are all fbx from 3d modeling tools.

I refer to various tutorials and I reached to all the way here...still struggling with them.
The ultimate goal is to show the avatar is wearing "fabric clothes". That's all.

I wanna listen to your advice, and if you have any ideas worth with, please comment me!

Thank you

p.s. I'm working on a t shirt by the way. lol

It doesn't seem to be the case for Obi 6.x. In 7.0 there is a new particle shader built with Shader Graph. I'm not against Shader Graph, but this one shader alone takes 90s to compile. Considering it's something not shown in the game usually, that's 90s wasted. Is it possible to work around it?

Also my project doesn't has HDRP, so it shows this "unknown" target. But when I delete it the whole shader gets broken:

   

(not sure if it's related to the compile time tho)

Is there a flag on the particle that I can set to make it been excluded from the mesher, but not from the simulation? In other word I'd like the particle to be simulated, but hidden.