09-09-2018, 12:25 AM
(05-09-2018, 05:05 PM)josemendez Wrote: Yep, it is not normal to have to use LateUpdate(). We benchmarked the FluidViscosity sample scene in several CPUs, and there are the frame times for them (in milliseconds):
Windows - Intel Xeon E5 (quad core): 8.7 ms/frame (114 fps)
Mac - Intel Core i7 (quad core): 11.2 ms/frame (89 fps)
Mac - Intel Core i5 (dual core): 17 ms/frame (58 fps)
None of them come even close to the +30 ms/frame you're getting. Make sure you try with all profilers disabled (both Obi's and Unity's, even when in non-deep profiling mode). Also try a standalone version of the scene, to rule out editor issues.
AMD's bulldozer-based CPUs are known for really low IPC (instructions per cycle) so they are usually way slower than other CPUs, specially for sequential tasks where the amount of cores is not relevant. However performance should not really suffer that much, since most of Obi is parallelized.
Thanks jose, you've been a great help trying to figure out what's going on. A tested a build version on a slightly "newer" AMD computer, an FX-8300 with similar results. It's looking like the FX series isn't capable of running Obi fluid without a lot of compromises.
I was finally able to achieve something runable by bringing down the simulation quality.
https://i.imgur.com/RlnVZek.gifv