When comparing jMonkey3 vs Armory3D, the Slant community recommends Armory3D for most people. In the question“What are the best 3D game engines?” Armory3D is ranked 10th while jMonkey3 is ranked 12th. The most important reason people chose Armory3D is:
Does everything in the same application. No exporting-importing assets, make a cube, hit run, cube appears, make a character, hit run, the character appears!
Specs
Ranked in these QuestionsQuestion Ranking
Pros
Pro Java is a great development platform
Java is a well-optimized just-in-time compiled language. It's faster than languages without an effective native-code compiler such as Python or Ruby, similar in speed to other just-in-time compiled languages such as C#, while slightly slower than compiled languages such as C or C++ (with some low-level and numeric benchmarks being similar to C++).
Java also has a wide variety of high-class IDEs available.
Pro Multiplatform support
Code can be ported to mobile (iOS is in the works) and other Android supported devices with minor changes to the code (just change some implementations that vary on the platform such as inputs and user interface). It can even run on certain Raspberry Pi devices.
Pro Free and open-source
jMonkey is completely free, meaning it's possible to develop and release a game with no fees or royalties. Because it is open-source, jMonkey has plenty of people fixing bugs and, adding to the engine as well as creating a variety of plugins that can be used in the engine.
Pro Not limited to using its own IDE
Unlike some engines, jMonkey doesn't force its own IDE. You can use its Netbeans-based IDE, but you can also set up a project to work in another IDE such as Eclipse. You can still use the special tools from jMonkey's IDE in such projects.
Pro Engine modifications can be made using Java
Because jMonkey is implemented in Java, the same language its apps are typically developed in, developers will have an easier time modifying the engine to their needs.
Pro Has everything
jMonkey3 handles input from computers and mobile devices. It handles networking, physics, rendering, terrain, and cinematics.
Pro Ease of extensibility
Engine is modifiable.
Pro Freedom of choice for architecture
The user is not compelled to use any programming architecture nor standard in order to make a project working. JME allows the freedom to use what is best for a game.
Pro Offers both low-level and high-level ways of editing shaders
Modifying shaders can be done either via a visual tool called Shader Nodes or via GLSL that allow you to make your own shaders without the engine getting in the way or having to hack around to do so.
Pro Runs inside Blender
Does everything in the same application. No exporting-importing assets, make a cube, hit run, cube appears, make a character, hit run, the character appears!
Pro State of the art physically based rendering
Physically based
Cycles material nodes
Voxel-based global illumination
Temporal anti-aliasing
Tessellated displacement
Screen-space raymarching
HDR pipeline
Pro Free and open source
Pro Easy to use
Pro Node based programming and materials support
Pro Lightweight
Pro Export to multiple platforms
Export to all platform that Kha supports.
Pro A good community
Although the is an obvious lake of community help, it is still there if you look on the Armory forum or there discord your sure to find help for any problem you have.
Pro A growing community with more tutorials and documentation.
Although Armory has been a little slow in the development, tutorials on YouTube are being released almost daily and the documentation is also being updated regularly.
Pro No programing experience needed
Cons
Con Terrible API reference
The methods are not defined.
Con Not an engine for total beginners
While it's clear that you need to know Java first before using this engine, it is recommended that you have some programming experience as well. Most performance issues and memory leaks are more due to bad programming practices than the engine itself.
Con Slow release cycle
jMonkey3 lacks manpower to have a fast and decent release cycle.
Con Relies on archaic tool chain
jMonkey Engine uses Apache Ant for build automation, which is archaic and backwards, even by Java standards.
Con Lack of documentation
Con Not many developers use it
Armory3d seems to be quite exotic and it should be hard to find developers to help in projects.
Con Still in development
Con Slow development
Focus from the developer has shifted to another project, so development of this has slowed considerably.
Con Good looking but a terrible choice for any serious development
Terrible lack of support and lack of a serious delivery strategy. Multiple breaking changes to the master branches (usually the only branch actually) from the core projects as well as the myriad of dependencies it uses make it a nightmare to have something stable to create with. Might be good for prototyping if you stick to the releases, but stay away if you are planning to create something serious.