CryEngine vs Urho3D

CryEngine has some C#template and also C# based system to write your function/ideas in to your game.

CryEngine 5.4 now supports DX12 and Vulkan

Cry Engine has volumetric fog rendering which allows for realistic cloud shadows that actually render shadows onto the fog itself. Combined with their time of day system, it's possible to create incredibly realistic weather effects. On top of this, color grading allows user to post process pallets allowing them to change the color tone for different type weather, such as using a deep dark blue for rain.

It can shoot, walk on patrol points, can see the player and so on.

Cryengine (starting on Cryengine V) has Virtual Reality support. Developers can create games with VR support for multiple platforms: PlayStation VR, Oculus Rift and HTC Vive.

Cry Engine has realistic water effects that even simulate ocean physics. Features such as waves that respond to global wind, and dynamic water volume tessellation allow for some of the most realistic water effects available to a game developer. The engine also takes into account LOD (level of detail) on water geometry to allow it to stay performant for water at a distance.

Where Cry Engine really shines is with rendering scenes of nature. The Crysis games feature incredibly detailed vegetation and weather effects and it's the Cry Engine that enables that. The engine has many features to create a cohesive realistic looking world. Dynamic water effects allow users to have beautiful oceans, fog and cloud effects allow for realistic weather, and a plethora of lighting effects optimized for natural looking scenes make Cry Engine one of the best engines for creating vast beautiful landscapes.

By having all these features built together from the ground up, Cry Engine is capable of doing more complex effects more efficiently, than other engines that didn't have these effects planned from their inception.

Supports miltiple platforms including: Xbox One, Xbox 360, PS3, PS4, Wii U, PC, iOS, and Android.

Flow graphs resemble flowcharts where each box represents a function or value, with connections between them representing program flow. This provides a better at-a-glance indication of game logic than a simple list of events, and makes complex behaviors easier to accomplish.

Crytek has launched a dedicated Q&A forum for everything Cryengine related. It's called Cryengine Answers and it's a community dedicated to sharing and answering any question related to Cryengine.

The Cryengine marketplace is an online marketplace which enables developers to access and use individual assets from thousands of materials, sounds and 3D objects created by the community. Even Crytek's own library assets are available there.

Cryengine has an optimized volumetric cloud system for Virtual Reality to give clouds full 3D spatial rendering. This ensures a high rendering quality with a minimal performance hit.

Simply by looking at the RC log when exporting can greatly improve your work. Cryengine doesn't handhold you constantly and helps greatly with avoiding bad practices in asset creation.

The entire engine is open source and makes use of other open source libraries. Source code is licensed under MIT and available on GitHub.

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.

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.

Only use what you need.

Builds are quite fast, aids in rapid development.

Urho3D is written in a modular and super-clean way, so that it can be integrated into the other parts of your game seamlessly.

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).

You can configure rendering pipeline.

There are no lights limits per mesh.

Information on enabling OR support can be found here.