Umi Water Pro — known limits
The limits of Umi Water apply too (Umi Water limits).
- Desktop. The FFT ocean and ripples need compute shaders: not WebGL, not OpenGL ES 3. On Android / iOS they are off by default (Allow On Mobile turns them on for a strong Vulkan phone; they cost 30–100+ ms on phones) and the water falls back to Gerstner waves.
- Ripples are simulated in a window around one camera (the
Focus, or theMainCamera-tagged camera; without either they do not run), so no split-screen ripples, and they pass through static obstacles. - Rivers: knot heights must go downhill; a waterfall is a height field (no gap behind the curtain), and it starts only where the curve between two knots drops steeper than 45°. Where channels meet, height and current blend (no hydraulics). The current carries the Gerstner waves, not the FFT ocean or the shore waves.
- Shore waves are one wave train that comes in to every coast (a lee side from the swell direction is optional); breakers spill, they do not curl.
- The water map is baked in the editor into an asset (otherwise at load); colliders that move at runtime do not change it, and moving the water bakes again. Water colour shows from above only, not in the underwater fog.
- Planar reflection mirrors the rest level only: flat water (lakes, pools, calm sea), not the slope of a river. It renders the scene a second time per camera (about +25 % GPU in our showcase at half resolution) and is not drawn at Low quality.
- Light shafts are computed at half resolution; caustics add a depth-normals prepass in a renderer without SSAO.
- The FFT ocean cannot predict the future:
TrySamplewith a future time extrapolates the last snapshot for at most 0.25 s. - A scene needs one
WaterParticlesand aMainCamerafor foam and the river mist.