Add to Chrome
Add to Edge
Add to Firefox
Add to Opera
Add to Brave
Add to SafariWhen comparing pyglet vs Wave, the Slant community recommends Wave for most people. In the question“What are the best 2D game engines?” Wave is ranked 33rd while pyglet is ranked 43rd. 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.
Specs
Question Ranking
Pros
Pro 3D support
Since pyglet is so tightly woven with OpenGL it allows the support of drawing in 3D.
Pro Cross-platform
Works with Windows, Linux, and OS X.
Pro Written in pure Python
A small advantage, but being a core Python developer, it may be the best to stick to the roots and develop with pyglet as it is able to compile using other Python interpreters.
Pro Extensive learning material
In addition to online API documentation, the Wave Engine team provides tutorials via IndieDB, plus sample projects and "QuickStarters" via GitHub.
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.
Pro Many components are open source
Several core components and official extensions of the Wave Engine are publicly hosted on GitHub.
Cons
Con Small community/popularity
There is a decent amount of documentation and API to go along with pyglet, but in terms of community support there seems to be very little.
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.
