Depending on the graphical fidelity you're chasing Unity is probably the most polished of the 3 majors.
UE4 is a great tool but has a slower development cycle.
CryEngine is almost broken unless you're willing to do a deep dive in the source.
If by "explore game dev" you mean, "make games" Unity or UE4 will serve you well. UE4 has a nexus of great artists using the tool so recruiting artists that are familiar with the toolset is easier. Unity is some multiple of more productive, pending your skill level with C#.
I've evaluated all 3, am a proficient programmer in C++ and C#(among others), and have shipped several games with Unity. I've also worked on a couple of shipped titles with UE4.(nothing major)
On the other hand, Blueprints and the node-based material editor are really nice for quickly snapping content together.
Yea I think it is about time I gave Unity another go, and will set aside some time to go over some tutorials.
I just recall doing things like setting up path finding and AI was much easier in UE and setting up player characters etc was all already built into UE templates.
The whole UE IDE or workflow also just made more sense to me, and was more polished. Maybe I just didn't give Unity enough of a chance.
edit: I am a Java guy myself, and would like to do some amateur gamedev in that direction (online FPS), but im worried about above mentioned point.
There are plenty of production games that can live with < 10ms pauses.
I'm also not sure about the new c# -> to native compilers coming out.
For example GC.TryStartNoGCRegion
https://msdn.microsoft.com/en-us/library/dn906201%28v=vs.110...
SafeBuffers
https://msdn.microsoft.com/library/system.runtime.interopser...
Or using array segments
https://msdn.microsoft.com/en-us/library/9cc4bx8k(v=vs.110)....
Unity has made a lot to spread C# love among game devs, but it also gave a bad reputation to those unaware how .NET really is.
Not really. If you look to the future, I'd recommend Rust for making game engines. They by nature should be latency sensitive, and any kind of non deterministic behavior caused by garbage collector is really unacceptable.
Rust is a nice language, but Unity already uses C++ outside of the user-facing scripting layer.
Not everywhere. Phones, tablets and older or low end laptops are very popular.
In every other case, you're better off using a language whose resource management model doesn't fight you.
Swift is the best of both worlds in this regard.
Besides, it is not guaranteed that you'll succeed with a manual strategy for dealing with garbage. Naive strategies have a really low throughput. They may not stop the world, but will be slow.
Apparently we need to go through this cycle every few decades.
Garbage-collection has a bad name for some reason in game-dev circles, which maybe makes sense if you're developing a fast-twitch action game or shooter - a GC pause might drop enough frames to matter there, but for most games, Java or C# should be fine.
Are most games adventure, puzzle solving, or turn-based?
certainly "fast-twitch action games" and "fast twitch shooters" are a minority of all games.
The best selling console games are sports simulators and first person shooters. The next popular are open world RPG/action (Skyrim, Fallout), then we have fighting and racing games. 2.5D platformsrs are also popular now. All of these games need the deterministic guarantees of "fast twitched action games".
It's not so much performance as much as control. Objective-C is a lot slower than C++, but making action games in pure Objective-C is viable because you are still in control of a system that allows for deterministic resource cleanup and stable frame rate.
In the US, I'd say turn based RPGs and puzzle games are by far the least popular genre on consoles across the board. They may be most widely produced games, they are hardly the most widely consumed ( outside of Mobile).
I specified "fast twitch action", not just action. For instance, both of the open-world action games you mentioned are single-player only, so issues like lag and slowdown are less critical. Also, enemies in those games are almost always slow-moving- definitely no fast-twitch required.
For fast twitch action (not shooter), I might include things like street fighter, where button timing and reflexes are critical. Most 2.5d platformers I've seen would not suffer that much for the occasional dozen-millisecond GC pause. In fact, many of them have worse pauses than that for less prosaic reasons. ;-)
Swift's ARC is basically automatic boilerplate for resource management that's applied at compile time. It's extremely flexible in that you can also use raw pointers and manage memory manually if you want to. A native language with ARC as a passive option is a way better tool for making games than a garbage collected one on the VM, IMO.
> ;-)
I'll never understand why people think winking online is a socially competent thing to do.
You surely need it if you plan to work on high performance engines. Hopefully Rust will find its place there as well.
Got a little bleak when I saw CryEngine and C++. As someone who uses C# and Java it's becoming pretty clear I need to start learning C++ if I want to explore game dev.
I realize Unity uses C# but when I compare UE, Unity and CryEngine it really feels like Unity still has a long way to go. The features you get out the box with UE for example are far superior to Unity.
Anyway, I just went off topic. It looks like an interesting option for developing multiplayer focused games.