Ultra Water
Humpalumps/Ultra-WaterReviewed by AI
What it does
A water renderer for three.js, the 3D library used in browser games and visualisations. It comes with a demo island scene you can fly around: wind waves, waves that bend and break near the shore, foam, sunlight patterns on the seabed, an underwater view with sun shafts, and crates and boats that bob on the swell. It is source code for people building their own 3D scene, not a finished program. You install Node, run two commands and open the page; phones and tablets get a lighter setting automatically.
How easy it is to install
C · install 1 or 2 tools · Windows
- Windows C
- macOS C
- Linux C
There is no download to install: on any of the three systems you need Node installed, then `npm install` and `npm run dev`, and you open the address the terminal prints (README). The scene itself needs a browser with WebGL2 and a reasonably strong graphics card; the author's numbers come from an RTX 3060.
Numbers on GitHub
- Stars
- 500on Oct 31, 2026
- Downloads
- —all releases
- Growth
- +500stars in 3 days
Stars over time
Facts
- Runs on
- Windows, macOS, Linux
- You need to install
- Node.js
- To build from source
- Node.js
- Disk space
- 100 MB–500 MB · estimate
- Accounts or keys
- None
- Cost
- Free
- License
- MIT (Permissive)
- Last update
- Oct 28, 2026
Risk signals (4)
- Infobrand new no releases
Project facts: created 2026-10-28, last push 2026-10-28, 0 GitHub releases, 0 open issues, already 318 stars. There is no version history to judge it by yet.
AI review
- Infonot packaged for reuse
package.json is marked "private": true and still carries another project's identity: "name": "gelatin-game-engine", "description": "Gelatin Game Engine". It is not published as an installable package, so reusing it means copying files from src/ by hand.
AI review
- Infobuilt with ai agents
README: "The design was argued out with a second agent before building, and again for each round of upgrades." The repository also has a .claude/ folder at the top level.
AI review
- Infoperformance numbers self measured
The README's own benchmark section says earlier published numbers were wrong ("Earlier versions of this README quoted numbers 2-4x lower") and that the newest foam feature "hasn't been re-measured cleanly yet". The frame rates come from the author's own in-page benchmark on one PC and one phone.
AI review
Evidence is shown in its original language.
What Radar could not check
- Whether the quoted 200+ fps holds on a different graphics card, browser or operating system
- How it behaves in browsers other than Chrome, and on Macs or iPhones
- How much disk the npm install takes (the estimate of 100-500 MB is a guess, not a measurement)
- How much work it really is to move the water into an existing three.js project, since there is no documented interface