As I promised before, I will dedicate a big portion of my time to create tutorial videos for all Obi 5.0 assets, and publish them in our Youtube channel. There's a few ones already:

Cloth:
https://www.youtube.com/playlist?list=PL...akLOwboUJQ

Rope:
https://www.youtube.com/playlist?list=PL...Kns3UmsJ8B

Fluid:
https://www.youtube.com/playlist?list=PL...cnaiy5PYL_

Softbodies:
https://www.youtube.com/playlist?list=PL...3wTse_r6x8

I'm not a professional video editor, and I have a funny accent, but will do my best to get as much knowledge across as I can. Expect new videos to be added soon. Any kind of feedback or (constructive) criticism is most welcome!

Hi,

First of all congratulation on releasing the 5.0 version: the edition of ropes definitely got much easier, I like it!

I must, however, come with a major concern when it comes to the project structure: the fact that actors need to be children of an obi solver is a big problem, for a few reasons:

• It makes it impossible to create rope prefabs and to edit them in prefab mode, which is now core in production for unity 2019+: the ropes do not have a solver in this, so it can't be edited properly. But most of my work, and I suspect most of the users will be in the same scenario, revolves around nested prefabs.
  
• It makes it hard to link to a solver when being in a multiscene scenario, which is I think very common in current Unity's workflow
  
• It forces a hierarchy logic that is often not desirable, especially so when the solvers are not colliding with each other.
  

Hello, recent Obi Fluid user here!

Now that 5.0 is out, with "Experimental LWRP Support", How would I actually test this feature?

I'm using Unity version 2019.3.0b11 with the Universal Render Pipeline (Which should work the same as LWRP), this is a blank project with the Fluid Package

I have the fluid rendererer feature attached to my Pipeline asset, but the fluid still won't render (But I can get the particle renderer to work)

Is there something I'm missing, or is the update not yet compatible with URP?

[attachment=480]

Hi Obi team,

I'am lucky to test Obi V5 beta, you made a great job, congrats.
I'm new with Obi and i'am trying to understand some issues i have.

I test Obi with Unity 2019.2.2f1.
I have an animated mesh (with animator set to update mode Animate Physics) and a cloth attached to hip bone. I set simple obi colliders (capsule and sphere), set blueprint etc.
The behavior of the cloth is quite good but i have penetration. 

On the capture debug particles are inside the colliders. What i missed? Is this issue is rely on the update order (unity animation, obi fixed update,...) ?

Do you have any idea how i can fix this or a workaround?
I tried to increase colliders thickness or particle size but it's not satisfying. 
Your character clothing demo is the goal i'am trying to reach.

Thx.
Jonathan

Hi! How constraints Z position in 3D world for soft body? If switch Mode in solver to 2D, then all meshes is broken.

With the release of 5.0, we've designed things in a way that allows us to completely decouple simulation data (blueprints) from the simulation engine (solver+updater). This also resulted in better backwards compatibility for future versions, as changes in the way data is processed or laid out in memory at runtime will not necessarily affect the way data is stored in serialized form. The resulting workflows are also much simpler, imho.

This is not an arbitrary decision. Our plan moving forwards is to introduce interchangeable simulation engines: One of them will be the current native library, but we have another two in mind:

- A high-performance C# implementation based on Jobs + Burst. Expect not much difference in performance with the current engine, as we already use multithreading and SIMD internally. However, this will allow to support all platforms, and to include the full engine source code with the asset.

- A compute-shader based engine. Expect a huge increase in performance, but also quite some limitations in functionality.

This won't happen overnight, but we have already paved the way. Personally I'm very excited with the road ahead .

Let me know your thoughts on this!

Hi all,

Obi 5.0: Cloth, Rope, Fluid and Softbody are now available in the Asset Store. Compatible with Unity 2019.2.9 or higher.

A word of warning: before upgrading your existing projects, please note that Obi 5.0 is not backwards compatible with 4.x. Workflow and APIs have changed quite considerably compared to previous versions, so my advice is to use 5.0 when starting new projects, or if you're willing to spend a significant amount of time upgrading your existing project.

We have also updated and extended the online documentation:
http://obi.virtualmethodstudio.com/tutorials/

We will continue updating the docs, and uploading minor Obi versions packed with improvements and bugfixes. Also, I've allocated time in my agenda to make decent video-tutorials, which is something pretty much everyone has requested. I will be dropping them on our youtube channel one by one as I make them.

As always, we're dead set on making Obi as fast, versatile and robust as possible. If you have questions, comments, requests or think you found a bug, do not hesitate to contact us.

cheers,

Hi! Now I finally got everything working thanks to Jose, but sometimes the softbody gets stuck in the air and I think it is due to invmasses and velocities set to zero, so, is there a way to reset them without saving the previous one in variables?

Hi! Really enjoying using Obi Cloth so far, and I'm hoping to learn more about optimizing it to use in our game. It's a VR game, but right now I'm working on a scene where a character's clothes moves in response to wind. Right now, all I have in the scene is the character's shirt. I'm using a cloth proxy, where the source cloth uses a mesh of about 400 vertices and 200 clothing particles, and the target is a mesh of about 2300 vertices. The solver is only using distance, skin and aerodynamic constraints, with 1 iteration each for distance and skin constraints. Wind is being simulated with a spherical force zone that rotates around the player, with intensity and turbulence of 25.

On average, performance is pretty good, but there are a lot of irregular spikes when I profile it. On average obi will run about 1-2 ms per frame (if I add up ObiSolver.FixedUpdate(), ObiExternalForce.FixedUpdate() and ObiSolver.LateUpdate() ), but it'll randomly spike to anywhere between 5 and 20 ms.

I've seen other posts that recommend lowering the max timestep but that doesn't seem to help. I've lowered it down to 0.011 with a fixed timestep of 0.011 (set by SteamVR), and there are still spikes. Also things start to slow down and look weird, and other parts of the game depend on physics so I don't want to mess with global time settings too much.

Screenshot of a spike with maximum allowed timestep set to 0.011:
[attachment=471]

Another spike, while maximum allowed timestep is 0.02:
[attachment=476][attachment=475]

Similar spikes occur when I have the solver in after fixed update and late update mode.

After Fixed Update:
[attachment=474]

Late Update:
[attachment=472]

In addition, there seems to be quite a performance draw in general from MeshSkinning.Update(). When I disable the skinned mesh renderer, there is an almost identical performance cost from VSync, if that is relevant. If you have any suggestions for how to improve this or the spikes, that would be great!

Is this possible?

I want to fake a rope paying extending like a endless conveyor belt. 
Alternatively I would use two cursors to add in one end and delete in the other, but i guess it would have higher performance to not simulate particles at all and just change the uv anchor, however doing "renderer.uvAnchor = renderer.uvAnchor - speed * Time.deltaTime" does not work at runtime or in executeineditormode.

(19-11-2019, 01:15 PM)TheMunk Wrote: Is this possible?

I want to fake a rope paying extending like a endless conveyor belt. 
Alternatively I would use two cursors to add in one end and delete in the other, but i guess it would have higher performance to not simulate particles at all and just change the uv anchor, however doing "renderer.uvAnchor = renderer.uvAnchor - speed * Time.deltaTime" does not work at runtime or in executeineditormode.