Add to Chrome
Add to Edge
Add to Firefox
Add to Opera
Add to Brave
Add to SafariWhen comparing Panda3D vs CopperCube, the Slant community recommends Panda3D for most people. In the question“What are the best 3D game engines?” Panda3D is ranked 4th while CopperCube is ranked 15th. The most important reason people chose Panda3D is:
The liberal license allows use of the engine for any purpose without restrictions or royalties.
Specs
Question Ranking
Pros
Pro Free, open-source, and permissive license
The liberal license allows use of the engine for any purpose without restrictions or royalties.
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 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 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 Allows creating 3D apps and games without programming
Pro Good 3D editor
Includes easy to use 3D editor for quickly clicking together 3D games.
Pro Native WebGL support
Can create 3D games as real WebGL apps, running inside websites. Doesn't use a cross compiler, so WebGL apps are small and download quickly.
Pro Good terrain editor
CopperCube includes a terrain editor. Terrain can be drawn with height painting tools directly in the editor, textures can be painted quickly with automatic texture blending into the terrain. There are also tools for placing grass and bushes, and for distributing meshes automatically over the terrain.
Pro Exports to irrlicht
It was also written by the founder of irrlicht, although it is not open source.
Pro Available on Steam
CopperCube is available on Steam It was Greenlit.
Pro Easy to learn and to use
Pro Fast prototyping
You can quickly develop an experimental working model of the product (prototype), because the engine gives you access to a lot of prefabs, plugins and settings. And, you can use the visual programming to speed up the process, even if later you have to write code in order to improve the final product.
Pro Oculus Rift support
Supports both DK2 and DK1.
Cons
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 Terrible compilers support
Does not support any other compilers then MSVC on Windows, neither Clang nor MinGW.
Con Developer isn't very competent
Panda3D only has one developer and he utterly fails to fix problems with his engine, instead focuses on style guidelines and breaking code.
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.
