Game Development · head to head
libGDX vs Armory3D
Armory3D
Game Development
Open-source 3D game engine integrated with Blender
- From
- Free
- Rated
- -
The short version
- Each has a real cost: libGDX libGDX is a Java framework built on OpenGL ES, so projects are tied to the JVM toolchain; Armory3D compiled binaries are sold to fund the project while the source code itself is free to build from scratch
- They diverge on capability: libGDX covers Java language support, Armory3D covers Blender integration.
Where they differ
Only the attributes on which libGDX and Armory3D actually diverge.
Identical on both: starting price (Free), pricing model (free), free tier (Yes), user rating (Not yet rated), category (Game Development).
What each one covers
Drawn from each product's published feature list. An absence here means we hold no record of it - not that the product lacks it.
Only in libGDX
- Java language support
- Graphics rendering
- Audio engine
- Input handling
- Physics integration (Box2D)
- Animation system
- 2D and 3D rendering
- Java
Only in Armory3D
- Blender integration
- 3D graphics rendering
- Physics engine (Bullet)
- Audio system
- Haxe scripting
- Skeletal animation
- Material system
- Blender
Both cover
- Particle effects
- Open-source
- Local deployment
- Mobile deployment
- Web deployment
- Windows support
- Macos support
- Linux support
What people use each for
The jobs each tool is most often brought in to do.
libGDX
- Writing 2D or 3D games in Java from a single codebasenot Armory3D
- Publishing a Java game to desktop, Android, iOS and HTML5not Armory3D
- Rapid prototyping where an opinionated engine workflow is unwantednot Armory3D
Armory3D
- 3D game developmentnot libGDX
- Blender-based gamesnot libGDX
- Web gamesnot libGDX
Where each one falls short
Documented limitations, not opinions. Every one is a constraint you would hit in normal use.
libGDX
- libGDX is a Java framework built on OpenGL ES, so projects are tied to the JVM toolchain
- Publishing targets are limited to Windows, macOS, Linux including Raspberry Pi, Android, iOS and HTML5
- libGDX is a community-maintained Apache 2.0 project with no vendor and no paid support tier
- libGDX ships as a framework rather than an editor, so there is no visual scene editor included
Armory3D
- Compiled binaries are sold to fund the project while the source code itself is free to build from scratch
Pricing, plan by plan
libGDX
Free- FreeFree
- Full framework
- Java support
- Cross-platform
Armory3D
Free- FreeFree
- Full engine
- Blender integration
- 3D graphics
Which should you pick?
Choose libGDX if
- You need java language support.
- You want to start without paying.
- You work on Windows, Macos, Linux, Ios, Android, Web.
- You also want graphics rendering.
Choose Armory3D if
- You need blender integration.
- You want to start without paying.
- You work on Windows, Macos, Linux, Html5, Android.
- You also want 3d graphics rendering.
Questions people ask
- Is libGDX or Armory3D better?
- Neither clearly leads. libGDX starts at Free and Armory3D at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
- Which is cheaper, libGDX or Armory3D?
- libGDX starts at Free and Armory3D at Free.
- Does libGDX or Armory3D run on more platforms?
- libGDX runs on Windows, Macos, Linux, Ios, Android, Web. Armory3D runs on Windows, Macos, Linux, Html5, Android.
- Can I use libGDX for free?
- Both have a free tier, so you can try either at no cost before committing.
- What is libGDX best used for?
- libGDX is most often used for writing 2d or 3d games in java from a single codebase, publishing a java game to desktop, android, ios and html5, rapid prototyping where an opinionated engine workflow is unwanted. Of those, writing 2d or 3d games in java from a single codebase and publishing a java game to desktop, android, ios and html5 are not what Armory3D is typically brought in for.
- What can libGDX do that Armory3D cannot?
- libGDX covers Java language support, Graphics rendering, Audio engine, Input handling. Armory3D covers Blender integration, 3D graphics rendering, Physics engine (Bullet), Audio system. Both handle Particle effects, Open-source, Local deployment, Mobile deployment.