But being open-source with a very permissive license ( zlib, in Orx's case) is always a plus. I'm not an open-source extremist I don't mind using a good closed source library / framework if it does the job correctly and has a good API and documentation. If you're stuck with something, or you miss an API, just drop a post in the forum and you'll get a response in no time. The author of Orx (alias iarwain) is really a nice guy, open-minded, and very helpful (both regarding Orx itself and gamedev in general), and that's priceless for me. Here are the main reasons why I stick with Orx. Under the hood, Orx uses OpenGL-accelerated rendering, with auto-batching when possible, OpenAL for sound positioning, and Box2D for physics. (Admittedly, that's a subjective statement.) I've tried different game engines and frameworks (Corona SDK, AndEngine, and recently Unity) before finding Orx, and, since then, I've never found anything similar or easier to use for my needs. In this article, I'll share tips and resources for learning Orx, and show you what it's capable of. It's data-driven, and uses a simple yet powerful configuration system which allows you to quickly prototype and validate ideas.
#Orx game engine portable#
Orx is an open source, portable 2D game engine, which currently runs on Windows, Mac, Linux, iOS and Android (2.3+), and uses OpenGL (ES for iOS/Android) for render acceleration.
0 kommentar(er)
