Add to Chrome
Add to Edge
Add to Firefox
Add to Opera
Add to Brave
Add to SafariWhen comparing libGDX vs Oxygine, the Slant community recommends Oxygine for most people. In the question“What are the best 2D game engines?” Oxygine is ranked 12th while libGDX is ranked 15th. 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
Question Ranking
Pros
Pro Lots of resources to learn from
Lots of references, tutorials and open source code to learn from.
Pro Great performance across devices
While it may not always have the best performance for a particular device or system, it's one of the few engines which consistently performs very well across different platforms.
Pro Fantastic UI toolkit (scene2d)
scene2d is a 2D scene graph, scene2d.ui is a UI toolkit on top of that. It enables very complex mobile and desktop UIs.
Pro Can use any JVM language
Since it's built with Java and runs on the JVM, any language that compiles to Java bytecode can be used to develop games with libGDX.
Pro Uses Box2D
A Java port of the Box2D physics engine is included in libGDX.
Pro Allows you to migrate from 2D to 3D within same framework
LibGDX supports both 2D and 3D game development. Allowing developers to migrate from 2D to 3D with ease without having to switch the engine they are using or having to learn a new API.
Pro Doesn't force a specific design
Unlike some engines, which only allow you to make your game in a few specific ways, libGDX allows you to design any type of game you wish as it is extremely customisable.
Pro Active and helpful community
The libGDX community, in the official libGDX forum is extremely helpful and approachable for any kind of question regardless of the its quality or difficulty.
The forums themselves are a very helpful resource for any issue or guide simply by searching past posts in there.
In addition to the forums, there's also the official #libgdx IRC channel on Freenode.
Pro Interfacing with platform specific code
Sometimes it is necessary to access platform specific APIs, e.g., adding advertisement services or leaderboard functionality provided by frameworks.
Pro Free, open source & permissive license
libGDX uses the Apache License 2.0.
Not only is libGDX free and open source but also it's license gives you a lot of power over the engine. As long as you provide a copy of the license, give credit, do not hold devs liable and do not use libGDX logo in any engine forks you can do pretty much anything you want.
Pro Kotlin support
It is written in Java so you can easily make games using Kotlin and Ktx project will help you get all advantages of this language.
Pro Very easy to customize
Pro Constantly improved
LibGDX itself is pretty mature, and get updates not quite frequently, but various libraries for it are actively updated.
Pro Across platform support
You can write once and run anywhere (Android, IOS, Desktop, Browser) also lately came with lib to deal with VR.
Pro Support for 3rd party tools
libGDX has built in support for many 3rd party tools, including (but not limited to) Bullet Physics, Box2DLights and the well-praised Tiled Map Editor.
Pro Lots of tutorials to get you going
Even though the official documentation might be lacking, there are many tutorials on YouTube for libGDX.
Pro Excellent font rendering support
Very good tools for rendering fonts.
Pro Similar to the Microsoft XNA framework
Old XNA users may like libGDX since it's API is actually very similar to XNA's.
Pro Focusing on object pool patterns, to control memory without pointers
Unlike Unity or other engine, it allows to optimize a language that uses garbage collector when using patterns of objects you can control the use of memory without needing a language like C / C ++, getting the same speed in a more productive language.
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 Not starter friendly
Even default applications fail to load in Android. It doesn't have any documentation on errors either.
Con Documentation could be better
Other than a brief installation / getting started overview, libGDX's documentation consists of an official wiki with several incomplete pages, and automated Javadocs. The community recognizes these shortcomings, and new users are encouraged to ask for help.
Con The project slowed down in development
The number of active developers has decreased, many open issues and pull requests.
Con Build system is clunky
LibGDX uses Gradle, which is very demanding of memory and makes IDEs freeze on anything if your computer is not powerful enough.
Con Does not create compiled code
LibGDX runs entirely on Java and does not create executable binaries.
Con A bit difficult to use
This engine is not well put together. Is made from various free modules each with their own peculiarities. At times it feels you need to learn a couple of libraries rather than just one. Is not an engine for beginners as it requires coding. Lots of coding. You need to be intermediate to advanced in Java to develop in LibGDX.
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.
