I've been trying to publish a game with UE4 for about 1 year now (on and off). I get put off by the abundance of default assumptions the engine makes about your game (if it's not a standard shooter you gotta change about 90% of the default stuff the Gameplay Framework gives you). Also UE doesn't really help with its inheritance based infrastructure. I'd much rather work within an ECS context but you just run into a lot of non-clean glue between the legacy inheritance based systems inside UE and your custom components. It's just a mess. Also, iteration times are significantly slow. If you're working with C++ things get twice as slow (at least). You really have to have your math figured out if you don't want to waste time recompiling your code every 5-8 minutes. I haven't tried Unity yet but I'll be trying it out starting this month. I'm very excited about the apparent ease of driving procedural animations and the CineMachine. Wish me luck lol
@@novaria Good luck with Unity. I actually spent the last month building a camera behavior system the leverages cinemachine in an animation timeline. It’s very cool and can make working with cameras trivially easy.
I personally develop AAA titles using Notepad and a bread board as my only tools. How are they related? Who knows. I just work at Ubisoft and my only purpose is to introduce bugs into games.
As a person who tinkered with C++ and C# who tried both engines I have to say Unreal was easier for me. The thing with the blueprint system is if you understand the basic game logic blueprints are a great help.
yes, I was trying to understand unity for pretty long, but then when I tried Unreal I instantly understood the engine. Its probably true that even a 10 yr old could pull of an OK game with unreal.
Exact experience that I had. Blueprinting just clicked, and Unreal Engine is overall less stressful for me. But many people love Unity, and if you're able to get past the C# hurdle than I am sure it has its benefits also.
There are also visual scripting languages for Unity like BOLT or Playmaker. Bolt is like C# but without writing it and Playmaker is like an easy understandable tool. I work in C# but playmaker saves me sanity and time sometimes.
yeah blueprint good all and all but you cant build a solid foundation with blueprints (i can't at least) maybe i know c# a lot more but writing with c# a lot faster for me (not talking about code performance) i can build better foundations and better structure for my game with c# if i could write c++ better i would use unreal
It is typical 'programmer-circuited' brain's thinking. The basis 'understanding basic game logic' already assumes certain kind of userbase and it is absolutely not pointing normal audiences. You can confine targets to specific group, but it may lead you from your saying. (Re-Definition of EASYNESS if ooo, if ooo, if ooo...)
I think this was literally one of the best videos breaking down pros and cons for someone who is literally starting today on his first unreal engine 5 use. Thanks man!
I appreciate your analysis of these two incredible engines. I use Unity, but am constantly curious and amazed by Unreal. Since I am still really at a beginner / intermediate phase in learning Game Dev, I am glad to be using Unity and C#. I have found c# much more readable code than scripts I have seen in C++, so that is something. Thanks for the updated discussion!
'ey man, I just found this video randomly while looking up differences between the engines. I don't even know what your channel is about but that intro had me subbing so fast! haha, right on!
Thank you very much for this informative video. We are currently planning a game project for university and we have do decide for an engine. Your video helped me to create a complete comparison sheet which I can discuss with the team.
Great video! I am learnig Unity and making my first game, I thought about switching to Unreal, but it is very difficult. Your video helped me a lot. I will continue with Unity and improve my abilities there. Thank you!
Just came across your channel watched this and and found it very informative clearly presented. new sub great job I'm just thinking of trying game development. And this helped loads going to take your advice and try both 30 days on each thankyou
I'm a computer engineering student and planning to make my own game in the future, this is helpful for to know which is better. Thank you for giving the comparison with great explanation to clear out my confusion.
Great video! Learned a lot about both Unity and Unreal. Since both engines have their own pros and cons, I like how you ended the video saying it’s pretty much up to the individual and what’s best for them. The fact that both Unreal and Unity can publish Nintendo games was surprising.
I’ve worked in AAA studios as a game programmer since 2006 to now. And I agree with everything you said. Very informative. I currently use both for my personal projects for different purposes.
شكرا لك شرح ممتاز ومباشر و الاهم المقارنة صادقة دون تحيز Thank you for an excellent and direct explanation, and most importantly, the comparison is honest without bias
9:20 - unlike others, my problem is not coding. My problem is the visual part of the development. I'm not creative enough and not good in visualizing, that's what's holding me back.
@@elangel986 I think you have a clearer future in this field than me. Because in making games visualization and creativity is more important since there are ways now to develop a no code project in Unreal and even in Unity.
@@lowkeygaming4716 there are much more money in coding, so i dont agree... and creativity in programing is also very important! You cant make a game without a coder, but you can make a game without skills in visual stuff. All of the one man gamemakers are coders. (coming from a "creative guy")
@@lowkeygaming4716 i wish i could say the same, i got no budget to hire someone and when i try to study programming my brain gives up, For visual there are lots of assets for free to use, so it would be much easier for ya.. you can do it!!
Same here, coding is not even the problem but I cant model, design. I am good with making stories having ideas and coding everything but Ill end up having to use free models which doesnt fit my expectations.
Thanks. Very informative. Never thought I would see a day Unreal is cheaper for most than Unity. Also I was reading about Unreal 5's Nanite engine. As a former architect visualizer I used to produce just high poly for still and animated scenes. I just don't want to spend time, and that feature can be a game changer for that. I just want to get back to this sector as a hobby.
The amount of free tools, high quality materials and assets, professional level hair systems and all these things along with the engine itself made Unreal a no-brainer for me. Yes, its probably harder to learn, but once you have passed that first learning curve the features are too many to pass. Also, i wouldn't call it only a 3rd/1st person shooter engine. As long as it's not 2d games, Unreal can do it just as well.
i've used unity for a long time and get frustrated that a lot of basic stuff isn't build in. i'm temped to try unreal since all the free tools sound much more polished that the hit and mis unity asset store stuff
Thanks Brendan that was really good. I use Unreal but hear a lot about Unity so watched this to help compare the two. It has given me a lot of insight into Unity which I know next to nothing about. It has also helped me appreciate how much I have already learnt about Unreal and visual scripting. It was the Kite demo stuff I saw for Unreal that got me into it, the open world stuff I find fascinating.
Very informative video with lots of easy-to-digest information, cheers for this. I've always been fascinated by game development but only dipped my toes into some RPG Maker things in the late 2000s/early 2010s, and more recently Frictional Games' in-house HPL engine. I just downloaded Unreal yesterday and have been tinkering around for a few hours. I think I'll try Unity at some point too as it may be more accessible for someone of my entry level. Both seem phenomenally powerful and capable. Thank you for going into as much detail as you did here, hope you're doing well.
Fantastic video, Brendan. I nearly agreed with you on every single point. I've been using Unity for several years, but I think I'll be making the switch to Unreal for a smaller project, but with a focus on graphical fidelity. As much as I love Unity, the lighting system just isn't cutting it. Both engines have their pros and cons and I can't say it's a wise decision to be 100% loyal to either one of them 100% of the time. Different use cases for different engines. Thanks for taking the time to make this, it's well thought out and you have some great insight.
Brendan, great video thanks for replying to the comments below and sharing your expertise as such. Very valuable. Do you have any thoughts on Maya, Blender, 3Ds Max? Pros and cons?
Good video. If you're going to make shooters Unreal will definitely give you wind in your sails. I started with Unity about 3 years ago but I mostly make FPS games in Unreal these days and it's just brilliant.
This is probably the best Unity vs Unreal video I have seen! One my biggest gripe massive amount of preview packages (and they sit in preview for years, although it is kind of changing now) and with Unity is having to rely on 3rd party plugins or you have to create things on your own. Just to be clear I am not talking about things you can/should make yourself. I am talking about things that engine should natively provide.
thank you for this video! Going to go with Unreal engine the work that you put into it looks worth it but thats my opinion we will see if I feel the same after a few months of working with it lol
One little thing not mentioned in the video is the fact that some of the mentioned games like Inside were made with access to unity engines source code, so they had total rewrites of parts of the graphics engine. Which means you are limited with the normal unity version (source code access costs a LOT of money with unity) Unreal's compile times are usually long if you use the old methods of including engine.h. The newer coding paradigm is to include all needed headers on a per object / component basis, that speeds up the compile time with less overhead.
most of the time you don't need to rewrite source code but if you need to rewrite source code you can make your own system also rewriting unreal source code is almost impossible did you ever tried to rewrite unreal engine source code its so hard
Props man! Some serious quality in this video. Have you released games through both of these engines? Or has most of your development time gone towards non-game applications? I would be interested in hearing more about these non-game applications either way.
Thanks, Jared! While I've made games in both engines and exhibited them at expos I don't think I have any of my Unreal games available to the public. Most of my development has definitely been with non-game applications. These apps are all over the spectrum, but most have to do with 3D simulation and data representation, I do plan to do a video specifically about this topic sometime in the future I'm just not sure when. If you'd like to know more details feel free to DM me on Twitter @BrendanDickins
Excellent presentation, thanks!! I'm considering both for Architectural presentation which I assume knocks out 80% of the difficulty and learning curve, tools and functionality as a game must be much harder with interactive requirements. AND trying to use my DWG files from Autocad Architecture. Datasmith brought them straight into Unreal and I was doing a walkthru within hours and a couple of days have a basic walkthru I could show a client. Not flash but an excellent tool. That Unreal's graphics, lighting and realism is higher does pull me that way. With programming, I suspect I won't really need it so whilst C# sounds way better to a non-programmer (and old bloke) it is probably not necessary. Now Lumion created an add-on to Autocad to export to .dae and it creates a model I can bring straight into Unity and selection is grouped to materials set in Autocad Arch which seems to be ideal. It also has a LiveLink to Lumion which looks brilliant. Ah, a world of great choices!! Where to spend my time, which to learn.
Very awesome to hear this being used in an Architecture sense, back when I worked for a consultancy we looked at Architecture as a potential vertical to market to but never ended up going anywhere with it. Lots of my work has been in the medical, automotive, and consumer products space with room planning and laying out warehouses or buildings so very close to Architecture.
@@BrendanDickinsonUnity The trick for me, in the lower end of the market is not redoing stuff and I've rendered in Autocad Architecture (save any round tripping) for years but they keep changing but not really improving the interface and it's SO SLOW. So finally, I am pushed kicking and screaming to use a 2nd tool. This current project - the client has now made big design changes so the Unreal file is scrapped and I will need to reimport a new model. Not how I wanted to work but if the outcomes are much better.... I am hoping I can set up a template file to import into, ready to do my bidding quick and clean. Thanks for your contribution to a 'prospective's' perspective on where to go.
Having used both engines, both as a teacher and as a developer, I feel this was very biased towards Unity. Now, don't get me wrong. Unity is just fine if you want to make whatever. It shines in 2D games, it can pull off nice 3D games too if you know what you're doing, and you can build apps on it. But the main issue, which was pointed out in the video but not made as big a deal as it is in reality, is that everything in Unity is half-assed, like the devs start to add support to something then just stop midway through. I remember working with AR was a pain in the ass because we had to use one specific version where everything we needed kinda worked as expected. One version later it was all broken and still is to this day. Fiddle with the engine long enough and you'll find ceilings like this on almost everything. VR also had issues in certain versions. Arduino support was only good in a few others too. When I was a teacher, we had like five versions of Unity always installed so we could hop back and forth through them as needed. This restricts what you can do as a developer, because if you want to make a mobile game that uses two of these features and they are spread apart on different engine versions, there's nothing you can do. I also felt a lack of research on what Unreal can do. Yes, you can do non-games in Unreal. You can do these in any engine; I've done it even in Game Maker a couple years ago. It's being used extensively in the movies industry, but also in other stuff, from simulations to car HUDs. You can also very easily compile HTML5 games with it, and it isn't as bloated as people expect. Android games are also very viable, as well as 2D games. The thing with 2D games is that most of the 3D resources aren't available in 2D; like animation notifications, which are extensively used in 3D, as well as certain AI features like EQS (which wouldn't make sense in 2D anyway), but you can do good stuff. There are lots of 2D Unreal games out there, and if you're willing to spend on plugins, there's amazing stuff like Pixel 2D, which brings the 3D work pipeline back into Paper2D. Blueprint was also very underrated in this video. It's an awesome tool to teach the developer how the engine works under the hood, as when/if the user decides to move on to C++, they'll be already familiarized with how Unreal structures everything, making the transition to C++ very smooth, and it's also a very good way to hit the ground running in C++. Unity is very accessible when you want to do basic stuff, but when it gets advanced, it really steeps up in the learning curve in C#, and Bolt isn't very comparable to the Blueprint Editor, since you have to fiddle around in the engine to even get it working, whereas in Unreal you just right-click anywhere to create a BP and start coding. There are other things too that went missing, like each engines philosofies and basic QoL stuff that's available in Unreal but missing in Unity. Overall I felt like you didn't know enough of Unreal to give an opinion on it.
i feel you need to do a blog post on your experience and drop us a link. A lot of us newbies would like to learn from your experience with both engines
In my opinion to find what's best for you is test drive them create a smallish prototype keep it the same in both engines and then you will be able to sum up what works for you don't listen to others it has to be you who make the decision but i do agree with the face C# is defiantly easier to get your head around . I do have to say there a few points that has been missed here on the unreal front such as the learning tools that unreal offers developers with some very interesting and informative content, i always find it very strange that a lot of guys that don't work with unreal make the point that to them the ui is hard to understand at the start but when you break them both down they are very similar. Remember guys and girls whoever you listen to on this topic there is always a bias opinion on engines not that they mean to it's just how it is, your the only one that can decide what's right for you. Good job on the breakdown Brendan
Great vid btw, I think the pros & cons of each you gave are quite accurate. From what I know in a nutshell Unity's problem is *severe* lack of reliable features, direction & stability and Unreal's issue is a lack of freely available knowledge pool both in the context of anything beyond surface level complexity. Also most ppl agree that working with C# is a much better experience. I'm working on a AA 3D ARPG on Unity and quite frankly Unity feels like a mere 3D rendering engine with some bare minimum game dev tools hacked onto it. I had to write up pretty much everything by myself and fill in several blanks with 3rd party systems. It's sad that when you get so far you realize late that you kinda have been lured by appetizing tutorials with deceiving simplicity. I've been wanting to transition to UE for quite some time cuz Unity nowadays doesn't seem interested in saving what looks like a sinking ship despite the myriad complaints they get on a daily basis on their forums though porting entire big projects is just too painful an experience to repeat and there's no denying the overwhelming popularity of Unity being a significant advantage that can to some degree offset the many, *many* cons through the sheer amount & quality of external resources if you're a solo dev or small team with limited budget/resources. For every good thing in Unity I can name 3 more bad ones and I've noticed that despite when even actively looking for what possible cons UE has cuz it looks too good to be true and you'd generally hear ppl having a good experience with it while on the Unity camp you'll read hundreds of walls of texts of complaints & rants. So basically the main reasons I'm still using it are: C#, community resources & docs and the fact I went too deep into development to consider porting now unless maybe the process isn't too painful and if Epic find interest in my project someday to consider helping for the port. Then again the knowledge & skills I learned and resources I acquired are too valuable to throw away now.. An engine + a language's frameworks are quite big and require a lot of time and patience. That or hopefully Unity comes to its senses and start making the engine more stable, with faster iteration times (read assembly reload..) with reliable *native* features instead of dumping all the responsibility on 3rd party to make a quick buck. I don't think UE is perfect either tho cuz the main complaint I hear from ppl using it is a very significant lack of information so what good is having a huge box of tools if you can't have an extensive enough manual to use them to make something complex so the main worry in using it is getting stuck in some obscure parts of the engine and not finding answers or workarounds cuz you have to realize that the majority of online users are just hobbyists in the end. I'm open for feedback on this though cuz my knowledge of UE is limited since I haven't used it.
I am doing a lot of procedural world generation. I did it with Unity and Unreal and atm I honestly think, if you want to implement a lot of procedural content, Unity will work better. There are already very good third-party plug-ins and way more documentation/tutorials.
I like Unity because it suits my specific project well and does what I need it to. Unreal looks AMAZING but I am too lazy to learn C++ AND a new engine. Maybe one day.
@asiri maduranga I do some solo game development on the side as "Light Pyro Media"" but I haven't released anything yet. I mainly do contract concept art for other groups.
Thank you, great video. I been with Unity3D for, hmmmm 8 years I think, a long time. I going to learn UE for 2022 and build a game with it. The move from C# to C++ I hope is not a long path. As you said, give it 30 days. I will and see if I make the switch. The only sad part was the drop of support on 2D for UE. Maybe UE see Unity is wha ahead of the game and they only want to focus on 3D only. The 2.5D in UE may work just as well. The test will be on a phone.
Hi, Brendan. Thank You for this amazing video. Right now i am on my way of choice between this two engines. My task is to make a simple application disassembles some technical devices. For example, press a part of device and it shows how it is works and what other parts it is made of. According your opinion what of this two engines is best for that? Materials and 3d models i make in other program. Have some experience in coding. Thank you in advance .
Hi Maxim, sorry it's taken me so long to respond. For a more simple application that seems more business oriented I would definitely use Unity. The fact that Unity doesn't constrain as much will help you out.
Hi Brendan and thank you for this great insightful video on which engine is better, even though in the end it seems to come down to personal preference. Anyway hopefully you can take the time to answer my question as this is already a year old video. I'm completely new to game design, and just want to give it a go and see where this adventure ends. Now for coding, I've seen that C++, even though it's more difficult than C#, the following description can be found on it: "Developers tend to choose C++ when it comes to the speed of applications. It's a more powerful language to run video games and operating systems, while C# is a beginner-friendly language and it's better for creating Windows software and web development, usually backend." Wouldn't that make C++ the better choice despite that it's more difficult to learn? Probably also depends on the type of game I'd like to build. I'm thinking along the lines of Dragon Age, with the realtime-with-pause mechanic, where I can opt to command characters to perform multiple tasks, before unpausing the game and seeing the characters do exactly that. Graphics at first, when learning aren't a big deal, but I'm under the impression that, when Unreal Engine 5 is released in full effect, it's probably the best there is on the market and with regards to delivering an as polished as possible game, it's probably wiser to go for learning Unreal Engine 4, which will make for an easier switch to UE5, than Unity, unless Unity will drop an engine update soon which rivals the photorealistic options of UE5. I'm tempted to consider Unreal Engine over Unity, but perhaps my arguments make no sense.
No problem Omkara, I think you're honestly worrying too much about the capabilities of the engine and the type of coding language you'll be using. For your purposes I would say that neither of these matter in any way except if there's something you can't do in one engine that you need. I would say given your description of the type of game you're trying to make, you could do that with either engine. You aren't going to be held back by anything other than your preferences and learning speed. So what I would recommend is the same as in the video, give each engine a try since they are both free and give them a couple weeks each, maybe a month. Then you should know which one you're more comfortable with, and I would move forward with that. On the topic of graphics, are you doing a hyper-realistic game? There aren't many games that are at that level of fidelity and the ones that are, are more showcases or experiences than a game, or made by large studios with dozens if not hundreds of people working on the same game and millions in the budget. There are very few solo developers that end up going that route, also many of the best games out there are not hyperrealistic, dragon age graphics are very possible in either of these engines. As for coding, this is really preference unless you are pushing the limits of a pc. C++ is more powerful and can be faster since it's a lower level language than C#, however nowadays most optimization doesn't actually come from that kind of coding, you can still manage memory and most other things using C#, and the things that actually need to be optimized are models and textures, especially when running high end graphics, not code. Of course there will be people on both sides that say one language is better than the other for this or that, but if you actually learn how to code, it's not that difficult to switch over to other languages. For example I know C#, C++, Python, Java, and JavaScript to name a few. The hardest thing to learn is how to code in the first place, all the foundational stuff stays the same and can be applied to each language. Another thing to keep in mind is that you'll need to learn the API's for each engine, which means not only learning C# or C++, but how they work within Unity or Unreal, this is where I think you should focus while beginning. Hopefully that helps you with some of your questions. Personally I would try to create one mechanic or interaction that you would like in your game, in each engine. By that point you'll probably understand which one you want to go with, really there is no wrong answer for your particular case.
I’ve just moved from Unity to Unreal 5 and MY GOD. Unreal is.... well, UNREAL the power behind the engine is breath taking. I’ve always found that you can have good post processing with unity but it takes so much hassle and time, Unreal is just beautiful to look at straight out of the box. I recommend unreal any day of the week
After 5 years of dev of my project, I've decided to rewrite it in UE 5; Unity 2021 w DX 12, DXR, HDRP is abysmal in performance, Nanite and lumen gets me 12x fps in the same scenes (and look waaaay better).
@@LoudFiat I've just started with unity, idk why I'm watching this video, I was looking for "terrain ideas" because I'm getting fed up with it, every time I make a terrain it looks like a trash, nvm, how is UE after 6 days of your comment?
A few things that were wrong. Most importantly, with Forest, you seem to have confused high-resolution textures from an asset pack with "good graphics." Forest is a go-to example of a default Unity project with no unique art direction or style. The engines are not free in a similar way under a certain income. UE4 is completely free to the point of source access, profiling tools etc. whilst Unity even if you don't make x amount they've now paywalled a collection of useful features that most serious devs would need when working on a full game. Unreal is NOT a good or even ok option for mobile dev just because you've seen Infinity running on mobile. A game created by a dedicated team from the engine creators. Unity is a much better option for mobile, not even close due to all the lacking features and difficulties with building a mobile game with unreal. Hopefully, it's obvious that I'm not fanboying either side as the two main things that were wrong were pro the other engine. Just annoying to see another, "use whichever" VS video when there are some clear and easy selling points for both when you've actually had some experience using both for a long enough period of time rather than just doing a days research to release a video. And more of a preference thing but you only looked at the coding languages based on what you like to use, which also makes it clear you've used Unity for a long time. But C++ is the better language, more flexible, full control over memory and it's more performant. If you're serious about developing, the learning curve is pretty irrelevant as after the tiniest percent of the overall time you'll be developing through your life, you'd have become proficient at either.
First off I want to say this is all great stuff, and I appreciate the comment. I have to be honest in that I don't know how the guys at Endnight decided to handle all the assets in The Forest, what I do know is that the team that built it has a background in film visual effects, having worked on films such as The Amazing Spider-Man 2 and Tron: Legacy. They were able to bring this knowledge to Unity to create a visually impressive game (and one that happens to be #7 on steams top sellers at the moment). It's probably an unpopular opinion but I don't personally believe anything is wrong with buying high-quality asset packs to use in your game, especially if that's a skill set that you're lacking. I did mention that UE4 gives you source access which is very nice for experienced developers. Unity also gives you access to the entire feature set of the engine in the free version; there is nothing paywalled within the software, although this wasn't always the case. The only exception here is the customizable splash screen, online services like usage analytics (not the profiler, which is available for free) and cloud builds, which you can find replacements for. I do agree that if someone wants to make a mobile game it's going to be easier to use Unity, I should have made this more explicit in my video. As for the coding language, this really is a matter of opinion. I know a lot of people who prefer to work in C++ and I know people that refuse to use Unreal for the sheer fact there is no easy support for C#. Which language is technically better is irrelevant, and I think up for discussion, as they are both fine languages for making games through these engines. This is a big thing that drives people's decisions on which engine to use, and if you have knowledge of programming I'm sure you already lean one way or another. If you don't have experience programming, it is my opinion that you should start by learning something like C# or Java and therefore Unity is going to be a more natural fit, but it's just that, an opinion. Also, I'm assuming most people who are searching and watching this video are people who are just starting out and want some guidance. Because of that learning curve is something that I have to cover. I've seen several beginners open up Unreal only to spend weeks banging their heads against a desk not able to get the results they wanted, and in turn, this caused them to drop it and move to Unity. I'm not trying to say that this will factor in later on, but it could help prepare people when they otherwise might not know what they are jumping into. Again thank you for the comment, it made me really think about some of the points I made and why I discussed the things I did!
There is no better language. It's fair to say c++ is more powerful as it gives you more control over low-level stuff. But more power and control can be both a good and a bad thing depending on circumstances and needs - in many cases simplicity and fast iteration times are better. Also keep in mind this video is mostly for beginners. Custom memory management and data alignment is cool to have but i'm sure it's something most hobby or even indie game developers won't ever want to or need to worry about - also with DOTS/ECS you can have performance mostly comparable with c++ in c#. Sure it's only in preview at the moment but i'm more than sure it will be production ready long before any beginner will learn c++ to the point where he'll be able to implement anything more performant in c++. TL;DR; if you're just starting to learn go with c#. You can always learn c++ later.
Wait.. Is unreal competing with unity? According to me unity has only got 2-3 world known famous games.. and unreal easy to mention 100+? guess I have to go do more research. Thanks for the heads up. I thought unreal was the leader in the industry.
I personally just started to use unreal engine, and I'm using blueprints but plan to switch to C++ soon since I spend a whole week learning the language. tbh, i don't think the unreal engine interface is that complicated. it took me 20 mins of tutorials and after that it was all really easy. But I have to admit, trying to fix bugs is pretty hard and there aren't many results when you try to search up how to fix a bug. But I'm planning to stick with unreal because of all its tools and also all the amazing assets in the marketplace.
when you create your game with your own codebase is a lot easier to debug thats why i don't like blueprints if you know what your doing while code c++ you will be fine
@@TheRealKingSolomon unity seems to be easier to use and my first project is an interactive movie, but Unreal seems terrific for photorealistic imagery and 3D games, so that will be for another project. I’m also wanting to do a scroller and some RPGs and just found there are other engines for that! I think my criteria will have to be open source to begin with as long as possible, but unity and unreal make it easy for you to start for free. I’m gonna take basic lessons of both of them and see which makes me feel more comfortable.
Thank you I was looking for some insight on making a game. So it's one of the two engines. I believe I will go with unreal engine. I am new to this, so forgive me if I butcher this. But I want to build a game on unreal engine running vulkan API over DX12
Hello, can you design a game with a big size like resident evil in Unity I moved a bunch of models to Unity and when it got to 8 GB Unity started crashing and not working please help
How about networking (online, netcode), how hard to hack/cheat in those engines, is there one which is better for networking than the other ? also is there one engine that is harder for people to cheat, make hacks and exploits? or are those too broad to be able to pick one engine which would do better? Great video by the way! :)
Using Unreal. Day 4. 2D pixel game. Making a platformer, demo. Not sure what to do but taking notes as I go. Reason for unreal engine for me is that I will help my friend with the game music and graphics. Since he is using Unreal, I thought, "why not learn a little", just to understand what it can and cannot do. Then I can recommend and help better. So if I do this a little every day, whole year. I bet I can make my own game 2022. Since I work, I only have a few hours each week to actually invest in this. But its fine, because Cyberpunk 2077 doesnt work on my old PC I am using, lol. I have no clue why I am still typing.. Have a better year 2021 guys! Thanks.
Iv been really caught on this topic. Ive been drawn towards the Unreal world for creating a game becuase part of my job is also creating Architectural Visuals and walk throughs. unreal really looks like it can deliver on this hyperrealistic output but my only real programming option is blueprints where as in UNITY I will be able to avail of C# a programming langued I am quite proficient in. Im starting to think i should just move forward with unreal use Blueprints and slowly learn c++ over the next few years.
Unreal is going to be adding a new scripting language called Unreal Verse in Unreal Engine 5 (confirmed by Sweeney himself in the last livestream of 2020). I'm not sure what it's going to offer that Blueprints and C++ don't, as there isn't much info on it other than what they showed in the livestream, but Epic has been talking for a few years now about an intermediary language to address the complaints about Blueprints and C++.
Hello, i would like to become an environment artist. Currently i am learning Unreal and i like it very much. When i look at freelance jobs, unity seems to have more jobs positions than unreal. My question is: Should i learn environment design on both engines or it will be much better if i just focus on Unreal?
I still remember the very first moment I installed and touched these two game engines, with very little knowledge on C# and C++. After a solid day on Unity: I know how to make a game from end to end. After a solid day on Unreal: One single editor palette gone drove me crazy.... I know millions of ppl are better than me but hey that's me...
Agreed, both engines currently have HUGE gaps that make it nearly impossible for an entry level user to get what he wants using either of them. Unity: - Can build a whole game level, import a 3D character, code his entire movement and interaction system and build the UI system in one day. Can basically do anything using C#, incredible customization capability. - Takes 3 weeks to figure out how to make the game look like it wasn't developed in 1995 using the MS-DOS version of the DOOM engine. Unreal: - Solid visuals out of the box, can import a level and make it look stunning and realistic in one day. - Takes 2 weeks to figure out how to import a character and make him walk forward when you press 'w'. - Takes another 2 months to 'compile shaders' if you accidentally change any default material in the scene. Neither is usable to build a full fledged game out of the box. I have gone back and forth between the two and gotten frustrated each time. An ideal engine would be something that will provide the realism of Unreal while giving the coding simplicity of Unity. Unfortunately Unity has no intention of fixing their shitty graphics, in fact they keep cutting graphics features like lens flares in new releases, while Unreal only advertises graphics and not ease of use, so doesn't look like that option will be available anytime soon.
Hi Brendan, on Unity's side I think you missed Ghost of a Tale, which is sometimes referred to as one of the most beautiful 3D games made with that engine. Then again, I may be biased... ;)
What game engine do you use and why did you decide on that over all the others?
I've been trying to publish a game with UE4 for about 1 year now (on and off). I get put off by the abundance of default assumptions the engine makes about your game (if it's not a standard shooter you gotta change about 90% of the default stuff the Gameplay Framework gives you). Also UE doesn't really help with its inheritance based infrastructure. I'd much rather work within an ECS context but you just run into a lot of non-clean glue between the legacy inheritance based systems inside UE and your custom components. It's just a mess. Also, iteration times are significantly slow. If you're working with C++ things get twice as slow (at least). You really have to have your math figured out if you don't want to waste time recompiling your code every 5-8 minutes. I haven't tried Unity yet but I'll be trying it out starting this month. I'm very excited about the apparent ease of driving procedural animations and the CineMachine. Wish me luck lol
@@novaria Good luck with Unity. I actually spent the last month building a camera behavior system the leverages cinemachine in an animation timeline. It’s very cool and can make working with cameras trivially easy.
@@BrendanDickinsonUnity Sounds cool! Will you put up a little demo video of it sometime? Thanks, just downloaded the engine again haha.
I've actually been talking it over with the team and I probably will post a feature highlight video sometime, just need to find time!
@@BrendanDickinsonUnity yehe, same old issue as always. I know it just too well. I'll share some short clips if I get something exciting working.
I personally develop AAA titles using Notepad and a bread board as my only tools. How are they related? Who knows. I just work at Ubisoft and my only purpose is to introduce bugs into games.
What are you on 😂 who thinks of this
Underrated lmfao
I'm pretty good at introducing bugs into games myself, are there any openings at Ubisoft?
@@Lord_Volkner There is no interview process for those with zero programming experience. If you're resume is blank, you're hired!
@@PinoyBoyist Well, darn. Looks like I'm over-qualified.
As a person who tinkered with C++ and C# who tried both engines I have to say Unreal was easier for me. The thing with the blueprint system is if you understand the basic game logic blueprints are a great help.
yes, I was trying to understand unity for pretty long, but then when I tried Unreal I instantly understood the engine.
Its probably true that even a 10 yr old could pull of an OK game with unreal.
Exact experience that I had. Blueprinting just clicked, and Unreal Engine is overall less stressful for me. But many people love Unity, and if you're able to get past the C# hurdle than I am sure it has its benefits also.
There are also visual scripting languages for Unity like BOLT or Playmaker. Bolt is like C# but without writing it and Playmaker is like an easy understandable tool. I work in C# but playmaker saves me sanity and time sometimes.
yeah blueprint good all and all but you cant build a solid foundation with blueprints (i can't at least) maybe i know c# a lot more but writing with c# a lot faster for me (not talking about code performance) i can build better foundations and better structure for my game with c# if i could write c++ better i would use unreal
It is typical 'programmer-circuited' brain's thinking.
The basis 'understanding basic game logic' already assumes certain kind of userbase and it is absolutely not pointing normal audiences.
You can confine targets to specific group, but it may lead you from your saying. (Re-Definition of EASYNESS if ooo, if ooo, if ooo...)
I knew so little about game engines and this video was a great starting point for me. Thanks a ton, man!! Super informative.
If I used unreal to make a project, I would pray I ended up paying the 5% lol.
I think this was literally one of the best videos breaking down pros and cons for someone who is literally starting today on his first unreal engine 5 use. Thanks man!
I appreciate your analysis of these two incredible engines. I use Unity, but am constantly curious and amazed by Unreal. Since I am still really at a beginner / intermediate phase in learning Game Dev, I am glad to be using Unity and C#. I have found c# much more readable code than scripts I have seen in C++, so that is something. Thanks for the updated discussion!
Wow. That was impressively put together. Well done man
Thanks, well explained, and solved many questions I had about starting up in this spectacular and difficult world. Cheers man
'ey man, I just found this video randomly while looking up differences between the engines. I don't even know what your channel is about but that intro had me subbing so fast! haha, right on!
Thank you very much for this informative video. We are currently planning a game project for university and we have do decide for an engine. Your video helped me to create a complete comparison sheet which I can discuss with the team.
Great video!
I am learnig Unity and making my first game, I thought about switching to Unreal, but it is very difficult.
Your video helped me a lot.
I will continue with Unity and improve my abilities there.
Thank you!
Honestly a clear and logical summary, highlighting what is important and unique in both. Thanks man, you can really help a brother in need.
Great, high quality analysis Brendan! Thanks a bunch for sharing :)
Just came across your channel watched this and and found it very informative clearly presented. new sub great job I'm just thinking of trying game development. And this helped loads going to take your advice and try both 30 days on each thankyou
Very nice explanation thankyou so much 🙏🏼🙏🏼🙏🏼
well organized video it was easy to grasp all the information
I appreciate it!
I'm a computer engineering student and planning to make my own game in the future, this is helpful for to know which is better. Thank you for giving the comparison with great explanation to clear out my confusion.
Great video! Learned a lot about both Unity and Unreal. Since both engines have their own pros and cons, I like how you ended the video saying it’s pretty much up to the individual and what’s best for them. The fact that both Unreal and Unity can publish Nintendo games was surprising.
Excellent and concise comparison of these two engines. Your content is great. Thank you for your hard work.
Great video! Good mix of visuals and opinions / talking.
Helpful and instructive. Thank you Brendan.
Great video, really clear and logical comparison of both engines. Thanks a lot.
This is a very helpful, and one of the few videos that doesn't spew silly things at you, just the facts, thank you.
I’ve worked in AAA studios as a game programmer since 2006 to now. And I agree with everything you said. Very informative. I currently use both for my personal projects for different purposes.
Lol I was born in 2006
@@sohailaali2081 so.... what's that information for?))
He is talking about how experienced he is
@@Andredy89 he's 16
@@sohailaali2081 unfortunate, the early 2000's were a great time
شكرا لك شرح ممتاز ومباشر و الاهم المقارنة صادقة دون تحيز Thank you for an excellent and direct explanation, and most importantly, the comparison is honest without bias
Awesome explanations ! Thank you so much !
man, you helped a lot, great video
what a great video. really fun to watch and easy to understand. its great. i cant quite state it enough.
Thanks for the informative post. I also hope that you find a few more FPS locked into your camera bodies :)
This was SUPER helpful. Thank you
9:20 - unlike others, my problem is not coding. My problem is the visual part of the development. I'm not creative enough and not good in visualizing, that's what's holding me back.
Um the opposite, i have problems with coding because i don’t actually take time to study, i love doing visual,UI, and modelling(blender)
@@elangel986 I think you have a clearer future in this field than me. Because in making games visualization and creativity is more important since there are ways now to develop a no code project in Unreal and even in Unity.
@@lowkeygaming4716 there are much more money in coding, so i dont agree... and creativity in programing is also very important!
You cant make a game without a coder, but you can make a game without skills in visual stuff. All of the one man gamemakers are coders. (coming from a "creative guy")
@@lowkeygaming4716 i wish i could say the same, i got no budget to hire someone and when i try to study programming my brain gives up,
For visual there are lots of assets for free to use, so it would be much easier for ya.. you can do it!!
Same here, coding is not even the problem but I cant model, design. I am good with making stories having ideas and coding everything but Ill end up having to use free models which doesnt fit my expectations.
*Great intro lol.* Love it! Keep at it.
Thanks. Very informative. Never thought I would see a day Unreal is cheaper for most than Unity. Also I was reading about Unreal 5's Nanite engine. As a former architect visualizer I used to produce just high poly for still and animated scenes. I just don't want to spend time, and that feature can be a game changer for that. I just want to get back to this sector as a hobby.
I have been using both and totally agree with you!
The amount of free tools, high quality materials and assets, professional level hair systems and all these things along with the engine itself made Unreal a no-brainer for me. Yes, its probably harder to learn, but once you have passed that first learning curve the features are too many to pass. Also, i wouldn't call it only a 3rd/1st person shooter engine. As long as it's not 2d games, Unreal can do it just as well.
It is harder because the skill cap on Unreal is higher. Working with Unity felt like you are being held back.
Do you think a card game would be working well in Unreal?
@@lych1669 i'm no expert but unless you need killer graphics why bother with unreal, unity is far easier and like the video said, a better sandbox
i've used unity for a long time and get frustrated that a lot of basic stuff isn't build in. i'm temped to try unreal since all the free tools sound much more polished that the hit and mis unity asset store stuff
@@TheSateef Thanks, but don't your two comments kinda contradict each other?
Awesome comparison! Thank you! Subscribed! 🙌
This is a really great video, I really learn so much things from this. But, you forgot to mention some topics like poly count, rendering techniques.
Great video and engine comparison!
Great video. Great information. Thank you.
Thanks, this was very helpful!
Thanks Brendan that was really good. I use Unreal but hear a lot about Unity so watched this to help compare the two. It has given me a lot of insight into Unity which I know next to nothing about. It has also helped me appreciate how much I have already learnt about Unreal and visual scripting. It was the Kite demo stuff I saw for Unreal that got me into it, the open world stuff I find fascinating.
Thanks for this, helped me alot!
Truly grateful with your content!!!
Most Excellent review! thanks
Very informative video with lots of easy-to-digest information, cheers for this. I've always been fascinated by game development but only dipped my toes into some RPG Maker things in the late 2000s/early 2010s, and more recently Frictional Games' in-house HPL engine. I just downloaded Unreal yesterday and have been tinkering around for a few hours. I think I'll try Unity at some point too as it may be more accessible for someone of my entry level. Both seem phenomenally powerful and capable. Thank you for going into as much detail as you did here, hope you're doing well.
Fantastic video, Brendan. I nearly agreed with you on every single point. I've been using Unity for several years, but I think I'll be making the switch to Unreal for a smaller project, but with a focus on graphical fidelity.
As much as I love Unity, the lighting system just isn't cutting it.
Both engines have their pros and cons and I can't say it's a wise decision to be 100% loyal to either one of them 100% of the time. Different use cases for different engines. Thanks for taking the time to make this, it's well thought out and you have some great insight.
Brendan, great video thanks for replying to the comments below and sharing your expertise as such. Very valuable. Do you have any thoughts on Maya, Blender, 3Ds Max? Pros and cons?
Blender: free and open source.
the other programs: very expensive and closed source.
You decide
Good video. If you're going to make shooters Unreal will definitely give you wind in your sails. I started with Unity about 3 years ago but I mostly make FPS games in Unreal these days and it's just brilliant.
That explained a lot, ty
Awesome infos thanks👍👍👍👍
This is probably the best Unity vs Unreal video I have seen!
One my biggest gripe massive amount of preview packages (and they sit in preview for years, although it is kind of changing now) and with Unity is having to rely on 3rd party plugins or you have to create things on your own. Just to be clear I am not talking about things you can/should make yourself. I am talking about things that engine should natively provide.
What does the engine not natively provide?
Great tutorial, so when you've created your game and compiled it, Is it instantly available on the game store for others to play?
thank you for this video! Going to go with Unreal engine the work that you put into it looks worth it but thats my opinion we will see if I feel the same after a few months of working with it lol
One little thing not mentioned in the video is the fact that some of the mentioned games like Inside were made with access to unity engines source code, so they had total rewrites of parts of the graphics engine. Which means you are limited with the normal unity version (source code access costs a LOT of money with unity)
Unreal's compile times are usually long if you use the old methods of including engine.h. The newer coding paradigm is to include all needed headers on a per object / component basis, that speeds up the compile time with less overhead.
Unity now has a scriptable render pipeline so you could actually write your own renderer or modify the built in one I believe.
most of the time you don't need to rewrite source code but if you need to rewrite source code you can make your own system also rewriting unreal source code is almost impossible did you ever tried to rewrite unreal engine source code its so hard
Awesome video, thanks
Props man! Some serious quality in this video. Have you released games through both of these engines? Or has most of your development time gone towards non-game applications? I would be interested in hearing more about these non-game applications either way.
Thanks, Jared! While I've made games in both engines and exhibited them at expos I don't think I have any of my Unreal games available to the public. Most of my development has definitely been with non-game applications. These apps are all over the spectrum, but most have to do with 3D simulation and data representation, I do plan to do a video specifically about this topic sometime in the future I'm just not sure when. If you'd like to know more details feel free to DM me on Twitter @BrendanDickins
@@BrendanDickinsonUnity This is really interesting thing, will wait for it :D
Excellent presentation, thanks!!
I'm considering both for Architectural presentation which I assume knocks out 80% of the difficulty and learning curve, tools and functionality as a game must be much harder with interactive requirements.
AND trying to use my DWG files from Autocad Architecture.
Datasmith brought them straight into Unreal and I was doing a walkthru within hours and a couple of days have a basic walkthru I could show a client. Not flash but an excellent tool.
That Unreal's graphics, lighting and realism is higher does pull me that way.
With programming, I suspect I won't really need it so whilst C# sounds way better to a non-programmer (and old bloke) it is probably not necessary.
Now Lumion created an add-on to Autocad to export to .dae and it creates a model I can bring straight into Unity and selection is grouped to materials set in Autocad Arch which seems to be ideal.
It also has a LiveLink to Lumion which looks brilliant.
Ah, a world of great choices!! Where to spend my time, which to learn.
Very awesome to hear this being used in an Architecture sense, back when I worked for a consultancy we looked at Architecture as a potential vertical to market to but never ended up going anywhere with it. Lots of my work has been in the medical, automotive, and consumer products space with room planning and laying out warehouses or buildings so very close to Architecture.
@@BrendanDickinsonUnity The trick for me, in the lower end of the market is not redoing stuff and I've rendered in Autocad Architecture (save any round tripping) for years but they keep changing but not really improving the interface and it's SO SLOW. So finally, I am pushed kicking and screaming to use a 2nd tool.
This current project - the client has now made big design changes so the Unreal file is scrapped and I will need to reimport a new model. Not how I wanted to work but if the outcomes are much better.... I am hoping I can set up a template file to import into, ready to do my bidding quick and clean.
Thanks for your contribution to a 'prospective's' perspective on where to go.
thank you for clarifying.
Having used both engines, both as a teacher and as a developer, I feel this was very biased towards Unity.
Now, don't get me wrong. Unity is just fine if you want to make whatever. It shines in 2D games, it can pull off nice 3D games too if you know what you're doing, and you can build apps on it. But the main issue, which was pointed out in the video but not made as big a deal as it is in reality, is that everything in Unity is half-assed, like the devs start to add support to something then just stop midway through. I remember working with AR was a pain in the ass because we had to use one specific version where everything we needed kinda worked as expected. One version later it was all broken and still is to this day. Fiddle with the engine long enough and you'll find ceilings like this on almost everything. VR also had issues in certain versions. Arduino support was only good in a few others too. When I was a teacher, we had like five versions of Unity always installed so we could hop back and forth through them as needed. This restricts what you can do as a developer, because if you want to make a mobile game that uses two of these features and they are spread apart on different engine versions, there's nothing you can do.
I also felt a lack of research on what Unreal can do. Yes, you can do non-games in Unreal. You can do these in any engine; I've done it even in Game Maker a couple years ago. It's being used extensively in the movies industry, but also in other stuff, from simulations to car HUDs. You can also very easily compile HTML5 games with it, and it isn't as bloated as people expect. Android games are also very viable, as well as 2D games. The thing with 2D games is that most of the 3D resources aren't available in 2D; like animation notifications, which are extensively used in 3D, as well as certain AI features like EQS (which wouldn't make sense in 2D anyway), but you can do good stuff. There are lots of 2D Unreal games out there, and if you're willing to spend on plugins, there's amazing stuff like Pixel 2D, which brings the 3D work pipeline back into Paper2D.
Blueprint was also very underrated in this video. It's an awesome tool to teach the developer how the engine works under the hood, as when/if the user decides to move on to C++, they'll be already familiarized with how Unreal structures everything, making the transition to C++ very smooth, and it's also a very good way to hit the ground running in C++. Unity is very accessible when you want to do basic stuff, but when it gets advanced, it really steeps up in the learning curve in C#, and Bolt isn't very comparable to the Blueprint Editor, since you have to fiddle around in the engine to even get it working, whereas in Unreal you just right-click anywhere to create a BP and start coding.
There are other things too that went missing, like each engines philosofies and basic QoL stuff that's available in Unreal but missing in Unity. Overall I felt like you didn't know enough of Unreal to give an opinion on it.
i feel you need to do a blog post on your experience and drop us a link. A lot of us newbies would like to learn from your experience with both engines
tldr; anyways unreal best:)
In my opinion to find what's best for you is test drive them create a smallish prototype keep it the same in both engines and then you will be able to sum up what works for you don't listen to others it has to be you who make the decision but i do agree with the face C# is defiantly easier to get your head around .
I do have to say there a few points that has been missed here on the unreal front such as the learning tools that unreal offers developers with some very interesting and informative content, i always find it very strange that a lot of guys that don't work with unreal make the point that to them the ui is hard to understand at the start but when you break them both down they are very similar.
Remember guys and girls whoever you listen to on this topic there is always a bias opinion on engines not that they mean to it's just how it is, your the only one that can decide what's right for you.
Good job on the breakdown Brendan
Lol one thing I am definitely getting from this video is you love C#
You’re not wrong lol
Great vid btw, I think the pros & cons of each you gave are quite accurate.
From what I know in a nutshell Unity's problem is *severe* lack of reliable features, direction & stability and Unreal's issue is a lack of freely available knowledge pool both in the context of anything beyond surface level complexity.
Also most ppl agree that working with C# is a much better experience.
I'm working on a AA 3D ARPG on Unity and quite frankly Unity feels like a mere 3D rendering engine with some bare minimum game dev tools hacked onto it. I had to write up pretty much everything by myself and fill in several blanks with 3rd party systems.
It's sad that when you get so far you realize late that you kinda have been lured by appetizing tutorials with deceiving simplicity.
I've been wanting to transition to UE for quite some time cuz Unity nowadays doesn't seem interested in saving what looks like a sinking ship despite the myriad complaints they get on a daily basis on their forums though porting entire big projects is just too painful an experience to repeat and there's no denying the overwhelming popularity of Unity being a significant advantage that can to some degree offset the many, *many* cons through the sheer amount & quality of external resources if you're a solo dev or small team with limited budget/resources.
For every good thing in Unity I can name 3 more bad ones and I've noticed that despite when even actively looking for what possible cons UE has cuz it looks too good to be true and you'd generally hear ppl having a good experience with it while on the Unity camp you'll read hundreds of walls of texts of complaints & rants.
So basically the main reasons I'm still using it are: C#, community resources & docs and the fact I went too deep into development to consider porting now unless maybe the process isn't too painful and if Epic find interest in my project someday to consider helping for the port. Then again the knowledge & skills I learned and resources I acquired are too valuable to throw away now.. An engine + a language's frameworks are quite big and require a lot of time and patience.
That or hopefully Unity comes to its senses and start making the engine more stable, with faster iteration times (read assembly reload..) with reliable *native* features instead of dumping all the responsibility on 3rd party to make a quick buck.
I don't think UE is perfect either tho cuz the main complaint I hear from ppl using it is a very significant lack of information so what good is having a huge box of tools if you can't have an extensive enough manual to use them to make something complex so the main worry in using it is getting stuck in some obscure parts of the engine and not finding answers or workarounds cuz you have to realize that the majority of online users are just hobbyists in the end.
I'm open for feedback on this though cuz my knowledge of UE is limited since I haven't used it.
I am doing a lot of procedural world generation. I did it with Unity and Unreal and atm I honestly think, if you want to implement a lot of procedural content, Unity will work better. There are already very good third-party plug-ins and way more documentation/tutorials.
I tinkered alot with Rust lang, GO, and even C++ SFML. And eventually settled down with Unity C#. C sharp is a great language.
I like Unity because it suits my specific project well and does what I need it to.
Unreal looks AMAZING but I am too lazy to learn C++ AND a new engine. Maybe one day.
@asiri maduranga I do some solo game development on the side as "Light Pyro Media"" but I haven't released anything yet.
I mainly do contract concept art for other groups.
It feels like Brendan scaled me down 100x and won't let me leave until I hear what he has to say about game engines 3:29
Thank you, great video. I been with Unity3D for, hmmmm 8 years I think, a long time. I going to learn UE for 2022 and build a game with it. The move from C# to C++ I hope is not a long path. As you said, give it 30 days. I will and see if I make the switch. The only sad part was the drop of support on 2D for UE. Maybe UE see Unity is wha ahead of the game and they only want to focus on 3D only. The 2.5D in UE may work just as well. The test will be on a phone.
It's honestly a luxury problem as you have so many good options 😖
Then the problem is choice.
It is..... inevitable
“I’m going to enjoy watching you die Mr. Anderson”
Hi, Brendan. Thank You for this amazing video. Right now i am on my way of choice between this two engines. My task is to make a simple application disassembles some technical devices. For example, press a part of device and it shows how it is works and what other parts it is made of. According your opinion what of this two engines is best for that? Materials and 3d models i make in other program. Have some experience in coding. Thank you in advance .
Hi Maxim, sorry it's taken me so long to respond. For a more simple application that seems more business oriented I would definitely use Unity. The fact that Unity doesn't constrain as much will help you out.
@@BrendanDickinsonUnity thx a lot good man!!! Unity is great.
Hi Brendan and thank you for this great insightful video on which engine is better, even though in the end it seems to come down to personal preference. Anyway hopefully you can take the time to answer my question as this is already a year old video. I'm completely new to game design, and just want to give it a go and see where this adventure ends.
Now for coding, I've seen that C++, even though it's more difficult than C#, the following description can be found on it:
"Developers tend to choose C++ when it comes to the speed of applications. It's a more powerful language to run video games and operating systems, while C# is a beginner-friendly language and it's better for creating Windows software and web development, usually backend."
Wouldn't that make C++ the better choice despite that it's more difficult to learn? Probably also depends on the type of game I'd like to build. I'm thinking along the lines of Dragon Age, with the realtime-with-pause mechanic, where I can opt to command characters to perform multiple tasks, before unpausing the game and seeing the characters do exactly that.
Graphics at first, when learning aren't a big deal, but I'm under the impression that, when Unreal Engine 5 is released in full effect, it's probably the best there is on the market and with regards to delivering an as polished as possible game, it's probably wiser to go for learning Unreal Engine 4, which will make for an easier switch to UE5, than Unity, unless Unity will drop an engine update soon which rivals the photorealistic options of UE5.
I'm tempted to consider Unreal Engine over Unity, but perhaps my arguments make no sense.
No problem Omkara, I think you're honestly worrying too much about the capabilities of the engine and the type of coding language you'll be using. For your purposes I would say that neither of these matter in any way except if there's something you can't do in one engine that you need. I would say given your description of the type of game you're trying to make, you could do that with either engine. You aren't going to be held back by anything other than your preferences and learning speed. So what I would recommend is the same as in the video, give each engine a try since they are both free and give them a couple weeks each, maybe a month. Then you should know which one you're more comfortable with, and I would move forward with that.
On the topic of graphics, are you doing a hyper-realistic game? There aren't many games that are at that level of fidelity and the ones that are, are more showcases or experiences than a game, or made by large studios with dozens if not hundreds of people working on the same game and millions in the budget. There are very few solo developers that end up going that route, also many of the best games out there are not hyperrealistic, dragon age graphics are very possible in either of these engines.
As for coding, this is really preference unless you are pushing the limits of a pc. C++ is more powerful and can be faster since it's a lower level language than C#, however nowadays most optimization doesn't actually come from that kind of coding, you can still manage memory and most other things using C#, and the things that actually need to be optimized are models and textures, especially when running high end graphics, not code. Of course there will be people on both sides that say one language is better than the other for this or that, but if you actually learn how to code, it's not that difficult to switch over to other languages. For example I know C#, C++, Python, Java, and JavaScript to name a few. The hardest thing to learn is how to code in the first place, all the foundational stuff stays the same and can be applied to each language. Another thing to keep in mind is that you'll need to learn the API's for each engine, which means not only learning C# or C++, but how they work within Unity or Unreal, this is where I think you should focus while beginning.
Hopefully that helps you with some of your questions. Personally I would try to create one mechanic or interaction that you would like in your game, in each engine. By that point you'll probably understand which one you want to go with, really there is no wrong answer for your particular case.
Great advice. 10/10
great info but i wish you had talked about VR support
Thanks for the help
Great information, going to give Unity a try
thank u bro!!! But can u pliss make some programing-coding tutorials?? plisss i will aprisheit that an again thank uu
The video is very informative. Thanks for sharing your experience, Brendan!
I’ve just moved from Unity to Unreal 5 and MY GOD. Unreal is.... well, UNREAL the power behind the engine is breath taking. I’ve always found that you can have good post processing with unity but it takes so much hassle and time, Unreal is just beautiful to look at straight out of the box. I recommend unreal any day of the week
no, you are breath taking!
I just wish I could use c# out of the box
Me fearing of the simulation theory right and with an unplug will destroy us forever: Nah! I’m with unity.
After 5 years of dev of my project, I've decided to rewrite it in UE 5; Unity 2021 w DX 12, DXR, HDRP is abysmal in performance, Nanite and lumen gets me 12x fps in the same scenes (and look waaaay better).
@@LoudFiat I've just started with unity, idk why I'm watching this video, I was looking for "terrain ideas" because I'm getting fed up with it, every time I make a terrain it looks like a trash, nvm, how is UE after 6 days of your comment?
Is all the stuff said in the pricing section of the video still accurate one year later
A few things that were wrong. Most importantly, with Forest, you seem to have confused high-resolution textures from an asset pack with "good graphics." Forest is a go-to example of a default Unity project with no unique art direction or style.
The engines are not free in a similar way under a certain income. UE4 is completely free to the point of source access, profiling tools etc. whilst Unity even if you don't make x amount they've now paywalled a collection of useful features that most serious devs would need when working on a full game.
Unreal is NOT a good or even ok option for mobile dev just because you've seen Infinity running on mobile. A game created by a dedicated team from the engine creators. Unity is a much better option for mobile, not even close due to all the lacking features and difficulties with building a mobile game with unreal.
Hopefully, it's obvious that I'm not fanboying either side as the two main things that were wrong were pro the other engine. Just annoying to see another, "use whichever" VS video when there are some clear and easy selling points for both when you've actually had some experience using both for a long enough period of time rather than just doing a days research to release a video.
And more of a preference thing but you only looked at the coding languages based on what you like to use, which also makes it clear you've used Unity for a long time. But C++ is the better language, more flexible, full control over memory and it's more performant. If you're serious about developing, the learning curve is pretty irrelevant as after the tiniest percent of the overall time you'll be developing through your life, you'd have become proficient at either.
First off I want to say this is all great stuff, and I appreciate the comment. I have to be honest in that I don't know how the guys at Endnight decided to handle all the assets in The Forest, what I do know is that the team that built it has a background in film visual effects, having worked on films such as The Amazing Spider-Man 2 and Tron: Legacy. They were able to bring this knowledge to Unity to create a visually impressive game (and one that happens to be #7 on steams top sellers at the moment). It's probably an unpopular opinion but I don't personally believe anything is wrong with buying high-quality asset packs to use in your game, especially if that's a skill set that you're lacking.
I did mention that UE4 gives you source access which is very nice for experienced developers. Unity also gives you access to the entire feature set of the engine in the free version; there is nothing paywalled within the software, although this wasn't always the case. The only exception here is the customizable splash screen, online services like usage analytics (not the profiler, which is available for free) and cloud builds, which you can find replacements for.
I do agree that if someone wants to make a mobile game it's going to be easier to use Unity, I should have made this more explicit in my video.
As for the coding language, this really is a matter of opinion. I know a lot of people who prefer to work in C++ and I know people that refuse to use Unreal for the sheer fact there is no easy support for C#. Which language is technically better is irrelevant, and I think up for discussion, as they are both fine languages for making games through these engines. This is a big thing that drives people's decisions on which engine to use, and if you have knowledge of programming I'm sure you already lean one way or another. If you don't have experience programming, it is my opinion that you should start by learning something like C# or Java and therefore Unity is going to be a more natural fit, but it's just that, an opinion.
Also, I'm assuming most people who are searching and watching this video are people who are just starting out and want some guidance. Because of that learning curve is something that I have to cover. I've seen several beginners open up Unreal only to spend weeks banging their heads against a desk not able to get the results they wanted, and in turn, this caused them to drop it and move to Unity. I'm not trying to say that this will factor in later on, but it could help prepare people when they otherwise might not know what they are jumping into.
Again thank you for the comment, it made me really think about some of the points I made and why I discussed the things I did!
There is no better language. It's fair to say c++ is more powerful as it gives you more control over low-level stuff. But more power and control can be both a good and a bad thing depending on circumstances and needs - in many cases simplicity and fast iteration times are better. Also keep in mind this video is mostly for beginners. Custom memory management and data alignment is cool to have but i'm sure it's something most hobby or even indie game developers won't ever want to or need to worry about - also with DOTS/ECS you can have performance mostly comparable with c++ in c#. Sure it's only in preview at the moment but i'm more than sure it will be production ready long before any beginner will learn c++ to the point where he'll be able to implement anything more performant in c++.
TL;DR; if you're just starting to learn go with c#. You can always learn c++ later.
THIS^ There is such a cult-like following for unity this is constantly overlooked!
In the end C++ and C# are all compiled and it’s more about the coder’s abilities to optimize.
@@plunntic I learned Unity a little bit, made a jam game, lost my motivation and am now starting to learn unreal
It is good for Unreal to compete with Unity
They will continue to improve and will not easily increase prices :)
I think this is something often overlooked. The competition between them has been absolutely amazing for developers and the community in general.
Wait.. Is unreal competing with unity? According to me unity has only got 2-3 world known famous games.. and unreal easy to mention 100+? guess I have to go do more research. Thanks for the heads up. I thought unreal was the leader in the industry.
I personally just started to use unreal engine, and I'm using blueprints but plan to switch to C++ soon since I spend a whole week learning the language. tbh, i don't think the unreal engine interface is that complicated. it took me 20 mins of tutorials and after that it was all really easy. But I have to admit, trying to fix bugs is pretty hard and there aren't many results when you try to search up how to fix a bug. But I'm planning to stick with unreal because of all its tools and also all the amazing assets in the marketplace.
when you create your game with your own codebase is a lot easier to debug thats why i don't like blueprints if you know what your doing while code c++ you will be fine
Thank you so much
This is just great as has reafirmed my decision to start by giving unity a chance and checking later on unreal. Thank you!
What's your reasoning I'm having a hard time choosing one to build on.
@@TheRealKingSolomon unity seems to be easier to use and my first project is an interactive movie, but Unreal seems terrific for photorealistic imagery and 3D games, so that will be for another project. I’m also wanting to do a scroller and some RPGs and just found there are other engines for that! I think my criteria will have to be open source to begin with as long as possible, but unity and unreal make it easy for you to start for free. I’m gonna take basic lessons of both of them and see which makes me feel more comfortable.
Thank you I was looking for some insight on making a game. So it's one of the two engines.
I believe I will go with unreal engine. I am new to this, so forgive me if I butcher this. But I want to build a game on unreal engine running vulkan API over DX12
Hello, can you design a game with a big size like resident evil in Unity I moved a bunch of models to Unity and when it got to 8 GB Unity started crashing and not working please help
How about networking (online, netcode), how hard to hack/cheat in those engines, is there one which is better for networking than the other ? also is there one engine that is harder for people to cheat, make hacks and exploits? or are those too broad to be able to pick one engine which would do better?
Great video by the way! :)
Best Video of the year
He: Graphic is the main part of any game
Google Play trends: Ohh , really . O didnt know
Using Unreal. Day 4. 2D pixel game. Making a platformer, demo. Not sure what to do but taking notes as I go. Reason for unreal engine for me is that I will help my friend with the game music and graphics. Since he is using Unreal, I thought, "why not learn a little", just to understand what it can and cannot do. Then I can recommend and help better. So if I do this a little every day, whole year. I bet I can make my own game 2022. Since I work, I only have a few hours each week to actually invest in this. But its fine, because Cyberpunk 2077 doesnt work on my old PC I am using, lol. I have no clue why I am still typing.. Have a better year 2021 guys! Thanks.
Don't do 2D with unreal... 3D unreal 2D unity
@@youtubedeletedmyaccountlma2263 true. Too much clutter for a 2d game
Iv been really caught on this topic. Ive been drawn towards the Unreal world for creating a game becuase part of my job is also creating Architectural Visuals and walk throughs.
unreal really looks like it can deliver on this hyperrealistic output but my only real programming option is blueprints where as in UNITY I will be able to avail of C# a programming langued I am quite proficient in. Im starting to think i should just move forward with unreal use Blueprints and slowly learn c++ over the next few years.
Unreal is going to be adding a new scripting language called Unreal Verse in Unreal Engine 5 (confirmed by Sweeney himself in the last livestream of 2020). I'm not sure what it's going to offer that Blueprints and C++ don't, as there isn't much info on it other than what they showed in the livestream, but Epic has been talking for a few years now about an intermediary language to address the complaints about Blueprints and C++.
@@sigrid714 thanks for that i will focus on unreal and hopefully this new feature comes in soon
Bro, Can we use both game engines to make our games?
Hello, i would like to become an environment artist. Currently i am learning Unreal and i like it very much. When i look at freelance jobs, unity seems to have more jobs positions than unreal. My question is: Should i learn environment design on both engines or it will be much better if i just focus on Unreal?
So this video was posted on my birthday and also I have that sweater lol
Thanks Mrbeast for the great tut
Really good review man. Personally I like Unity better, but I'm just comfortable there.
I still remember the very first moment I installed and touched these two game engines, with very little knowledge on C# and C++.
After a solid day on Unity: I know how to make a game from end to end.
After a solid day on Unreal: One single editor palette gone drove me crazy....
I know millions of ppl are better than me but hey that's me...
Agreed, both engines currently have HUGE gaps that make it nearly impossible for an entry level user to get what he wants using either of them.
Unity:
- Can build a whole game level, import a 3D character, code his entire movement and interaction system and build the UI system in one day. Can basically do anything using C#, incredible customization capability.
- Takes 3 weeks to figure out how to make the game look like it wasn't developed in 1995 using the MS-DOS version of the DOOM engine.
Unreal:
- Solid visuals out of the box, can import a level and make it look stunning and realistic in one day.
- Takes 2 weeks to figure out how to import a character and make him walk forward when you press 'w'.
- Takes another 2 months to 'compile shaders' if you accidentally change any default material in the scene.
Neither is usable to build a full fledged game out of the box. I have gone back and forth between the two and gotten frustrated each time. An ideal engine would be something that will provide the realism of Unreal while giving the coding simplicity of Unity. Unfortunately Unity has no intention of fixing their shitty graphics, in fact they keep cutting graphics features like lens flares in new releases, while Unreal only advertises graphics and not ease of use, so doesn't look like that option will be available anytime soon.
@@malliyana201 as a result, what is your choice?
@@malliyana201 There are tons of games with stunning graphics made in unity though
@@pollomagico271 True
Hi Brendan, on Unity's side I think you missed Ghost of a Tale, which is sometimes referred to as one of the most beautiful 3D games made with that engine. Then again, I may be biased... ;)
For sure! I actually didn't learn about Ghost of a Tale until about a week after I made this video, otherwise I definitely would have included it.
noob question here!
If i’m a Mac user (M1 chip) is Unreal a viable option for me? or should I stick learning unity? 🙁
Good video bro
Do you have an online tutorial where I can learn gaming