So I have turned off surface and self collisions for a cloth and also my sheet is 9x9 = 81 particles. I've tried using many techniques, the sub steps to 1-2, collision iteration is only 1. Using multiple collision layers to avoid multiple collisions. 

The problem im facing is frame rate drop when my cloth falls on the floor as it lay down completely flat on the floor, i think it could be due to all 81 points colliding with the floor. Any other options I can use to reduce physics based processing or increase my framerate? Does total number of colliders in scene effect?

Update: I tried reducing cloth collision points to only 4 and im still getting same results as it hits the floor, looks like number of points colliding isn't the issue. But as soon as it collides with floor my frame rate drops, any way to optimize or trace it? Because as long as im holding the blanket in hand with attachments, it works fine, but as soon a single collision happens or any single particle collides anywhere i get a frame rate drop.

I want to have a crane that get certain behavior once a tension threshold is certain amount.

On top of that I want the motor that retract or extend the rope to sound like its making more effort depending on the tension amount.

Is this achievable? if so, how? 

Best regards,
Daniel.

I'm working on simulating a Chemistry Lab in Unity. Here's what it looks like right now: https://file.io/6cEnvfVUCXTK. But I'd like to make my object hold Obi Fluid. Here's the mesh: https://imgur.com/a/dz5o3ue. I've tried it with a different object that had more vertices as well, so I'm not sure what's wrong. I suspect that it's an issue with the mesh, but can someone please help? Thanks

I need to spawn objects in runtime, so everything needs to be a prefab. When creating a scene, I instantiate obi rope and spawn 2 plugs, that I can pick up, I connect them to the rope and that is it. On host: Everything works fine, on client: rope gets disconnected from plug and starts to do some weird movement. That only happens when everything is instantiated in runtime.

Hi all,

My colleagues and I have been using Obi to research the robot manipulation of shoelaces. We recently published a paper using this simulation environment.



Here is our open-source repo: ImperialCollegeLondon/UniLace (github.com).

Here is the paper: Benchmarking and Simulating Bimanual Robot Shoe Lacing | IEEE Journals & Magazine | IEEE Xplore.

Please feel free to contact us if you have any questions about our simulation!

Best Regards,
Haining

Hi there, hope you're doing good.

I wanted to inquire if Obi Fluid 7 works on Apple Vision Pro with the change from previous screen-space ellipsoid splatting to isosurface mesh extraction. Currently vision OS builds from Unity currently only support Single-Pass Instanced rendering so I'm curious if the team has tested this in house before I proceed further. 

Thank you so much for your time.

Hi Everyone,

i have an Problem where i need the Particle Position of my Cable. It works fine when i have one Cable in the Scene. But as soon as i use more than one, somehow i get the same Particle from one Cable for all other Cables. I have a Script attached to every Cable and in this Script i search the specific Actor of every Gameobject and use those Particles (as you can see in the attachement). But somehow all the Cables use the same Particle of the first Cable which is in the Actor List. Hopefully i explained my Problem good enough if yall need more Information feel free to ask. Maybe im just dumb but i cant seem to find the Error.

Attached Files

Thumbnail(s)
   

OK, I have a truly bizarre one for you. 

If you put enough Obi Colliders overlapping in the same place, even fully static box colliders, the Compute backend goes absolutely mental. It has some kind of overflow and starts adding random updraughts of force to particles in random areas, some near the colliders (but not touching) and some nowhere near it. Burst is unaffected.

I noticed it in a game where I have a level made out of modular parts and each Wall has an obi collider. I added some more colliders to the level and noticed that my fluid started randomly jumping up all over place and wouldn't stop. Even with the most aggressive smoothing, the fluid never reached a rest state and just kept jiggling. A ton of trial and error to find out that it's caused by obi colliders just being in the scene and switched on and not even necessarily near the fluid, and then I managed to recreate it by stacking enough colliders in the same spot.


Replication steps:

• Create a new blank URP project
  
• Install Obi Fluid 7.03
  
• Launch Faucet And Bucket test scene and fix the scene materials
  
• Set the Solver to Compute back-end and the emitter to speed 6 and lifespan 8
  
• Edit the fluid blueprint to expand it to 12,000 particles and re-generate it
  
• Create a 3D Cube at coordinates Vector3(0.879999876,1.23000002,-2.41999984). Add an Obi Collider.
  
• Launch the Scene. Now duplicate the cube in place using Ctrl-D until you get to 16 cubes.
  
• When you get to 16 cubes, you'll see obvious jets shooting out of the fluid below and near the cube, and another jet randomly on the far edge of the fluid.
  

• If you disable the obi colliders on the cubes 1 at a time you can see the effect diminish with each one.
  
• If you move any of the cubes so that their colliders are no longer overlapping, they no longer contribute to the effect.
  
• If you move the group of cubes around or re-scale them all, it changes the characteristics of the random bits of force causing the jets
  
• Change the box collider size's y value on all the cubes slowly. When it hits 3, an entire quadrant of particles randomly jumps up in the air. Increase it further to just over 8.0, the effect disappears and everything goes back to normal. 8 world units tall seems to be a magic number, is that the unit size of the collider grid or something?
  

Very much in the spirit of Halloween here, but ObiInstancedParticleRenderer appears to be haunted as it's rendering ghost particles.

Replication steps:

• Create a new blank URP project
  
• Install Obi Fluid 7.03
  
• Change shader target in ProceduralInstanced.shadergraph from BuiltIn to Universal
  
• Launch Faucet And Bucket test scene and fix the scene materials
  
• Disable the emitter's ObiFluidSurfaceMesher, add ObiParticleRenderer and ObiInstancedParticleRenderer components
  
• Set the emitter's lifespan to 1 second and speed to 8, and launch the scene
  
• Once the scene is open, you'll see the error. Set the Speed to 0 while the scene is live to get a really clear example of the ghost particles, which will then stay around indefinitely.
  

dear obi community and obi experts

I have a question: we are trying to synchronize two softbody actors over network, as suggested on this thread.


As a start we made two identical obi softbody setups running in the same unity application.

One setup involves:
- one obi solver
- two actors (spheres) with slightly different properties.
- obi colliders as a bounding box

We copied the setup within the unity hierarchy and placed it next to the original setup, in PlayMode we noticed that the two setups behave differently after already a few seconds.

The image attached shows the problematic. The setups run side by side with the same parameter values but already differ after a few seconds. Where is the randomness?

According to my understanding the softbody physiscs engine should be deterministic and therefore should behave identical when an identical copy is running on the same machine. Am I wrong?


thank you

Attached Files

Thumbnail(s)