Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
WaitForAllTasks spent a lot of time!
#5
(20-09-2017, 01:57 PM)josemendez Wrote: What are your ObiSolver settings? You could try reducing the amount of constraint iterations. If you're not piling a lot of fluid (inside a container for instance) 2 density iterations should be enough.

You can add the ObiProfiler component to your solver and you'll get a very detailed on-screen graph of the core usage in your CPU when you run the scene, and how much time each internal Obi function is taking up. If you could take a screenshot of it I could tell you more. 50 ms/frame is definitely not normal for just 1000 particles, unless you're using a huge/lots of MeshColliders or something similar.

As a reference, the FluidViscosity test scene with 3000 particles takes about 6-8 ms/frame in my computer (a pretty modest 4-core cpu).

Hi jose,

I attach my configuration of the solver and the profiler image. It seems the collision processing takes much time. But in my scene i used just 5 mesh colliders (4 mesh colliders used for 4 walls in the room). It's definitely not normal.
Reply


Messages In This Thread
RE: WaitForAllTasks spent a lot of time! - by sunyifeng83 - 21-09-2017, 03:43 AM