The open Crest repository is the built-in renderer only
A class-leading water system implemented in Unity
At a glance
- What is it?
- Crest is a water system for Unity whose open repository targets the built-in renderer, while the high definition and universal render pipeline variants are separate packages on the Unity Asset Store, and a fifth major version is sold the same way. Installing it is copying one folder into an existing project, and the version table in the README pins four editor versions to four different releases.
- Who is it for?
- Crest suits a Unity project on the built-in renderer that wants an ocean system and is willing to read the online documentation, since the two shader variants cost money. It does not suit a project on a scriptable render pipeline that expects the open repository to cover it, because those packages are separate, nor a project on a graphics backend the requirements exclude outright.
- Can I use it commercially?
- Yes. MIT is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
- Is it still maintained?
- Yes. The repository last received commits 150 days ago.
- What is it written in?
- Mainly C#, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.
Star history
- wave-harmonic/crest3,944 ★ · +40
| Repository | 2026-09-26 | 2026-11-15 |
|---|---|---|
| wave-harmonic/crest | 3.9k | 3.9k |
40 Stars in the last 50 days, measured from the daily GitHub snapshot. Compare with other projects
Editorial analysis
This repository targets one renderer, and the others are products
One line decides which package you need, and it comes before everything else in the file: the repository targets the built-in renderer, and other render pipelines are handled elsewhere. Those elsewhere packages are three separate listings on the Unity Asset Store, one for the built-in renderer with the high definition pipeline variant, one for the high definition pipeline, and one for the universal pipeline. Then a second line, short and without ceremony, says a fifth major version is now available, linking to its own store listing. So the distribution model is a free repository for the default pipeline and paid packages for the other two, with the next major version sold rather than released. The repository itself is under a permissive licence and has no published releases, only tags.
Two graphics backends are excluded by name
The requirements section has three lines and the third is the one that will end a conversation fastest. Unity needs to be at a specific recent editor version or later, the shader compilation target needs to be at a given level or above, and Crest does not support the OpenGL or WebGL backends. That is a hard exclusion rather than a warning, so a project building for the web, or for a platform where only the older graphics interface exists, is out of scope regardless of licensing. The compiler target line matters because the water system is largely a shader problem, and a project that has deliberately lowered the shader target for older hardware will find the system unavailable. Both numbers are written as minimums, so the rule is simple: meet them or do not use it.
Installation is copying one folder into an existing project
There is no package manager step and no installer. The instruction is to take the latest stable release from the top of the tags page, extract the files, and copy everything under the Crest assets directory into a project you already have. Two subdirectories are called out in a note, and both are optional in different senses. The examples directory is described as useful for a first time user but not required for the core functionality, which is the polite way of saying it is a large folder of scenes you will probably delete. The development folder is not needed at all unless you intend to work on Crest itself. So the practical install is smaller than the download, and the only decision is whether to keep the sample scenes as a reference while you wire the system into your own scene.
Four editor versions map to four pinned releases
A small table answers the question the minimum version creates, which is what to do if your editor is older than the current requirement. Four editor versions are listed, each with the Crest version built for it. Two of the newer editor lines share a single release, so the same tag serves both, and the two older lines each have their own, older release. That table is the whole backward compatibility story, and it is a static one: there is no range, and no note about which of those releases still receive fixes. The consequence for an upgrade path is that moving your editor forward means moving your Crest version forward too, and the reverse is not obviously true, since the older lines are pinned to tags that are no longer the newest.
The video gallery is the feature list
The README is mostly a wall of video links, and the project is candid about it. A gallery block holds a dozen embedded players, then a separate block of six more introduced as a handful of nice scenes, then the word and many more. None of it is a feature list, which is unusual and not necessarily a criticism: for a visual system the scenes are the argument, and a bullet list of gerstner wave options would tell you less than a clip of a harbour at sunset. What is missing is any written explanation of what the system does, so a reader has to watch before deciding, and a reader who is deciding from a search result gets nothing at all until they open the file. The links out at the top are the only written description: an advanced water system implemented in Unity.
Documentation is split between the project and the community
Two documentation sources are named, and the split is by authorship. Full documentation is hosted on a readthedocs address, configured from a file in the repository, and the sources for it are the docs directory. Separately there is a wiki, described as carrying community contributions, which is where fixes and recipes that never made it into the official documentation live. The repository root follows the same split, with a contribution guide and a contributors file for the project itself, and a links file that is presumably where the video showcase and store listings are kept. The practical advice for an adopter is to read the official documentation for the system and the wiki for the specific renderer or version you have, since the two are not guaranteed to agree on the same feature.
MIT in the repository, paid listings in the store
The licensing picture is the thing to hold in your head before reading anything else. The repository carries a permissive licence, the code you copy from it is yours to use under those terms, and the assets directory is what you copy. The high definition and universal pipeline variants and the fifth major version are store packages with their own pricing, sold by a publisher page linked in the header. Funding is handled the usual way, with a sponsor page offering tiers and the file saying plainly that support increases development bandwidth. There are no GitHub releases to install, only tags, and the last push to the default branch is dated 2026-06-18 with the repository not archived, so the tag list is the only version history a user has to reason about.
Editorial conclusion
Crest suits a Unity project on the built-in renderer that wants an ocean system and is willing to read the online documentation, since the two shader variants cost money. It does not suit a project on a scriptable render pipeline that expects the open repository to cover it, because those packages are separate, nor a project on a graphics backend the requirements exclude outright. Before installing, check which editor version you have against the pinned version table, and copy only the core folder if the example scenes are not what you want in your project.
Frequently asked questions
What is Crest in Unity?
An advanced water system implemented in Unity, described in the repository as class leading. The open repository targets the built-in renderer, while the high definition and universal render pipeline variants and the fifth major version are separate packages sold on the Unity Asset Store.
What are the requirements for Crest?
Unity at a specific recent editor version or later, a shader compilation target at a given level or above, and the system does not support the OpenGL or WebGL backends at all. So a web build or a project that has lowered its shader target is out of scope.
How do I install Crest in a Unity project?
Take the latest stable release from the top of the tags page, extract the files and copy everything under the Crest assets directory into an existing project. The examples folder is optional and useful for a first time user, and the development folder is only needed if you intend to work on Crest itself.
Which Crest version works with my older Unity editor?
The README pins four editor versions to four releases: two newer editor lines share one release, and each of the two older lines has its own older release. Take the release listed for your editor version rather than the newest tag, since the table is the only compatibility statement in the file.
Is Crest free to use?
The repository is under a permissive licence and the code you copy from it is covered by those terms. The render pipeline variants for the high definition and universal pipelines, and the fifth major version, are paid packages on the Unity Asset Store rather than open repository contents.
Official sources
Add this badge to your README
If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.
[](https://hysenlabs.com/projects/wave-harmonic-crest)Star history chart for your README
[](https://hysenlabs.com/projects/wave-harmonic-crest)Was this useful?