When comparing ShiVa3D vs libGDX, the Slant community recommends libGDX for most people. In the question“What are the best 3D game engines for Android?” libGDX is ranked 1st while ShiVa3D is ranked 5th. The most important reason people chose libGDX is:
Lots of references, tutorials and open source code to learn from.
Specs
Ranked in these QuestionsQuestion Ranking
Pros
Pro Streamlined API
Pro Great performance on mobile
Smaller platform specific executables, native code export, good FPS even for complex scenes. ShiVa has great advanced optimization features, including PVS and LOD, decreasing number of drawcalls even in complex level. Platform specific profiles allow developers to customize size and compression level for textures and test those settings directly in editor. Other engine features, like lightning baking, mesh combining and GPU skinning will boost performance too.
Pro Straightforward pricing with capable free option
The free ShiVa Web version is limited to web publication, but otherwise has the same capabilities as the $200 ShiVa Basic. Upgrading to the $1000 ShiVa Advanced brings tools geared toward team development and professional releases, such as integrated SVN support and profiling tools. All versions are royalty-free.
Pro Lua can be used for fast coding and C++ for optimization
All game logic can be scripted in Lua. ShiVa also provides a cross-compiler from Lua to C++, allowing Lua scripts to be further optimized and compiled to native code for performance.
Pro C++ plugin development options
Pro Native C++ export
Pro Robust
Pro Competent GUI system
Pro Great support
In addition to the help forum, Basic and Advanced licensees have chat and direct email access to the developers.
Pro Lots of resources to learn from
Lots of references, tutorials and open source code to learn from.
Pro Great performance across devices
While it may not always have the best performance for a particular device or system, it's one of the few engines which consistently performs very well across different platforms.
Pro Fantastic UI toolkit (scene2d)
scene2d is a 2D scene graph, scene2d.ui is a UI toolkit on top of that. It enables very complex mobile and desktop UIs.
Pro Can use any JVM language
Since it's built with Java and runs on the JVM, any language that compiles to Java bytecode can be used to develop games with libGDX.
Pro Uses Box2D
A Java port of the Box2D physics engine is included in libGDX.
Pro Allows you to migrate from 2D to 3D within same framework
LibGDX supports both 2D and 3D game development. Allowing developers to migrate from 2D to 3D with ease without having to switch the engine they are using or having to learn a new API.
Pro Doesn't force a specific design
Unlike some engines, which only allow you to make your game in a few specific ways, libGDX allows you to design any type of game you wish as it is extremely customisable.
Pro Active and helpful community
The libGDX community, in the official libGDX forum is extremely helpful and approachable for any kind of question regardless of the its quality or difficulty.
The forums themselves are a very helpful resource for any issue or guide simply by searching past posts in there.
In addition to the forums, there's also the official #libgdx IRC channel on Freenode.
Pro Interfacing with platform specific code
Sometimes it is necessary to access platform specific APIs, e.g., adding advertisement services or leaderboard functionality provided by frameworks.
Pro Free, open source & permissive license
libGDX uses the Apache License 2.0.
Not only is libGDX free and open source but also it's license gives you a lot of power over the engine. As long as you provide a copy of the license, give credit, do not hold devs liable and do not use libGDX logo in any engine forks you can do pretty much anything you want.
Pro Kotlin support
It is written in Java so you can easily make games using Kotlin and Ktx project will help you get all advantages of this language.
Pro Very easy to customize
Pro Constantly improved
LibGDX itself is pretty mature, and get updates not quite frequently, but various libraries for it are actively updated.
Pro Across platform support
You can write once and run anywhere (Android, IOS, Desktop, Browser) also lately came with lib to deal with VR.
Pro Support for 3rd party tools
libGDX has built in support for many 3rd party tools, including (but not limited to) Bullet Physics, Box2DLights and the well-praised Tiled Map Editor.
Pro Lots of tutorials to get you going
Even though the official documentation might be lacking, there are many tutorials on YouTube for libGDX.
Pro Excellent font rendering support
Very good tools for rendering fonts.
Pro Similar to the Microsoft XNA framework
Old XNA users may like libGDX since it's API is actually very similar to XNA's.
Pro Focusing on object pool patterns, to control memory without pointers
Unlike Unity or other engine, it allows to optimize a language that uses garbage collector when using patterns of objects you can control the use of memory without needing a language like C / C ++, getting the same speed in a more productive language.
Cons
Con Outdated
The current version 1.9.2 of ShiVa was released in December 2013. While there is active development on version 2.0, its beta is available only to paid licensees of the current version.
Con ShiVa 2.0 has been worked on for nearly 4 years!
After 4 years of development and promises ShiVa 2.0 has JUST gotten into beta access.
Con High Cost
Costs $200 for the basic version alone, which allows you to publish to any format other than web. The Team/Pro version costs $1000
Con Not starter friendly
Even default applications fail to load in Android. It doesn't have any documentation on errors either.
Con Documentation could be better
Other than a brief installation / getting started overview, libGDX's documentation consists of an official wiki with several incomplete pages, and automated Javadocs. The community recognizes these shortcomings, and new users are encouraged to ask for help.
Con The project slowed down in development
The number of active developers has decreased, many open issues and pull requests.
Con Build system is clunky
LibGDX uses Gradle, which is very demanding of memory and makes IDEs freeze on anything if your computer is not powerful enough.
Con Does not create compiled code
LibGDX runs entirely on Java and does not create executable binaries.
Con A bit difficult to use
This engine is not well put together. Is made from various free modules each with their own peculiarities. At times it feels you need to learn a couple of libraries rather than just one. Is not an engine for beginners as it requires coding. Lots of coding. You need to be intermediate to advanced in Java to develop in LibGDX.