When comparing ShiVa vs Unity 2D, the Slant community recommends Unity 2D for most people. In the question“What are the best 2D game engines?” Unity 2D is ranked 7th while ShiVa is ranked 92nd. The most important reason people chose Unity 2D is:
2D game creation was a major feature request from the Unity community and was added with version 4.3. 2D is provided in both the Pro and Free distribution of Unity.
Specs
Ranked in these QuestionsQuestion Ranking
Pros
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 Great support
In addition to the help forum, Basic and Advanced licensees have chat and direct email access to the developers.
Pro Native c++ export
Pro C++ plugin development options
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 Built into Unity 4.3+
2D game creation was a major feature request from the Unity community and was added with version 4.3. 2D is provided in both the Pro and Free distribution of Unity.
Pro Integrates with Mecanim
Mecanim brings state machines and blending to 2D bone animation. The state machine editor allows for designers and programmers to visually create a Finite State Machine (FSM) to control when animations should play. Mecanim also allows for blending so an animation can transition smoothly between two states without the need of in between frames made by an animator.
Pro Sprite Sheet and Bone based animation supported
Both types of 2D animation for game development are supported in Unity’s system and can be used interchangeably in the timeline.
Pro Easily change sprites dynamically
Usually used for character customization, programmers can change any sprite in a bone animation at runtime easily by referencing the bone and loading the new sprite from the resources folder.
Cons
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 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 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 Lacks critical features
- Vertices can't be animated, so you can't have ANY organic feel (like... lungs breathing).
- Parent bone can't be animated without affecting the children. This is especially impeding for organic feel, again.
- No option to show & unshow assets (or it is hidden), like for switching weapon on your character for exemple.
Con Poor script interface for texture atlases
Accessing individual sprites within an atlas texture is possible at runtime, but requires use of the Resources folder subsystem.