Mobile Optimizations

[pstudios]

Hi, I love the fluid plugin and it works great on my computer. However, on my android device which is pretty new is struggling to get through the basics of my small scale fluid animation, I would appreciate it if anyone could tell me as many steps as possible to optimize the efficiency on mobile devices (im fine with a reduction in quality as i want my project to work on as many devices as possible) any and all tips would be greatly appreciated. Thanks!

[josemendez]

Hi, I love the fluid plugin and it works great on my computer. However, on my android device which is pretty new is struggling to get through the basics of my small scale fluid animation, I would appreciate it if anyone could tell me as many steps as possible to optimize the efficiency on mobile devices (im fine with a reduction in quality as i want my project to work on as many devices as possible) any and all tips would be greatly appreciated. Thanks!

Hi there!

First of all, profile your scene in your device (trough ADB). Focusing your effort on something you're not sure its the bottleneck (could be simulation or rendering, seen both on different types of mobile devices) is generally not a good idea.

In case your bottleneck is rendering (highly likely if you're using the built-in fluid shaders, as they're meant for high-end desktops), you will need to write a simpler shader. We can help you with that if needed.

In case the problem is simulation, try to:
- Make Unity's physics timestep larger, and max timestep smaller.
- Reduce your fluid material resolution.
- Reduce the amount of density constraint iterations in your ObiSolver.

cheers!

[oddgoo]

Hi there!

First of all, profile your scene in your device (trough ADB). Focusing your effort on something you're not sure its the bottleneck (could be simulation or rendering, seen both on different types of mobile devices) is generally not a good idea.

In case your bottleneck is rendering (highly likely if you're using the built-in fluid shaders, as they're meant for high-end desktops), you will need to write a simpler shader. We can help you with that if needed.

In case the problem is simulation, try to:
- Make Unity's physics timestep larger, and max timestep smaller.
- Reduce your fluid material resolution.
- Reduce the amount of density constraint iterations in your ObiSolver.

cheers!

Greetings, I am a new customer and also wondering about this.

Our game is focused on mobile, and would love to have much simpler fluid renderer shaders, is there an example we can work from? My quick search didn't show any results.

Thank you for your attention

---

Greetings, I am a new customer and also wondering about this.

Our game is focused on mobile, and would love to have much simpler fluid renderer shaders, is there an example we can work from? My quick search didn't show any results.

Thank you for your attention

Actually, I've just found the flat and opaque shaders, and I'm happy to profile with those 

[Artem]

Hi there!

First of all, profile your scene in your device (trough ADB). Focusing your effort on something you're not sure its the bottleneck (could be simulation or rendering, seen both on different types of mobile devices) is generally not a good idea.

In case your bottleneck is rendering (highly likely if you're using the built-in fluid shaders, as they're meant for high-end desktops), you will need to write a simpler shader. We can help you with that if needed.

In case the problem is simulation, try to:
- Make Unity's physics timestep larger, and max timestep smaller.
- Reduce your fluid material resolution.
- Reduce the amount of density constraint iterations in your ObiSolver.

cheers!

Hello. Can you provide information where i can find "physics timestep larger, and max timestep smaller" and material resolution?

[josemendez]

Hello. Can you provide information where i can find "physics timestep larger, and max timestep smaller" and material resolution?

"Material resolution" is part of the fluid material asset used by your emitter. Here's the full documentation:
http://obi.virtualmethodstudio.com/tutor...rials.html

[Artem]

"Material resolution" is part of the fluid material asset used by your emitter. Here's the full documentation:
http://obi.virtualmethodstudio.com/tutor...rials.html

thanks for the answer.  

I was able to achieve 37 fps at 800 particles on xiaomi mi4s and would like to achieve 60 fps. 

Can you help me?

thanks.

[EbruBozkurt]

thanks for the answer.  

I was able to achieve 37 fps at 800 particles on xiaomi mi4s and would like to achieve 60 fps. 

Can you help me?

thanks.

Hello

I'm new around here and I liked using obi. It works fine on my computer, but when I throw it into the phone, my liquid spills out regardless of the collider of the bottle I put into it.

My main goal is to use it in Augmented Reality, but I can't move on to it before I can figure it out.

Can you help me please?

[josemendez]

Hello

I'm new around here and I liked using obi. It works fine on my computer, but when I throw it into the phone, my liquid spills out regardless of the collider of the bottle I put into it.

My main goal is to use it in Augmented Reality, but I can't move on to it before I can figure it out.

Can you help me please?

If you’re using MeshColliders for your bottles/containers, don’t. They’re “hollow”, which means only their surface produces collisions. Particles will easily tunnels trough their surface when moving them around. Use distance fields instead:

http://obi.virtualmethodstudio.com/tutor...ields.html

[MikeSan]

Hello.

I'm using Obi Fluid and I noticed that it takes a long time to launch the app on my Android device.
At first I thought it was a problem with my project, but when I built and launched the sample scene "FaucetAndBucket", it took the same time.
It takes about 10 seconds until the MainScene starts playing.
How can I reduce the startup time?
Thank you.

My environment
Unity 2019.3.7f1
Obi Fluid 6.0.1
Device GalaxyS10

[josemendez]

Hello.

I'm using Obi Fluid and I noticed that it takes a long time to launch the app on my Android device.
At first I thought it was a problem with my project, but when I built and launched the sample scene "FaucetAndBucket", it took the same time.
It takes about 10 seconds until the MainScene starts playing.
How can I reduce the startup time?
Thank you.

My environment
Unity 2019.3.7f1
Obi Fluid 6.0.1
Device GalaxyS10

Hi there,

I'm unable to reproduce this, opening the FaucetAndBucket scene takes 2-3 seconds on a Galaxy S4 for us. Obi does not do any preprocessing at startup, so there should be no waiting time at start. Simulation is done every the same way frame since startup.

Maybe you can use Unity's profiler to determine what's causing that extra wait at start in your device.

let me know how it goes,