Orx vs HaxeFlixel
When comparing Orx vs HaxeFlixel, the Slant community recommends Orx for most people. In the question“What are the best 2D game engines?” Orx is ranked 5th while HaxeFlixel is ranked 24th. The most important reason people chose Orx is:
Powerful config system that makes orx data-driven and provides an easy to use load/save system.
Specs
Ranked in these QuestionsQuestion Ranking
Pros
Pro Powerful config system
Powerful config system that makes orx data-driven and provides an easy to use load/save system.
Pro Friendly community
Good friendly development community ready to help each other with tips and advice for setting up and best practices.
Pro Automatic hot-loading of resources
Automatic hot-loading of resources upon modification on disk, shortens drastically iteration times.
Pro High performance
Written in C with high emphasis on memory and CPU efficiency.
Pro Supports desktop and mobile
Supports Windows, Linux, Mac OS X, iOS and Android.
Pro Data configuration
Orx is a Data Driven engine that greatly reduces required code. You can configure object definitions, bodies, cameras, sound, animation, event tracks, etc.

Pro Custom shader support
GLSL code can be added straight into data configuration files and can be applied to any texture: background or objects whivh allows for some amazing effects. All GLSL versions are supported, again by providing the shader language version in your configuration file.
Parameters are supported and values over time for shader animation.
Pro Flexible clock system
Clock system that provides time consistency and allows time stretching + high precision timers
Pro Flexible and simple FX
Color and translation FX are simple to configure and apply to objects.
Pro Good animation engine
Includes a chaining graph & custom animation events for synchronization.
Pro Free and open source
Uses the zlib license. Lets you use Orx for free for any kind of projects, even for commercial ones.
Pro Input controls and binding
All input devices are fully supported: Joysticks, Mouse, Gamepad, Keyboard and Touchscreen. Multiple physical devices and be mapped the same binding.
Pro Excellent results on performance benchmark
Rated the fastest engine in the OpenFL’s BunnyMark since October 2015.
Pro Great audio support
Samples for sound effects, or streams for music. All sounds can be groups via audio buses just like in a typical DAW (Digital Audio Workstation).
All sounds can be spatial relative to the camera.
Pro Viewport scheme allowing multiple views
Camera/viewport scheme allowing multiple views displayed with camera translation, zoom and rotation.
Pro Good render support
Fragment (pixel) shader support, render to texture, MRT, easy composition and custom rendering support.

Pro Easy post-processing/compositing for complex visual effects
Pro Integrated runtime profiler
Integrated runtime profiler (with graphical display) to easily spot which parts of your game need to be optimized.
Pro Collision handling and rigid body physics
Pro Screenshot capture tool
Supports .bmp, .png, .jpg, .tga and .dds
Pro Multi-Threading
Pro Great IDE Support
Out of the box Windows support for:
- Visual Studio
- Codelite
- CodeBlocks
- gmake
Out of the box Mac support for:
- XCode
- Codelite
- gmake
Out of the box Linux support for:
- Codelite
- CodeBlocks
- gmake
Pro Well-supported C++ wrapper
Orx provides a excellent c++ wrapper for object oriented design, called: orx/Scroll. You can, of course, roll your own.
Pro Powerful language
Haxe is a powerful, cross-platform and open source language.
Pro 75+ demos
All demos have included GitHub link, so you can learn from the examples
Pro Getting started guide
Has a starting guide for people who are completely new to HaxeFlixel; from installing Haxe to a beginner-friendly HaxeFlixel tutorial.
Pro Uses Haxe
(excerpt from source): To help you do this, the (Haxe) toolkit contains three main components:
the Haxe Language - a modern high-level, strictly typed programming language
the Haxe Standard Library - a complete cross-platform standard library
the Haxe Compiler - an incredibly fast cross-compiler
Pro Fully free
HaxeFlixel is fully free and open source.
Pro Hardware accelerated rendering on native platforms
Pro Active development community
(excerpt from source):
There is a multitude of channels to interact with the community:
Our google groups forums
#haxeflixel on IRC (freenode.net)
@HaxeFlixel on Twitter
The HaxeFlixel organization on GitHub
The HaxeFlixel page on IndieDB
Join our development chat on Slack[1]
HaxeFlixel group on Steam
Pro Powerful debugger overlay
You can watch variables, log (trace) messages, and check for memory/frame rate performance.
Pro Modelled after Flixel
But with considerable improvements -- the HaxeFlixel team are constantly working improving and fixing the HaxeFlixel API, as compared to the original Flixel which is no longer updated.
Pro Easy 2D game development
(Haxe)Flixel does a lot of things for you like tilemaps and collision detection, which makes it super easy to create 2D games.
Pro Outstanding community
The HaxeFlixel team and contributors are very active on Github and other community places (like Slack), and are usually able to respond to your questions within a day or two.

Pro Similar syntax to Actionscript 3
Haxe's syntax is similar to AS3, so Flash developers can transition to HaxeFlixel if they are familiar with AS3/Flixel.
Pro Excellent, robust API
The API has all of the features that you'd expect from a powerful engine without sacrificing organization and flexibility
Pro Cross Platform
The open source Flash API is powered by OpenFL, which allows you to compile to Windows, Mac, Linux, iOS, Android, and even major consoles (coming soon).
Pro Cross-platform IDE environment
On Windows, the IDE of choice is FlashDevelop, but if you're looking for cross-platform IDE (Windows/Mac/Linux), there's Sublime Text which includes a package for Haxe syntax highlighting, as well as auto-completion.
Cons
Con Feature discovery and explanation could be better
Some features are not well explained / highlighted: for example, unless you use the interactive project initialization, you have to go over the tutorials and examples in the wiki to learn that there is an optional C++ layer, Scroll, developed on top of the C API. Similarly, some major information are missing from the website, wiki and Doxygen documention, and are left for the users to discover in source headers and INI template files, or by searching the forum (e.g. the 0,0 coordinate being the center of the screen and not top left, the list of all Orx scalar types and their use, etc).
Con No network support
Con Small community
HaxeFlixel devs are not as large as (example) Unity devs, so the amount of support and exposure is limited.
