Not a VS thread at all just want to get some honest opinions.
Given that UE4 has blueprints say you were picking a new Engine and starting over would you still go with Unity?
Not counting your years of experience lets say you were to suddenly forget everything you knew about Unity. One of the main reasons I seem to be using Unity appears to be the vast amount of youtube tutorials. From a beginner perspective UE4 is really difficult to get started with but I heard Blueprints changes all of this, so not sure.
To me platformer games seem to be easy with Unity and I heard to stay away from UE4 for this.
UE4 looks great TBH, but I don’t think its enough to make me to make the change. I spent a lot of time learning and getting stuff together and making projects worth while now. I don’t think UE4 can offer the speed and productivity that unity can. Make games and get them out there I say!
Yes. I was already a programmer and already knew C# before Unity was first released.
Making the right choice in my opinion isn’t just asking for and listening to advice on a forum which is what seems to have been happening the past couple of days. Making the right choice involves actually sitting down with each engine and learning it as well as watching the community for the engine to see how friendly and helpful they are.
Unity was not my first choice. One of the first engines I evaluated was actually UDK (aka Unreal 3) but because of how difficult it was to work with I abandoned it in favor of Unity. That said even after choosing Unity I still try out new engines as they are released like Unreal 4, CryEngine V, and Lumberyard. I can’t remember if I tried Stingray or not.
Who knows. I fell into Unity by random chance when I was searching for free game engines. At the time Unity Free had a decent feature set, and Unreal required an expensive lisence.
Now both Unreal and Unity are fully featured for free. There is not much in the price difference to influence a hobbyist. It’s virtually impossible to strip away my biases when making an engine choice.
Yes. I reevaluate things from time to time and Unity is still the best overall choice. I’ve tried probably most of the popular engines and always come back to Unity. There are pros and cons to every choice, but if you are starting out I can’t think of a better engine than Unity.
Everytime I find a good github project, editor enhancement, asset, improving those tools etc its like another reason to stick to using Unity. If I didn’t already have this experience using the engine for a year now I’d say I’d be looking at UE4 again, and just like before I’d probably come over to Unity It’s also the community or the amount of resources available to tap into and get head start on things. Unity’s killer feature is the community resources, and if they all built most the tools using c#, any other engine would be stupid not to tap into that developer community by supporting the same language. Of course if they want to put in some other killer feature like I dunno an awesome smooth/block voxel engine with multiplayer taken care of, terrain, modding etc, then its one of those things any indie developer might overlook the state of the rest of the engine so long as the game they are wanting build has some of its biggest requirements met in the engine, its alot easier to build smaller features/tools/systems, while things like core game engine features take a lot longer.
There is plenty of things I like about UE4 features, like the stuff they have built in, from Unity you’d be spending at least $$$ upfront at the asset store to have the same tools and features to use for a game, honestly if I wasn’t doing this indie dev thing solo I would consider UE4 much more favorably even for a small indie team… but as solo? nah UE4 doesn’t seem to have any intention to support c# and by the looks of it won’t in the future either. So you or your indie team would need someone with good c++ skills that likes using that dinosaur language of header file headaches else you stick completely to visual blueprint spaghetti hell. Personally I need some sane balance inbetween like c#/java and don’t want to get caught up in using c++ as indie, too many things do to solo where focusing on building systems for a game in C++ is not fun unless you’re in a team and everyone can do certain things its better, so if you have a team with some mixed talents or don’t mind sticking to blueprints… then yeh else nah.
And I would also consider Cryengine this year, if they stay on track with with the improvements/training material/documentation. As the stuff they have been doing since 5x has been really good adopting c# along with the new blueprint/component like system is a nice inbetween of UE4/Unity imo … which is a no brainer to me if you make an engine and want to consider indies, c# is must imo. And if they sort out the pipeline especially for building UI’s so its not that scaleform nonsense and have some sort of built in GUI builder like UE4 does, tied into the schematyc stuff, then they’ll be getting serious. It’s a shame Crytek took so long to get a clue on making these engine improvements but better late than never I guess.
No. When I was looking for an engine, I looked for a more general purpose game engine. Tutorial and community are plus but not the main thing for me, at that time. So I picked the unity as it served my main purpose as well as the secondary ones at that times. It was the time when people were using UDK, around 2012-13.
However many things have been changed around me and the game development world. I am not sure currently which engine I will use for my ultimate dream game. But I am sure it will NOT be unity For current profession’s sake, I am using unity as I am mostly familiar with unity, compared to other engines.
I’d be looking for decent documentation, some possibility of freelance work, and maybe an store for addons. Most likely even if I picked up Unreal 4 at first, I’d wound up with unity engine in the end again.
I would say yes, I mean don’t get me wrong, I’m really enticed by the idea of AAA graphics, cryengine’s GI solution etc, but in the end it all boils down to… as a one man band what is the quickest and easiest to develop in. That answer is unity, and it is the only one that works reliably on my mac mini. You’ll find a lot of indies go through the same process, switching to unreal engine then coming back to unity because they understand that with a AAA game comes a lot more effort. Additionally, the greatness of a game isn’t determined by flashy graphics anymore, it’s game play and narrative. Mind you I’ve been using unity for just over a year now, and the last spec I tried unreal engine on was still too low.
I am not sure why people think blueprints are such a great thing. Just learn C#, it is not that hard and gives you a huge amount of flexibility way beyond blueprints. People spend more time learning work-arounds to avoid programming than it would actually take to learn programming.
I recently tried out most of the main engines out there (with some, like UE, I have been playing around for years) and these trials reinforced my belief that Unity still is the best engine for my purposes.
I am also generally pretty happy with Unity overall, especially when it comes to features and how productive it allows me to be. I can work very easily and quickly using it and so far I didn’t have to make any compromises when it came to actually creating what I had envisioned. Since our project is nearing its finishing stages, that means a lot to me.
I am fairly confident that without Unity, our game wouldn’t exist.
But that is only for our specific purposes. If I had a large game development studio with a big budget and lots of professional employees working on an AAA PC/console game which requires the best of the best graphics, I might go with Unreal or CryEngine.
I think I made the right choice going with Unity all those years ago.
Based on my mobile focus, I would probably go with Cocos if making the choice now, but it would be a close run thing. I would chose Unity 3 over either of them if it was still a viable option.
I actually tried to switch to UE4 for about a year. I ended up finally accepting that I don’t work well with its workflow and gave up and came back to Unity. So yes, I can confidently say that I’d pick Unity again.
What engine you choose largely depends on what you want to make, size of team and requirement of source code (you can license Unity’s for a price though) and so on.
So for mobile I would go with Unity in a heartbeat. Picture gets fuzzy when you do big 3D stuff with big visuals on console / desktop only.
For mobile, or lots of platforms, there’s only Unity IMHO.
Yeah I remember asking and people telling me about this thingy called source code. And that is free in UE4 then I thought to myself what the hell is source code so I looked it up.
Apparently its black magic as far as I am concerned seeing as I am a one man dev doing 2D platformer and don’t know 2 hoots about programming. LOL I am now learning basics of C# so writing source code in C++ isn’t for this lifetime that is for sure.
Yes, I would go with Unity. I try to keep myself up to date with all available game engines, and Unity offers the best deal for us. In addition to that, the size of the community and asset store are two major advantages as well.
Blueprints have no appeal to me as a programmer in a small team.
It’s also the community or the amount of resources available to tap into and get head start on things. Unity’s killer feature is the community resources, and if they all built most the tools using c#, any other engine would be stupid not to tap into that developer community by supporting the same language. Of course if they want to put in some other killer feature like I dunno an awesome smooth/block voxel engine with multiplayer taken care of, terrain, modding etc, then its one of those things any indie developer might overlook the state of the rest of the engine so long as the game they are wanting build has some of its biggest requirements met in the engine, its alot easier to build smaller features/tools/systems, while things like core game engine features take a lot longer.
For current profession’s sake, I am using unity as I am mostly familiar with unity, compared to other engines.