When comparing Panda3D vs Urho3D, the Slant community recommends Urho3D for most people. In the question“What are the best 3D game engines?” Urho3D is ranked 4th while Panda3D is ranked 7th. The most important reason people chose Urho3D is:
The entire engine is open source and makes use of other open source libraries. Source code is licensed under MIT and available on [GitHub](https://github.com/urho3d/Urho3D).
Ranked in these QuestionsQuestion Ranking
Pro Free, open-source, and permissive license
The liberal license allows use of the engine for any purpose without restrictions or royalties.
Pro Supports most popular physics engines
Panda3D has in-depth integration with industry standard physics engines such as Bullet, NVIDIA PhysX and ODE, but also offers a simpler built-in physics engines that will cover more basic needs.
Pro Will be very easy for developers already familiar with Python
Although it's possible to use only C++ to program in Panda3D, all its power is available to the Python scripting language, while not trading in performance since the performance-critical parts are implemented in C++.
It has a powerful binding layer that exposes the vast majority of the API via Python-based interfaces.
Pro Flexible scene and object hierarchy system
Creating weird world constructs is generally a breeze. The node system the engine runs with allows to build self-looping worlds and, on large scale, non-Euclidean scenes without having to introduce a huge amount of custom code.
Pro Powerful profiling and debugging tools
Panda3D has a suite of powerful tools to help track down performance bottlenecks, memory leaks and examine internal state.
Pro Supports browser deployment
Panda3D offers web plug-ins that allow deployment of an application to all major browsers. A WebGL port is in the works as well.
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 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 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 Fat-free codebase
Only use what you need.
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 Does not require an editor to get going
Pro Small turnaround times while developing
Builds are quite fast, aids in rapid development.
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 Unofficial Oculus Rift support
Information on enabling OR support can be found here.
Con No unified editing program
Unlike Unity and Unreal, Panda3D doesn't currently offer a single, unified editing program in which objects can simply be dragged in and assigned properties (although third-party solutions are available). Developers are expected to design their scenes in a modelling program like Maya or Blender instead, and import them into Panda3D using Python code.
Con Limited tutorial
Step by step tutorial is limited. Manual is too general and short without examples. Samples are too complex for beginners.
Con Direct3D support is behind
Direct3D support not up to par with OpenGL support, only version 9 is supported
Con Loading Pandas3d will change your builtins to contain non explicit references to non-standard helper functions
A lot of the pollution comes from storing global state. Instead, you can store and update the global state of a namespace instead. As for the built-in pollution, you can make a wrapper that backs up builtins, imports pandas and then restores builtins, though this may not work as pandas almost certainly uses it's extra builtins to work. The best thing to do would be to explicitly import the same objects that are in the builtins over the top of the modified builtin namespace, although it doesn't remove the code smell, it helps to make things look less (if not at all) magic.
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.
Con The UI can be hard on the eyes
Urho3D's UI could cause eye strain.