<![CDATA[Obi Official Forum - All Forums]]> https://obi.virtualmethodstudio.com/forum/ Thu, 07 May 2026 09:47:35 +0000 MyBB <![CDATA[How to make better rope ends]]> https://obi.virtualmethodstudio.com/forum/thread-4619.html Mon, 04 May 2026 17:45:28 +0200 Mediafarm]]> https://obi.virtualmethodstudio.com/forum/thread-4619.html I'm struggling a lot trying to figure this thing.
As you see in the image, I attached the rope on a gameobject through obi particle attachment. In this case i'm using the dynamic type but it's the same as static.
The problem is that I want the rope to continue the direction of that rope knot (that is a mesh) maybe making it rigid for a portion, now instead it's like floating.

.png   Screenshot 2026-05-04 174435.png (Size: 453.98 KB / Downloads: 1) ]]> I'm struggling a lot trying to figure this thing.
As you see in the image, I attached the rope on a gameobject through obi particle attachment. In this case i'm using the dynamic type but it's the same as static.
The problem is that I want the rope to continue the direction of that rope knot (that is a mesh) maybe making it rigid for a portion, now instead it's like floating.

.png   Screenshot 2026-05-04 174435.png (Size: 453.98 KB / Downloads: 1) ]]> <![CDATA[ObiFluidRendererFeature compile error]]> https://obi.virtualmethodstudio.com/forum/thread-4618.html Sat, 02 May 2026 17:41:25 +0200 ruitar]]> https://obi.virtualmethodstudio.com/forum/thread-4618.html
Using Unity 6.4 (6000.4.2f1) and I get the following error: 

Assets/Obi/Scripts/Fluid/Rendering/URP/ObiFluidRendererFeature.cs(247,30): error CS0115: 'VolumePass.Execute(ScriptableRenderContext, ref RenderingData)': no suitable method found to override

I followed instructions in https://obi.virtualmethodstudio.com/manu...setup.html and have all the dependencies. 

The setup seems to work with older versions but I get the error specifically for 6.4. 

Would appreciate any help! Thanks.]]>
Using Unity 6.4 (6000.4.2f1) and I get the following error: 

Assets/Obi/Scripts/Fluid/Rendering/URP/ObiFluidRendererFeature.cs(247,30): error CS0115: 'VolumePass.Execute(ScriptableRenderContext, ref RenderingData)': no suitable method found to override

I followed instructions in https://obi.virtualmethodstudio.com/manu...setup.html and have all the dependencies. 

The setup seems to work with older versions but I get the error specifically for 6.4. 

Would appreciate any help! Thanks.]]> <![CDATA[Issues with closed loops]]> https://obi.virtualmethodstudio.com/forum/thread-4617.html Sat, 02 May 2026 04:32:36 +0200 N_U_P]]> https://obi.virtualmethodstudio.com/forum/thread-4617.html
1. The Obi Rope Extruded Renderer Material does not smoothly connect at the ends of the rope, and as a result, there is a visible gap.

[Image: broken-loop.png]


2. I get a very strange behavior at the connected ends of my closed rope if I shrink it too fast using the Obi Rope Cursor. The connection between the first and last particles looks "broken", and those two particles also don't get affected by gravity correctly. Instead, they "slide" downwards much slower than gravity would dictate.

[Image: brokenjoint.png]

Is there a way to fix these issues and make a rope that looks and acts more like a real loop of rope? Thank you!]]>
1. The Obi Rope Extruded Renderer Material does not smoothly connect at the ends of the rope, and as a result, there is a visible gap.

[Image: broken-loop.png]


2. I get a very strange behavior at the connected ends of my closed rope if I shrink it too fast using the Obi Rope Cursor. The connection between the first and last particles looks "broken", and those two particles also don't get affected by gravity correctly. Instead, they "slide" downwards much slower than gravity would dictate.

[Image: brokenjoint.png]

Is there a way to fix these issues and make a rope that looks and acts more like a real loop of rope? Thank you!]]> <![CDATA[Artifacts on simulated cloth but not original mesh (something to do with normals)]]> https://obi.virtualmethodstudio.com/forum/thread-4616.html Thu, 30 Apr 2026 06:54:38 +0200 CptnFabulous]]> https://obi.virtualmethodstudio.com/forum/thread-4616.html
We have a system that procedurally generates cloth garments, then generates blueprints and simulates them on a virtual mannequin. One issue we’ve noticed with one of our garments is strange, dark artifacting on the bust and one of the thighs, that isn’t present on the regular mesh but appears once simulation starts. The artifacting shifts and changes when the garment is dragged (using ObiParticlePicker), which suggests it has something to do with the cloth particles’ positions and normals. The dark spots must be the shader's lighting rendering those section as in shadow.

Pictures (I can't show too much because of NDAs)
The first two are the problem areas, the second two are the same areas with ObiSkinnedClothRenderer disabled: (so rendering the unsimulated mesh using SkinnedMeshRenderer).


My theory was that the particles might be too constrained and forced to bunch up in unnatural ways, but I tried increasing the skin radius and that didn’t help (it just made the rest of the garment fall away too much). I'm not sure what else could be doing it that's specifically because of the cloth simulation. If it was because of the normals not being calculated properly, I imagine the artifacts would appear even without simulation. Any idea of what could be doing this? I tried searching but wasn't sure how to articulate the question.

Additional details:
  • Obi Cloth 7.0.3, in Unity 2022.3.62f3
  • The material’s shader uses custom code to calculate the texture, but the lighting data is default for Unity’s URP so that shouldn't be causing any weird lighting behaviour. The artifacts also occur when using the completely standard URP Lit shader, and don't appear when rendering with a shader that doesn't have any lighting code.
  • I also made a slight modification to ObiSkinnedClothBlueprint.CommitBlueprintChanges(). It ran the base function followed by an override that’s basically identical except for one different value (CreateDefaultSkinmap's 'mapBonesToParticles' bool being true instead of false), resulting in severe lag spikes when generating complex garment shapes. I modified the ObiClothBlueprint’s base function to replace the one boolean with a reference to a property that’s overridden in ObiSkinnedClothBlueprint, and deleted the override. This seems to perform the same functions with considerably better performance, but could this change be affecting the normals in some way?
Thanks!]]>
We have a system that procedurally generates cloth garments, then generates blueprints and simulates them on a virtual mannequin. One issue we’ve noticed with one of our garments is strange, dark artifacting on the bust and one of the thighs, that isn’t present on the regular mesh but appears once simulation starts. The artifacting shifts and changes when the garment is dragged (using ObiParticlePicker), which suggests it has something to do with the cloth particles’ positions and normals. The dark spots must be the shader's lighting rendering those section as in shadow.

Pictures (I can't show too much because of NDAs)
The first two are the problem areas, the second two are the same areas with ObiSkinnedClothRenderer disabled: (so rendering the unsimulated mesh using SkinnedMeshRenderer).


My theory was that the particles might be too constrained and forced to bunch up in unnatural ways, but I tried increasing the skin radius and that didn’t help (it just made the rest of the garment fall away too much). I'm not sure what else could be doing it that's specifically because of the cloth simulation. If it was because of the normals not being calculated properly, I imagine the artifacts would appear even without simulation. Any idea of what could be doing this? I tried searching but wasn't sure how to articulate the question.

Additional details:
  • Obi Cloth 7.0.3, in Unity 2022.3.62f3
  • The material’s shader uses custom code to calculate the texture, but the lighting data is default for Unity’s URP so that shouldn't be causing any weird lighting behaviour. The artifacts also occur when using the completely standard URP Lit shader, and don't appear when rendering with a shader that doesn't have any lighting code.
  • I also made a slight modification to ObiSkinnedClothBlueprint.CommitBlueprintChanges(). It ran the base function followed by an override that’s basically identical except for one different value (CreateDefaultSkinmap's 'mapBonesToParticles' bool being true instead of false), resulting in severe lag spikes when generating complex garment shapes. I modified the ObiClothBlueprint’s base function to replace the one boolean with a reference to a property that’s overridden in ObiSkinnedClothBlueprint, and deleted the override. This seems to perform the same functions with considerably better performance, but could this change be affecting the normals in some way?
Thanks!]]> <![CDATA[ECS Physics/Graphics Support]]> https://obi.virtualmethodstudio.com/forum/thread-4615.html Thu, 23 Apr 2026 22:29:29 +0200 Jawsarn]]> https://obi.virtualmethodstudio.com/forum/thread-4615.html
Wondering if there's any plans to support ECS Physics and/or ECS Graphics?
Would be great not to have to add a GO per entity for those we want to add Oi Colliders to, and also if we can keep the rendering on ECS side.]]>
Wondering if there's any plans to support ECS Physics and/or ECS Graphics?
Would be great not to have to add a GO per entity for those we want to add Oi Colliders to, and also if we can keep the rendering on ECS side.]]> <![CDATA[Any upcoming Softbody sales planned?]]> https://obi.virtualmethodstudio.com/forum/thread-4614.html Wed, 22 Apr 2026 16:19:30 +0200 Youxi]]> https://obi.virtualmethodstudio.com/forum/thread-4614.html ]]> ]]> <![CDATA[Memory Leak - AccumulateTransmissionURP.shader]]> https://obi.virtualmethodstudio.com/forum/thread-4613.html Mon, 20 Apr 2026 22:47:28 +0200 Egate]]> https://obi.virtualmethodstudio.com/forum/thread-4613.html
Frame debugger shows nothing using this shader. 

Memory profiler shows: 
Shortest Path To Root shows "ROOT: Material "Hidden/AccumulatedTransmissionURP"
Referenced by: empty
References TO: Shader "Hidden/AccumulatedTransmissionURP"


Oddly this bug is only apparent when testing on PC. If i test a build on android this leak does not happen. 

Im unsure of how to continue diagnosing this. Anyone have any advice?

Thanks and Thank you for the great physics package!]]>
Frame debugger shows nothing using this shader. 

Memory profiler shows: 
Shortest Path To Root shows "ROOT: Material "Hidden/AccumulatedTransmissionURP"
Referenced by: empty
References TO: Shader "Hidden/AccumulatedTransmissionURP"


Oddly this bug is only apparent when testing on PC. If i test a build on android this leak does not happen. 

Im unsure of how to continue diagnosing this. Anyone have any advice?

Thanks and Thank you for the great physics package!]]> <![CDATA[Deleting collider invalidates collider id in ObiPinConstraintsBatch.colliderIndices]]> https://obi.virtualmethodstudio.com/forum/thread-4612.html Fri, 17 Apr 2026 11:20:22 +0200 nicity]]> https://obi.virtualmethodstudio.com/forum/thread-4612.html Our upcoming game uses Obi 6.5.4. It is co-op game with two players that are connected via tether and also both players have controllable whip, all three objects are ObiRopes.
Both players have ObiColliders with PinConstraint for both ends of the tether.
On the scene we have some attachable objects with ObiCollider that are dynamically spawned for limited time, with Enable / Disable calls.

From time to time we observe index out of bounds in PinConstraintsBatchJob.Execute.
Locally we added validation of colliderIndex wrt shapes array bounds. 
if (colliderIndex < 0 || colliderIndex >= shapes.Length)
{
    UnityEngine.Debug.LogError($"Collider index {colliderIndex} is out of range of '{shapes.Length}' Length at {i}");
    continue;
}
After fixing couple of issues on our side due to attaching whip to invalid objects (colliderIndex == -1) we started (rarely) observe of colliderIndex being beyond shapes.Length.
After extensive tracking down we found that invalidation of colliders in ObiColliderWorld.DestroyCollider may change collider index that is used in ObiPinConstraintsBatch and possibly in other places.
This situation happens for us for ObiColliders in players and their ids are near the colliderHandles.Count 
Invalidation of another collider will take collider at the end of colliderHandles and insert it to the invalidated collider place changing its index. 
int index = handle.index;
int lastIndex = colliderHandles.Count - 1;
colliderHandles.Swap(index, lastIndex);
colliderHandles[index].index = index;

ObiPinConstraintBatch will still use old collider id that will more than shapes.Length in PinConstraintsBatchJob
For what I see in the sources of ObiRope 7.1 the problem can also happen there.
I'd appreciate ideas how to address the issue easy and cleanly.]]> Our upcoming game uses Obi 6.5.4. It is co-op game with two players that are connected via tether and also both players have controllable whip, all three objects are ObiRopes.
Both players have ObiColliders with PinConstraint for both ends of the tether.
On the scene we have some attachable objects with ObiCollider that are dynamically spawned for limited time, with Enable / Disable calls.

From time to time we observe index out of bounds in PinConstraintsBatchJob.Execute.
Locally we added validation of colliderIndex wrt shapes array bounds. 
if (colliderIndex < 0 || colliderIndex >= shapes.Length)
{
    UnityEngine.Debug.LogError($"Collider index {colliderIndex} is out of range of '{shapes.Length}' Length at {i}");
    continue;
}
After fixing couple of issues on our side due to attaching whip to invalid objects (colliderIndex == -1) we started (rarely) observe of colliderIndex being beyond shapes.Length.
After extensive tracking down we found that invalidation of colliders in ObiColliderWorld.DestroyCollider may change collider index that is used in ObiPinConstraintsBatch and possibly in other places.
This situation happens for us for ObiColliders in players and their ids are near the colliderHandles.Count 
Invalidation of another collider will take collider at the end of colliderHandles and insert it to the invalidated collider place changing its index. 
int index = handle.index;
int lastIndex = colliderHandles.Count - 1;
colliderHandles.Swap(index, lastIndex);
colliderHandles[index].index = index;

ObiPinConstraintBatch will still use old collider id that will more than shapes.Length in PinConstraintsBatchJob
For what I see in the sources of ObiRope 7.1 the problem can also happen there.
I'd appreciate ideas how to address the issue easy and cleanly.]]> <![CDATA[Spawn obi rope with scripted transform and attachment]]> https://obi.virtualmethodstudio.com/forum/thread-4611.html Fri, 17 Apr 2026 05:32:08 +0200 anxis]]> https://obi.virtualmethodstudio.com/forum/thread-4611.html Chained Together. I spawn my players at runtime, and with that in mind, I also spawn a prefab that contains a solver and a rope. Then I attach the start of the rope to Player 1 and the end to Player 2.
This part works well the rope is correctly attach but its placement is completely off.
So I'm wondering do I need to change the way I manage this system, or is there a way to adjust the rope path via scripting?]]> Chained Together. I spawn my players at runtime, and with that in mind, I also spawn a prefab that contains a solver and a rope. Then I attach the start of the rope to Player 1 and the end to Player 2.
This part works well the rope is correctly attach but its placement is completely off.
So I'm wondering do I need to change the way I manage this system, or is there a way to adjust the rope path via scripting?]]> <![CDATA[Help with water in a bottle.]]> https://obi.virtualmethodstudio.com/forum/thread-4610.html Thu, 16 Apr 2026 21:33:43 +0200 Watson89]]> https://obi.virtualmethodstudio.com/forum/thread-4610.html However, the water immediately explodes outward and that’s it, it doesn’t stay inside the bottle at all. The water in the demo bottle works perfectly, but in my bottle it doesn’t, even though I followed the same steps.
Maybe I’m doing something wrong? I can send my bottle model if needed. Please help.]]> However, the water immediately explodes outward and that’s it, it doesn’t stay inside the bottle at all. The water in the demo bottle works perfectly, but in my bottle it doesn’t, even though I followed the same steps.
Maybe I’m doing something wrong? I can send my bottle model if needed. Please help.]]> <![CDATA[Erro en el Script de ObiFluidRenderer]]> https://obi.virtualmethodstudio.com/forum/thread-4609.html Tue, 14 Apr 2026 21:24:09 +0200 d38u993r]]> https://obi.virtualmethodstudio.com/forum/thread-4609.html usando Obi Fluid en Unity 6.4 (6.000.4.0f1) no puedo ejecutar ninguna escena de ejemplo esto debido a que obtengo errores de consola en un Script que pertenece a Obi Fluid



Este son los errores que muestra



[Image: error-consola.png]

buscando dentro de Obi Fluid veo que es el siguiente Script  ObiFluidRenderFeature.cs. aquí no se si deba de mostrar el otro icono # que es con el que se identifican los archivos scripts ecritos en C #
[/url][url=https://postimages.org/][Image: Assets-proyecto.png]

si lo selecciono en el inspector se ve así
[Image: script-properties.png]

Ahora si abro el archivo para ver mejor el código fuente, vemos que no encuentra esos métodos. esos son lo que están causando el Error
[Image: script.png]



Ahora si entro a la otra carpeta RemderBatches vemos que el Script se muestra con el icono que debe de llevar y no el otro icono del archivo que está mal.

[Image: script-correcto.png]


al igual que en el inspector se ve claro su código, esto sin la necesidad de abrir el código para poderlo visualizar correctamente
[Image: script-correcto-inspector.png]


esta es la segunda vez que cargo Obi Fluid en otra computadora (del trabajo) y me sale el mismo error que en la computadora (de la casa) donde tengo el proyecyo.

en el del trabajo intente con otro proyecto que solo tiene un cubo y un plano.

.png   error_consola.png (Size: 50.85 KB / Downloads: 0)

.png   Assets_proyecto.png (Size: 28.51 KB / Downloads: 0)

.png   script.png (Size: 139.08 KB / Downloads: 0)

.png   script_properties.png (Size: 231.08 KB / Downloads: 0)

.png   script_correcto.png (Size: 22.76 KB / Downloads: 0) ]]> usando Obi Fluid en Unity 6.4 (6.000.4.0f1) no puedo ejecutar ninguna escena de ejemplo esto debido a que obtengo errores de consola en un Script que pertenece a Obi Fluid



Este son los errores que muestra



[Image: error-consola.png]

buscando dentro de Obi Fluid veo que es el siguiente Script  ObiFluidRenderFeature.cs. aquí no se si deba de mostrar el otro icono # que es con el que se identifican los archivos scripts ecritos en C #
[/url][url=https://postimages.org/][Image: Assets-proyecto.png]

si lo selecciono en el inspector se ve así
[Image: script-properties.png]

Ahora si abro el archivo para ver mejor el código fuente, vemos que no encuentra esos métodos. esos son lo que están causando el Error
[Image: script.png]



Ahora si entro a la otra carpeta RemderBatches vemos que el Script se muestra con el icono que debe de llevar y no el otro icono del archivo que está mal.

[Image: script-correcto.png]


al igual que en el inspector se ve claro su código, esto sin la necesidad de abrir el código para poderlo visualizar correctamente
[Image: script-correcto-inspector.png]


esta es la segunda vez que cargo Obi Fluid en otra computadora (del trabajo) y me sale el mismo error que en la computadora (de la casa) donde tengo el proyecyo.

en el del trabajo intente con otro proyecto que solo tiene un cubo y un plano.

.png   error_consola.png (Size: 50.85 KB / Downloads: 0)

.png   Assets_proyecto.png (Size: 28.51 KB / Downloads: 0)

.png   script.png (Size: 139.08 KB / Downloads: 0)

.png   script_properties.png (Size: 231.08 KB / Downloads: 0)

.png   script_correcto.png (Size: 22.76 KB / Downloads: 0) ]]> <![CDATA[Collider World Bug]]> https://obi.virtualmethodstudio.com/forum/thread-4608.html Thu, 09 Apr 2026 13:45:42 +0200 Qriva0]]> https://obi.virtualmethodstudio.com/forum/thread-4608.html
Observation - when new prefab is instantiated into scene (and old one is removed), then for some reason ObiColliders are not registered properly and in result there is no collision with them, unless reenabled.

Investigation - it looks like collider world is destroyed (and also solver implementation and everything else) when there are no colliders to manage. However it does not take into account colliders that should be added during next update. I think that Collider becomes enabled so it registers itself in collision world, but because other collider become destroyed/disabled, then it runs various checks, including DestroyIfUnused() and because number of colliders drops to zero it gets destroyed, but it does not care that there are colliders waiting to be registered! Also actor needs to be reset and is disabled for split of second so Teardown() is called and whole simulation dropped for no reason.

Is adding additional check 'collidersToAdd.Count == 0' in the if statement below valid way to fix this problem?

Code:
private void DestroyIfUnused()
{
    // when there is no data and no implementations, the world gets destroyed.
    // don't check materialHandles.Count == 0, as these are scriptable objects and may outlive the world.
    if (colliderHandles.Count == 0 &&
        rigidbodyHandles.Count == 0 &&
        forceZoneHandles.Count == 0 &&
        implementations.Count == 0)

        Destroy();
}
]]>
Observation - when new prefab is instantiated into scene (and old one is removed), then for some reason ObiColliders are not registered properly and in result there is no collision with them, unless reenabled.

Investigation - it looks like collider world is destroyed (and also solver implementation and everything else) when there are no colliders to manage. However it does not take into account colliders that should be added during next update. I think that Collider becomes enabled so it registers itself in collision world, but because other collider become destroyed/disabled, then it runs various checks, including DestroyIfUnused() and because number of colliders drops to zero it gets destroyed, but it does not care that there are colliders waiting to be registered! Also actor needs to be reset and is disabled for split of second so Teardown() is called and whole simulation dropped for no reason.

Is adding additional check 'collidersToAdd.Count == 0' in the if statement below valid way to fix this problem?

Code:
private void DestroyIfUnused()
{
    // when there is no data and no implementations, the world gets destroyed.
    // don't check materialHandles.Count == 0, as these are scriptable objects and may outlive the world.
    if (colliderHandles.Count == 0 &&
        rigidbodyHandles.Count == 0 &&
        forceZoneHandles.Count == 0 &&
        implementations.Count == 0)

        Destroy();
}
]]> <![CDATA[Connectivity Particle Binding]]> https://obi.virtualmethodstudio.com/forum/thread-4607.html Thu, 02 Apr 2026 16:44:54 +0200 Eritar]]> https://obi.virtualmethodstudio.com/forum/thread-4607.html
Is there any way to make Particle Binding limited to vertex connectivity? 
For example, if my character has close by geometry, like fat folds on a belly, or structure similar to brain or corals, is there an easy way to limit binding to connected geometry, so one particle may bind to a single closest fat fold, for example?

Also I greatly appreciate all your help along the forum posts, but I don't want to spam you with "Thanks, that worked!" messages.
Thank you very much!
]]>
Is there any way to make Particle Binding limited to vertex connectivity? 
For example, if my character has close by geometry, like fat folds on a belly, or structure similar to brain or corals, is there an easy way to limit binding to connected geometry, so one particle may bind to a single closest fat fold, for example?

Also I greatly appreciate all your help along the forum posts, but I don't want to spam you with "Thanks, that worked!" messages.
Thank you very much!
]]> <![CDATA[Better method to change rod shape]]> https://obi.virtualmethodstudio.com/forum/thread-4606.html Wed, 01 Apr 2026 10:44:46 +0200 Qriva0]]> https://obi.virtualmethodstudio.com/forum/thread-4606.html I change shape of the rod to make it bend an it works, but final behaviour is not exactly "right".
The thing is that moving, pulling elastic rod makes everything very soft, forces do not propagate well, it's like pushing soft spaghetti. Keeping shape work in similar way, it the rod is stiff it bends very fast to target shape, but making it softer results in very slow "lerp like" change of rotation.

The thing is I want my rod to be overall soft enough, but at the same time change shape reasonably fast. On top of that I want to avoid situation where huge rigidity force the rod to break constraints, for example see image below. If rod changes shape with colliders around, it has no idea that the bend I set is not possible to do and the whole thing shakes, explodes, or is at least very unstable. 
I made system that moves bending slower and checks if lambdas in constraint are not too big, but it's clunky, I don't like my implementation. What else can be done?


.png   rod_bend.png (Size: 5.77 KB / Downloads: 1) ]]> I change shape of the rod to make it bend an it works, but final behaviour is not exactly "right".
The thing is that moving, pulling elastic rod makes everything very soft, forces do not propagate well, it's like pushing soft spaghetti. Keeping shape work in similar way, it the rod is stiff it bends very fast to target shape, but making it softer results in very slow "lerp like" change of rotation.

The thing is I want my rod to be overall soft enough, but at the same time change shape reasonably fast. On top of that I want to avoid situation where huge rigidity force the rod to break constraints, for example see image below. If rod changes shape with colliders around, it has no idea that the bend I set is not possible to do and the whole thing shakes, explodes, or is at least very unstable. 
I made system that moves bending slower and checks if lambdas in constraint are not too big, but it's clunky, I don't like my implementation. What else can be done?


.png   rod_bend.png (Size: 5.77 KB / Downloads: 1) ]]> <![CDATA[Obi Rod collision causing weird stretching behavior]]> https://obi.virtualmethodstudio.com/forum/thread-4605.html Fri, 27 Mar 2026 17:54:44 +0100 violinviolin19]]> https://obi.virtualmethodstudio.com/forum/thread-4605.html ]]> ]]>