Two years after my previous mobile game, I decided to start a new 2D puzzle game. I wanted to try a new technology and chose Unity. In this article, I’ll explain why I chose Unity in the first place, and describe what I liked and disliked. After developing a fully working prototype of my new game in about two months (not my full time job, working when kids are sleeping), I finally came back to a framework I used previously: cocos2d-x.
Why choosing unity
Mobile game developement is a hobby, and I love learning new things. Unity had new features for 2D games since v4.3 (Sprites), and became free for small teams with the personal edition. I knew C# quite well already from experience of previous XBLIG games.
What I liked in Unity
Here are some of the great features in Unity that I used while developing my prototype. Keep in mind that I’m focused on simple 2D games, and not on huge 3D FPS. Also, I’m single developer on the project, doing both programming and game design.
A prefab is a set of objects tied together. It’s easy to instantiate prefabs programmatically in real time in the game. For example, to create a pack selection screen such as this one from a previous project, I made a prefab and modified by script the values of each pack. If you want to change the layout or overall look of the prefab, there’s nothing to change in the code, everything is done in the editor.
The editor is very well done and it’s easy to add properties to game objects. You can also add specific features. Here is a small list of stuff that helped me debugging and developing my game:
* showing game object bounds (see tweet below)
* showing mouse position on screen
* logging debug information on screen
* changing language in real time
— Francois Guibert (@Frozax) September 27, 2015
Running in the editor
When you run the game in the editor, you still have access to variables and exposed settings of your game objects. You can also view objects outside the window. It’s handy when you don’t see an object on screen to know whether it’s invisible or simply out of screen.
The editor also lets you try some new layouts while the game is running by simple moving your instances.
Profiling is another great feature recently made available for free in Unity 5. You can see in real time memory allocations, rendered meshes and CPU usage of any script. Sorting scripts by CPU usage helps to understand where to optimize first.
— Francois Guibert (@Frozax) September 7, 2015
This is one of the feature that made me try Unity in the first place. Being able to deploy on all platforms with a single click. It’s not as simple as that in reality, because sometimes you need to create projects and build them with external tools (iOS, Windows 8.1 for example). With my prototype, I built Windows, Linux, WebGL, Android and Windows Phone 8.1 builds very quickly and without major issues.
Visual Studio Integration
I initially used MonoDevelop and honestly didn’t like it. However, I discovered Visual Studio Tools for Unity and used it with Visual Studio Community 2015 and now I have a great dev environment. Unity recently included the plugin in the editor package directly. You can even set breakpoints and step into your code directly in Visual Studio.
What I didn’t like in Unity
Let’s look now at the issues I had with Unity.
I found the 2D features not good enough for my needs. There was a promising new UI system, but it’s slow and not recommended on mobiles. I also had to play with texture tiling (repeating UVs) and there is no support natively in the 2D sprite game objects. I had to re-code a sprite using a 3D quad to have access to UV settings. And last but not least:
— Francois Guibert (@Frozax) September 11, 2015
When working with artists, I find it useful to send them a desktop version of the game so that they can change the raw resources files and see their work in game. Unfortunately, there is no easy way to do that in Unity without sending the whole project with assets and source code. I had to develop a specific function to load custom files at startup. See this reddit thread if you want more information and sample code on this topic.
Because Unity has to include the C# libraries in your packaged game, games take a lot of space: A simple empty game without resources and only displaying a white screen takes 28.5 Mb on Windows and 18.4 Mb on Android (EDIT: I didn’t realize you could create ARM only binary, in this case the size is 9.5 Mb)! My latest mobile game (made with cocos2dx) takes 4.7 Mb, code, resources and art included. It’s not a problem for big productions but it is for smaller games.
Visual Studio Tools instability
I told above that I loved Visual Studio integration but the stability is for from perfect. I had to kill Unity and Visual Studio at least twice a day because they stopped responding. When it happened middle of a big debugging session, it’s very frustrating.
I raised the issue in the 2D section, but it also happened with mandatory function: this tweet sums it all:
— Francois Guibert (@Frozax) August 29, 2015
In the free version, you have to use Unity’s splash screen on every platform. I knew that from the beginning and understand that, as I use a free version of the tool. But that’s a drawback nonetheless.
I think this is only in the free version, but Unity games connect to Internet and therefore forces Android permissions (INTERNET and ACCESS_NETWORK_STATE). As a user, I don’t like being asked for too many permissions. I’m still unsure if I’ll have ads in my next game (I probably won’t), but if I don’t, I surely don’t want to have extra permissions in my app.
The last two issues can simply be solved by purchasing Unity Pro. As I’m doing this as a hobbyist, I don’t have a big budget to put into gamedev, and I’m really not sure my game sales will be able to cover the costs of Unity Pro (about 171 € per month or 3420 € once if I want support for Windows, iOS, Android and Windows Phone 8.1).
Switching to cocos2dx
I considered some of the issues so important (splash screen and big packages, mostly) that I looked for other multiplatform engines and decided to come back to cocos2dx. Since I used cocos2dx v1 a few years ago, there has been many great changes, and I am now using v3. It’s really a powerful framework, and I made my own fork where I can do some specific tweaks. Cocos2d-x is not as “plug’n’play” as Unity and the documentation is sometimes too light, but I don’t feel limited. I have working Android, Windows Phone, iOS and Windows builds for now.
Unity3D is a good tool, but I don’t think it’s suited to small 2D games. Cocos2d-x team have made some great changes and are still very active.
Feel free to comment, tweet or share this article.
While actively learning Unity, I made a series of #UnityTips tweets, here are the best ones:
— Francois Guibert (@Frozax) September 5, 2015
— Francois Guibert (@Frozax) September 8, 2015
— Francois Guibert (@Frozax) September 9, 2015
— Francois Guibert (@Frozax) September 18, 2015
— Francois Guibert (@Frozax) September 20, 2015
— Francois Guibert (@Frozax) September 24, 2015
— Francois Guibert (@Frozax) September 30, 2015