When comparing ENIGMA Development Environment vs Urho3D, the Slant community recommends ENIGMA Development Environment for most people. In the question“What are the best 2D game engines?” ENIGMA Development Environment is ranked 60th while Urho3D is ranked 61st. The most important reason people chose ENIGMA Development Environment is:
Almost full support for GML, The ability to create and access C++ types, templates, and functions, compile DLLs and other C/C++ scripts
Specs
Ranked in these QuestionsQuestion Ranking
Pros
Pro Raw C++ power and GML accessibility
Almost full support for GML,
The ability to create and access C++ types, templates, and functions, compile DLLs and other C/C++ scripts
Pro Cross platform
Support for Windows, Mac and Linux.
Pro Compatible with GameMaker
Enigma can support over 90% of gamemaker's GML language
Pro Friendly user interface
besides the powerful combination between GML and C++, beginners can also use drag and dropping.
Pro Free and Open Source

Pro Faster than GameMaker
Written in C++, many features have been demonstrated running much faster than interpreted equivalents in GameMaker (up to 10-20 times faster than GM 8.1).
Pro Under active development
Changes are made daily to add new functions/fixing bugs.
Pro Helpful error messages
A full stack trace with available cores and memory information as well as operating system and Java version including file names and number is generated whenever an exception is encountered, with a handy link to submit the issue to GitHub.

Pro Free and fully open source
The entire engine is open source and makes use of other open source libraries. Source code is licensed under MIT and available on GitHub.
Pro Good documentation
The documentation for Urho3D can be split in two parts: auto-generated from class references and documentation written to cover the various aspects, features and systems of the engine. The written documentation is pretty good. It covers most of the aspects of the engine in clear and understandable English.
Pro Includes a lot of samples
There are a lot of sample projects included with the engine for both C++ and Angelscript. They are mostly very simple applications built to demonstrate the engines capabilities and features.
Pro Fat-free codebase
Only use what you need.
Pro Small turnaround times while developing
Builds are quite fast, aids in rapid development.
Pro Very high code quality
Urho3D is written in a modular and super-clean way, so that it can be integrated into the other parts of your game seamlessly.
Pro Good 3D level editor
Pro In constant active development
Bugs are usually fixed that same day. Core devs are very active on forums. New features are always being worked on. HTML5, DirectX11, and OpenGL3.1 support have recently been added (as of 4/15/15).
Pro Does not require an editor to get going
Pro Flexible rendering pipeline
You can configure rendering pipeline.
Pro Multi-Lights
There are no lights limits per mesh.
Pro Unofficial Oculus Rift support
Information on enabling OR support can be found here.
Cons
Con A few bugs & glitches
Because Enigma is under very rapid development, with new functions added almost daily, some bugs and unexaplainable glitches can happen, though they also gets patched quickly.
Con No code refactoring
Like any C++ based programs, the ability to refactor is limited. However, the new Ide for engima will support a few refactoring cababilities
Con It has been stopped developing
The owner has moved to build new 3D engine, however, that is also experimental stage, not for production.
Con Little documentation and small community
There are some high-level design docs and a bunch of examples, but code is poorly commented and nothing much more can be found.
Con The UI can be hard on the eyes
Urho3D's UI could cause eye strain.
Con There is no support for reflections
Neither SSR nor cubemap parallax correction are implemented in engine.
Con Bad Android support
You can not compile this engine using latest Android Studio.
Con May be a bit hard to get started
To install Urho3D you need to get the archive from GitHub (be careful to download the master branch) and extract it. After that, you need to compile the engine with CMake. If all the dependencies are installed, then it should be a straightforward process, otherwise you will need to track down and install all the missing dependencies.
For people who don't have much experience with CMake this whole process may seem a bit like magic. For people who do have experience with CMake, the whole installation will be relatively easy.
