When comparing Genome2D vs Oxygine, the Slant community recommends Oxygine for most people. In the question“What are the best 2D game engines?” Oxygine is ranked 18th while Genome2D is ranked 47th. The most important reason people chose Oxygine is:
Most interesting is ability to build C++ Oxygine application for Web via Emscripten. So you write C++ code and it will compile it to HTML5/JS.
Specs
Ranked in these QuestionsQuestion Ranking
Pros
Pro Lightning fast
It's the fastest gpu-based framework out there for flash. It's beautifully optimised. It has very low rendering latency, low level OpenGL calls that other tech simply cannot do (ie Unity) due to Stage3D, and thus can render a lot more data quicker
Pro Cross-platform mobile, desktop and web
Supports Windows, Mac OS X, Linux, iOS, Android, Web and native Flash.
And with the HTML5 export, it also potentially supports development for the Wii U :)
Pro Haxe!
Haxe is a strictly typed programming language that saves development time but still compiles high performance executables, and can build for tons of different platforms (flash, c++, html5, java, c#, etc.)
Pro Access to direct draw features
Has access to direct draw features so you can make you own rendering structures (scene graphs etc).
Pro Automatic dynamic batching
Automatically batch geometries with dynamic batching techniques (by using constant buffers).
Pro Component based architecture
Pro Games can be built as HTML5 applications
Most interesting is ability to build C++ Oxygine application for Web via Emscripten. So you write C++ code and it will compile it to HTML5/JS.
Pro Functionality can be extended with a bunch of available extenions
All of them available publicly at github.
- oxygine-movie for playing Theora movies with alpha channel
- oxygine-sound player for ogg sound/music with streaming
- oxygine-freetype library
- oxygine-billing for in-app-purchases on Android/iOS
- oxygine-spine for playing Spine animations
- oxygine-magicparticles for playing particles made with MagicParticles
Pro Will be familiar to users of ActionScript3/Flash API
If you are familiar with ActionScript3/Flash API, then you will find it easy to begin working in Oxygine. Oxygine is much like Flash in C++, as its Event Handling model is very close to that of ActionScript 3 and SceneGraph.
Pro Easy to use C++ API with optional C++11 features
Oxygine is written in C++. It provides easy to use API, which is designed with "do more with less code" philosophy. It uses a managed scenegraph system that takes care of rendering and updates, and provides ability to extend with custom rendering and updates.
Pro Free, open source and cross-platform
Oxygine is a free framework that works on OS X, Windows, Linux, iOS, Android, HTML5. It's licensed under MIT with source code available on GitHub.
Pro Robust
It's very rare to experience bugs with Oxygine.
Pro Allows playing movies with alpha channel
Using oxygine-movie extension for Oxygine you could play in your game any videos encoded with Theora codec.
You movie could have alpha channel and used as simple sprite instead of classic spreadsheet animations.
Pro Allows for flexible contol over draw processes
Pro Fast
Cons
Con Lacks documentation
The API documentation is minimal, there's not many tutorials and the ones that are there are very small and only cover the basics. If you want to learn how to properly use it, you have to ask the community or read the source code and figure it out.
Con Not too many games to showcase it
Con Slow development rate
Con Inactive
The project does not seem to be active: there has been no new commit since mid-2019, the Twitter feed for the engine stopped posting news in 2018, and the forum is offline as of May 2021.
Con Little community support
Oxygine is a young framework. It was first released in 2013 and has yet to gather a large community. As of February 2016, the forum had just 123 members.
Con Not many tutorials available
There are not many tutorials available that teach developers on how to make a game with Oxygine from scratch. Because of this, it may be harder to pick it up or to start learning game development by using this engine.