When comparing CopperCube vs GameMaker Studio 2, the Slant community recommends GameMaker Studio 2 for most people. In the question“What are the best game engines for point & click adventure games?” GameMaker Studio 2 is ranked 37th while CopperCube is ranked 47th.
Specs
Ranked in these QuestionsQuestion Ranking
Pros
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.
Pro Quick prototyping
Pro Good user interface
Pro Well-optimized engine
Pro Has a trial version (but limited functions, can't export)
Pro Many unofficial tutorials
Most GMS1 tutorials are fine for GMS2
Pro Highly customizable IDE
Although users must work within the IDE and editor, GMS2 has many options to customize the look and feel
Pro Good documentation
Pro Huge, generous community
Cons
Con Not the best scripting language out there
GML is just weird; if you want to learn programming, it is not the best because it teaches bad habits and has many odd shortcuts and shortcomings that won't transfer to a real language
Con HTML5 export is buggy, doesn't "just work"
Con Quite expensive
Windows ($100) + HTML5 ($140) + Mobile ($400) + UWP ($400) is $1,050, plus $800 anually for each console export separately. But doesn't do anything any of the free engines can't do, and the stability and tech support aren't great.
Con Unstable
Users frequently report crashes and hangs, particularly when working with assets, and the software uses a complicated underlying meta-file structure that may become corrupted and cannot be rebuilt
Con Limited support for OOP
Con Small development team
The core programming team is only 5-10 people, with about 30 employees total, so bug fixes can take a long time to be addressed, and there aren't many official tutorials