WPF provides some amazing features to work with animations. I was wondering if it would be fit for the development of simple games like <a href="http://www.istrolid.com/" rel="nofollow">Istrolid</a>. I believe WPF can replicate almost (if not all) of the animation in Istrolid. I am good with WPF, but I am yet to start with Unity.
Is WPF better in my case or is it worth investing time in learning Unity for the development of such simple games.Answer1:
WPF supports both
3D rendering but it will <strong>only</strong> work on Windows. Unity is multi-platform and will work on more than 10 platforms. If you want to be making games for Windows <strong>only</strong> then use WPF. If you want a game that can be played on
Windows and many more then go with Unity. I would recommend you go with Unity. If you know how to use
WPF that means that you are good with C#. You should just jump into Unity.
Personally, working with both I would run with Unity, but that is more a personal opinion. The Unity animations are amazing and simple. Getting used to the interface is a bit tricky, but PLENTY of online tutorials, YouTube and more for simple parts of development to even very complex. Good luck on your research / development.Answer3:
Unity is better for creating games where you want to have the physics, audio and rendering struggle all done. The environment is very user-friendly, the development is smooth and you better know whats going on in the game. But might restrict some of the features.
In WPF, you need to care about a lot of things before you can even start to make a game. But you're pretty much limitless. You have full access to .NET Framework, other libraries and such, you have the full control.
It's a personal preference whenever you enjoy the process of making the game from the very start or you just want to go straight in the game development environment. For simple games, the Unity is usually a better choice.
Also, the platform support isn't much of the question unless you want to make a mobile game (I would go straight to Unity there). 85% of computers use Windows OS, so the platform support isn't such a big deal.
<strong>Edit:</strong> Oh well, you can use .NET libs in Unity as well by importing them into the project - they will be referenced straight. Still, it overall depends on what you prefer.Answer4:
The real problem that should interest you here is <strong>Engine</strong>.
<strong>Unity</strong> is a ready and cross-platform complete engine with physics and stuff.
In other side:
<strong>WPF</strong> is just .Net Framework and you (well.. and some libraries), so that's up on you to carry on all that stuff (creating physics, renderer, etc..) for making a game.
If you are planning to create some very custom stuff or something easy like tic-tac-toe for windows then go with <strong>WPF</strong>.
But if you want to create some 3D first person space shooter, then personally I would suggest you to use <em>Unity</em> or some other (already completed) engine (or if you have a lot of time and creativity, create your own engine).