Free licenses for test reports. Drop-In Sky & Weather and Drop-In Water. Test them on AMD, Intel or Apple GPUs, macOS or Linux. The license is yours to keep. Apply by email.

Drop-In Waterfall — Realistic URP System documentation

Havoila Studio · Version 1.1.0 · Unity 2022.3 LTS and newer · Universal Render Pipeline 14 and newer

Drop-In Waterfall combines a falling-water column with an irregular, animated outline, fake self-shadowing, mist, spray, drips and a transparent river. The effect is designed for desktop, mobile and XR projects using URP. Its shaders require no camera depth or opaque texture. They are lit by the scene: the sun or the moon with its shadows, the ambient light and, optionally, point and spot lights; they take Unity's fog, or Drop-In Sky's fog and ground mist. The river can sample Unity reflection probes.

The effect is authored with one component, Waterfall. It saves only its settings, its look and its river bake, in your scene or prefab, and builds its meshes and the river's data texture in memory when the scene loads; the editor sets up its Shuriken particle systems. Nothing is written to your project, and nothing runs per frame.


1. Key features

  • Falling-water column. Ribbons follow the real ballistic path of the water. Streak textures are sampled at each water parcel's "birth time", so the streaks accelerate and stretch with gravity without any simulation.
  • Irregular, living outline. Bulges, necks and a sideways wobble travel down with the water. They are animated in the vertex shader.
  • Fake self-shadowing. Thick masses of water block the sky and show as darker grey patches and surges that travel down the column.
  • Volume from particles. Water clumps, column spray, column mist, a mist blast along the pool, slowly rising mist and impact spray.
  • Mist tubes. Animated mist wrapped around the foot of the waterfall. The walls fade where they are seen edge-on, so the mist reads as a soft volume from every side.
  • Lit by the scene, day and night. The sun or the moon lights the water and spray: wrapped around the column, through the thin water and spray from behind, glowing when you look towards the light through them, with the main light's shadows. Nothing glows by itself, so at night the waterfall is as dark as the rocks around it. It takes Unity's fog, and Drop-In Sky's fog and ground mist when they are present.
  • Works from any viewpoint. Nothing is oriented towards a camera or a viewer position: walk or fly all around the waterfall.
  • Drips. Drip sources along the rock, each with fine, streaked drops and an optional GPU-only rain-curtain ribbon.
  • River and plunge pool. Transparency, depth colour, flow-mapped ripples and foam come from a one-time top-down bake, so there is no depth texture at runtime. Three bake modes cover a flat pool, any ground mesh or terrain, and a river path drawn on the ground in the Scene view.
  • Artist-friendly Inspector. Instant section toggles, inline materials, sliders with tooltips, live rebuild and slow-motion Scene preview.
  • Scene view handles for the lip, exit velocity, widths, drip sources, pool, river region, mist tubes and the impact spray's aim.
  • Create menu with ready-made layouts (6 m, 15 m and 35 m drops) and a ready-to-use prefab.
  • XR rendering. Single-pass instanced and multiview variants, premultiplied alpha, fixed effect queues, and water-height and near-camera fades.

2. Requirements and compatibility

Unity 2022.3 LTS or newer. Tested with 2022.3.62f3 and 6000.6.7f1.
Render pipeline Universal Render Pipeline 14 (Unity 2022.3) or newer, tested with URP 14.0.12 and 17.6. Built-in RP and HDRP are not supported.
Target use Desktop, mobile and XR. Shaders include single-pass instanced and multiview variants. Validate graphics API, stereo rendering and performance on your target device.
URP settings Nothing special: the depth texture and opaque texture can stay off (the optional soft particle intersections need the depth texture). The main light's shadows reach the effect while the URP Renderer's Transparent Receive Shadows is on, as it is by default.
Effect dependencies URP only. The demo's fly camera works with the Input System and the legacy Input Manager.
Enter Play Mode Options Supports disabled Domain Reload and Scene Reload. Checked through two consecutive play/stop cycles in Unity 6000.6.7f1.

3. Package contents

HavoilaStudio/DropInWaterfall/
  Runtime/        The Waterfall component (builds its meshes at load), river bake, looks, Inspector attributes
  Editor/         Builder, river bake, Inspector, handles and preview
  Shaders/        Four effect shaders and shared HLSL
  Materials/      Nine default effect materials
  Textures/       Six effect textures
  Prefabs/        Waterfall_Medium and its materials
  Demo/           Example scene, fly camera and environment
  Documentation/  Markdown and PDF guide

4. Quick start

Open the demo

  1. Open Demo/DropInWaterfall_Demo.unity inside the package folder.
  2. Select the object with the Waterfall component. The Inspector shows every part of the effect.
  3. Press Play, or tick Live preview in the Inspector to animate the effect in the Scene view. In Play mode, fly around it: right mouse to look, W A S D Q E to move, Shift faster, the mouse wheel for the speed.

The effect can be viewed from any side. To add one to your own URP scene, follow either of the workflows below.

Create your own waterfall

  1. Move the Scene view so its pivot is where the plunge pool should be.
  2. Choose Tools > Havoila Studio > Drop-In Waterfall > Create Waterfall > Small / Medium / Tall.
  3. A complete waterfall is created with the package's materials. Its look is its own (section 6): nothing is written to your project.
  4. Use the Scene handles (Inspector toolbar: Column, Drips, Pool, Mist) to fit it to your cliff.
  5. Press Bake river once the pool and river are in place.

Or drop the prefab

Drag Prefabs/Waterfall_Medium.prefab into your scene, as many times as you like. Each copy is independent: editing one never changes the prefab or the others (section 11).

5. How it works

Part What is built Cost
Column, sheath, drip curtains Curved ribbons, one mesh per ribbon (one for all the curtains); vertices follow a ballistic path. Built in memory when the waterfall loads. Geometry depends on ribbon count and resolution
Mist tubes Open, flared tubes merged into one mesh, with animated noise and soft fades. Built in memory when the waterfall loads. Geometry depends on tube count and resolution
River Surface mesh and data texture (depth, foam, flow), built from the river bake saved on the waterfall 5 base texture fetches plus optional probe samples
Particles Shuriken systems for clumps, mist, spray and each drip source, set up by the editor CPU: live particle count; GPU: overdraw
  • Coordinates. Every position in the component is in the local space of the waterfall GameObject: move the GameObject to move the whole waterfall. Rotate it around Y only and keep a scale of 1, because gravity is always world-down. The meshes, the river flow and the particles turn with the waterfall (a prefab instance rotated and rebuilt with 1.0: after one Rebuild).
  • Orientation. Everything is oriented from the main column's exit direction (out from the cliff), never towards a camera. The ribbons bulge out along it; the lip, the drip edges and the emitters run across it. The waterfall therefore looks right from any viewpoint.
  • Height fades, and optional soft particles. The particle and mist shaders fade out above the water surface, so they never cut hard into the pool, without a depth texture. Each waterfall gives its water height to its own renderers (property blocks), and again whenever it is moved. Where large mist puffs meet rocks or ground, tick Soft intersections on the particle material; it needs the URP Depth Texture.

6. Inspector reference

The header toolbar contains:

  • Live rebuild. Value changes rebuild the effect automatically. The river bake is excluded because it takes a few seconds.
  • Live preview. Animates the particles and shaders in the Scene view without entering Play mode.
  • Rebuild / Rebuild all. Rebuild all also re-bakes the river.
  • Scene handles. Choose which group of handles is shown in the Scene view. The handles of a part that is switched off are hidden (its button is greyed out).
  • All ON / All OFF and Expand all / Collapse all.

Every section has an ON/OFF toggle. Toggling hides or shows the generated objects instantly, with no rebuild. Hover any field for a tooltip.

Looks. The material blocks inside the sections show each material's settings as this waterfall shows them. A change is instant and saved on the waterfall, its look: the material file is not changed, so other waterfalls using the same material keep theirs. Changed settings are marked ●, and the block's title counts them. Reset forgets them; Save as material… saves the material with them as a new file, used by this waterfall from then on; Apply to material writes them into the material itself (every object using it changes). Two settings stay on the material for every waterfall using it, because they are shader keywords: Receive shadows and the river's Reflection probes (select the material to change them).

A waterfall made with Drop-In Waterfall 1.0 shows only Convert to 1.1 until it is converted (section 11). A prefab asset selected in the Project window is read-only: Open Prefab to edit it.

Section Controls
General Preview speed (editor slow motion), Save as prefab
Waterfall column Lip, exit direction and speed, bottom height, widths, offsets, arc, resolution, opacity, fade-in, seed, and the column material (colours, body, streak motion, irregular shape, self-shadowing)
Column sheath The other ribbons (a soft halo around the column) and their material
Column clumps Rate, shadow tint (random darker clumps) and the clump material
Column spray Rate, droplet size, streak length and the spray material (shared with Impact spray)
Column mist / Impact mist blast / Impact rising mist Rate, size, growth, life time, speed, area, spread, drag, lift, opacity, spin, max particles, and the mist material (shared by the three)
Impact spray Rate, size, growth, streak length, life time, speed, area, direction (Circular: up and out all around the impact, with an outward angle; Cone: aimed one way, with a heading from the column's exit direction, an elevation and a spread), gravity, opacity, max particles
Mist tubes The tube list (centre, bottom and top radius, height, tint, seed, speed) and the mist material (billow size, rise and swirl speed, shape, edge-on fade, fades)
Drips The drip sources (position, width, bottom, rate, curtain opacity), the drop settings shared by all sources (rate multiplier, size, stretch, life time, speed, spread, gravity, opacity, cap), the drop material, and the curtains (show / hide, curtain material)
River Bake mode and settings (bake resolution, depth smoothing, max texture size on Android), plunge pool, flow, reflection probes, reflection smoothness/strength/tint
Advanced The raw ribbon list (add or remove ribbons), the main column index, the Build particles option

7. Scene handles

Group Handles
Column Lip (moves every ribbon), exit velocity (a sphere 1 s ahead of the lip: direction and speed), top and bottom width, bottom height. The trajectories of every ribbon are drawn.
Drips Position, width and bottom of each drip source
Pool Plunge pool centre and radius, river bake region (box), water level; in Path mode the pool outline. Press Bake river afterwards.
Mist Centre, bottom radius, top radius and height of each mist tube
River Path mode: the river path points (position on the ground, water height, width). Press Bake river afterwards.
Impact Impact spray: height and radius of the splash zone (cubes), opening angle (sphere on the edge ray) and, in Cone mode, the aim (sphere at the tip of the axis: heading and elevation). The flight of the droplets is drawn down to the water, and the spray follows while you drag.

A group's handles are only shown while its part is switched on: Column with the column or the sheath, Drips with the drips, Mist with the mist tubes, Pool and River with the river, Impact with the impact spray.

While you drag a handle, only the ribbons are rebuilt, so dragging stays fast. The full rebuild runs when you release the mouse. Every handle edit can be undone.

8. River bake

The river is baked once, from above, over the River region box. X runs downstream.

Mode Use it for
Flat Rectangle No ground needed. A rounded pool with an irregular shoreline fills the region at Water level. It is the default for new waterfalls.
Below Water Level Any ground mesh (MeshFilter) and/or Terrain. The water is wherever the ground is below Water level and connected to the pool, and the real depth is measured.
Path A river path drawn on the ground in the Scene view (handles: River), with a width and a water height per point, and an optional pool outline (handles: Pool). Works with any ground, including scans split into many textured meshes.

The bake stores its result on the waterfall's FX_River object, in the scene or prefab: the data texture (R depth, G foam, BA flow, kept as a PNG, with a smaller copy for Android when it is larger than Max size on Android) and the surface mesh's grid. Nothing is written to your project: the waterfall rebuilds the texture and the mesh from it when it loads. The flow is stored in the waterfall's own space, so it turns with the waterfall (a river converted from 1.0 keeps its world-space flow until it is baked again). Bake river turns orange when the river settings changed since the bake. The flow follows the geodesic distance from the pool through the water (along the path in Path mode), so it turns with river bends and spreads radially in the pool. Foam comes from the impact, the rapids (fast and shallow water) and, with Texture Foam, the white water photographed in the ground texture.

9. Shaders

The waterfall, mist, particle and river shaders use premultiplied transparency, include stereo variants and are lit by the scene (see Lighting and fog below). Their render queues are:

  • River: Transparent-50
  • Mist: Transparent-10
  • Column and particles: Transparent
Shader Notes
Column 4 fetches of one RGBA streak texture, plus 1 for self-shadowing. Vertex-animated outline. Lit per pixel by the main light (its shadow map and cookie add a fetch each when the scene has them).
Mist 3 fetches of one RGBA noise texture, seamless around the tubes. Edge-on, height and near-camera fades. Lit per vertex.
Particle 1 fetch (R alpha, G self-shading). Height and near-camera fades, adjustable additive amount, optional soft intersections (1 depth fetch). Lit per vertex.
River 5 base texture fetches: data, 2 ripple normals and 2 foam samples. Reflection probes add samples. Includes ripple distortion, smoothness, probe blending, box projection, Fresnel, depth absorption and shore fade. Body and foam lit per pixel by the main light.

River reflections. River material > Reflection probes is on by default. Place and bake a Unity Reflection Probe whose influence volume covers the water, or use a custom/realtime probe. Outside local probes, URP uses the scene's environment reflection. Reflection smoothness controls blur, Reflection strength controls the Fresnel contribution, and Reflection tint colours the reflected environment (white leaves it unchanged). Ripples distort the reflection automatically.

Enable Reflection Probe Blending and Box Projection on the active URP asset to use those features; box projection must also be enabled on the probe. Forward and Forward+ rendering are supported. River renderers use Blend Probes.

Untick Reflection probes to use the original flat-colour reflection without probe texture samples. Baked or custom probes avoid realtime capture cost; probe sampling still adds GPU work, especially with blending. No camera depth or opaque texture is required.

The editor preview can slow the effect down with a global clock (_HavoilaWaterfallTime / _HavoilaWaterfallTimeMode). In builds the shaders always use _Time.

Lighting and fog

The effect is lit as the rest of the scene is, so it fits in from noon to midnight:

  • Main light. The sun, or the moon when a sky makes it the main light. It wraps around the column (light scatters inside the water), passes through the thin water and the spray from behind, and glows when you look towards it through them. The column and the river take it per pixel, with the main light's shadows (a cliff's shadow falls across the falls) and its cookie (Drop-In Sky's cloud shadows); the mist and the particles take it per vertex.
  • Ambient light. The scene's ambient light (Lighting > Environment), which Drop-In Sky updates from its sky, dark at night. The generated renderers do not use light probes.
  • Point and spot lights. Off by default: tick Point and spot lights on a material, for a campfire by the pool. They light the effect per vertex, without shadows, in Forward and Forward+.
  • Nothing glows by itself. The material colours are the water's colours under a white light of intensity 1, as on a Lit material. Under a brighter sun the water is brighter, and at night it is as dark as the rocks around it, whatever exposure the camera uses.
  • Per material: Scene lighting (1 = lit by the scene; 0 = fixed colours, the same by day and by night), Glow against the light, Light through thin water and Light through thick water (column: how much the sun shines through the frayed edges, and through the core when the falls are backlit), Receive shadows, Point and spot lights.

Only realtime light reaches the effect: it uses no lightmaps or light probes. Under a directional light set to Baked, the waterfall shows the ambient light only: set the light to Mixed or Realtime, or lower Scene lighting.

Fog. Transparent objects are drawn after the scene has been fogged, so the effect fogs itself, per vertex:

  • With Unity's fog (Lighting > Environment > Fog), it is fogged as opaque surfaces are.
  • With Drop-In Sky (sold separately), it takes the sky's fog and its ground mist, which the sky publishes for transparent objects; Unity's fog is then off. Drop-In Waterfall reads these values by name and does not depend on Drop-In Sky: without it, nothing changes.

10. Performance

Cost depends on ribbon and tube resolution, river area and bake resolution, enabled emitters, particle caps, screen coverage and reflection settings. Mesh counts are not measured draw-call counts: use Unity's Profiler or Frame Debugger in your target configuration.

The effect uses six supplied PNG textures, plus per-waterfall baked data:

Texture Source resolution Purpose
T_WaterfallStreaks 256 x 1024 Falling-water streaks and self-shading
T_ParticleAtlas 1024 x 512 Particle shapes and shading
T_MistNoise 512 x 512 Mist tube noise
T_Foam 512 x 512 River foam
T_RiverNormal 512 x 512 Ripple normal map
T_Droplet 64 x 64 Fine drips and spray

River-data dimensions depend on the bake settings. Environment geometry, environment textures, lightmaps and reflection cubemaps have separate costs. Profile the effect in your own scene rather than treating an example scene as a fixed performance budget.

Loading. Each waterfall builds its meshes and decodes its river texture once, when it loads: a few milliseconds for the shipped waterfalls, up to a few hundred for a 4096 px river bake. Identical waterfalls (instances of one prefab) share one set. Nothing runs per frame. A river bake takes about 1.4 times its PNG's size in the scene or prefab file and about 2.7 times in memory, for each placed copy (the built meshes and texture are shared, the bake itself is not): tens of KB for usual bakes, a few MB for the largest. A river converted from 1.0 keeps its 1.0 mesh and takes several times more. The built meshes are not readable from scripts in players.

Lighting adds per-pixel work to the column and the river only: the main light's shadow map and cookie (one fetch each when the scene has them). The mist and the particles take their light per vertex, and every part takes its fog per vertex. Point and spot lights, when ticked, loop over the lights per vertex. Soft intersections add one depth fetch per particle pixel.

To save CPU or GPU on standalone VR:

  • Reduce particle CPU work. Lower Drip sources - particles > Rate Multiplier, per-source rates or particle caps.
  • Reduce transparent overdraw. Use fewer, smaller or shorter mist tubes and fewer mist particles.
  • Budget reflections. Prefer baked or custom probes, lower cubemap resolution when appropriate, or untick Reflection probes on the river material. Realtime captures add rendering work beyond the river shader itself.
  • Untick Receive shadows on the column and river materials if the main light's shadow map is too costly on your device; keep Point and spot lights and Soft intersections off.
  • Turn off the parts that are hidden in your view.
  • Measure frame time on the target device at the intended resolution and refresh rate.

11. Multiple waterfalls, moving and prefabs

  • Nothing is written to your project. A waterfall saves its settings, its look and its river bake in the scene or prefab, like any component. Its meshes and river texture are built in memory when it loads.
  • Every copy is independent. Duplicates (Ctrl+D), copy and paste, prefab instances and unpacked copies each have their own settings, look and river: editing one never changes the others. Prefabs carry everything: Save as prefab, Apply, Revert, overrides and variants work as with any component, and Undo, Discard changes and reloading a scene undo every change made to a waterfall (Save as material… and Apply to material write material files on purpose).
  • Moving and rotating. The water height follows the waterfall. The meshes, the river flow and the particle velocities turn with it, the package's prefabs included; a prefab instance rotated or edited and rebuilt with 1.0 follows after one Rebuild (the Console names it when its scene opens, and its Inspector offers Rebuild). Keep the rotation around Y only and the scale at 1.
  • At runtime, instantiate a waterfall with its position (Instantiate(prefab, position, rotation)), or call Refresh() on it after moving it. Call Refresh() after changing its settings from a script: it rebuilds the meshes, not the particle systems.
  • Keep the Waterfall component, in the editor and in builds: it builds the meshes. Its checkbox hides the falls, mist and river only (the particles are separate components).
  • Materials stay shared on purpose. Each waterfall's look is its own (section 6); a change to a material file reaches every waterfall using it, except the settings a waterfall changed for itself. The package's materials keep their values in future updates (a new look comes as a new material).
  • The property blocks of a waterfall's FX_* renderers belong to it (they carry its water height, river and look): a script that sets its own block on them replaces those values.
  • Waterfalls made with 1.0 (with the Create menu, unpacked copies, your own prefabs) keep their 1.0 look but can't be edited until you press Convert to 1.1 in their Inspector, or Tools > Havoila Studio > Drop-In Waterfall > Convert 1.0 Waterfalls in Open Scenes. Two exceptions: an unpacked Waterfall_Medium copy shows the river saved in Prefabs/Waterfall_Medium again (with 1.0, baking another Medium could change the river it showed: if its flow looks wrong, convert it and press Bake river), and with 1.0.0 an unpacked copy of the demo waterfall shows no river until it is converted. Prefabs saved with 1.0's Save as prefab from a placed Waterfall_Medium or demo waterfall are variants of it: like placed copies, they switch to 1.1 at once (open one and press Rebuild if its copy was rotated or edited). Converting keeps their materials and river exactly as they were and builds their meshes from their settings: the same meshes, except an unpacked Waterfall_Medium copy, whose falls become the 15 m its settings give (1.0 shipped it with meshes from a 32 m version). The Console lists the 1.0 files they no longer use (their FX_*.asset meshes, T_RiverData.png): delete those once no other 1.0 waterfall uses them, and keep the materials and any prefab saved next to them. Converting your own prefab changes the prefab file and every instance, and can't be undone: keep a copy. Its instances get their own 1.0 river back when it is in their 1.0 folder (their Output folder, or <scene>_Waterfall/<their name>): at once, or with Restore its river in scenes that are not open; one renamed or copied since that bake, baked before its scene was first saved, or whose scene was renamed or moved shows the prefab's river: press Bake river on it (its settings are kept). An instance of the package's prefab that baked a river of its own into its own output folder offers Restore its river; one that baked into the package's Prefabs/Waterfall_Medium or Demo/Generated folder (the 1.0.0 and 1.0.1 defaults) shows the prefab's river: press Bake river on it.

12. Limitations

  • The falling water is a set of curved ribbons, not a volume. Seen exactly along the lip, the column looks thinner, as a real waterfall does.
  • Only realtime lights reach the effect (Mixed or Realtime; not Baked), and it takes the scene's ambient light, not light probes. Point and spot lights are per vertex, without shadows or cookies. The water has no specular sun glints, and the effect casts no shadows. River reflections come from probes or a flat tint. There is no water interaction or collision.
  • Transparent surfaces can still sort imperfectly when they overlap other transparent objects.
  • Reflection probes provide cubemap reflections, not planar or screen-space reflections. A baked probe does not update when scene objects move.
  • The river is a static bake: its shape, depth and flow do not change at runtime.
  • The waterfall object must be rotated around Y only and keep a scale of 1.
  • The particle systems are set up by the editor: settings changed from a script at runtime reach the meshes (Refresh()), not the particles.
  • Static batching does not apply to the FX_* objects (their meshes are built at load; the shaders also need local space).
  • URP only.

13. Troubleshooting

  • I change a value and nothing happens. Check that Live rebuild is ticked and that the section is ON. River settings need Bake river.
  • The particles are frozen in the Scene view. Tick Live preview. Unity only simulates particles in edit mode while they are selected; the preview drives them for you.
  • Mist or particles are cut, or invisible near the water. Bake the river again so the waterfall knows its water level. Also check the Fade above water value of the material.
  • The river covers the banks. Lower Water tolerance, raise the ground, or shrink the River region and bake again.
  • The river reflection is missing or flat. Enable Reflection probes on the river material, bake a probe covering the river, and check its influence volume, tint and strength.
  • The waterfall is too dark. It is lit by the realtime main light: a sun set to Baked does not reach it. Set the light to Mixed or Realtime (and bake again), or lower Scene lighting on the waterfall's materials. Check the scene's ambient light (Lighting > Environment) too.
  • The waterfall glows at night. Set Scene lighting to 1 on every waterfall material.
  • No shadow of the cliff on the falls. Turn on Transparent Receive Shadows on the URP Renderer, check the light's shadows and the Shadow Distance, and Receive shadows on the materials.
  • The column looks flat when the sun is to its side. It was made with an early 1.0 version, whose meshes have no surface normals: press Convert to 1.1, then Rebuild.
  • Large mist puffs cut lines into rocks or ground. Tick Soft intersections on the particle material, set its distance, and turn on the Depth Texture on the URP asset.
  • Materials are pink. URP is not the active render pipeline.
  • Another waterfall changed too. A material file they share was changed (Apply to material, or the material's own Inspector). Change the look in the waterfall's Inspector instead, or use Save as material… for a copy.
  • Its Inspector only offers Convert to 1.1. The waterfall was made with Drop-In Waterfall 1.0: convert it (section 11).
  • A waterfall shows nothing after updating. Its Waterfall component was removed (1.0 allowed it): add it back (on a prefab instance: Overrides > the removed component > Revert). The Console names such scenes when they open.
  • The particles of a rotated waterfall fly the wrong way. It is a prefab instance, or a prefab saved from one, rotated or edited and rebuilt with 1.0, which kept that build's particles: press Rebuild (its Inspector offers it; for a prefab, open it and press it there).
  • Bake river is orange. The river settings changed since the bake, or the river was converted from 1.0: press it to bake with the current settings.

14. Support

Havoila Studio · support@havoila.com · havoila.com

Online documentation: havoila.com/assets/drop-in-waterfall/docs/

Please include your Unity and URP versions, the target platform and a screenshot of the Inspector.

15. Version history

  • 1.1.0: nothing is written to your project: each waterfall saves its settings, look and river bake in the scene or prefab and builds its meshes when it loads, so copies and prefabs are independent and carry everything; each waterfall's look is its own (the material files are not changed); the river flow and the particles turn with the waterfall; waterfalls made with 1.0 keep their look until Convert to 1.1; Waterfall_Medium shows the 15 m falls its settings describe; the demo has its own fly camera (no XR Legacy Input Helpers needed) and its environment in player builds; several waterfalls rebuild together; the editor buttons are off in Play mode.
  • 1.0.1: the impact spray can be aimed (Direction: Circular or Cone), with new Impact Scene handles; the default river material no longer points at the demo's river texture (after updating, press Bake river on a waterfall that uses Materials/M_River itself); after a few days of use, a band under the Inspector's header asks for a review on the Asset Store (Write a review opens the store page, its close button hides it for good).
  • 1.0.0: first release.