When comparing Flax Engine vs Wave, the Slant community recommends Wave for most people. In the question“What are the best 3D C# game engines?” Wave is ranked 6th while Flax Engine is ranked 7th. The most important reason people chose Wave is:
In addition to online [API documentation](http://waveengine.net/Engine/Documentation), the Wave Engine team provides [tutorials](http://www.indiedb.com/engines/wave-engine/tutorials) via IndieDB, plus [sample projects](https://github.com/WaveEngine/Samples) and "[QuickStarters](https://github.com/WaveEngine/QuickStarters)" via GitHub.
Ranked in these QuestionsQuestion Ranking
Can be used for free until you hit a rather high revenue cap, at which point you have to pay royalties.
Pro Powerful C# scripting
C# scripting is really well made, comparable to Unity, but without any of the legacy cruft.
Supports most platforms, including Windows, Linux, Android, Nintendo Switch, ...
Pro C++ support
The entire core is written in C++ and it supports writing game code in C++. The interoperability between C# and C++ is also nothing to scoff at.
Pro Excellent documentation
The documentation is well written, up to date and accepts improvements from the community.
Pro Great and extensible editor
The editor is both powerful and simple. My favourite part is how easy it is to extend the editor with custom magic.
Pro Source code available
The entire source of the engine is available on Github, though not under an open source license.
Pro Modern rendering backend
Has a very modern, performant and beautiful rendering backend.
Pro Supports multiple IDEs
Works with any text editor and comes with proper support for Visual Studio, VSCode and Jetbrains Rider.
Pro Supports coding in C#, F# and Visual Basic
Wave Engine explicitly supports all three core .Net Platform languages.
Pro Oculus Rift support
The Wave Engine team provides an official, open-source Oculus Rift extension via GitHub.
Con New software
As is standard with new software, not all of the bugs have been ironed out yet.
Con Few plugins
Unlike more mature engines, there isn't a vibrant ecosystem of plugins yet.
Con Not open source
While the source code is available, it's not quite open source
Con Not latest C# version
It uses Mono and is still on some variant of C# 7.
Con No OpenGL support
It only supports modern APIs, namely Vulkan and DirectX. This means that it won't run on very old machines.
Con Mandatory splash screen
Games and applications made with Wave Engine must display a splash screen advertising it. No splash-free license option is available.
Con Not many tutorials available
Con Outdated UI
The UI looks like it is from Windows XP days. A refresh is much needed.